Subject: bin/22418: dhclient does not always (never?) update default route
To: None <gnats-bugs@gnats.netbsd.org>
From: Rhialto <rhialto@azenomei.knuffel.net>
List: netbsd-bugs
Date: 08/09/2003 17:11:41
>Number:         22418
>Category:       bin
>Synopsis:       dhclient does not always (never?) update default route
>Confidential:   yes
>Severity:       critical
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Aug 09 15:13:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Rhialto
>Release:        NetBSD 1.6.1
>Organization:
	
>Environment:
System: NetBSD loelappie.falu.nl 1.6.1 NetBSD 1.6.1 (LOELAPPIE) #1: Fri Jul 11 19:56:16 CEST 2003 root@loelappie.falu.nl:/usr/src/sys/arch/i386/compile/LOELAPPIE i386
Architecture: i386
Machine: i386
>Description:
	
dhclient does not always (never?) update default route

When using netbsd 1.6.1 with cable ISP NetCabo.pt, I see the following
problem. Netcabo has the tendency to give a very short-time lease to a
192.168.*.* address, then when it expires it gives a real public
address. However, dhclient (or dhclient-script) does not cope properly
with this situation. It does not update the default route; although, as
far as I can see, it is provided in the dhcp message.
Also, during initial boot, a message "can't assign requested address"
appears, although it is not clear what command is causing it.

This is the final situation, which is clearly not usable:

Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use    Mtu  Interface
default            192.168.100.1      UGS         1      379      -  vr0
127                127.0.0.1          UGRS        0        0  33220  lo0
127.0.0.1          127.0.0.1          UH          3        0  33220  lo0
192.168.100.18     127.0.0.1          UGHS        0        0  33220  lo0
213.22.22/23       link#1             UC          1        0      -  vr0
213.22.22.69       127.0.0.1          UGHS        0        0  33220  lo0
213.22.23.254      00:08:20:cc:dc:70  UHLc        0        0      -  vr0

vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	address: 00:a0:cc:d4:f7:42
	media: Ethernet autoselect (10baseT)
	status: active
	inet 213.22.22.69 netmask 0xfffffe00 broadcast 213.22.23.255
	inet6 fe80::2a0:ccff:fed4:f742%vr0 prefixlen 64 scopeid 0x1

>How-To-Repeat:
	
	Connect a computer to a cable modem of NetCabo (Portugal), and
	use DHCP.

>Fix:
	manually enter the command (as root) route change default
	(whatever it should be in reality). Fortunately the address
	seems to find its way in the routing tables somehow (the last
	entry above).

-Olaf.
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet?

___ Olaf 'Rhialto' Seibert      -- The evil eye is caused by the black
\X/ rhialto/at/xs4all.nl        -- tongue - Tom Poes, "Het boze oog", 4456.
>Release-Note:
>Audit-Trail:
>Unformatted: