MadDogMatt
@verizon.net
| reply to HaloBox
Re: Business FIOS looses connection
I had considered attempting to do this, but I really don't feel comfortable taking machines and directly connect them to the internet. That would also take about every machine we have to test.
Keep in mind this design has worked at several other ISP's without issue, this is not new. The config that is being used has been reduced to a textbook NAT config as well. If it was a design issue I doubt we would be able to pass traffic at all but, I can make this config work for 6 hours before the issue re-occurs.
The only thing I can think of is this must have something to do with how Verizon builds the route table for the static IP addresses. A wireshark trace clearly shows traffic leaving the router for the ONT, I find it hard to believe that its an issue with the design... the traffic just never makes it back. I also find it interesting that I don't see ANY arp requests from the Verizon router. its almost like the verizon network is building the route table by arp broadcasts. |
|
birdfeedr
Premium
join:2001-08-11
Warwick, RI
 ·Verizon FIOS
| said by MadDogMatt :
The only thing I can think of is this must have something to do with how Verizon builds the route table for the static IP addresses. A wireshark trace clearly shows traffic leaving the router for the ONT, I find it hard to believe that its an issue with the design... the traffic just never makes it back. I also find it interesting that I don't see ANY arp requests from the Verizon router. its almost like the verizon network is building the route table by arp broadcasts.
You may be onto something there. While I have no proof and I'm not a network engineer, I know enough and have seen enough to know that something is odd in Verizon's network. Look around and see complaints of DNS issues and slow page loads, even no page loads. Sometimes things get fixed with a Retry, sometimes things are fine minutes later. Sometimes it takes a call to FSC, where they say we aren't aware of any issues, but suddenly something gets fixed and it now works.
It's their ad-hoc, flexible routing that seems to stumble to its knees on occasion. It may be their "high-bandwidth so close to the end-point" requirements that you're seeing. |
|
rmatthewcole
join:2000-10-20
Chesterfield, VA | since they are not doing normal subnets with static routes, does anyone know how they are routing the static IP addresses? This would go a long way to resolving the problem. |
|
HaloBox
join:2002-01-10
·Verizon FIOS
| reply to MadDogMatt
said by MadDogMatt :
I had considered attempting to do this, but I really don't feel comfortable taking machines and directly connect them to the internet. That would also take about every machine we have to test.
If you are short on machines, you can always direct connect a single firewalled laptop and cycle through and test each IP address. At least then you would know each address works. While you are doing this, you could inspect the routes and see if you can spot some irregularities. |
|
