| View previous topic :: View next topic |
| Author |
Message |
solamour
l33t
Joined: 21 Dec 2004
Posts: 726
Location: San Diego, CA
|
 Posted: Fri Nov 17, 2006 7:02 am Post subject: [Solved] Can't ping when connected via wireless |
 |
|
| Code: | +------+
| B |
+------+
|
|
+-----+ +------+ +-----+
| A |.....| AP |-----| C |
+-----+ +------+ +-----+
A: Gentoo notebook, 192.168.0.3, connected via wireless with madwifi and WPA-PSK
B: Gentoo desktop, 192.168.0.254
C: WinXP desktop, 192.168.0.1
A <--> B : Can ping each other.
B <--> C : Can ping each other.
A ---> C : A can ping C.
A <--- C : C can't ping A.
|
Basically C can't ping A, even though A can ping C. Also if A is connected to AP with a network cable instead of wireless, everything is OK. I'd appreciate any suggestions.
__
sol
Last edited by solamour on Sun Mar 15, 2009 8:14 am; edited 3 times in total |
|
| Back to top |
|
 |
solamour
l33t
Joined: 21 Dec 2004
Posts: 726
Location: San Diego, CA
|
| Posted: Fri Nov 17, 2006 7:04 am Post subject: |
|
|
Well, never mind. I left it for a while, and it now works. Weird...
[edit]
It works sometimes, but not always. Well, most of the time, it doesn't. Darn...
__
sol
Last edited by solamour on Sat Nov 18, 2006 6:13 am; edited 1 time in total |
|
| Back to top |
|
|
WackyDoo
n00b
Joined: 16 Mar 2004
Posts: 44
Location: Ottawa
|
| Posted: Fri Nov 17, 2006 5:44 pm Post subject: |
|
|
I have a similar problem. My setup uses WPA2/wpa_supplicant, with a gentoo wireless PC (dlink dwl520 PCI) , a wired PC, and Dlink DI624 AP.
Usually the wireless PC is not pingable from the wired PC (no route to xx.xx.xx.xx error). A workaround is to continually run "ping -i 15 routeraddr" on the wireless machine. I should reboot into windows on the wireless machine to see if it is an AP problem or a linux problem. |
|
| Back to top |
|
|
defenderBG
l33t
Joined: 20 Jun 2006
Posts: 817
|
| Posted: Sat Nov 18, 2006 1:17 pm Post subject: |
|
|
can u post the routing table of C?
(normaly done with just "route")
i asume there is the problem.
and post as well the subnet mask... might be a causing a problem as well... |
|
| Back to top |
|
|
solamour
l33t
Joined: 21 Dec 2004
Posts: 726
Location: San Diego, CA
|
| Posted: Sun Nov 19, 2006 3:17 am Post subject: |
|
|
Here is the routing table of C.
| Code: | ===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 50 56 c0 00 08 ...... VMware Virtual Ethernet Adapter for VMnet8
0x3 ...00 50 56 c0 00 01 ...... VMware Virtual Ethernet Adapter for VMnet1
0x4 ...44 45 53 54 42 00 ...... Nortel IPSECSHM Adapter - Packet Scheduler Minip
ort
0x5 ...00 50 bf 31 24 62 ...... Realtek RTL8139/810x Family Fast Ethernet NIC -
Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.254 192.168.0.1 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 20
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 20
192.168.22.0 255.255.255.0 192.168.22.1 192.168.22.1 20
192.168.22.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.22.255 255.255.255.255 192.168.22.1 192.168.22.1 20
192.168.135.0 255.255.255.0 192.168.135.1 192.168.135.1 20
192.168.135.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.135.255 255.255.255.255 192.168.135.1 192.168.135.1 20
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1 20
224.0.0.0 240.0.0.0 192.168.22.1 192.168.22.1 20
224.0.0.0 240.0.0.0 192.168.135.1 192.168.135.1 20
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
255.255.255.255 255.255.255.255 192.168.22.1 192.168.22.1 1
255.255.255.255 255.255.255.255 192.168.135.1 192.168.135.1 1
255.255.255.255 255.255.255.255 192.168.135.1 4 1
Default Gateway: 192.168.0.254
===========================================================================
Persistent Routes:
None |
It was working OK today. Hope it stays that way.
__
sol |
|
| Back to top |
|
|
solamour
l33t
Joined: 21 Dec 2004
Posts: 726
Location: San Diego, CA
|
| Posted: Sun Mar 15, 2009 8:13 am Post subject: |
|
|
One thing I noticed is that, often times it takes while before I can ping a laptop via WiFi, but once it starts working, it keeps working fine. I'm still not sure what's causing the problem and got tired of waiting for it to work, so I ended up assigning static IPs to all WiFi connected devices. Somewhat clumsy, but it's good enough for me.
| Code: | /etc/dnsmasq.conf
dhcp-host=00:11:22:33:44:55,laptop_name,192.168.0.10,1h |
__
sol |
|
| Back to top |
|
|
|
Networking & Security
