Date: Fri, 20 Apr 2007 14:49:07 +0300 From: Alexander Motin <mav@mavhome.dp.ua> To: Nikos Vassiliadis <nvass@teledomenet.gr> Cc: freebsd-net@freebsd.org, Tom McLaughlin <tmclaugh@sdf.lonestar.org> Subject: Re: net/mpd4: Unable to pass pass traffic as pptp client Message-ID: <4628A8B3.2090900@mavhome.dp.ua> In-Reply-To: <1176816181.00725799.1176802803@10.7.7.3> References: <1176776612.00725618.1176764402@10.7.7.3> <1176816181.00725799.1176802803@10.7.7.3>
next in thread | previous in thread | raw e-mail | index | archive | help
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@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4628A8B3.2090900>