Red Hat Bugzilla – Bug 445131
mtu boot argument ignored
Last modified: 2008-08-01 22:00:26 EDT
Description of problem:
For some reason, as of recently, I had to set a lower-than-1500 mtu on one of my
notebooks for reliable network operation. This has been easy to do with config
files, but it proved to be challenging to get Fedora 9-Preview installed on this
notebook with kickstart, for the mtu argument appears to be ignored for install
time. As a result, the machine ends up unable to access the nfs-mounted install
media: the TCP connections used to implement NFS break unless I force the TCP
MSS to a lower value on the server, emulating to some extent the effects of
setting the MTU on the installing client. I could verify during installation
that the dhcp-configured ethernet interface had MTU set to the default value,
rather than to the one I'd specified.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Boot up with e.g. mtu=500
2.Check that the setting made to the interface
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Is this still a problem in the final release of F9?
This should be working in recent rawhide trees.