On Wednesday 02 July 2008 18:59, Ram kumar wrote: > I have a ethernet controller,in which the ping works fine................. > > ping 192.168.1.1(my default gateway)....................i get.............. > > 64 bytes from 192.168.1.1: seq=0 ttl=64 time=46.315 ms > > the same way when i ping google with the ip address............ > > # ping 64.233.167.99 (google's ip address) > > i get................... > > PING 64.233.167.99 (64.233.167.99) 56(84) bytes of data. > 64 bytes from 64.233.167.99: icmp_seq=1 ttl=240 time=91.3 ms
Ok. So routing works. > But when i use my wireless which is eth1 to ping my default gateway > > ping -I eth1 192.168.1.1 > > i get.................... > > 64 bytes from 192.168.1.1: seq=0 ttl=64 time=46.315 ms Wait a second. If you have two interfaces, typically only one of these interfaces is connected to the network which eventually is connected to Internet. That's the network where your default gateway machine is. Why are you trying to ping default gateway FROM ANOTHER network?! > but when i ping google....... > > ping -I eth1 64.233.167.99 > > ping hangs after that........................ Of course. <wireless network> - eth1[your box]eth0 - <wired network> - 192.168.1.1[default gateway] - <network> - []... - <network> - [google] The google is on the "other side". I surprised that ping -I eth1 192.168.1.1 works... -- vda _______________________________________________ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
