On Thu, 2009-09-10 at 13:11 -0700, Dan Williams wrote: > On Thu, 2009-09-03 at 02:31 +0530, ritz wrote: > > On Wed, 2009-09-02 at 10:56 -0400, Derek Atkins wrote: > > > ritz <[email protected]> writes: > > > > > > > Hello > > > > > > > > I do not see any option to set MTU under NMSettingVPN. All I could > > > > find was for ethernet, and wireless. Are there any plans to add this ? > > > > > > The way I do this is manipulating the helper script to reset the MTU > > > after the VPN comes up. It's a PITA. > > > > > > > reference: > > > > http://live.gnome.org/NetworkManagerConfiguration > > > > http://bugzilla.gnome.org/show_bug.cgi?id=584200 > > > > > > -derek > > > > > > vpnc-console uses the the below to set MTU correctly > > > > if [ -n "$INTERNAL_IP4_MTU" ]; then > > INTERNAL_IP4_MTU is pretty new I guess? Must be added in 0.5.x I guess. > In any case, the patch below is about what should get used, yes.
No, vpnc doesn't set $INTERNAL_IP4_MTU at all -- it's only there in vpnc-script for the benefit of openconnect (which _does_ negotiate with the server and set it appropriately). -- David Woodhouse Open Source Technology Centre [email protected] Intel Corporation _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
