I, unfortunately, cannot refer to a specific trouble case within this post, as it would violate the first bullet point in the 'Posting to the Verizon Community' section of the Terms and Conditions I agreed to. Ironically, that bullet-point, in of itself, exemplifies my post's message, in that tech support is designed primarily with a focus of absorption, rather than one of resolution.
I'm experiencing an issue, and have tried to bring it to Verizon's attention from all directions (short of using a megaphone outside of HQ). There is a private IP address (LAN, RFC1918) being advertised on Verizon's Boston-area tier 1 network:
Tracing route to 10.5.0.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 4 ms 4 ms 4 ms L100.BSTNMA-VFTTP-103.verizon-gni.net [*.*.*
.*]
3 6 ms 3 ms 5 ms G0-14-4-7.BSTNMA-LCR-21.verizon-gni.net [130.81.
212.76]
4 8 ms 4 ms 4 ms so-3-0-0-0.BOS-BB-RTR1.verizon-gni.net [130.81.1
51.218]
5 35 ms 14 ms 19 ms xe-3-0-4-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
23.185]
6 22 ms 16 ms 22 ms B200.NWRKNJ-LCR-21.verizon-gni.net [130.81.209.1
47]
7 * * * Request timed out.
8 20 ms 19 ms 27 ms 10.5.0.1
Trace complete.
This causes a conflict with a device on my company's network, making remote access to it (for anyone on Verizon's network) impractical.
To resolve this, here's what I tried:
-Called the NOC in the whois record for the public IP address closest to the publicly-routed LAN IP (http://whois.domaintools.com/130.81.209.147). They told me to contact their abuse department.
-Called the abuse number from the whois record, which is out of service.
-Emailed abuse@verizon.net and security@verizon.net. Received an automated (surprise!) response containing the following:
"Unfortunately, we cannot investigate or respond to each email that we receive, but we will attempt to identify and review those emails where we think action is needed." <--I wish I could do this at work!
I received a text message saying that the case was opened and it would be resolved by the end of April 7th. I also received an email from a do-not-reply address with irrelevant do-it-yourself online information.
Today, I received a text saying the ticket has been closed out, but the problem remains. At no point was I contacted via email by a genuine human engineer.
I am out of ideas and I don't know what else I can do to communicate this to my service provider... How do I fix this?
Please go to your profile page for the forum by clicking on your name, and look at the top of the middle column where you will find an area titled "My Private Support Cases".
There you will find a link to the private board where you and the agent may exchange information. This should be checked on a frequent basis as the agent may be waiting for information from you before they can proceed with any actions. Please keep all correspondence regarding your issue in the private support portal.
conf_t,
Since we haven't heard back from you as requested in your private support case, it appears assistance is no longer required. Please make a new post anytime you need assistance.
- Joseph_VZ
Looks like this problem is more widespread than just New Jersey. I'm getting the announcement here in the Buffalo, NY Area. I'm on FiOS at the moment (I'm a DSL User of Verizon) working on someone's computer, so here's a trace which I can provide. They definitely need to fix this...
Tracing route to 10.5.0.1 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 1 ms 1 ms 1 ms L100.BFLONY-VFTTP-04.verizon-gni.net [71.186.236.1]
3 1 ms 1 ms 2 ms G0-1-0-2.BFLONY-LCR-22.verizon-gni.net [130.81.104.56]
4 11 ms 11 ms 11 ms xe-0-1-1-0.NY325-BB-RTR2.verizon-gni.net [130.81.209.36]
5 49 ms 53 ms 60 ms xe-4-1-6-0.NWRK-BB-RTR2.verizon-gni.net [130.81.23.235]
6 18 ms 19 ms 18 ms B100.NWRKNJ-LCR-22.verizon-gni.net [130.81.209.163]
7 * * * Request timed out.
8 19 ms 19 ms 19 ms 10.5.0.1
Trace Complete
They are putting in Carrier Grade NAT on the DSL network, but typically those IPs only appear for those on PPPoE FiOS or DSL.
Start a new topic or ask questions in the open forum.
