wireless, Broadcom & jaunty

[Joep L. Blom]

Derek Broughton wrote:
> Joep L. Blom wrote:
> 
> 
> wmaster0 is some kind of pseudo-device related to your wifi.  pan0, I think, 
> is bluetooth related and may show up if you have bluetooth server software 
> installed even if you don't have a bluetooth device.

> Actually, DHCP discovery packets are sent to the broadcast address (ie, 
> every device on the subnet sees them), not a particular server.  I'm not 
> sure how that could be an issue, though.
> 
> 
> Do you _have_ response packets?  No need to get into packet sniffing - what 
> actually shows in syslog?  If you don't actually see DHCPOFFER, then it 
> seems your router never hears from you.
>
Derek thanks.
The problem is that it's not always the same. I now have rebooted and 
the system now behaves differently.
When I look in the syslog it doews the following:
1. The kernel module associates the card (eth0) with the wireless router 
but it associates the IPv6 address with it: as seen here:
....
May  3 14:25:32 velsatis kernel: [ 1085.872563] eth0: direct probe to AP 
00:c0:49:54:77:9e try 1
May  3 14:25:32 velsatis kernel: [ 1085.874373] eth0 direct probe responded
May  3 14:25:32 velsatis kernel: [ 1085.874379] eth0: authenticate with 
AP 00:c0:49:54:77:9e
May  3 14:25:32 velsatis kernel: [ 1085.876609] eth0: authenticated

May  3 14:25:32 velsatis kernel: [ 1085.876616] eth0: associate with AP 
00:c0:49:54:77:9e
THIS IS THE MAC ADDRESS OF THE WIRELESS ROUTER

May  3 14:25:32 velsatis kernel: [ 1085.878475] eth0: RX AssocResp from 
00:c0:49:54:77:9e (capab=0x431 status=0 aid=6)
May  3 14:25:32 velsatis kernel: [ 1085.878480] eth0: associated
May  3 14:25:32 velsatis kernel: [ 1085.878610] ADDRCONF(NETDEV_CHANGE): 
eth0: link becomes ready

May  3 14:25:33 velsatis avahi-daemon[3399]: Registering new address 
record for fe80::20c:76ff:fe71:bd44 on eth0.*.
!!! THIS IS THE IPv6 MAC ADDRESS OF THE WIRELESS CARD !!!

with ifconfig the inet6 address is that address but the MAC address is 
00:0c:76:71:bd:44.
Therafter the dhcpclient starts and gives then:
May  3 14:25:36 velsatis dhclient:
May  3 14:25:36 velsatis dhclient: wmaster0: unknown hardware address 
type 801
May  3 14:25:36 velsatis avahi-daemon[3399]: Withdrawing address record 
for fe80::290:f5ff:fe32:20cb on eth1.
May  3 14:25:36 velsatis dhclient: wmaster0: unknown hardware address 
type 801
May  3 14:25:36 velsatis dhclient: Bind socket to interface: No such device
etc.
So I assume there are several mixups in the network configuration but I 
haven't found out which scripts I have to adapt to correct this.
Hoep you have some ideas?
Joep