Hi All,

I'm trying to move to kernel 2.6.24 and the new iwl3945 drivers. I've
uninstalled the old ipw3945 modules and daemons, and followed all the
steps described here http://wiki.debian.org/iwlwifi, but I still can't
connect to my router. The errors I see are:

Apr 1 19:11:56 nibbler dhclient: wmaster0: unknown hardware address
type 801
Apr 1 19:11:56 nibbler dhclient: Listening on
LPF/wlan0/00:18:de:11:ec:08
Apr 1 19:11:56 nibbler dhclient: Sending on
LPF/wlan0/00:18:de:11:ec:08
Apr 1 19:11:56 nibbler dhclient: Sending on Socket/fallback
Apr 1 19:11:56 nibbler dhclient: receive_packet failed on wlan0:
Network is down

ifconfig shows the proper devices:

wlan0 Link encap:Ethernet HWaddr 00:18:de:11:ec:08
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)

wmaster0 Link encap:UNSPEC HWaddr
00-18-DE-11-EC-08-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)

my /etc/udev/rules.d/z25_persistent-net.rules contains:

# PCI device 10ec:8169 (r8169)
SUBSYSTEM=="net", DRIVERS=="?*", SYSFS{address}=="00:17:31:b5:2e:c8",
NAME="eth0"

# FireWire host adapter 00e01800035a8648 (/class/net/eth1)
SUBSYSTEM=="net", DRIVERS=="?*",
SYSFS{address}=="00:e0:18:00:03:5a:86:48", NAME="eth1"

# PCI device 0x8086:0x4222 (iwl3945)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:18:de:11:ec:08",
ATTR{type}=="1", NAME="wlan0"

And /etc/network/interfaces has:

iface wlan0 inet dhcp
pre-up ip link set wlan0 up
wireless_essid mynetwork

iface eth0 inet dhcp

iface lo inet loopback

auto lo


Is there some other configuration I'm missing? Thanks in advance,
David



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, Apr 01, 2008 at 07:30:26PM -0700, David Jantzen wrote:
> Hi All,
>
> I'm trying to move to kernel 2.6.24 and the new iwl3945 drivers. I've
> uninstalled the old ipw3945 modules and daemons, and followed all the
> steps described here http://wiki.debian.org/iwlwifi, but I still can't
> connect to my router. The errors I see are:
>
> Apr 1 19:11:56 nibbler dhclient: wmaster0: unknown hardware address
> type 801

I see this error too, I think it can be ignored.

> Apr 1 19:11:56 nibbler dhclient: Listening on
> LPF/wlan0/00:18:de:11:ec:08
> Apr 1 19:11:56 nibbler dhclient: Sending on
> LPF/wlan0/00:18:de:11:ec:08
> Apr 1 19:11:56 nibbler dhclient: Sending on Socket/fallback
> Apr 1 19:11:56 nibbler dhclient: receive_packet failed on wlan0:
> Network is down
>
> ifconfig shows the proper devices:
>
> wlan0 Link encap:Ethernet HWaddr 00:18:de:11:ec:08
> 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)
>
> wmaster0 Link encap:UNSPEC HWaddr
> 00-18-DE-11-EC-08-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)

clearly the interface is up. What does iwconfig wlan0 show?

My experience in this transition is that the order things need to be
done has changed. I do all my stuff with custom scripts, so I can't
speak to how the more automated systems handle it, but for example, I
can't change the mode unless the interface is down...

>
> my /etc/udev/rules.d/z25_persistent-net.rules contains:
>
> # PCI device 10ec:8169 (r8169)
> SUBSYSTEM=="net", DRIVERS=="?*", SYSFS{address}=="00:17:31:b5:2e:c8",
> NAME="eth0"
>
> # FireWire host adapter 00e01800035a8648 (/class/net/eth1)
> SUBSYSTEM=="net", DRIVERS=="?*",
> SYSFS{address}=="00:e0:18:00:03:5a:86:48", NAME="eth1"
>
> # PCI device 0x8086:0x4222 (iwl3945)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:18:de:11:ec:08",
> ATTR{type}=="1", NAME="wlan0"
>
> And /etc/network/interfaces has:
>
> iface wlan0 inet dhcp
> pre-up ip link set wlan0 up
> wireless_essid mynetwork

what other parts of the wireless config need to get set? mode, channel
key etc?

you may have to pull some of that out and put it in a script to call
from /etc/network/interfaces to get it working until the transistion
is fully completed (maybe it already is? doesn't quite seem to be to
me).

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH8vkiaIeIEqwil4YRAiWjAJ9go0i0qGUU+U3g0ltKAx OnGV5XgACgsrfA
ibswMohhiNxPP5xENLERZQI=
=lwuN
-----END PGP SIGNATURE-----

Thanks for the Andrew. I ran iwconfig wlan0 and see:

wlan0 IEEE 802.11g ESSID:"dorkyduck"
Mode:Managed Frequency:2.412 GHz Access Point:
Not-Associated
Tx-Power=17 dBm
Retry min limit:7 RTS thrff Fragment thr=2346 B
Encryption key3BB-B904-C560-09B3-D9A8-C961-3F
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

This is after manually setting the essid and WEP key. I'm able to scan
for networks and see mine, however it won't associate to the access
point. What else would need to be set?

Thanks,
David

On Tue, 2008-04-01 at 20:10 -0700, Andrew Sackville-West wrote:
> On Tue, Apr 01, 2008 at 07:30:26PM -0700, David Jantzen wrote:
> > Hi All,
> >
> > I'm trying to move to kernel 2.6.24 and the new iwl3945 drivers. I've
> > uninstalled the old ipw3945 modules and daemons, and followed all the
> > steps described here http://wiki.debian.org/iwlwifi, but I still can't
> > connect to my router. The errors I see are:
> >
> > Apr 1 19:11:56 nibbler dhclient: wmaster0: unknown hardware address
> > type 801
>
> I see this error too, I think it can be ignored.
>
> > Apr 1 19:11:56 nibbler dhclient: Listening on
> > LPF/wlan0/00:18:de:11:ec:08
> > Apr 1 19:11:56 nibbler dhclient: Sending on
> > LPF/wlan0/00:18:de:11:ec:08
> > Apr 1 19:11:56 nibbler dhclient: Sending on Socket/fallback
> > Apr 1 19:11:56 nibbler dhclient: receive_packet failed on wlan0:
> > Network is down
> >
> > ifconfig shows the proper devices:
> >
> > wlan0 Link encap:Ethernet HWaddr 00:18:de:11:ec:08
> > 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)
> >
> > wmaster0 Link encap:UNSPEC HWaddr
> > 00-18-DE-11-EC-08-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)
>
> clearly the interface is up. What does iwconfig wlan0 show?
>
> My experience in this transition is that the order things need to be
> done has changed. I do all my stuff with custom scripts, so I can't
> speak to how the more automated systems handle it, but for example, I
> can't change the mode unless the interface is down...
>
> >
> > my /etc/udev/rules.d/z25_persistent-net.rules contains:
> >
> > # PCI device 10ec:8169 (r8169)
> > SUBSYSTEM=="net", DRIVERS=="?*", SYSFS{address}=="00:17:31:b5:2e:c8",
> > NAME="eth0"
> >
> > # FireWire host adapter 00e01800035a8648 (/class/net/eth1)
> > SUBSYSTEM=="net", DRIVERS=="?*",
> > SYSFS{address}=="00:e0:18:00:03:5a:86:48", NAME="eth1"
> >
> > # PCI device 0x8086:0x4222 (iwl3945)
> > SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:18:de:11:ec:08",
> > ATTR{type}=="1", NAME="wlan0"
> >
> > And /etc/network/interfaces has:
> >
> > iface wlan0 inet dhcp
> > pre-up ip link set wlan0 up
> > wireless_essid mynetwork
>
> what other parts of the wireless config need to get set? mode, channel
> key etc?
>
> you may have to pull some of that out and put it in a script to call
> from /etc/network/interfaces to get it working until the transistion
> is fully completed (maybe it already is? doesn't quite seem to be to
> me).
>
> A


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, Apr 02, 2008 at 10:34:06AM -0700, David Jantzen wrote:
> Thanks for the Andrew. I ran iwconfig wlan0 and see:
>
> wlan0 IEEE 802.11g ESSID:"dorkyduck"
> Mode:Managed Frequency:2.412 GHz Access Point:
> Not-Associated
> Tx-Power=17 dBm
> Retry min limit:7 RTS thrff Fragment thr=2346 B
> Encryption key3BB-B904-C560-09B3-D9A8-C961-3F
> 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
>
> This is after manually setting the essid and WEP key. I'm able to scan
> for networks and see mine, however it won't associate to the access
> point. What else would need to be set?

have you tried

iwconfig wlan0 ap any

or manually specifying the ap? see man iwconfig

A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH9BUPaIeIEqwil4YRAlZGAJ9yPusHEru5Ac1CikqvsE 94fTaAewCgxoXA
5l0b0O5QvP8mbAFgPVrbVW4=
=ew7J
-----END PGP SIGNATURE-----

Aha, that worked. Thanks Andrew! Now I just have to make my manual
configuration play nice with the gnome network monitor. Probably worth
adding this pointer to the Debian wiki page on iwl3945.

On Wed, 2008-04-02 at 16:21 -0700, Andrew Sackville-West wrote:
> On Wed, Apr 02, 2008 at 10:34:06AM -0700, David Jantzen wrote:
> > Thanks for the Andrew. I ran iwconfig wlan0 and see:
> >
> > wlan0 IEEE 802.11g ESSID:"dorkyduck"
> > Mode:Managed Frequency:2.412 GHz Access Point:
> > Not-Associated
> > Tx-Power=17 dBm
> > Retry min limit:7 RTS thrff Fragment thr=2346 B
> > Encryption key3BB-B904-C560-09B3-D9A8-C961-3F
> > 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
> >
> > This is after manually setting the essid and WEP key. I'm able to scan
> > for networks and see mine, however it won't associate to the access
> > point. What else would need to be set?
>
> have you tried
>
> iwconfig wlan0 ap any
>
> or manually specifying the ap? see man iwconfig
>
> A


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org