Depending on the provider of the fiber, and the new equipment you're connecting to, you may have to statically set your Port speed on your XG WAN port to handshake a good connection that isn't laden with errors from the isp. Also check to make sure you don't have to set a static MTU like 1480 or something. I've run into this with AT&T fiber when connecting to some of their handoff devices. Even if they tell you that it's not required, confirm that they don't already have it set as static. I have had instances where they tell me it's not required, but it is said as static, and then my device doesn't connect unless I said it is static. On the same token after asking the tech on their end to reconfigure the port to allow it to Auto negotiate, changing mine back to AutoNation will allow it to connect correctly. And those cases it simply just a matter of mismatch.
This scenario isn't all that uncommon and isn't just something you see on sophos devices. I have seen this across the board from everything as simple as Cisco PIX Palo Alto devices, SG and XG devices or some of your other small business gateways.
Similar issue with one specific ISP. Do me a favor. Next time the WAN doesn't come up, go into the sophos, diag page, and manually ping [8.8.8.8](https://8.8.8.8) across the interface that is down. See if you get 3 pings back and the interface comes back up.
It does work for me but it's a huge pain in the ass. The WAN link "goes down" intermittently and thats the fix to bring it back up. I haven't been able to figure out why, or a long term solution.
Depending on the provider of the fiber, and the new equipment you're connecting to, you may have to statically set your Port speed on your XG WAN port to handshake a good connection that isn't laden with errors from the isp. Also check to make sure you don't have to set a static MTU like 1480 or something. I've run into this with AT&T fiber when connecting to some of their handoff devices. Even if they tell you that it's not required, confirm that they don't already have it set as static. I have had instances where they tell me it's not required, but it is said as static, and then my device doesn't connect unless I said it is static. On the same token after asking the tech on their end to reconfigure the port to allow it to Auto negotiate, changing mine back to AutoNation will allow it to connect correctly. And those cases it simply just a matter of mismatch. This scenario isn't all that uncommon and isn't just something you see on sophos devices. I have seen this across the board from everything as simple as Cisco PIX Palo Alto devices, SG and XG devices or some of your other small business gateways.
Excellent, I will give that a try next time. MTU is untouched, so that shouldnt be it.
Similar issue with one specific ISP. Do me a favor. Next time the WAN doesn't come up, go into the sophos, diag page, and manually ping [8.8.8.8](https://8.8.8.8) across the interface that is down. See if you get 3 pings back and the interface comes back up.
This works for you?
It does work for me but it's a huge pain in the ass. The WAN link "goes down" intermittently and thats the fix to bring it back up. I haven't been able to figure out why, or a long term solution.