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" Code:
eth0 Link encap:Ethernet HWaddr 00:0D:61:B2:2A:EA Code:
|
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 |
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) |
bump.. anyone have any idea how to fix this problem?
|
W00T!!!
I got it working.. I used the Cisco official drivers instead of the other ones :)
Posting this using Konqueror right now :D |
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 |
All times are GMT -5. The time now is 06:58 PM. |