republican-creole
site Search:


 
    All Forums Hot Topics Gallery






how-to block ads


 
Search Topic:
Share Topic
Posting?
Post a:
Post a:
Links: ·FiOS Map ·Vz FiOS FAQ ·General Fiber Optics ·Vz FiOS Monitors ·Submit a FAQ
AuthorAll Replies


mackey

join:2007-08-20
kudos:1

3 edits

reply to rickbarnett

Re: [net] Anyone have FIOS w/ ip in 96.xxx.xxx.xxx Range?

Hell, I can't even pull up www.verizon.com right now...

From 96.228.34.1xx:

telnet www.pepboys.com 80
Trying 168.220.64.66...
telnet: connect to address 168.220.64.66: No route to host

ping -n www.pepboys.com
PING www.pepboys.com (168.220.64.66) 56(84) bytes of data.
From 168.220.64.66 icmp_seq=1 Packet filtered
From 168.220.64.66 icmp_seq=2 Packet filtered
From 168.220.64.66 icmp_seq=3 Packet filtered
From 168.220.64.66 icmp_seq=4 Packet filtered
From 168.220.64.66 icmp_seq=5 Packet filtered
From 168.220.64.66 icmp_seq=6 Packet filtered

--- www.pepboys.com ping statistics ---
6 packets transmitted, 0 received, +6 errors, 100% packet loss, time 5002ms

traceroute -n -n www.pepboys.com
traceroute to www.pepboys.com (168.220.64.66), 30 hops max, 40 byte packets
1 192.168.10.1 0.804 ms 0.814 ms 1.168 ms
2 72.84.200.1 6.496 ms 9.045 ms 9.251 ms
3 130.81.58.48 9.142 ms 9.243 ms 9.267 ms
4 130.81.29.84 13.842 ms 13.904 ms 16.263 ms
5 152.63.36.201 16.382 ms 16.428 ms 16.456 ms
6 152.63.41.149 18.778 ms 18.013 ms 18.046 ms
7 204.255.169.2 20.202 ms 14.973 ms 17.256 ms
8 12.123.8.118 19.865 ms 21.960 ms 21.902 ms
9 12.122.16.109 21.975 ms 17.485 ms 19.664 ms
10 12.122.3.37 17.665 ms 17.455 ms 17.345 ms
11 12.122.16.206 19.536 ms 17.438 ms 19.574 ms
12 12.122.11.30 17.167 ms 17.439 ms 17.405 ms
13 12.123.1.181 17.206 ms 16.946 ms 17.380 ms
14 168.220.64.66 22.182 ms !X * *

I've also gotten:

12 12.122.11.30 19.804 ms 17.245 ms 17.185 ms
13 12.123.1.181 112.026 ms 107.913 ms 107.890 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 168.220.64.66 20.492 ms !X * *

PING 4.79.19.59 (4.79.19.59) 56(84) bytes of data.
64 bytes from 4.79.19.59: icmp_seq=1 ttl=55 time=9.00 ms
64 bytes from 4.79.19.59: icmp_seq=2 ttl=55 time=8.81 ms
64 bytes from 4.79.19.59: icmp_seq=3 ttl=55 time=10.2 ms
64 bytes from 4.79.19.59: icmp_seq=4 ttl=55 time=9.38 ms

--- 4.79.19.59 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms
rtt min/avg/max/mdev = 8.818/9.375/10.290/0.574 ms

traceroute -n -n 4.79.19.59
traceroute to 4.79.19.59 (4.79.19.59), 30 hops max, 40 byte packets
1 192.168.10.1 0.623 ms 0.583 ms 0.952 ms
2 72.84.200.1 4.699 ms 4.759 ms 7.216 ms
3 130.81.58.50 6.935 ms 7.089 ms 7.114 ms
4 130.81.29.84 11.715 ms 11.782 ms 14.161 ms
5 152.63.36.201 14.202 ms 14.233 ms 14.245 ms
6 152.63.41.153 16.609 ms 16.285 ms 16.315 ms
7 4.68.63.169 16.288 ms 14.664 ms 14.665 ms
8 4.68.17.132 12.572 ms 4.68.17.196 14.603 ms 14.553 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


pflog
Bueller? Bueller?
Premium,MVM
join:2001-09-01
El Dorado Hills, CA
kudos:3

I can't ping www.pepboys.com either, but I can connect to it just fine in a browser.

A ping from my FreeBSD box returns:


floyd@pflog:~% ping www.pepboys.com
PING www.pepboys.com (168.220.64.66): 56 data bytes
36 bytes from 12.124.176.70: Communication prohibited by filter
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 6cf0 0 0000 32 01 53f2 71.162.151.6 168.220.64.66


If you look at my route to www.pepboys.com, you'll see that it's the router just before www.pepboys.com doing the filtering of icmp.

Here's my regular mtr (which uses ICMP):


Host Loss% Snt Last Avg Best W rst StDev
1. 71.162.151.1 0.0% 1 4.0 4.0 4.0 4.0 0.0
2. 130.81.96.84 0.0% 1 5.4 5.4 5.4 5.4 0.0
3. 130.81.29.212 0.0% 1 7.0 7.0 7.0 7.0 0.0
4. 152.63.3.77 0.0% 1 6.0 6.0 6.0 6.0 0.0
5. ???
6. 152.63.41.149 0.0% 1 11.4 11.4 11.4 1 1.4 0.0
7. 192.205.35.37 0.0% 1 10.4 10.4 10.4 1 0.4 0.0
8. 12.123.8.118 0.0% 1 14.4 14.4 14.4 1 4.4 0.0
9. 12.122.16.93 0.0% 1 13.4 13.4 13.4 1 3.4 0.0
10. 12.122.3.37 0.0% 1 14.9 14.9 14.9 1 4.9 0.0
11. 12.122.16.206 0.0% 1 14.0 14.0 14.0 1 4.0 0.0
12. 12.122.11.30 0.0% 1 12.9 12.9 12.9 1 2.9 0.0
13. 12.123.1.181 0.0% 1 19.4 19.4 19.4 1 9.4 0.0
14. 12.124.176.70 0.0% 1 16.0 16.0 16.0 1 6.0 0.0
15. ???


And here's a tcptraceroute:


floyd@pflog:~% tcptraceroute www.pepboys.com 80
Selected device em0, address 71.162.151.6, port 57722 for outgoing packets
Tracing the path to www.pepboys.com (168.220.64.66) on TCP port 80 (http), 30 hops max
1 L300.VFTTP-16.PHLAPA.verizon-gni.net (71.162.151.1) 4.677 ms 4.558 ms 4.827 ms
2 P6-2.LCR-03.PHLAPA.verizon-gni.net (130.81.96.84) 7.319 ms 7.102 ms 7.310 ms
3 130.81.29.212 7.303 ms 7.138 ms 7.294 ms
4 0.so-6-0-0.XL1.PHL6.ALTER.NET (152.63.3.77) 7.288 ms 7.135 ms 7.403 ms
5 0.so-5-2-0.XL3.IAD8.ALTER.NET (152.63.36.25) 12.269 ms 12.217 ms 12.605 ms
6 0.ge-6-0-0.BR2.IAD8.ALTER.NET (152.63.41.149) 12.356 ms 12.348 ms 12.357 ms
7 192.205.35.37 12.606 ms 12.328 ms 12.482 ms
8 tbr2.wswdc.ip.att.net (12.123.8.118) 14.980 ms 14.776 ms 14.977 ms
9 cr2.wswdc.ip.att.net (12.122.16.93) 14.978 ms 14.778 ms 14.979 ms
10 cr2.n54ny.ip.att.net (12.122.3.37) 15.102 ms 14.778 ms 14.978 ms
11 tbr2.n54ny.ip.att.net (12.122.16.206) 14.977 ms 14.778 ms 14.978 ms
12 gbr6.n54ny.ip.att.net (12.122.11.30) 14.979 ms 14.779 ms 14.978 ms
13 ar16.n54ny.ip.att.net (12.123.1.181) 14.978 ms 14.780 ms 14.982 ms
14 12.124.176.70 92.437 ms 104.895 ms 74.943 ms
15 www.pepboys.com (168.220.64.66) [open] 72.573 ms 49.736 ms 72.445 ms


If you run tracetcp for www.pepboys.com, where does it stop for port 80? As you can see, I get there fine from my host, but if that router is blocking all ICMP and not passing it, then maybe it's also out of date and filtering the 96/8 class A because it still thinks it's in the bogons list.

A tcp traceroute with the above from those of you who can't get to it would be very important information in diagnosing the problem here.

--
Hello...is there anybody in there?


pflog
Bueller? Bueller?
Premium,MVM
join:2001-09-01
El Dorado Hills, CA
kudos:3

reply to mackey
Sorry mackey See Profile, I just noticed you're on what appears to be a Linux box. In that case, you should be able to get the tcptraceroute package for your distro and run that. Windows users can use the tracetcp url I gave in my previous post.
--
Hello...is there anybody in there?


Wednesday, 30-May 04:33:06 Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo
over 12.5 years online © 1999-2012 dslreports.com.
Most commented news this week
Hot Topics