share/vyatta-cfg/templates/interfaces/serial/node.tag/cisco-hdlc/mru/node.def | 4 share/vyatta-cfg/templates/interfaces/serial/node.tag/e1-options/mru/node.def | 4 share/vyatta-cfg/templates/interfaces/serial/node.tag/e1-options/mtu/node.def | 4 share/vyatta-cfg/templates/interfaces/serial/node.tag/frame-relay/mru/node.def | 4 share/vyatta-cfg/templates/interfaces/serial/node.tag/t1-options/mru/node.def | 4 share/vyatta-cfg/templates/interfaces/serial/node.tag/t1-options/mtu/node.def | 4 scripts/serial/vyatta_update_serial.pl | 57 ++-------- 7 files changed, 16 insertions(+), 65 deletions(-)
New commits: commit 776c32c8611a288203e9a275981c77103bb0ffeb Author: Bob Gilligan <[email protected]> Date: Fri May 8 14:08:31 2009 -0700 Bugfix 3336, 3340: Remove parameters from CLI that are not supported by wanpipe. The wanpipe code now automatically determines the physical layer MTU based on the MTU being used by the datalink layer (i.e. the VIF) above it. So, there is no longer any need to configure the MTU of the physical layer. The MRU tracks the MTU, so there is no need to configure that either. Also, Frame Relay and Cisco HDLC protocols do not provide MRU negotiation as PPP does. So, they do not need to be configurable. http://suva.vyatta.com/git/?p=vyatta-serial.git;a=commitdiff;h=776c32c8611a288203e9a275981c77103bb0ffeb _______________________________________________ svn mailing list [email protected] http://mailman.vyatta.com/mailman/listinfo/svn
