Hi Jan,
I would use tcpdump and traceroute to aid in debugging. nmap might also
be useful.
I also forget exactly what to do here, so if someone else knows please
help out.
If i recall correctly, there is a way you can direct traffic to your vpn
using SNAT.
so like if iptables -t nat -A POSTROUTING -d vpn_endpoint -J SNAT
--to-source local_vpn_endpoint
I think thats correct. The idea here is to have only traffic to the vpn
use the vpn, no? Trafic would leave
your vpn endpoint, reach the other side. The other side would reply
back to your SNAT -to-source which
would get routed to your pc.
I know this works with the *swan implementations, so using some sort of
NAT may help.
I would use those tools to debug, but there are probably some others
that would help as well.
Have you ever tried OpenVPN? It have used it in an office situation
before, and people appreciated it.
Please correct me if I am wrong. Hope this helps.
Mike
Jan Klod wrote:
Still asking questions. I tried to follow probably the most simple case
presented here:
http://pptpclient.sourceforge.net/routing.phtml#all-to-tunnel
but result is no access to internet at all. How can I debug these things and
find out what is going on? Now it is like in the dark...
Is it considerable to be a proof, that pptp VPN tunnel is working, if I can
ping -i ppp0 <remote VPN address>?
Looking for solutions,
Jan
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
