Re: port-i386/49167: dhcpd drop lease and connection repeatedly used with a fxp interface

[Adrian Christiansen <adrian.christiansen%gmail.com@localhost>]

The following reply was made to PR kern/49167; it has been noted by GNATS.

From: Adrian Christiansen <adrian.christiansen%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: port-i386/49167: dhcpd drop lease and connection repeatedly used
 with a fxp interface
Date: Sun, 31 Aug 2014 21:04:19 +0200

 2014-08-31 20:15 GMT+02:00 Joerg Sonnenberger 
<joerg%britannica.bec.de@localhost>:
 > The following reply was made to PR kern/49167; it has been noted by GNATS.
 >
 > From: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: port-i386/49167: dhcpd drop lease and connection repeatedly used
 >  with a fxp interface
 > Date: Sun, 31 Aug 2014 20:13:50 +0200
 >
 >  On Sun, Aug 31, 2014 at 12:05:00PM +0000, 
 > adrian.christiansen%gmail.com@localhost wrote:
 >  > >Fix:
 >  > A poor work around might be to use dhclient instead of dhcpd.
 >
 >  Can you try to run dhcpcd -K? That disables the use of carrier status.
 >  The next question would be what PHY your interface is using.
 >
 >  Joerg
 >
 
 That did actually work!
 
 I've been poking a bit more at the issue. There's something odd going on...
 At first I thought it was dhclient filling out resolv.conf that made
 dhcpcd work, it's not. It was an error on my path since I killed
 dhclient and started dhcpcd again with /etc/rc.d/network start, this
 will clear the resolv.conf and I didn't know this.
 
 I did however notice this:
 
 fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
     capabilities=1400<TCP4CSUM_Rx,UDP4CSUM_Rx>
     enabled=0
     address: 00:d0:59:b8:17:9a
     media: Ethernet 100baseTX
     status: active
     inet 192.168.1.53 netmask 0xffffff00 broadcast 192.168.1.255
     inet alias 192.168.1.58 netmask 0xffffff00 broadcast 192.168.1.255
 
 If I have an inet defined, like the one left behind from dhclient,
 dhcpcd will work every time. Even if it's something stupid like all
 the way to 11.11.11.11. However I found that dhcpcd -K would still
 work without the extra inet IP.
 
 Before I forget again, the phy is inphy:
 
 inphy0 at fxp0 phy 1: i82562ET 10/100 media interface, rev. 0
 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto