busybox ping not able to reach public IP

[Denys Vlasenko]

On Wednesday 02 July 2008 23:14, Ram kumar wrote:
> > Please show output of "ip a l" and "ip r l" commands.
> 
> Here is the output...........
> 
> # ip a l
> 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
> 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
>     link/ether 00:1c:23:f8:ec:80 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.41/24 brd 192.168.1.255 scope global eth0
> 3: eth1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
>     link/ether 00:19:88:05:10:17 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.23/24 brd 192.168.1.255 scope global eth1
> 
> # ip r l
> 192.168.1.0/24 dev eth0  src 192.168.1.41
> 192.168.1.0/24 dev eth1  src 192.168.1.23
> 127.0.0.0/8 dev lo
> default via 192.168.1.1 dev eth0

You indeed have two networks with the same number.
I am not sure it is even supposed to work.
How kernel is supposed to know over which link
it should reach default gw?

I guess normally in such cases people just configure
two devices as bridge (brctl) or trunk them (ifenslave).

> Please let me know how to solve it ?????

I guess 192.168.1.1 sends the answer for ping back by wired network,
not wireless. That's why ping doesn see it.

You may see it if you'll run

tcpdump -nlieth0 -s0 icmp

and 

tcpdump -nlieth1 -s0 icmp

at the time you ping over wireless.
--
vda