You are not logged in.
Hey all, first post.
Loving Arch linux, used Redhat since back in the 6.0 days, then Fedora core 2-4, then Ubuntu. Tried all sorts of smaller distros, but I think Arch is a winner. Anywho onto the question.
I have a Broadcom Card. I am using bcm43xx-fwcutter with the file linked onto the wiki. I want to get my IP via DHCP.
I have noticed however that whenever I use iwconfig <interface> essid <essid>, I can not be assigned an IP address, but I can ping my network. If I use iwconfig <interface> essid any, it will work. But only if I let my system stand for a few minutes after booting, or restarting /etc/rc.d/network. Here is some basic info
[root@lungnet shawn]# lspci | grep -i broadcom
00:08.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)
[root@lungnet shawn]# ifconfig
eth1 Link encap:Ethernet HWaddr 00:30:BD:97:22:55
inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:52735 errors:0 dropped:1179 overruns:0 frame:0
TX packets:42330 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:49436328 (47.1 Mb) TX bytes:3968906 (3.7 Mb)
Interrupt:5 Base address:0x8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:584 (584.0 b) TX bytes:584 (584.0 b)
[root@lungnet shawn]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11b/g ESSID:"lungair" Nickname:"Broadcom 4306"
Mode:Managed Frequency=2.462 GHz Access Point: 00:18:D1:46:36:BA
Bit Rate=24 Mb/s Tx-Power=15 dBm
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=108/100 Signal level=-29 dBm Noise level=-67 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
[root@lungnet shawn]# iwlist eth1 scan
eth1 Scan completed :
Cell 01 - Address: 00:14:BF:38:A7:2B
ESSID:"linksys"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.437 GHz (Channel 6)
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality=85/100 Signal level=-64 dBm Noise level=-67 dBm
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Extra: Last beacon: 160ms ago
Cell 02 - Address: 00:18:D1:46:36:BA
ESSID:"lungair"
Protocol:IEEE 802.11bg
Mode:Master
Frequency:2.462 GHz (Channel 11)
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 22 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Quality=100/100 Signal level=-29 dBm Noise level=-67 dBm
Extra: Last beacon: 80ms ago
Yes, my wireless device ie eth1 and not wlan0. Not sure why, but it has always been this way.
On boot, or trying to start the network, the broadcom device times out on DHCP. After a few minutes, I can manually do it
iwconfig eth1 essid any
dhclient eth1
Here is my rc.d networking section. eth0 is a wired device, but my computer is almost always wireless, so I dont want the network script timing out every time, trying to DHCP from the non existent cat5.
#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="lungnet"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth1="dhcp"
wlan_eth1="eth1 essid any"
INTERFACES=(lo eth1)
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)
Any thoughts on how to get the network script working properly? I will be leaving town on work, and need to leave my computer with the girlfriend. There is no way she is going to be able to manually start the network everytime its needed.
Offline
hi. I have SE GC79 which is based on the same chipset and I'm using b43/b43legacy module (both modules work well, giving me wlan0 device). maybe U should try one of them. as far as i remember, i've had similar problem using bcm43xx module. my advice is: try b43-fwcutter with wl_apsta-3.130.20.0.o and b43/b43legacy module.
here is nice howto which worked for me: http://linuxwireless.org/en/users/Drivers/b43
Last edited by amokkk (2008-05-16 17:05:31)
Through the darkness of future past / The magician longs to see / One chants out between two worlds / Fire walk with me.
bobik_the_traveller: Dell LS/p3 400/128/40/Sony Ericsson GC79,Philips SNN6500
LAST.FM
Offline
I was blaming this on my router, but I think I'm having the same problem on two different machines -- a Celeron with a Linksys WPC11 and an OLPC XO-1 using the wireless connection. Symptoms are identical, with both computers using an open, keyless network. Any suggestions would be greatly appreciated ...
Last edited by k.mandla (2008-05-16 12:46:23)
Linux user No. 409907
Offline
lungdart, is there a reason you're not using netcfg2? It works perfectly for me. My wireless card is eth0 and my wired connection is eth1. I just switch profiles manually.
Offline
The only reason I dont use netcfg2 is because prior to right now, I have never heard of it.
I had tried the b43 with fwcutter-b43 and it would give me wlan0 but it didnt seem to work. Maybe ill try it again, as I never used the b43 legacy drivers.
Offline
Update:
Tried using the b43legacy drivers with the same outcome as the b43 drivers using the above mentioned tutorial.
[root@lungnet shawn]# iwconfig wlan0 essid lungair channel 1 ap 00:18:D1:46:36:BA
[root@lungnet shawn]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wmaster0 no wireless extensions.
wlan0 IEEE 802.11g ESSID:"lungair"
Mode:Managed Frequency:2.412 GHz Access Point: 00:18:D1:46:36:BA
Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2352 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
[root@lungnet shawn]# lsmod | grep 43
b43legacy 101016 0
ssb 30980 1 b43legacy
rfkill 6036 1 b43legacy
mac80211 130316 1 b43legacy
input_polldev 3720 1 b43legacy
led_class 3844 1 b43legacy
nls_cp437 5888 1
ppp_generic 24348 0
fan 4356 0
snd_seq 48432 4 snd_seq_oss,snd_seq_midi_event
Also notice another wierd thing when going back to the bcm43xx drivers. If i comment out the networking section in my rc.conf file, the drivers wont work when manually setup after the network script fails?
[root@lungnet shawn]# iwconfig eth1 essid lungair channel 1 ap 00:18:D1:46:36:BA
[root@lungnet shawn]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11b/g ESSID:"lungair" Nickname:"Broadcom 4306"
Mode:Managed Frequency=2.412 GHz Access Point: Invalid
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="lungnet"
#
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
---> #eth1="dhcp" <---
---> #wlan_eth1="eth1 essid any" <----
---> #INTERFACES=(lo eth1) <---
#
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
#
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network-profiles
#
#NET_PROFILES=(main)
I find that very odd.
Any other ideas?
Offline
Bump
Offline
Try netcfg2. The old way is deprecated. http://wiki.archlinux.org/index.php/Network_Profiles
Offline