vggeli
join:2003-09-17
| [General] Why can't I ping WAN IP?
DEVICE - WRT54G with firmware 4.20.7
ISP - AOL DSL
MODEM - Broadxent DSL Modem Broadband Blaster
WAN IP - 172.196.42.x
LAN IP - 192.168.1.x
OS - WINXP
PROBLEM - Why cannot I ping my WAN IP?
Tests tried:
- can ping 192.168.1.1
- can ping www.yahoo.com
- cannot ping 172.x.x.x
Any ideas? |
|
LBDSL
Lightning Bolt
VIP
join:2002-01-07
Auburn Hills, MI | a 172.x.x.x IP is a private IP, and Your ISP may have is set to not respond to pings
--
Lightning Bolt Technologies |
|
vggeli
join:2003-09-17 | Even if it is an internal IP, I can still ping wan ips..
Is there a technical article that I could read about this..
Please help |
|
skorell
join:2004-06-09
Chula Vista, CA | reply to vggeli
Have you made sure your router is setup to respond to WAN request? |
|
vggeli
join:2003-09-17
2 edits | Do you mean the "Disable the Block WAN request on the router"?
This doesnt matter because, this is how the traffic goes.
PC--->ROUTER--->MODEM--->INTERNET
not the other way around. |
|
will792
join:2003-11-18
Stamford, CT
| said by vggeli  :Do you mean the "Disable the Block WAN request on the router"? This doesnt matter because, this is how the traffic goes. PC--->ROUTER--->MODEM--->INTERNET not the other way around. Traffic has to go to your ISP router for WAN IP pings. It does come back but your router does not know that. All it knows that it is not data for LAN clients therefore should go out.
PC-->YOUR ROUTER-->MODEM-->ISP ROUTER-->MODEM-->YOUR ROUTER
You can see it if you use tracert command (The modem would not appear).
Will |
|
vggeli
join:2003-09-17 | I see.. so this is this really a problem with the router? |
|
Comp Cmndo
join:2003-08-12
FL-USA
| reply to vggeli
said by vggeli :...Is there a technical article that I could read about this... »Adelphia High Speed Internet »FAQ: Adelphia limits trace routes. How do you work around it? |
|
mateo94402
@broadcom.com
| reply to vggeli
Try the diagnostic tool InstantHelp if you can get a copy from other place. It can detect many of the common problems.
Downlaod from
»www.download.com/InstantHelp/300···=lst-0-1 |
|
koitsu
Premium
join:2002-07-16
Mountain View, CA
1 edit | reply to vggeli
You should be able to ping that IP. Here's some details:
First off, for those wondering, 172.196.42.0/24 is part-of the ARIN-delegated 172.192.0.0/12 netblock for America Online. It's NOT a reserved IP address:
NetRange: 172.192.0.0 - 172.216.255.255
CIDR: 172.192.0.0/12, 172.208.0.0/13, 172.216.0.0/16
NetName: AOL-172BLK-2
NetHandle: NET-172-192-0-0-1
Parent: NET-172-0-0-0-0
NetType: Direct Allocation
NameServer: DAHA-01.NS.AOL.COM
NameServer: DAHA-02.NS.AOL.COM
NameServer: DAHA-07.NS.AOL.COM
Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
RegDate: 2002-02-13
Updated: 2004-12-22
Secondly, from your own LAN, you should be able to ping your WAN IP (assuming that WAN IP is what your router has assigned to it).
WRT54* series routers have a loopback interface (they run Linux, so it's device lo0), and will detect packets from local interfaces going to other interfaces as having to traverse loopback.
Thirdly, the option labelled "Block Anonymous Internet Requests" (which blocks pings to your WAN IP across the WAN interface) DOES NOT apply to the LAN interface. Meaning, with that option ENABLED, you'll still be able to ping your WAN IP from a device on your LAN.
Here's a real-life example:
C:\Documents and Settings\jdc>ping -n 2 koitsu.dynalias.org
Pinging koitsu.dynalias.org [64.169.93.187] with 32 bytes of data:
Reply from 64.169.93.187: bytes=32 time<1ms TTL=64
Reply from 64.169.93.187: bytes=32 time<1ms TTL=64
Ping statistics for 64.169.93.187:
Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\jdc>tracert koitsu.dynalias.org
Tracing route to koitsu.dynalias.org [64.169.93.187]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms adsl-64-169-93-187.dsl.snfc21.pacbell.net [64.169.93.187]
C:\Documents and Settings\jdc>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : home.lan
IP Address. . . . . . . . . . . . : 192.168.1.50
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
--
Making life hard for others since 1977. In memory of 2005... |
|
ANoni
@cox.net | reply to vggeli
"This doesnt matter because, this is how the traffic goes."
Fix it youself than retard!! |
|
srinu_028
join:2005-07-25
600004 | reply to LBDSL
mr.lightning bolt
the wan ip he is getting is not private,its a public ip.
private ip for this range (class-b)would be 172.16-31.x.x. |
|
srinu_028
join:2005-07-25
600004
| reply to koitsu
its a good explaination given by koitsu.
first of all let us know are you able to go online with all your computers(assuming you are as u said u are able to ping yahoo.com).if yes u need not worry about pinging your wan ip.it if u are not online with any of your computers that means the ip which is assigned to you is properly responding,its better to contact aol then. |
|
vggeli
join:2003-09-17
| reply to vggeli
Yes, all the computers can get online on AOL browser.
I can ping the gateway 192.168.1.1
I just can't find an article that would explain why this happens. Koitsu's post is very useful on this case.
Comp Cmndo's article may be similar to what is happening.. |
|
