On Wednesday 06 January 2010 21:27:40 Christian von Roques wrote: > I don't like calling ifconfig twice, but the ifconfig(8) man-mage warns: > "Currently, not all devices support setting the MTU." > Granted, dhclient is usually used on devices which support setting the > MTU and the client-mtu option is rarely used, but figuring out what's > wrong if dhclient-script fails to configure the interface because it > can't set the MTU due to a client-mtu option being received for an > interface which does not support setting the MTU is a task which I don't > wish to impose on anybody. -- If this is too defensive, maybe use:
I'm not sure what type of interface you could run DHCP on that would not support setting the MTU. Be it a virtual interface of some type such as L2 tun(4), vlan(4), trunk(4) or an Ethernet interface. This used to be an issue with still a good number of Ethernet interface drivers, especially older drivers as of 4.4 but was fixed properly with 4.5. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
