Re: Trouble getting bcm43xx driver to work
The extra line you have is the route for all traffic NOT on the local network
and so it should not change ping-ing the router on the same network.
Just to be sure I have added a default route (to my AP/router) the same as
your settings. Alas, this does not seem to have made any difference.
At first I suspected that I had missed something basic but now I fear that
have found a more difficlut to find problem. If someone doesn't point out
where I have stuffed up I will resort to systematic trail-and-error with all
settings (wireless channel, essid, etc.) just in case there is an obscure bug
I can identify.
Thanks for your help,
Aaron
On Tuesday 03 January 2006 18:27, Bin Zhang wrote:
> On 1/3/06, Aaron <aaron@sun.com> wrote:
> > I am close to having the bcm43xx driver working but I am now stuck and
> > could really do with some pointers.
> >
> > THE SHORT VERSION:
> > 1. I have successfully built and installed bcm43xx, ieee80211softmac and
> > bcm43xx-fwcutter (one error extracting firmware file
> > bcm43xx_microcode11.fw). These are the latest daily snapshots (20060102)
> >
> > 2. I can manually "ifconfig ethX up" the wireless interface and see my
> > very open wireless network with "iwlist ethX scan".
> >
> > 3. SoftMac seems to associate (from dmesg output).
> >
> > 4. dhclient ethX fails to get an IP address but I can manually set an IP
> > address (in the correct range) with ifconfig.
> >
> > 5. I can not ping my wireless AP/router. Ping returns "Destination Host
> > Unreachable" even though my route table looks OK:
> > "Kernel IP routing table
> > Destination Gateway Genmask Flags MSS Window irtt
> > Iface 192.168.73.0 * 255.255.255.0 U 0 0
> > 0 eth2"
>
> It seems to me that you have a problem with your network configuration.
> (because you use ip static)
>
> I have
> ----------------
> # route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface 192.168.0.0 * 255.255.255.0 U 0 0
> 0 sta0 default 192.168.0.1 0.0.0.0 UG 0 0
> 0 sta0 ----------------
> (192.168.0.1 = ip_of_my_router)
>
> Also check your /etc/resolv.conf
>
> If you use the package resolvconf, you can add two lines
> in your /etc/network/interfaces:
> ---------
> dns-search tele2.fr <---my isp
> dns-nameservers 192.168.0.1 <---ip_of_my_router
>
> Regards,
> Bin
>
> > Does anyone have any ideas, pointers or RTFMs??
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-powerpc-REQUEST@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> > listmaster@lists.debian.org
Reply to: