net/mpd4: Unable to pass pass traffic as pptp client

Alexander Motin mav at mavhome.dp.ua
Fri Apr 20 12:49:11 UTC 2007


232487741
Nikos Vassiliadis wrote:
>>pptp0: connecting to 208.206.3.5 1723
>>[vpn] IPCP: LayerUp
>>  172.30.29.9 -> 208.206.3.5
>
>>ifconfig
>>[root at bofh tom]# ifconfig ng0
>>ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1396
>>        inet 172.30.29.9 --> 208.206.3.5 netmask 0xffffffff 
> 
> It seems that your external peer address is the same with the internal
> peer address. You connect to pptp-server-ip through your linksys and
> then say that pptp-server-ip is reachable through the tunnel. So it
> routes everything destined for pptp-server-ip  through the tunnel. I
> think that such configuration is valid for other operating systems.
> I don't know if you can work-around the problem on your own, maybe
> you have to contact the VPN concentrator's admin. Perhaps you can
> modify the routing table (the external peer address should be reachable
> as it was, though linksys) and invent some peer address using
> "ifconfig ng0 your_address 10.0.0.1 netmask 0xffffffff".
> But it's not nice...
> 
> Can you convice the concentrator's administrator to use another
> address for his internal side?

It would be a better way. But if it is not possible you could use 'ipfw 
fwd' rule to forward all PPTP's GRE and controling TCP packets via 
physical interface instead of tunnel.

-- 
Alexander Motin


More information about the freebsd-net mailing list