Date: Thu, 08 Jan 2004 03:08:02 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Chris Jones <cjones@gruntle.org> Cc: FreeBSD User Questions List <freebsd-questions@freebsd.org> Subject: Re: mpd PPTP to Cisco 3000 VPN Concentrator routing problem Message-ID: <1073549281.76587.12.camel@shumai.marcuscom.com> In-Reply-To: <20040108074911.GC357@gruntle.org> References: <20040108074911.GC357@gruntle.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-lXmyujvNKs0XVF3mRCbu Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-01-08 at 02:49, Chris Jones wrote: > Hi. I've gone over list archives and seen this issue discussed before, > but the sugggested solutions aren't working for me. I am using > mpd-3.15_1 on FreeBSD 4.9-STABLE to connect to a Cisco 3000 Series VPN > Concentrator. I have negotiated CHAP and MPPE and the ng0 interface > comes up, but when I try to do anything I get this: >=20 > $ ping 10.10.58.7=20 > PING 10.10.58.7 (10.10.58.7): 56 data bytes =20 > ping: sendto: Resource deadlock avoided =20 > ping: sendto: No buffer space available =20 >=20 > A little investigation showed that this is a known routing issue and > that it is possible to work around by re-addressing the ng0 interface > with the VPN concentrator's private IP and set a default route to it. I > did this, but I still have the same problem. :( >=20 > Does anyone see what I am doing wrong here? Below are my routing table > and ifconfig before running mpd, after running mpd, and after running > the "fix". Below that is my mpd.conf and its output (verbose). >=20 > I appreciate any help on this, I've been going crazy trying to figure > out what I'm doing wrong. I can get it to work using the OSX PPTP > client, but not mpd. Good luck. I have tried to get this working, but have never been able to get mpd encryption to work with the Concentrator's encryption (neither has anyone else to my knowledge). If you disable encryption on the concentrator, the tunnel will come up, and you will be able to pass traffic across it. Any other combination does not work. I haven't tried 3.16 yet, but looking at the ChangeLog, I doubt it addresses this problem. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-lXmyujvNKs0XVF3mRCbu Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQA//Q/hb2iPiv4Uz4cRApCbAJ4lsgVpuZLGABo5Xrrj4qodAhrhLgCfSoVD EweLqWoMfmqi/53zdRpyssw= =zegV -----END PGP SIGNATURE----- --=-lXmyujvNKs0XVF3mRCbu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1073549281.76587.12.camel>