Red Hat Bugzilla – Bug 149736
dhcp client in installer is lacking support for static-routes
Last modified: 2012-12-19 22:33:17 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)
Description of problem:
The dhcp client used in the installer (I think this is pump but I'm not sure
about that) doesn't recognize the static-routes option (option code 33, RFC
2132) transmitted via dhcp.
If you need a static route to contact the install server, a network install is
This is e.g. the case for the popular dedicated servers ("Rootserver") rented
from the largest German provider "United Internet" (the brands are e.g. "1 und
1", "GMX" and "Schlund und Partner").
They use a configuration with a subnet of 255.255.255.255. The default gateway
is thus not in the local net. A static route transmitted via dhcp fixes this
for the final system whose dhclient understands this option - but the dhcp
client used in the installer doesn't understand it.
So a regular network install is not possible on these servers.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure your DHCP server with the option "static-routes"
2. Start a network installation
3. Get an IP via DHCP
4. Change to virtual terminal 2 (the shell)
5. "route -n" shows that the static route transmitted via dhcp is not set
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Still a problem in FC6 test 2.
The installer does not send the needed DHCP option 121 in order to get the
classless static routes from the dhcp server (verified with ethereal).
Please change version to FC6 test 2 (I don't have enough permissions for that).
I had the same problem, PUMP not set properly the route. The latest anaconda
Source does not set the route. (IMHO iam not seeing any code which recognize
So my question is - exists a workaround to avoid this?
There is no workaround for this now, other than doing a manual TCP/IP
configuration during installation.
I need to fix this issue in libdhcp.
thanks for the fast reaction.
in the meantime i had modified the diskboot.img with a ks.cfg which has in the
%pre some route commands. (i had additionally build a static route command and
had placed this into the initrd.img but this has no success.
did you clued?
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
The Problem is still persisting.
Persisting in rawhide or in fc6? Thanks.
jupp, AFAIK Mr. Cantrell hasn't fixed yet.
Is any Chance that this Problem is fixed soon? We waste a lot of Money and we
cant install the Servers in the Datacenter.
Yeah, I'm interested in having this issue fixed too. Installing our servers
would be much more easy this way. Currently we have to create a disk image on
a local server and upload the image to the datacenter. Just using the regular
anaconda via serial console would be about 10 times faster.
Working on it now.
This has been fixed in libdhcp-1.24-2.fc7 in rawhide. Anaconda will have to be
rebuilt against this new libdhcp, and that may or may not happen today.