LinuxQuestions.org - microsoft MN-520 and novell desktop linux

- Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)

- - microsoft MN-520 and novell desktop linux (https://www.linuxquestions.org/questions/linux-wireless-networking-41/microsoft-mn-520-and-novell-desktop-linux-315458/)

microsoft MN-520 and novell desktop linux

I'm trying to get this card to work on a ibm thinkpad t22
Linux seems to recognize the card as a MN-520 when I do a cardctl ident. I added the card Microsoft
version Microsoft
bind orinoco_cs to pcmcia/config.opts.
In YAST I set default gateway to 192.168.1.1 and the proper nameservers in resolv.conf
When I do ifdown wlan0 and then a ifup wlan0 it says "Starting DHCP client on wlan0........no ip address yet..... backgrounding

any help would be appreciated
David

so does it not work? can you post the output of lspci? have you downloaded wireless-tools? is there an iwconfig command availble in console

The output of lspci is long, and I'm on another computer. What am I looking for?
I have wireless tools installed and iwconfig says
wlan0 IEEE 802.11-Ds ESSID:"wireless" Nickname;"wireless
mode:managed Frequency;2.437 GHz Access Point: 00:0c:41:1F::F7:88
Bit rate:2Mb/s Tx-power;2346 dbm
....

wait ten minutes and run ifconfig. doe sthe interface recieve an interface?

ifconfig gives me this
wlan0 Link encap:Ethernet HWaddr 00:50:F2:C1:EA:C4
inet6 addr: fe80::250:f2ff:fec1:eac4/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:62 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9874 (9.6 Kb) TX bytes:7856 (7.6 Kb)
Interrupt:3 Base address:0x100
I'm also using the built in ethernet card and it started working right away

I make sure the dhcp server is workign correctly

I'm pretty sure it is, It assigned an ip address for eth0, as an aside I put in an ibm wireless adaptor and it was recognised by ifconfig as eth1.It also uses the orinoco driver.

I did a ifdown eth0 and
ifup eth1 and it was assigned an ip address

can you manually assign an ip to the wireless card and get it to work?

moe:/home/david # ifconfig wlan0 192.168.1.104 netmask 255.255.255.0
moe:/home/david # ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:62 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4012 (3.9 Kb) TX bytes:4012 (3.9 Kb)

wlan0 Link encap:Ethernet HWaddr 00:50:F2:C1:EA:C4
inet addr:192.168.1.104 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::250:f2ff:fec1:eac4/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4241 (4.1 Kb) TX bytes:4432 (4.3 Kb)
Interrupt:3 Base address:0x100

moe:/home/david # route add default gw 192.168.1.1
moe:/home/david # ping 234.12.134.2
PING 234.12.134.2 (234.12.134.2) 56(84) bytes of data.

--- 234.12.134.2 ping statistics ---
16 packets transmitted, 0 received, 100% packet loss, time 15012ms

I can add an address manually, but it still can't seem to get anywhere

and if you ping the gateway 192.168.1.1?

moe:/home/david # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.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
moe:/home/david # ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.104: icmp_seq=2 Destination Host Unreachable
From 192.168.1.104 icmp_seq=2 Destination Host Unreachable
From 192.168.1.104 icmp_seq=3 Destination Host Unreachable

Sorry I keep having to switch between eth0 and wlan0

Are you sure you're using the correct driver for your card. It doesn't seem to be working. I realize this may seem a little odd to you, but you don't suppose this might me a deliberate microsfot obstruction of functionality?

Assign yourself a manual IP and then do:
route add default gw 192.168.1.1

This works for me.

If you check the output in post #9, I assigned it an ip address and did the route add default gw. It still couldn't ping the gateway.

I finally gave up trying today and installed Fedora Core 3. The card was instantly recognised and configured. I can't understand how two different distros, with essentially the same 2.6 kernels have completely different results.
Thanks to all that helped, it was a learning experience