Date: Mon, 22 Sep 2003 22:49:45 -0700 From: "Crist J. Clark" <cristjc@comcast.net> To: freebsd-questions@freebsd.org Subject: PPTP with mpd(8) Assigning Wrong Address Message-ID: <20030923054945.GA73782@blossom.cjclark.org>
next in thread | raw e-mail | index | archive | help
I have a fairly straightforward PPTP configuration. Since WEP is hopelessly broken, I use a VPN across my WLAN. I use IPsec for hosts who can handle it, but some Windows hosts are stuck with Microsoft VPN, PPTP (which is somewhat less hopelessly broken than WEP). The wireless AP is FreeBSD RELENG_4_8 running MPD 3.14. It has been working, but there is something strange going on. My mpd.conf looks like this, default: load wireless-client1 wireless-client1: new -i ng0 pptp pptp set ipcp ranges 192.168.159.254/32 192.168.159.1/32 load wireless-tunnel wireless-tunnel: set iface disable on-demand set iface idle 1800 set bundle enable multilink set link yes acfcomp protocomp set link no pap chap set link enable chap set link keep-alive 10 60 set link mtu 1400 set ipcp yes vjcomp set ipcp dns 192.168.44.150 set bundle enable compression set ccp yes mppc set ccp yes mpp-e40 set ccp yes mpp-e128 set ccp yes mpp-stateless But the problem is that the client is not being assigned 192.168.159.1. It gets 192.168.158.0. Here's the syslog, Sep 22 15:19:04 <daemon.info> buttercup mpd: [pptp] IPCP: rec'd Configure Request #6 link 0 (Req-Sent) Sep 22 15:19:04 <daemon.info> buttercup mpd: IPADDR 0.0.0.0 Sep 22 15:19:04 <daemon.info> buttercup mpd: NAKing with 192.168.158.0 Sep 22 15:19:04 <daemon.info> buttercup mpd: PRIDNS 0.0.0.0 Sep 22 15:19:04 <daemon.info> buttercup mpd: NAKing with 192.168.44.150 Sep 22 15:19:04 <daemon.info> buttercup mpd: PRINBNS 0.0.0.0 Sep 22 15:19:04 <daemon.info> buttercup mpd: SECDNS 0.0.0.0 Sep 22 15:19:04 <daemon.info> buttercup mpd: SECNBNS 0.0.0.0 WTF? I should note that 192.168.158.0/24 is the WLAN network. Why are we telling them to use that address? BTW, we do use the correct address for our end of the link. Like I said, this actually works, but it's not what I want, and I'm not sure what's going to happen if I have more than one PPTP client on this network at once. I'd say something like, wireless-client2: new -i ng1 pptp pptp set ipcp ranges 192.168.159.254/32 192.168.159.2/32 load wireless-tunnel But I'm not sure what address it would end up with. Any ideas? Am I misunderstanding some feature or limitation of PPTP? -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030923054945.GA73782>