[SOLVED] Not able to get an IP address when connecting to an open wireless network

jostber · 01-26-2015, 01:29 AM

Can you try to use the b43 driver and see if that works?

boomhower182 · 01-26-2015, 02:08 AM

My card isn't supported I have tried, in fact it was already there in the install and I had to blacklist it. I can revert everything and blacklist wl and try it again but I doubt it will work

boomhower182 · 01-26-2015, 02:15 AM

Just tried and doesn't work at all

business_kid · 01-26-2015, 03:50 AM

there are two drivers for that card. The b43 kernel drivers(b43, b43legacy), and the wl driver. At this stage, they may both be blacklisted. Just check

Code:

grep -e 'b43' -e 'brcmsmac' -e 'wl' /etc/modprobe.d/blacklist.conf

boomhower182 · 01-26-2015, 04:20 AM

I blacklisted b43 myself because it doesn't work with my card. I use the wl driver, with the wl driver I can see networks and join them if they are secured but if they are open then it can't get an IP address but it does associate with the ap

boomhower182 · 01-26-2015, 04:25 AM

Quote:

Originally Posted by boomhower182

Just tried and doesn't work at all

Sorry I didn't realize that I didn't specify that I was talking about the b43 driver in that post. Didn't mean for any confusion

turtleli · 01-26-2015, 05:47 AM

Can you try one of the following manual methods (make sure there's no running networkmanager, dhcpcd or wpa_supplicant processes):
A:

Code:

ip link set eth1 up
iw eth1 connect KCTCS-GUEST
dhcpcd eth1

B:
Use a /etc/wpa_supplicant.conf or other wpa_supplicant config file like

Code:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=root
ap_scan=1

network={
	ssid=KCTCS-GUEST
	scan_ssid=1
	key_mgmt=NONE
}

and then try

Code:

wpa_supplicant -B -i eth1 -Dnl80211 -c /etc/wpa_supplicant.conf
dhcpcd eth1

As a side note - the wl driver does tend to name the wireless device as eth{x}. If a different device name is preferred it can be changed in /etc/udev/rules.d/70-persistent-net.rules.

boomhower182 · 01-26-2015, 06:05 AM

A: will do the same as

Code:

Ifconfig eth1 up
Iwconfig eth1 essid KCTCS-GUEST
dhcpcd eth1

Which will connect to the access point then dhcpcd will timeout because it doesn't get a response

I'm also not at work at the moment, I just got home. I'll try B: when I go back to work which will be Saturday because I'm off all week.

turtleli · 01-26-2015, 06:30 AM

Quote:

Originally Posted by boomhower182

A: will do the same as

Code:

Ifconfig eth1 up
Iwconfig eth1 essid KCTCS-GUEST
dhcpcd eth1

Which will connect to the access point then dhcpcd will timeout because it doesn't get a response

I'm also not at work at the moment, I just got home. I'll try B: when I go back to work which will be Saturday because I'm off all week.

You are more or less correct, but using iwconfig means you use the legacy Wireless Extensions interface whereas iw uses the cfg80211 interface and the readme for the wl driver does say:

Quote:

This driver uses cfg80211 API. Code for Wext API is present and can be built
but we have dropped support for it.

Unfortunately I can't test if there's a difference with the wl driver since the Macbook with the Broadcom wireless device is somewhat dying and I also removed the Wireless Extensions support from the custom kernel it uses.

boomhower182 · 01-26-2015, 01:26 PM

I'll try to recreate the network here, if not I'll try it Saturday.

boomhower182 · 01-31-2015, 05:23 PM

Turtleli I have tried both of your suggestions and with no results. Still connects to the ap but doesn't get an ip.

turtleli · 01-31-2015, 06:31 PM

I'm out of ideas, I haven't tried and can't think of any other method of connecting to an unsecured network. Is it just this wireless network you can't connect to or is it all unsecured wireless networks?

boomhower182 · 01-31-2015, 06:37 PM

It's all unsecured networks, I'm starting to think I'll have to run a different distro which is not what I want to to, but at the end of the day or week or even weeks it's all about having something that works.

Gerard Lally · 01-31-2015, 07:23 PM

Quote:

Originally Posted by boomhower182

It's all unsecured networks, I'm starting to think I'll have to run a different distro which is not what I want to to, but at the end of the day or week or even weeks it's all about having something that works.

Has someone blocked your MAC address on the router?

boomhower182 · 01-31-2015, 07:26 PM

No my MAC address is not blocked, I can use other distros to connect.