Date: Thu, 17 Apr 2003 12:27:08 -0600 From: Brett Glass <brett@lariat.org> To: Sten Daniel Sørsdal <sten.daniel.sorsdal@wan.no>, <freebsd-net@freebsd.org> Subject: RE: Userland PPP/PPTP tunneling problem Message-ID: <4.3.2.7.2.20030417122205.02aed700@localhost> In-Reply-To: <0AF1BBDF1218F14E9B4CCE414744E70F07DE91@exchange.wanglobal. net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:18 PM 4/17/2003, Sten Daniel Sørsdal wrote: >This is a known issue with the Microsoft PPTP client. It adds the natural >netmask and not the specified one. I don't understand. Why is /24 more "natural" than /16? >In case of 192.168.x.x/16 that is a >255.255.255.0 netmask and with for example 80.80.80.0/24 is 80.0.0.0/8. Even more confusion. How does it come up with that? >The only known workarounds AFAIK are requiring the client to default route >Through the tunnel Which causes slowdowns and a huge extra drain on the office's Internet feed >- or - setup a (persistent?) route on the windows box. I suppose we could try a script. >Say if client gets 192.168.1.2 when client connects, you need to manually >Enter: route -p add 192.168.0.0 mask 255.255.0.0 192.168.1.2 >On the windows client before connecting. Is there a way to fire off a script automatically after connecting? >Microsoft doesnt seem to be interested in fixing this problem as the problem >persist even on Windows XP and has been known since Windows 98(??). Figures. --Brett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.7.2.20030417122205.02aed700>