"dhclient: DHCPRELEASE..." 1 second after "dhclient: bound ..."

[Nelson Strother]

  So to start fishing for some content for the proposed Fedora Linux
WiFi Manual (see:
    https://www.redhat.com/archives/fedora-list/2007-July/msg03209.html
), here is a situation.  On one laptop, one can find warm
fuzzies about its wireless adpater at f7 boot time in /var/log/messages/
e.g.:

  ... localhost NetworkManager: <info> eth1: Device is fully-supported
using driver 'orinoco_cs'.

But here are some later snippets from /var/log/messages/

Jul 18 18:57:12 localhost NetworkManager: <info>  Activation (eth1)
Stage 5 of 5 (IP Configure Commit) scheduled...
Jul 18 18:57:12 localhost NetworkManager: <info>  Activation (eth1)
Stage 4 of 5 (IP Configure Get) complete.
Jul 18 18:57:12 localhost NetworkManager: <info>  Activation (eth1)
Stage 5 of 5 (IP Configure Commit) started...
Jul 18 18:57:12 localhost avahi-daemon[2304]: Withdrawing address
record for fe80::202:2dff:fe53:4572 on eth1.
Jul 18 18:57:12 localhost avahi-daemon[2304]: Leaving mDNS multicast
group on interface eth1.IPv6 with address fe80::202:2dff:fe53:4572.
Jul 18 18:57:12 localhost dhclient: bound to 192.168.2.102 -- renewal
in 38304 seconds.
Jul 18 18:57:12 localhost avahi-daemon[2304]: Interface eth1.IPv6 no
longer relevant for mDNS.

My reaction was "how dare you withdraw my address record"!  So I
looked up avahi-daemon and found:

   This is a daemon which runs on client machines to perform Zeroconf
   service discovery on a network. avahi-daemon must be running on
   systems that use Avahi for service discovery. Avahi-daemon should not
   be running otherwise.

So via System, Administration, Services I could see Avahi daemon was
started, but by selecting its line, then selecting Stop, was rewarded
with "avahi-daemon stop successful", OK.  Now try connecting again:

Jul 18 19:28:28 localhost avahi-daemon[2304]: Got SIGTERM, quitting.
Jul 18 19:28:28 localhost avahi-daemon[2304]: Leaving mDNS multicast
group on interface eth1.IPv6 with address fe80::202:2dff:fe53:4572.
 :
Jul 18 19:29:21 localhost NetworkManager: <info>  Activation (eth1)
Stage 5 of 5 (IP Configure Commit) scheduled...
Jul 18 19:29:21 localhost NetworkManager: <info>  Activation (eth1)
Stage 4 of 5 (IP Configure Get) complete.
Jul 18 19:29:21 localhost NetworkManager: <info>  Activation (eth1)
Stage 5 of 5 (IP Configure Commit) started...
Jul 18 19:29:21 localhost dhclient: bound to 192.168.2.102 -- renewal
in 36026 seconds.
Jul 18 19:29:22 localhost NetworkManager: <info>  Activation (eth1)
successful, device activated.
Jul 18 19:29:22 localhost NetworkManager: <info>  SWITCH: terminating
current connection 'eth1' because it's no longer valid.
Jul 18 19:29:22 localhost NetworkManager: <info>  Deactivating device eth1.
Jul 18 19:29:22 localhost NetworkManager: <info>  Activation (eth1)
Finish handler scheduled.
Jul 18 19:29:22 localhost NetworkManager: <info>  Activation (eth1)
Stage 5 of 5 (IP Configure Commit) complete.
Jul 18 19:29:22 localhost dhclient: DHCPRELEASE on eth1 to 192.168.2.1 port 67
Jul 18 19:29:23 localhost kernel: eth1: New link status: Disconnected (0002)
Jul 18 19:29:23 localhost NetworkManager: nm_device_is_802_3_ethernet:
assertion `dev != NULL' failed

How dare you DHCPRELEASE just as we're starting!

  Just for consternation, here are other relevant facts:

 - This pairing of wireless adapter and this router operates well
   under a non-Linux operating system.

 - This wireless adapter has briefly operated well with each of
   two other wireless routers (in different locations;  the failing
   location is where this laptop would be primarily used).

 - I saw mention that an old driver and Linksys routers differed on
   their interpretation of 802.3 encapsualtion, but the current
   orinoco 0.15 drivers should be OK.  Yes, it is a Linksys router
   with which no useful connection is established.

       http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Orinoco.html


  Suggestions for configuration?  Bugzilla time?

Cheers,
Nelson