106 reputation
2
bio website
location
age
visits member for 4 years, 5 months
seen Apr 12 '11 at 13:37

Aug
27
awarded  Popular Question
Apr
11
asked Map eSata interface directly to NFS share
Apr
2
comment routing specific IP to ppp0 tunnel
Some other facts: I can ping 68.68.36.250 (this makes sense as its the IP of ppp0, but just stating). I can't ping 172.16.20.1 (this to me doesn't make sense as I have 172.16.20.1 in the route table, and whilst it's the server address of the ppp server I'd figure it should be reachable for the tunnel to really be a tunnel....)
Apr
2
comment routing specific IP to ppp0 tunnel
Switched server, same results. HOWEVER, new discovery:: Initializing the tunnel with "pppd call strongvpn debug dump nodetach", then opening a new terminal and doing pinging/tracing on the 208.85.40.20 shows nothing being sent by pppd... I'd assume the daemon should be throwing out some sort of garble.
Apr
2
comment routing specific IP to ppp0 tunnel
Eddy, thanks for the help to this point! tcpdump -n ip host 208.85.40.20 -i eth0 captures ping request/replys before touching the route table. Then after doing "route add 208.85.40.20 dev ppp0" and running tcpdump again with "tcpdump -n ip host 208.85.40.20 -i ppp0" it captures ping requests, but no reply back. I've tried this with iptables flush, firewall stopped, your rules, etc. All the same result. I assume if tcpdump shows it leaving the interface it is successfully passing the firewall? Maybe this is a ppp server issue, but its from strongvpn which is reputable.
Apr
1
comment routing specific IP to ppp0 tunnel
What you did yields what I had in my route table to begin with. traceroute'ing 208.85.40.20 afterwards does not return anything. =\
Apr
1
awarded  Student
Apr
1
asked routing specific IP to ppp0 tunnel