pptp connection unreliable with MacOSX client, help!
Raphaël Marmier
raphael at computer-rental.ch
Wed Jul 9 07:14:42 PDT 2003
I've setup a vpn server with poptop 1.1.3 from the ports (FreeBSD 4.8
release). It work fine, with mppe 128 enabled, from Windows 2000 and
MacOSX 10.2 (using the built-in vpn client).
I use it to mount a volume through nfs and samba, so I can use cvs in
local mode (needed).
However, on MacOSX, it is unreliable and the mountpoint freezes, until
I manage to disconnect and reconnect the vpn.
The following appears in /var/log/messages:
Jul 9 02:10:56 napalm pptpd[412]: CTRL: EOF or bad error reading ctrl
packet length.
Jul 9 02:10:56 napalm pptpd[412]: CTRL: couldn't read packet header
(exit)
Jul 9 02:10:56 napalm pptpd[412]: CTRL: CTRL read failed
Jul 9 02:11:58 napalm pptpd[421]: CTRL: EOF or bad error reading ctrl
packet length.
Jul 9 02:11:58 napalm pptpd[421]: CTRL: couldn't read packet header
(exit)
Jul 9 02:11:58 napalm pptpd[421]: CTRL: CTRL read failed
Jul 9 02:17:13 napalm pptpd[434]: GRE:
read(fd=5,buffer=804d580,len=8196) from PTY failed: status = 0
error = No error
Jul 9 02:17:13 napalm pptpd[434]: CTRL: PTY read or GRE write failed
(pty,gre)=(5,4)
Jul 9 02:18:35 napalm pptpd[441]: CTRL: EOF or bad error reading ctrl
packet length.
Jul 9 02:18:35 napalm pptpd[441]: CTRL: couldn't read packet header
(exit)
Jul 9 02:18:35 napalm pptpd[441]: CTRL: CTRL read failed
I've gone as far as setting nfs to tcp only, which helps go through
disconnection/reconnection cycles. But it seems that once the vpn
connection is wedged, it doesn't recover by itself.
I spent hours pinpointing this to pptp. Curiously, this problem
manifests itself only on slow llinks, such as dialups. I can reproduce
it by reducing the bandwidth with altq.
help...
Raph
More information about the freebsd-questions
mailing list