wireless, Broadcom & jaunty

[Joep L. Blom]

> On 05/01/2009 06:11 AM, Joep L. Blom wrote:
> 
> Typically it will be wlan0 and the first ethernet wired port will be
> eth0. There were some issues with Ubuntu mixing the mac assignements &
> even incrementing the ethx. There is a way to clear it, but I can't put
> my finger on it just now (it's here in the archives). The fact that udev
> is reassigning wlan0 to eth0 is a bit of a puzzle (to me) & worth
> looking into further.
> 
> To restart networking:
> 
> $ sudo /etc/init.d/networking restart
> 
> You can do the same for wicd if you'd like - but I've found that wicd
> isn't too happy about it afterwards. Networking will still work, but
> wicd panel icon doesn't work unless you log out/in again. I suppose
> there is a better way to get it (the wicd panel applet) kick started
> again - but I've not bothered to find it.
> 
> You might also check:
> 
> $ iwconfig
> $ ifconfig
> 
> afterwards & post the results.
> 
> 
> You can see what commands are available via 'ls /etc/init.d/' - init.d
> is quite handy.

Yes I agree with that but I know most services by head and 'service'
gives you some safety against accidental mistakes.

The results of iwconfig:
o        no wireless extensions.

eth1      no wireless extensions.

wmaster0  no wireless extensions.

eth0      IEEE 802.11bg  ESSID:"nwhq_wireless"
           Mode:Managed  Frequency:2.452 GHz  Access Point:
00:C0:49:54:77:9E
           Bit Rate=1 Mb/s   Tx-Power=20 dBm
           Retry min limit:7   RTS thr:off   Fragment thr=2352 B
           Power Management:off
           Link Quality=88/100  Signal level:-17 dBm  Noise level=-66 dBm
           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

pan0      no wireless extensions.

This looks normal except there is no IP-address for eth1 as my dhcp
server apparently refused it. The interesting fact is that in this case
wireless was the only network connection.

ifconfig:
eth0      Link encap:Ethernet  HWaddr 00:0c:76:71:bd:44
           inet6 addr: fe80::20c:76ff:fe71:bd44/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:747 errors:0 dropped:0 overruns:0 frame:0
           TX packets:93 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:91664 (91.6 KB)  TX bytes:9600 (9.6 KB)

eth1      Link encap:Ethernet  HWaddr 00:90:f5:32:20:cb
           UP BROADCAST MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
           Interrupt:19 Base address:0xe800

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:12 errors:0 dropped:0 overruns:0 frame:0
           TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:640 (640.0 B)  TX bytes:640 (640.0 B)

wmaster0  Link encap:UNSPEC  HWaddr
00-0C-76-71-BD-44-00-00-00-00-00-00-00-00-00-00
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
Where wmaster0 and pan0 reside I don't know. That eth1 had no IP-address
is correct: it is not connected.

The wired connection works OK.
The MAC-address 00:C0:49:54:77:9E is the address of the wireless router.
When I do a "networking restart" it gets it's wired address from the
dhcp-server but the wireless sends DHCPDISCOVER packets to the same
server on the net but the dhcp-server doesn't respond. This is the same
with or without the wired connection. Maybe I have to look at the
response packets from the dhcp-server?
It is still a mystery where the problem is.
Hope you have still some suggestions.
Joep


P.S. I'm resending this message as for some reason it didn't reach the 
list (at least I didn't receive it).
Joep