Bug 46425

Summary: dhcpcd invents a default route when none is supplied
Product: [Retired] Red Hat Linux Reporter: chris
Component: dhcpcdAssignee: Elliot Lee <sopwith>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-09-21 00:17:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description chris 2001-06-28 13:33:49 UTC
When the DHCP server doesn't supply the routersOnSubnet option in its
reply, dhcpcd assumes that it can use the giaddr instead, and just goes
ahead and uses it to invent its own static route:

 if ( ! DhcpOptions.val[routersOnSubnet] )
   {
     DhcpOptions.val[routersOnSubnet] = malloc(4);
     if ( DhcpMsgRecv->giaddr )
       memcpy(DhcpOptions.val[routersOnSubnet],&DhcpMsgRecv->giaddr,4);
     else
       memcpy(DhcpOptions.val[routersOnSubnet],
              DhcpOptions.val[dhcpServerIdentifier],4);

I can't find any warrant for doing this in RFC2131, and it's not the
behaviour I want (or expect).  Could it at least be made possible to
disable this behaviour using a command-line option?

Thanks very much,
Chris.

Comment 1 Elliot Lee 2001-09-21 00:17:51 UTC
I'll have to ask the upstream maintainer.

Comment 2 Elliot Lee 2001-12-31 19:00:53 UTC
Upstream maintainer says it is fixed in dhcpcd-1.3.21pl1, which is in rawhide.

Comment 3 Elliot Lee 2002-01-04 19:46:20 UTC
*** Bug 55312 has been marked as a duplicate of this bug. ***