Arch Linux

Reploid

Member

From: Cold Country up North

Registered: 2008-03-27

Posts: 110

Mysterious Network Problem :/

I have a network problem that puzzles me.

I can only surf the web using my wired connection to my router.
The wireless (intel 3945) option doesn't associate with the access point.
It doesn't work from the ubuntu live CD either.
It does, however work from my Palm TX!!

This would suggest that there is something wrong with my wireless hardware - BUT - I can search other networks with airodump-ng and I could crack the wep code of my neighbor...

And still, I can't surf the web on my neighbors net, nor on my own, using wireless.
Neither using Network Manager, nor using Wicd.

This is so strange. Any Sherlock Holmes-es out there who can offer assistance?

amranu

Member

Registered: 2008-09-25

Posts: 94

Re: Mysterious Network Problem :/

pacman -S iwlwifi-3945-ucode

?

Reploid

Member

From: Cold Country up North

Registered: 2008-03-27

Posts: 110

Re: Mysterious Network Problem :/

No, I have the iwlwifi, newest version.

The rc.conf, comments removed.

MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(tg3 iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore acpi-cpufreq cpufreq_conservative fuse loop)

HOSTNAME="archcomputer"

wlan0="dhcp"
eth0="dhcp"
INTERFACES=(!wlan0 !eth0)

gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

DAEMONS=(syslog-ng @fam hal @alsa !netfs crond !dhcdbd !network !networkmanager wicd @cpufreq)

Any other ideas?

amranu

Member

Registered: 2008-09-25

Posts: 94

Re: Mysterious Network Problem :/

Have no idea why you're telling your interfaces to use dhcp in that when they're not being handled by the network daemon, but whatever. But yeah, don't think the problem is there.

mutlu_inek

Member

From: all over the place

Registered: 2006-11-18

Posts: 684

Re: Mysterious Network Problem :/

Hmm... rc.conf looks fine.

What I don't quite understand is what exactly happens. Do wicd and nm associate with the ap? Do you get an ip? Or does the association fail?

If you don't get an ip for some reason, you could try to add

interface "eth0" {
        send dhcp-client-identifier <PUT YOUR MAC ADDRESS HERE>;
}

to /etc/dhclient.conf

Also, you could have a look at the logs and run nm and wicd from console to see what's going on.

ralvez

Member

From: Canada

Registered: 2005-12-06

Posts: 1,718

Website

Re: Mysterious Network Problem :/

Well if what I read in your post is what you actually have in your /etc/rc.conf I'm sure it will never work.
you have

wlan0="dhcp"
eth0="dhcp"
INTERFACES=(!wlan0 !eth0)

... the "!" before an interface name means NOT or disabled. So in actual fact you are indicating not to use neither eth0 nor wlan0.

If you intend to use your wireless you must un-comment wlan0

Hope this helps.

R.

mutlu_inek

Member

From: all over the place

Registered: 2006-11-18

Posts: 684

Re: Mysterious Network Problem :/

Well if what I read in your post is what you actually have in your /etc/rc.conf I'm sure it will never work. [...] If you intend to use your wireless you must un-comment wlan0

Nope. It is correct if he is using Wicd. Networkmanager is nearly the same, only "lo" must be enabled and the "dhcp" lines need to be commented out. It's look like this:

lo="lo 127.0.0.1"
#wlan0="dhcp"
#eth0="dhcp"
INTERFACES=(lo !wlan0 !eth0)

Edit: This did make me wonder now, though: why is the device called "wlan0"? iwl3945 moved from that to "eth0" ages ago. Maybe this is the mistake?

Last edited by mutlu_inek (2008-11-30 03:34:35)

Reploid

Member

From: Cold Country up North

Registered: 2008-03-27

Posts: 110

Re: Mysterious Network Problem :/

Ok, late reply. Time Zone diff zzz zzz.

I start my PC with the wired connection (working) and type dmesg to see the output fresh after restart.
Then I type dmesg after I have unplugged the cable, and made an attempt to connect to my net in wicd.
link to whole dmesg, the unplugged situation at the bottom: http://pastebin.com/m3c52f9c8

This is what I get:

tg3: eth0: Link is down.
iwl3945 0000:03:00.0: PCI INT A disabled
iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
iwl3945 0000:03:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106)
Registered led device: iwl-phy0:radio
Registered led device: iwl-phy0:assoc
Registered led device: iwl-phy0:RX
Registered led device: iwl-phy0:TX
wlan0: authenticate with AP 00:13:46:5c:08:91
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: authenticated
wlan0: associate with AP 00:13:46:5c:08:91
wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
wlan0: authenticate with AP 00:13:46:5c:08:91
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: authenticated
wlan0: associate with AP 00:13:46:5c:08:91
wlan0: mismatch in privacy configuration and mixed-cell disabled - abort association
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate
wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate

My wireless connection has been called wlan0 forever, that hasn't changed, not before, not after the iwl, and I can't recall having made any changes to the wireless conf in ages, although I have been messing around with aircrack.

Last edited by Reploid (2008-11-30 08:35:56)

Painless

Member

Registered: 2006-02-06

Posts: 234

Re: Mysterious Network Problem :/

I posted a reply to another post.

Try using:

QUIRKS=(preessid)

in your netcfg profile.  This worked for me.