retitle 394052 ppp: report mtu value used thanks False report. I played with mtu configuration option and it does effect the traffic; it's not reflected in debug output though.
So, let's reformulate this: when pppd says it negotiated a certain client mru value, which differs (being larger, it seems) from the actual mtu it will use, it should say so and tell which mtu that is. I still have the packets not reaching the client problem, but I'm not sure at this point why they're not. On Thu, Oct 19, 2006 at 07:56:41AM +0200, Filip Van Raemdonck wrote: > > I'm trying to connect Windows systems as VPN roadwarriors to a gateway > running ppp over l2tp over ipsec. The gateway is in Singapore, and has > non-ideal internet connection (mainly, the MTU/MRU had to be lowered > for some things to work properly). > > For ppp, I set mtu and mru as well: > > ... > mtu 1200 > mru 1200 > ... > > Checking the ppp log, the client asks for a mru of 1400, larger than what > the ppp configuration has set as mtu; pppd happily acknowledges it despite > its lower mtu setting. It looks like the mtu configuration is ignored and > pppd starts sending packets larger than what the tcp-ip (and thus ipsec) > layer of the gateway can send. > > ... > Oct 18 15:24:00 scotos pppd[16120]: rcvd [LCP ConfAck id=0x1 <mru 1200> > <asyncmap 0x0> <auth chap MS-v2> <magic 0x9fcb8fc7> <pcomp> <accomp>] > Oct 18 15:24:00 scotos pppd[16120]: rcvd [LCP ConfReq id=0x1 <mru 1400> > <magic 0x2c3d20c0> <pcomp> <accomp> <endpoint > [local:95.21.d7.70.e2.45.4b.6a.ad.23.8b.3d.b6.46.05.06.00.00.00.02]>] > Oct 18 15:24:00 scotos pppd[16120]: sent [LCP ConfAck id=0x1 <mru 1400> > <magic 0x2c3d20c0> <pcomp> <accomp> <endpoint > [local:95.21.d7.70.e2.45.4b.6a.ad.23.8b.3d.b6.46.05.06.00.00.00.02]>] Regards, Filip http://www.sysfs.be/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
