Minrich,

I've implemented your suggestion and the Network Manager was unable to detect any wireless networks at all. I posted results here: http://pastebin.com/m5a2f0b96.

Oddly enough, I re-enabled encryption on my router and my Network Manager was able to, once again, discover all available wireless networks but I still can't connect to the internet wirelessly. What's next?

Here is a magic potion:

You could try bringing, as root, the wlan0 interface down and then up:

# ifdown wlan0

# ifup wlan0

# iwconfig wlan0

# iwlist wlan0 scan

# ifconfig -a

NB the first command may fail - don't worry about it - it just clears the ifstate
the second command brings it up, the third command should show the essid (access point name) you are connected to, the fourth scans for all aps within range, and the fifth shows what IP address your wlan0 interface is linked to and whether it is transmitting and receiving.


Your pastebin dump shows that the scan worked fine with encryption off.

In your post - all of them is wireless. What do you mean?

nimnull22 - I ahd to think about your post for a while .... but M's post says that his network manager (god bless them all) doesn't see anything whilst we see a sucessful scan and know that the wlan0 interface is up and working but not connected/connecting to the Nexus access point.

So when he gets back to us, I intend to give him some manual iwconfig settings to lock his machine into the Nexus ap, like you I don't use network managers! That's probably why we keep meeting like this ( I know you come here often - so I won't ask! ).

He won't be able manually connect to AP while NM is active, we talked about it here.
Some one's asked already about it.

Minrich,

Here you go: http://pastebin.com/m6054ba58

Sooooooo sorry, try again substituting eth2 for wlan0, I am following too many threads at once.

duh, you need the B43 driver / firmware

0 members found this post helpful.

Minrich,

Here you go: http://pastebin.com/m30447cb7

Still can't connect to the net wirelessly. Do you think I may be missing a driver?

the iwconfig eth2 output shows that you are connected to the right access point 00:22:57:1F:E9:CF which is the Nexus MAC address see your scan output Cell2.

However you have put encryption back 'on' on the nexus router and we haven't got there yet.

If you reset the encryption to open, then try in a browser to open http://192.168.1.1 you should wirelessly connect to the router admin / password page. we'll progress from there if you are successful. Incidentally, there is tons of traffic going through eth2 1.6MB received and 108.8KB transmitted according to the output of sudo ifconfig -a

Wait
From his post:
Cell 02 - Address: 00:22:57:1F:E9:CF
ESSID:"Nexus"
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:5/5 Signal level:-30 dBm Noise level:-92 dBm
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Preauthentication Supported
IE: Unknown: bla bla
Encryption keyn
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 12 Mb/s
24 Mb/s; 48 Mb/s

ESSID:"Nexus" has encryption, and card associated with it.

IEEE 802.11bg ESSID:"Nexus" Nickname:""
Mode:Managed Frequency:2.462 GHz Access Point: 00:22:57:1F:E9:CF

And he has IP, inet addr:192.168.1.3

eth2 Link encap:Ethernet HWaddr 00:22:5f:06:e9:7b
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0



He need to show us output for: "route -n"

I couldn't connect to http://192.168.1.1 from my machine so I had to use my windows desktop to disable Nexus' encryption protocols. Once completed, I tried to connect to http://192.168.1.1 from my laptop and was unable to do so. Tried to do it wired and wirelessly. Same result.

http://pastebin.com/m372b870c

I take it I'm not missing a driver, right?

sudo route -n does not produce any output. Since disabling my router's encryption protocols I am unable to connect to Nexus. Oddly enough, the system requests my WPA2 password but I disabled that.

Screenshot: http://yfrog.com/5hdisabledprotocolsj

What nimnull22 said

Please post the output of:

route -n

it should look like this:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth2

If 192.168.1.1 isn't the address of the Nexus router do you know what is? How do you connect to it in Windows?

Being physically connected to the modem, I ran route -n once again.

Result: http://pastebin.com/m27a8613d

I did use http://192.168.1.1 to connect to my router from my Windows machine.