LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 02-16-2004, 08:50 AM   #1
njs12345
LQ Newbie
 
Registered: Feb 2004
Distribution: LFS 5.0
Posts: 14

Rep: Reputation: 0
Networking Linux and Windows - Ping doesn't work


I'm a bit of a newbie to networking under linux(and I'm not that great under windows either ) but I'd like to set up my wireless LAN.

I have a proxy server on my host computer, running Windows XP. When I set up my LAN using iwconfig, I can get the little "Connected" icon in the system tray on the host, but ping doesn't work from either computer.

Host IP - 192.168.0.1
Client IP - 192.168.0.2

iwconfig output on Linux:
Code:
eth1      IEEE 802.11-DS  ESSID:"linux"  
          Mode:Ad-Hoc  Frequency:2.412GHz  Cell: 1A:02:51:01:4F:01  
          Bit Rate:11Mb/s   Tx-Power=17 dBm   Sensitivity=0/0  
          Retry limit:16   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:10  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:89  Invalid misc:755   Missed beacon:0

wifi0     IEEE 802.11-DS  ESSID:"linux"  
          Mode:Ad-Hoc  Frequency:2.412GHz  Cell: 1A:02:51:01:4F:01  
          Bit Rate:11Mb/s   Tx-Power=17 dBm   Sensitivity=0/0  
          Retry limit:16   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:10  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:89  Invalid misc:755   Missed beacon:0
ifconfig -a output:
Code:
eth0      Link encap:Ethernet  HWaddr 00:0D:61:B2:2A:EA  
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:1620 (1.5 Kb)
          Interrupt:17 Base address:0x7e00 

eth1      Link encap:Ethernet  HWaddr 00:0C:30:B0:67:27  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:62 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:18995 (18.5 Kb)  TX bytes:0 (0.0 b)
          Interrupt:18 Base address:0xd800 

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:44 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4300 (4.1 Kb)  TX bytes:4300 (4.1 Kb)

wifi0     Link encap:UNSPEC  HWaddr 00-0C-30-B0-67-27-00-00-00-00-00-00-00-00-00-00  
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:2312  Metric:1
          RX packets:62 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:18995 (18.5 Kb)  TX bytes:0 (0.0 b)
          Interrupt:18 Base address:0xd800
ipconfig under windows output:
Code:

Windows IP Configuration





Ethernet adapter Wireless Network Connection:



        Connection-specific DNS Suffix  . : 

        IP Address. . . . . . . . . . . . : 192.168.0.1

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 

(internet connection below)
I don't think the problem is with the actual wireless cards themselves... but I'm using two Cisco Aironet 350 wireless cards in Ad-Hoc mode.
 
Old 02-16-2004, 05:47 PM   #2
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 65
All of the packets going to the linux box are coming up invalid misc:

Invalid misc:755

Which is bloody weird. Do the Cell's match on either side? Is WEP turned on at all?

Cheers,

Finegan
 
Old 02-17-2004, 03:01 AM   #3
njs12345
LQ Newbie
 
Registered: Feb 2004
Distribution: LFS 5.0
Posts: 14

Original Poster
Rep: Reputation: 0
What do you mean by a cell? I can't seem to find that anyware in the Wireless Settings box.. how could I find that out under Windows?

WEP is totally off. I'll work on getting it secure when I've got it working.

EDIT: I've taken two screenshots of what the Cisco driver statistics & status look like under Windows: (status) (statistics)

Last edited by njs12345; 02-17-2004 at 05:11 PM.
 
Old 02-18-2004, 02:48 PM   #4
njs12345
LQ Newbie
 
Registered: Feb 2004
Distribution: LFS 5.0
Posts: 14

Original Poster
Rep: Reputation: 0
bump.. anyone have any idea how to fix this problem?
 
Old 02-19-2004, 10:17 AM   #5
njs12345
LQ Newbie
 
Registered: Feb 2004
Distribution: LFS 5.0
Posts: 14

Original Poster
Rep: Reputation: 0
W00T!!!

I got it working.. I used the Cisco official drivers instead of the other ones

Posting this using Konqueror right now
 
Old 02-20-2004, 04:29 PM   #6
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 65
Ohhh,

Yeah sorry I didn't reply earlier, no inet access followed by a 3 day interview cramb session. Yeah, to explain some things as penance:

IBSS mode, or ad-hoc mode, the card takes its settings and scans accross the channel its given to see if there's already a cell with matching settings, essid, channel, wep, etc... if not, it creates and IBSS infrastructure network and creates its own cell. In a managed/Master network you'll see the MAC of the AP's hardware instead of a cell MAC address that as far as I know is just made up on the spot. Getting another ad-hoc pier to associate with a cell is a little more cumbersome then good old managed and its beacon frames, but by default more secure when running wep because there's just a little less chatter out there in the air... kismet and toys will still sniff one out in relatively short order though... like a week or so.

The firmware shipping with some of the cisco cards was incompatible with a bunch of the kernel drivers from about 2.4.19-22ish I think... and ad-hoc bugs tend to get noticed later as fewer people use that networking type.

Downgrade the firmware and you can switch drivers, which I think is the only way to currently put a cisco in scanning mode, but I might be wrong.

Cheers,

Finegan
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't ping from linux to Windows XP paulsm4 Linux - Networking 1 09-18-2005 09:25 PM
winxp+linux network, ping doesn't work frankie_DJ Linux - Newbie 3 07-26-2005 02:07 PM
Linux/Windows networking: ping only works one way qmm Linux - Wireless Networking 6 03-24-2004 05:21 AM
Problems networking Linux and Windows. Pinging does not work. ElijahLofgren Linux - Networking 29 02-12-2004 12:10 AM
Networking Troubles: Can't ping windows computers phishead Linux - Networking 3 04-05-2003 04:08 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 09:13 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration