wlan config problem

Dell Inspiron 9100 with a 1450 wireless card (broadcom chip). Configured the
card successfully with ndiswrapper under shrike. I can ping my win and linux
servers on the lan, but no internet. Fruitless efforts at DNS, and here I
am. Where is the magic config setting that I'm missing? Thanks in advance .
.. .

A bunch of stuff I've tried (sorry for the length, but you'd probably ask
for this output anyway):

[root@localhost root]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
wlan0

Sidebar: why 3 entries for wlan0? And where's the 192.168.1.0 coming from?

/etc/sysconfig/ifcfg-wlan0 (constructed myself from examples)



DEVICE=wlan0
BOOTPROTO=static
ONBOOT=yes
IPADDR=192.168.1.157
NETMASK=255.255.255.0
GATEWAY=192.168.1.1
BROADCAST=192.168.1.255
MTU=1454
WIRELESS_MODE=Managed
WIRELESS_ESSID=myESSID
WIRELESS_ENC_KEY=10DigitKey

Previous attempt at scripting automatic config into rc.local

iwconfig wlan0 mode Managed
iwconfig wlan0 essid myESSID
iwconfig wlan0 key restricted 10DigitKey
ifconfig wlan0 192.168.1.157
ifconfig wlan0 netmask 255.255.255.0
ifconfig wlan0 up


Sidebar: ESSID is reset if I ifdown the wlan0?

[root@localhost root]# iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11g ESSIDff/any
Mode:Managed Frequency:2.417GHz Access Point: 00:00:00:00:00:00
Bit Rate:11Mb/s Tx-Power:84 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption keyff
Power Managementff
Link Quality:100/100 Signal level:-89 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:6 Invalid misc:148 Missed beacon:0


[root@localhost root]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:140 (140.0 b) TX bytes:140 (140.0 b)

wlan0 Link encap:Ethernet HWaddr 00:90:96:F0:E2:F4
inet addr:192.168.1.157 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1454 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3387 (3.3 Kb) TX bytes:168 (168.0 b)
Interrupt:11 Memory:faff6000-faff7fff



/etc/resolv.conf

search 192.168.1.1

On 2004-10-07, D <(E-Mail Removed)> wrote:
> [root@localhost root]# netstat -rn
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> wlan0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> wlan0

?? 169.254.x.x ? This is usually done in Windows when a nic can't get
a correct ip address. Check better.

> Sidebar: why 3 entries for wlan0? And where's the 192.168.1.0 coming from?

192.168.1.0 means 'your local network'. It's the 169.254 that shouldn't be
there at all.

> /etc/resolv.conf
> search 192.168.1.1

?? What's this ? You didn't get the DNS correctly from the dhcp
server or you didn't configured it.

Davide

--
Windows contains FAT.
Use Linux -- you won't ever have to worry about your weight.

-- Ewout Stam

Thanks for the reply.

I'm using static IP's. I'm obviously not a linux networking expert, I just
want this darn card to access the net. Can anyone point me to how to
properly configure the DNS for this to work

I've tried setting the Gateway to my router's WAN address, as suggested in
an online article, but didn't work.

And, yes, how is a card in a linux machine getting a Windows default IP like
169.254.x.x? Is this due to ndiswrapper using the win driver?

D


"Davide Bianchi" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) .net...
> On 2004-10-07, D <(E-Mail Removed)> wrote:
>> [root@localhost root]# netstat -rn
>> Kernel IP routing table
>> Destination Gateway Genmask Flags MSS Window irtt
>> Iface
>> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
>> wlan0
>> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
>> wlan0
>
> ?? 169.254.x.x ? This is usually done in Windows when a nic can't get
> a correct ip address. Check better.
>
>> Sidebar: why 3 entries for wlan0? And where's the 192.168.1.0 coming
>> from?
>
> 192.168.1.0 means 'your local network'. It's the 169.254 that shouldn't be
> there at all.
>
>> /etc/resolv.conf
>> search 192.168.1.1
>
> ?? What's this ? You didn't get the DNS correctly from the dhcp
> server or you didn't configured it.
>
> Davide
>
> --
> Windows contains FAT.
> Use Linux -- you won't ever have to worry about your weight.
>
> -- Ewout Stam

On 2004-10-08, D <(E-Mail Removed)> wrote:
> I'm using static IP's.

Then the '169' thingy should _not_ be there. At all.

> want this darn card to access the net. Can anyone point me to how to
> properly configure the DNS for this to work

Basically the /etc/resolv.conf should contains:

nameserver <theipofyourprimarydnshere>
nameserver <theipofyourotherdnshere>
nameserver <theipofyourotherdnshere>
....

At least ONE 'nameserver' entry must be there.

You need to set the gateway to the IP of the machine/router that
give you connection outside in your LOCAL network. The meaning of
'gateway' is "all the packets that you don't know where to send,
send them to this IP". Of course he has to _know_ how to send to the
gateway _first_. So you need at least two entries in the routing table:
one for your local network (and you have that one) and one for the
gateway (that is usually in your local network).

> And, yes, how is a card in a linux machine getting a Windows default IP like
> 169.254.x.x? Is this due to ndiswrapper using the win driver?

Could be. I've never used ndiswrapper in my life so don't ask me...

Davide

--
I'm locked in a maze of little projects, all of which suck.
-- Chris "Saundo" Saunderson on alt.sysadmin.recovery

In article <Qtp9d.40525$223.9967@edtnps89>, D wrote:
>And, yes, how is a card in a linux machine getting a Windows default IP like
>169.254.x.x? Is this due to ndiswrapper using the win driver?

Looking at your ifconfig output, you are not actually getting an
IP address - you are only getting a route to that network.

It's a "feature" that Red Hat decided you couldn't live without,
If you look in /etc/sysconfig/network-scripts/ifup you'll find:

# Add Zeroconf route.
if [ -z "${NOZEROCONF}" -a "${ISALIAS}" = "no" ]; then
ip route replace 169.254.0.0/16 dev ${REALDEVICE}
fi

So if you set NOZEROCONF=yes in the /etc/sysconfig/network configuration
file, this "feature" will be disabled. This "feature" is called Zero-conf
or link-local, so you might look through the documentation for those words,
and see if RH says anything. It would not surprise me if they didn't.

Old guy

thanks for solving the 169 IP mystery. it's working now, except for a few
minor details (like why it's still listing the 169 IP).

kudos to the ndiswrapper group for letting us use new wireless devices until
linux drivers are available.

D

"Moe Trin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed).. .
> In article <Qtp9d.40525$223.9967@edtnps89>, D wrote:
> >And, yes, how is a card in a linux machine getting a Windows default IP
like
> >169.254.x.x? Is this due to ndiswrapper using the win driver?
>
> Looking at your ifconfig output, you are not actually getting an
> IP address - you are only getting a route to that network.
>
> It's a "feature" that Red Hat decided you couldn't live without,
> If you look in /etc/sysconfig/network-scripts/ifup you'll find:
>
> # Add Zeroconf route.
> if [ -z "${NOZEROCONF}" -a "${ISALIAS}" = "no" ]; then
> ip route replace 169.254.0.0/16 dev ${REALDEVICE}
> fi
>
> So if you set NOZEROCONF=yes in the /etc/sysconfig/network configuration
> file, this "feature" will be disabled. This "feature" is called Zero-conf
> or link-local, so you might look through the documentation for those
words,
> and see if RH says anything. It would not surprise me if they didn't.
>
> Old guy
>