First I want to thank SG and nickphx for helping me a lot solve my tunneling problem. Right now I can set up GRE tunneling between my master and slave servers and route IPs of slave servers. But I found an interesting phenomenon. At the master server, I use the following commands to test if tunneling is successful: Code: nc -s "slave IP" mta7.am0.yahoodns.net 25 I tested it every 10 minutes. Initially i can get yahoo's response, some time later it became no response, then again some time later, it responded again. I googled a lot and still not sure what the reason is. I leased this slave server from one budget ISP and is it possible that it's because of slave server's bad hardware/network? thanks in advance
problem solved..it's ISP's problem. you'd better find a good ISP that doesn't restrict traffic forwarding
There are innumerable ways in which ISPs can fuck with your traffic. Basically any rule you could imagine could be enabled on any upstream router. Always test, document, confront them with findings and go elsewhere if that does not help. Many ISPs will BS you about their policies especially QoS and throttling...
yeah, good experience. I know some guys who do GRE always co-lo their own boxes at local data centers. that's also my next step. Luckily there're some world class dc around me:flowers:
When I got started many years ago, I leased a few decent boxes that I would use to connect the tunnels to and mail from. After building up a good revenue stream I decided to buy hardware and colo locally. It was more work initially but now I have a nice stable "center of operations" to launch my massive assaults against recipients.
