If you are brand new, you should go to someplace like Burst, FDC, Joe's... where you can get cheap servers, and they do not ask a lot of questions in regards to IP space. The bad news is that most of the IP space will be beaten up. The good news is, it's cheap and you can learn the hard way without a lot of expense. Once you get better at mailing, you would then seek out providers with better quality IP space in general, or TLD specific depending on your data. You are going to pay a lot more for your servers to get that. But if you know what you are doing, and have your data segmented accordingly, it is much more profitable. You simply can do more with less. Good luck.
Here is a link to get a dedi for 1 month for just a buck. Should be prefect to cut your teeth on. http://www.burst.net/spc1.shtml
Thanks dude but Google has been my enemy on this. This site was the closest I could find but it appears to require router access. http://lartc.org/howto/lartc.tunnel.gre.html I'll keep searching.
If you are looking for help with tunneling PM me and I might be able to assist. As mentioned in this thread this subject is not appropriate for a public forum discussion. No fishing expeditions please, only contact me with your actual use case.
Alright, sorry about bringing that up. Its understandable certain topics don't want to be talked about. It makes it more difficult for a newbie to figure everything out.
tunneling is some secret? lol. wow simple howto: you need to know the following information: 2 servers. linux. ip address of server you will be tunneling ips from. ip address of server you will be tunneling ips to. ips you will be tunneling. on source server as root obviously.. iptables is lame and smells bad. chkconfig iptables off service iptables stop modprobe ip_gre ip tun add mode gre mytunnelname remote IP.OF.TARGET local IP.OF.SOURCE ttl 255 ip add add 10.0.0.1/30 dev mytunnelname ip link set mytunnelname up this tells linux to be nice and forward packets and proxy arp requests.. rp_filter is bad so we disable it. sysctl -w net.ipv4.conf.ip_forward=1 sysctl -w net.ipv4.conf.proxy_arp=1 sysctl -w net.ipv4.conf.default.rp_filter=0 do this for each ip you want to tunnel: route add IP.TO.TUNNEL gw 10.0.0.1 if you have a decent allocation and want to do it by cidr: route add IP/CIDR gw 10.0.0.1 On the server that will receive and (ab)use the ips: modprobe ip_gre ip tun add mode gre tunnelname remote IP.OF.SOURCE local IP.OF.TARGET ttl 255 ip add add 10.0.0.2/30 dev tunnelname ip link set tunnelname up sysctl -w net.ipv4.conf.default.rp_filter=0 for each ip you want to use now: ip add add IP.TUNNELED/cidr dev eth0 et voila. As long as your provider you're tunneling the IPs to doesn't have egress filtering or block source routing at their border you will be in business. Secret info.. jesus man, you guys make me laugh.
Fact of the matter, an average non-technical mailer is going to have trouble implementing and customizing your scripts, stress-testing their security and ensuring uptime. But as soon as you get into the territory of openly promoting "tunneling services for mailers" you immediately attract the attention of the well-known international gang of email haters that likes to blackmail US companies from the impunity and protection of their shady offshore heavens. You should be well aware that they do not recognize any email tunneling as a legitimate practice and have relentlessly attacked a few players in this space.
Theres no need for a noob to go right into tunneling. That's a road you shouldnt even be thinking of. What's the problem with buying a dedicated server, getting some IPs, and mailing your optin data the old fashioned way, keeping your domain in place and striving for reputation through warmups, etc over a normal 30 day period? Have you tried this simple approach yet?
