Red Hat Bugzilla – Bug 191328
network should support --mtu argument
Last modified: 2007-11-30 17:11:32 EST
Description of problem: Sometimes when doing a network-based Kickstart install, you might not have a full 1500 byte MTU available to you (such as when installing over a router using a VPN tunnel to connect to a remote FTP or HTTP server). Being able to explicitly specify the path MTU would make this more robust. Version-Release number of selected component (if applicable): How reproducible: put "ifconfig -a" into your ks.cfg's %post file. It will show the default MTU (!500 bytes for ethernet eth0). Steps to Reproduce: 1. n/a -- this is an enhancement request 2. 3. Actual results: n/a Expected results: Specifying: network --device=eth0 --bootproto=dhcp onboot=on --mtu should have two results: (1) the interface eth0 gets (re)configured with "ifconfig eth0 mtu XXX" (or via the appropriate ioctl) before the install process begins (including fetching any remote files); (2) the /etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever) should have the additional line "MTU=XXX" inserted. Additional info:
Committed to anaconda and pykickstart. We'll test this out in the next anaconda rebuild and see how it goes from there.
Could you please test with Rawhide and see if this is working as you expect?
I can test it as a patch... Can you point me at the diffs?
It will probably be easiest for you to just wait until FC6test1, since this requires changes to pykickstart, anaconda, and the loader. The update process for this is fairly complicated and unforgiving.