I recently "upgraded" to the FIOS G3100 Router from the FIOS Quantum Router (due to a move) and can no longer VPN to my work network. Below is a summary of the issue from my IT department.
Problem: Using and IPSec VPN connection to a Cisco firewall. After authentication, the firewall terminates the connection because the connection appears as a DoS attack. The logs show the following when connecting to the firewall:
2 Apr 06 2020 13:09:15 98.115.x.x x.x.x.x Deny IP teardrop fragment (size = 1480, offset = 0) from 98.115.x.x to x.x.x.x
Basically, the firewall is interpreting the connection as TearDrop DoS attack.
This works from other ISPs and the previous Fios connection. But under the new connection (and new router) the error occurs.
Any thoughts or advice on how to allow the FIOS G3100 Router to VPN externally would be appreciated.
Solved! Go to Correct Answer
Just for your information, VPN Fragmentation issue seems to be fixed in the latest firmware 22.214.171.124.
Users now does not need to use the Ethernet interface in order to connect to a remote IPsec VPN.
You should be able to log into the FiOS router's web interface at https://192.168.1.1/ or https://myfiosgateway.com/ (Admin username and password are printed physically on the router) and adjust the Firewall setting from Typical to "Low" or "Off". Hopefully that should be it, and this isn't a problem with IPSec ALG in the router being broken.
Thank you for the reply. That is not it. I have since learned that a wired connection allows me to connect via VPN, however a wireless connection does not. It appears to be something with the new router's wireless settings. I've tested most of the settings on the router, but still unable to find a resolution at this point in time.
Thanks for suggestion about trying it wired but it still wont work for me, i had no issues until i got upgraded to the new G3100. i even created some port forwarding rules to the ports that are required for the VPN and still no go. Calling Verizon tech support is no help either, they told me that no one has reported any similar issues therefore it should just be working. I had read on another post that someone had a similar issue and the issue was resolved by getting a new router, i don't know if that really would work, but i'm trying it it out. I will update this post once i get my new replacement.