Re: Problems with iwi0

[Riccardo Mottola <riccardo.mottola%libero.it@localhost>]

Hi David,

On 10/06/11 18:47, David Young wrote:
> On Thu, Oct 06, 2011 at 09:34:33AM +0200, Riccardo Mottola wrote:
> > I have troubles with iwi0, even now that I updated yo the current kernel.
> >
> > I run the following
> >
> > #!/bin/sh
> > ifconfig bge0 down
> > route delete default
> > ifconfig iwi0 ssid xxxxxxxx
> > ifconfig iwi0 nwkey 0xYYYYYYYYY
> > dhclient iwi0
> >
> >
> > dhclient is capable of receiving a correct IP, the default route
> > seem scorrect but the interface remains "down" and trying to ping
> > both a LAN or an internet hosts says "network is down".
> When you say that the interface remains down, what do you mean? dhclient
> should bring it up before it does anything else.  Send some ifconfig
> output, please.

After running the above script, "ifconfig iwi0" says:
iwi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        ssid xxxxxxxx nwkey 0xXXXXXXXX
        powersave off
        bssid 94:0c:6d:f7:a4:9c chan 6
        address: 00:15:00:38:b1:9e
        media: IEEE802.11 autoselect
        status: active
        inet 192.168.1.156 netmask 0xffffff00 broadcast 255.255.255.255
        inet6 fe80::215:ff:fe38:b19e%iwi0 prefixlen 64 scopeid 0x1

netstat -r


Destination        Gateway            Flags    Refs      Use    Mtu 
Interface
default            192.168.1.254      UGS         0        0      -  iwi0
127/8              localhost          UGRS        0        0  33192  lo0
localhost          localhost          UH          2        0  33192  lo0
192.168.1/24       link#3             UC          1        0      -  bge0
192.168.1.156      localhost          UGHS        0        0  33192  lo0
192.168.1.254      00:30:0a:0b:75:7e  UHLc        1       36      -  bge0


which looks reasomable too, the default is correct.

grid$ ping www.netbsd.org
ping: Cannot resolve "www.netbsd.org" (Host name lookup failure)
grid$ ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254): 52 data bytes
ping: sendto: Network is down
ping: sendto: Network is down

As said, the absurd is that on another network, same essid/key, same 
script... it works!

Riccardo