US Telco Support > Verizon > Verizon Fiber Optics > [net] Anyone have FIOS w/ ip in 96.xxx.xxx.xxx Range?

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

I'm not on a 96/8 address, I have a static IP in the 71/8 range, but just wanted to confirm that I can get to that IP from my FiOS line.

 Host                                                    Loss%   Snt   Last   Avg  Best  W rst StDev
 1. L300.VFTTP-16.PHLAPA.verizon-gni.net                  0.0%     2    5.0   5.1   5.0    5.1   0.0
 2. P6-2.LCR-04.PHLAPA.verizon-gni.net                    0.0%     2    6.6   6.6   6.6    6.7   0.1
 3. 130.81.29.214                                         0.0%     2    5.7   5.6   5.6    5.7   0.0
 4. 0.so-6-0-0.XL2.PHL6.ALTER.NET                         0.0%     2    7.1   9.6   7.1  1 2.0   3.5
 5. 0.so-6-0-0.XL4.IAD8.ALTER.NET                         0.0%     2   11.0  11.1  11.0  1 1.1   0.0
 6. 0.ge-7-1-0.BR2.IAD8.ALTER.NET                         0.0%     2   12.6  12.6  12.6  1 2.7   0.0
 7. 4.68.63.165                                           0.0%     2   11.7  11.6  11.6  1 1.7   0.0
 8. ae-32-89.car2.Washington1.Level3.net                  0.0%     2   10.6  10.6  10.6  1 0.6   0.0
 9. 4.79.19.59                                            0.0%     2   12.1  12.1  12.1  1 2.1   0.0

reply to rickbarnett
I can trace to it and i'm on a 96.xxx.xxx.xxx

reply to rickbarnett
I have had some reachability issues to places that have not updated their bogon filters on their routers.
96.x.x.x was not assigned a few years ago and it seems some places never update their filters.

reply to rickbarnett
I have a 96.xxx.xxx.xxx address and am able to ping and trace route to 4.79.19.59 with no problems.

reply to rickbarnett
Successful ping/tracert here as well. Rick, check reply to your earlier PM...

reply to rickbarnett
Yes, I -was- on this IP block:

CIDR: 96.224.0.0/11
NetName: VIS-BLOCK

I could not get to Web sites here and there, specifically those that use ATT as upstream transport. For example, www.pepboys.com.

I just called the Verizon FiOS Solution Center. The guy was great, I just told him to "break the MAC-IP DHCP lease" so that I could hopefully get a new IP address. Five minutes on the phone, release/renew, and I'm now on the following IP block:

CIDR: 71.160.0.0/11
NetName: VIS-BLOCK

I can now get to www.pepboys.com and other IP destinations that were previously filtered.

I figured it'd be pretty hard to call up ATT and try to tell them one of their routers or customer's routers hasn't updated bogon filtering lately!

Don Q.

Thanks, Don.
Wish my issue was that easy. My traces to the target IP die on a level3 router and VZ has constantly been trying to wash their hands of the issue, in spite of the fact the network admin at the target can see my ping packets reach their server. They just get lost on the return. VZ FIOS customers in surrounding co's can also reach out and touch but they haave been universally allocated 72/8 addys.
VZ has confirmed w/ level3 there are no blacklist/blackhole issues relating to my ip block. I am stuck with 96/8 as a result of being in a newly deployed GPON area. They have finally acknowledged ownership of the issue and are focusing on my upstream gateway at my CO. It has taken more than a month to get them to look past the easy solution where the typical response has been "Not our network, not our problem. I kinda wish it was a level3 issue, I know just who to talk to there. Verizon has steadfastly refused to allow me to share the results of my troubleshooting with the folks who sit at the switch.
The target IP I need to reach is a TISP that hosts several of my DIDs and are a super outfit. Cox HSI is such a crappy network with their incessant packet loss and jitter it is barely usable for email much less the rigors of VOIP. I have been running a torture test on my FIOS circuit and it is absolutely rock solid in terms of compatiility with VOIP. That is the main reason I have devoted days worth of my time on getting VZ to take hold of this issue and fix it. I am glad to hear your issue was resolved. Wish me luck

Rick

reply to rickbarnett
I can ping this IP I am on a 94 IP

traceroute to 4.79.19.59 (4.79.19.59), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 6.366 ms 0.873 ms 0.304 ms
2 96.232.200.1 (96.232.200.1) 8.546 ms 6.601 ms 8.252 ms
3 G13-3-382.LCR-03.NYCMNY.verizon-gni.net (130.81.96.154) 6.802 ms 6.784 ms 7.066 ms
4 130.81.29.200 (130.81.29.200) 7.587 ms 6.753 ms 7.563 ms
5 0.so-3-1-0.XT1.NYC9.ALTER.NET (152.63.10.37) 7.374 ms 6.475 ms 7.423 ms
6 0.so-7-0-0.XL3.NYC4.ALTER.NET (152.63.10.21) 7.593 ms 7.701 ms 7.095 ms
7 0.ge-5-0-0.BR3.NYC4.ALTER.NET (152.63.3.110) 7.349 ms 6.870 ms 7.530 ms
8 204.255.173.54 (204.255.173.54) 69.550 ms 6.580 ms 7.555 ms
9 vlan89.csw3.NewYork1.Level3.net (4.68.16.190) 12.399 ms vlan79.csw2.NewYork1.Level3.net (4.68.16.126) 16.078 ms vlan99.csw4.NewYork1.Level3.net (4.68.16.254) 11.108 ms
10 ae-94-94.ebr4.NewYork1.Level3.net (4.69.134.125) 6.685 ms ae-83-83.ebr3.NewYork1.Level3.net (4.69.134.105) 8.917 ms ae-73-73.ebr3.NewYork1.Level3.net (4.69.134.101) 12.058 ms
11 ae-3.ebr3.Washington1.Level3.net (4.69.132.89) 22.346 ms 17.247 ms 16.608 ms
12 ae-93-93.csw4.Washington1.Level3.net (4.69.134.174) 23.328 ms ae-84-84.csw3.Washington1.Level3.net (4.69.134.186) 14.668 ms 13.703 ms
13 ae-32-89.car2.Washington1.Level3.net (4.68.17.132) 14.987 ms ae-42-99.car2.Washington1.Level3.net (4.68.17.196) 14.096 ms 13.985 ms
14 * *

reply to rickbarnett
I don't know about GPON, how do I find out?

How long have you had FIOS??

If it was installed in the last few months, it may be GPON.

Can you try to trace to 4.79.19.59 again, looks like your earlier attempt failed.

What about Ping?

Thanks

Rick

reply to rickbarnett
Looks fine to me.

Target Name: N/A
IP: 4.79.19.59
Date/Time: 3/9/2008 12:31:10 PM

1 0 ms 0 ms [192.168.0.1]
2 3 ms 5 ms L100.VFTTP-24.PHLAPA.verizon-gni.net [72.78.114.1]
3 6 ms 3 ms P10-3.LCR-04.PHLAPA.verizon-gni.net [130.81.96.70]
4 7 ms 7 ms [130.81.29.214]
5 9 ms 6 ms 0.so-6-0-0.XL2.PHL6.ALTER.NET [152.63.3.81]
6 10 ms 10 ms 0.so-6-0-0.XL4.IAD8.ALTER.NET [152.63.0.130]
7 10 ms 8 ms 0.ge-7-0-0.BR2.IAD8.ALTER.NET [152.63.41.157]
8 12 ms 10 ms te-11-3-0.edge1.Washington4.Level3.net [4.68.63.169]
9 12 ms 13 ms ae-12-69.car2.Washington1.Level3.net [4.68.17.4]
10 16 ms 14 ms [4.79.19.59]

Ping statistics for 4.79.19.59
Packets: Sent = 2, Received = 2, Lost = 0 (0.0%)
Round Trip Times: Minimum = 14ms, Maximum = 16ms, Average = 15ms

reply to rickbarnett
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 * * *

reply to rickbarnett
My IP changed today for the first time. Now it's in the 96.xxx.xxx.xxx range. PM sent.

Edit: Apparently I can't ping or go to www.pepboys.com although I can ping the IP posted by OP fine.

reply to mackey
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

 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. ???

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

reply to mackey
Sorry mackey , 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?

reply to rickbarnett
Wanted to add. That with the new 96.xxx IP, I can no longer connect to the Verizon NY usenet server, only to the other one. You'd think Verizon's server would recognize it. Pepboys.com still doesn't work either.

Here's a tracert to the Verizon NY server.

Tracing route to news.verizon.net [130.81.64.196]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 3 ms 2 ms 2 ms L100.VFTTP-55.LSANCA.verizon-gni.net [96.229.188
.1]
3 4 ms 3 ms 4 ms G0-1-955.LCR-09.LSANCA.verizon-gni.net [130.81.6
0.112]
4 7 ms 5 ms 5 ms 130.81.28.72
5 85 ms 85 ms 85 ms 130.81.19.80
6 92 ms 92 ms 92 ms 130.81.19.110
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.