wireless, Broadcom & jaunty

[Derek Broughton]

Joep L. Blom wrote:

> Derek Broughton wrote:
>> Joep L. Blom wrote:
>> 
>>> Derek Broughton wrote:
>> 
>>>> 
>> 
>> No, this is the avahi-daemon (zeroconfig).  IF you don't get a dhcp
>> address before dhclient times out, avahi kicks in and gives you a private
>> IP that makes it possible for other systems on your LAN to see you.
> Well, again something learned but I assume it's hard-coded in avahi.

I think not everything in avahi is hard-coded, but it is _really_ difficult 
to configure :-(  I haven't found any useful documentation.

>> Well, no it isn't.  I mean, I'm sure it didn't get any, but it means your
>> router is either not listening, or your NIC is not talking, or both of
>> those
>> are happening but your NIC isn't _hearing_ a response.  None of those are
>> good.

> I agree. Therefore I tried with Wireshark (on another system) to look at
> the packets but I don't see any DHCPDISCOVER packets. I will look into
> it more.

So if dhclient says it _sends_ DHCPDISCOVER packages and wireshark says 
nothing else sees them, that says to me that the interface must exist but 
there's no broadcast address.  I can't think of a solution, though.

>> I'm still concerned about the device showing up on eth0.  What's in your
>> /etc/network/interfaces?
>> 
> Well, Interfaces has:
> # The loopback network interface
> auto lo
> iface lo inet loopback
> 
> iface eth1 inet dhcp
> 
> iface eth0 inet dhcp
> wireless-key XXXXXXXXXXXXXXXXXXXX
> wireless-essid nwhq_wireless
> 
> auto eth1
> 
> auto eth0
> 
> So this looks perfectly normal to me.

Yes, and actually easier than Network Manager where you have to pretty much 
guess at interface settings.

What do you see in the log after "sudo ifup eth0", and if that doesn't work 
what do you see after "sudo ifconfig eth0 up"

> I think it is something trivial but I still don't know what. And the
> laptop soesn't have a switch to turn wireless off (!) which I have on
> another laptop and it's very annoying as the switch inadvertently is
> pressen when you put this laptop in your lap (!).

<lightbulb/> 
My HP that did that all the time, but the latest broadcom drivers actually 
ignored the switch anyway.  What driver are you using?  Now that I look 
back:
  Broadcom 43xx driver loaded [ Features: PLR, Firmware-ID: FW13 ]
doesn't look right to me - that looks like the old one, that was blacklisted 
in Intrepid.

Since the HP in question has a failed drive, and won't be getting a new one 
until next week, I can't compare with my own machine (and even then, it'll 
need a fresh install, so I won't be certain it's the same as I had before).
-- 
derek