Re: ping problem ...
- From: "onkar" <onkar.n.m@xxxxxxxxx>
- Date: 25 Sep 2006 19:59:37 -0700
The router is connected to the same system.
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
/etc/resolv.conf ::
$cat /etc/resolv.conf
# MADE-BY-RP-PPPOE
nameserver 203.94.227.70
nameserver 203.94.243.70
nameserver 192.168.1.1
[root@my_computer services]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain my_computer localhost
(1)
Also, tell us a bit about your network. Where, for instance, is
192.168.1.1 in relation to the system you issue the ping on? Is it the
same system, or a different system.???
The router is connected to the same system.
Here is the data u asked :
------------------------------------------------------
$ /sbin/ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:137 errors:0 dropped:0 overruns:0 frame:0
TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8936 (8.7 Kb) TX bytes:8936 (8.7 Kb)
ppp0 Link encap:Point-to-Point Protocol
inet addr:10.112.112.112 P-t-P:10.112.112.113
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:20 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:0 (0.0 b) TX bytes:244 (244.0 b)
-----------------------------------------------------------
$ /sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.112.112.113 0.0.0.0 255.255.255.255 UH 0 0 0
ppp0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
lo
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo
0.0.0.0 10.112.112.113 0.0.0.0 UG 0 0 0
ppp0
----------------------------------------------------------------------
WITHOUT PING
# ./iptables -L -v -n -t filter
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
0 0 RH-Firewall-1-INPUT all -- * * 0.0.0.0/0
0.0.0.0/0
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
0 0 RH-Firewall-1-INPUT all -- * * 0.0.0.0/0
0.0.0.0/0
Chain OUTPUT (policy ACCEPT 175 packets, 14436 bytes)
pkts bytes target prot opt in out source
destination
Chain RH-Firewall-1-INPUT (2 references)
pkts bytes target prot opt in out source
destination
0 0 ACCEPT all -- lo * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT all -- sit0 * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT all -- ppp0 * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT icmp -- * * 0.0.0.0/0
0.0.0.0/0 icmp type 255
0 0 ACCEPT esp -- * * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT ah -- * * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT all -- * * 0.0.0.0/0
0.0.0.0/0 state RELATED,ESTABLISHED
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:80
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:443
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:21
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:22
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:23
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:25
0 0 REJECT all -- * * 0.0.0.0/0
0.0.0.0/0 reject-with icmp-host-prohibited
------------------------------------------------------------------------
WITH PING
#./iptables -L -v -n -t filter
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
0 0 RH-Firewall-1-INPUT all -- * * 0.0.0.0/0
0.0.0.0/0
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
0 0 RH-Firewall-1-INPUT all -- * * 0.0.0.0/0
0.0.0.0/0
Chain OUTPUT (policy ACCEPT 334 packets, 27640 bytes)
pkts bytes target prot opt in out source
destination
Chain RH-Firewall-1-INPUT (2 references)
pkts bytes target prot opt in out source
destination
0 0 ACCEPT all -- lo * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT all -- sit0 * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT all -- ppp0 * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT icmp -- * * 0.0.0.0/0
0.0.0.0/0 icmp type 255
0 0 ACCEPT esp -- * * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT ah -- * * 0.0.0.0/0
0.0.0.0/0
0 0 ACCEPT all -- * * 0.0.0.0/0
0.0.0.0/0 state RELATED,ESTABLISHED
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:80
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:443
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:21
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:22
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:23
0 0 ACCEPT tcp -- * * 0.0.0.0/0
0.0.0.0/0 state NEW tcp dpt:25
0 0 REJECT all -- * * 0.0.0.0/0
0.0.0.0/0 reject-with icmp-host-prohibited
Lew Pitcher wrote:
Lew Pitcher wrote:
onkar wrote:
I am configuring ADSL connection on my Linux box[snip]
every thing goes fine - network activated but ...
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
-----no response ----
OK, so you send pings out, but you don't get a ping response.
It's not your /etc/hosts nor your /etc/resolv.conf. Both of those files
work with hostname-to-ip address mappings, and since you are pinging by
IP address, neither of those files is involved with the ping.
It sounds like a routing problem of some sort.
One further thought. It could also be the results of a firewall
blocking pings. Do you run a firewall? Does rp-pppoe run the firewall
for you? What do your firewall rules look like? Show us the output of
/usr/sbin/iptables -L -v -n -t filter
both with ping working and with ping failing
--
Lew Pitcher
.
- Follow-Ups:
- Re: ping problem ...
- From: Lew Pitcher
- Re: ping problem ...
- References:
- ping problem ...
- From: onkar
- Re: ping problem ...
- From: Lew Pitcher
- Re: ping problem ...
- From: Lew Pitcher
- ping problem ...
- Prev by Date: Re: ping problem ...
- Next by Date: Re: D-Link GLB-502T ADSL Router problem in "Bridge mode"
- Previous by thread: Re: ping problem ...
- Next by thread: Re: ping problem ...
- Index(es):
Relevant Pages
|