Bug 1045087 - Setting gateway fails with classless static routes DHCP option
Summary: Setting gateway fails with classless static routes DHCP option
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-19 15:07 UTC by Tim Niemueller
Modified: 2018-08-22 16:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:47:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tim Niemueller 2013-12-19 15:07:41 UTC
Description of problem:
In our setup we require to provide a specific network route aside the default gateway. Therefore we use the classless route option of DHCP. This works fine for regular DHCP (on installed machines), but fails during installation.

For example, if I try to use a kickstart file from a web server via HTTP this fails if the web server is somewhere where routing across the default gateway is required (or if this is required to reach the DNS server).

Version-Release number of selected component (if applicable):
dracut-034-64.git20131205.fc20.x86_64
(determined after the completed installation on the machine before applying any updates)

How reproducible:
Always

Steps to Reproduce:
This assumes the following setup:

Machine to install ----- Gateway ------ Install server
                   |
                   |-- second router --- Other network

On the local network of the machine to install is a DHCP server which hands out two routes, one default gateway (1.2.3.1 in the example) and another router to a private network (router 1.2.3.2 for network 172.16.35.0/24 in the example).

The DHCP server has an entry like this:
subnet 1.2.3.0 netmask 255.255.255.0 {
  range 1.2.3.101 1.2.3.127;
  # the following commented out version would work,
  # but only provide a default gateway
  #option routers 1.2.3.1;
  # the following works with the installed machine, but not with dracut
  option classless-static-routes 24.172.16.35 1.2.3.2, 0 1.2.3.1;
  option ms-classless-static-routes 24, 172, 16, 35,  1, 2, 3, 2,     0, 1, 2, 3, 1;
}

1. Put a kickstart file on a webserver, e.g. on fedorapeople.org
2. Boot from installation DVD and add the following parameters in boot menu: ks=http://fedorapeople.org/SOMEWHER/ks.cfg
(assuming the machine acquires its network configuration from a DHCP server configured as mentioned above).

Actual results:
The installation fails, on the recovery console verify with "ip route" that the default gateway has not been recognized.

Expected results:
The dhclient in dracut should properly recognize the default route in the classless static routes case.

Comment 1 b3niup 2014-10-19 03:32:48 UTC
Also affects dracut (033-161.el7) in CentOS 7 x86_64 installer.

Comment 2 Kal McFate 2015-01-17 01:44:35 UTC
Expanding on this, it also fails if there are two interfaces with DHCP, one being private with provisioning network access with no gateway and the other being public with installation media, etc...

Comment 3 Fedora End Of Life 2015-05-29 10:03:36 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-30 00:47:24 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.