Re: kern/45505 (iwi0 does not come up correctly)

[Riccardo Mottola <rm%gnu.org@localhost>]

The following reply was made to PR kern/45505; it has been noted by GNATS.

From: Riccardo Mottola <rm%gnu.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: David Holland <dholland-bugs%netbsd.org@localhost>, 
kern-bug-people%netbsd.org@localhost, 
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/45505 (iwi0 does not come up correctly)
Date: Sun, 22 Jan 2012 19:48:08 +0100

 Hi,
 
 I can confirm that nuking it explicitely in the script, that is by 
 having it do:
 
 route delete default
 route delete 192.168.1.0
 ifconfig bge0 down
 
 gets wireless working.
 
 Riccardo
 
 On 01/22/12 17:30, David Holland wrote:
 > The following reply was made to PR kern/45505; it has been noted by GNATS.
 >
 > From: David Holland<dholland-bugs%netbsd.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: kern/45505 (iwi0 does not come up correctly)
 > Date: Sun, 22 Jan 2012 16:29:54 +0000
 >
 >   On Mon, Dec 12, 2011 at 03:10:06PM +0000, Riccardo Mottola wrote:
 >    >   >    So, let me make sure I understand... you were using bge0 on
 >    >   >    192.168.1/24 and disconnected it, then brought up iwi0 also on
 >    >   >    192.168.1/24, but the above route was still present and 
 > therefore all
 >    >   >    traffic got sent to bge0?
 >    >   >
 >    >   >    When you disconnected bge0 did you do "ifconfig down" on it?
 >    >
 >    >   Almost. I do power up the computer with a statically configured bge0,
 >    >   but I never connect a cable to it. I do explicitely "down" it though. 
 > I
 >    >   run the following script:
 >    >
 >    >   #!/bin/sh
 >    >   ifconfig bge0 down
 >    >   route delete default
 >    >   ifconfig iwi0 ssid XXXXXXX
 >    >   ifconfig iwi0 nwkey 0xXXXXXXX
 >    >   dhclient iwi0
 >
 >   AIUI downing the interface should remove its link-level route. If this
 >   is not happening, it should be easy to confirm, and it should be
 >   possible to work around the problem by nuking the route explicitly in
 >   that script.
 >
 >   As to why it might not be happening... probably someone who knows more
 >   about the network code needs to investigate.
 >
 >   --
 >   David A. Holland
 >   dholland%netbsd.org@localhost
 >
 
 
 -- 
 ---
 GNUstep maintainer and Application developer