WAN connection dropped dafter 20 minutes

I have an issue where WAN connection drops out after 20 minutes (almost on the dot).

I'm running a ISP router/fiberbox which have DMZ enabled to my Sophos XF Firewall.

I see alot of dropped ping requests - I have an idea that it might be because of dropped ping requests that the WAN is dropped (either from Sophos side or from router side)

Any ideas?

0 BlackChart over 7 years ago in reply to BlackChart

It actually seems like I found the error now.

I'm not sure if it's Sophos or my fibergateway that is the problem :)

I moved WAN IP scope from 10.10.10.1/24 to 192.168.156.1/24 and now everything works like a charm.
But one of the devices are not happy about using the 10.10.10.1/24 scope.

Regards,
Morten Trab
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel
0 BlackChart over 7 years ago in reply to Apurv Patel

Hmmm - Still the same problems, even though I triede a bit different setup.

Regards,
Morten Trab
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BlackChart over 7 years ago in reply to Apurv Patel

As I need stable internet as often as possible I currently have my Sophos offline.

Will see if I can get som time to do more tests during the upcoming weekend.

Regards,

Morten Trab

Regards,
Morten Trab
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Apurv Patel over 7 years ago in reply to BlackChart

Hi,

Thanks for the fast answer.

Is there a way we can access your appliance to have a closer look in that issue ?

Regards,

Apurv
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BlackChart over 7 years ago in reply to Apurv Patel

I've tried several different configuration setups, including ping wan gateway.

All with same result.

When the gateway is live I can ping both 8.8.8.8 and the gateway.
But when it dies after 20 minutes I can ping none of them.
Then I have to edit the WAN interface (just push edit and the save, not changing anything) and then everything is green for another 20 minutes

Regards,
Morten Trab
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Apurv Patel over 7 years ago in reply to BlackChart

Hi,

From logs,

it seems like that WAN gateway was earlier configured with monitoring condition as TCP to gateway IP. After changing monitoring condition from TCP to Ping and changed destination to 8.8.8.8 is not working. XG is not able to reach 8.8.8.8 via that particular WAN interface so it is marking gateway down.

So please verify connectivity with 8.8.8.8 through ISP.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 deeptibhavsar over 7 years ago in reply to rfcat_vk

Hi,

Thank you for the log files. We are looking into that.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rfcat_vk over 7 years ago in reply to John Henry Vindas Carballo

Hi,

that screen shot is for a different thread.

https://community.sophos.com/products/xg-firewall/sophos-xg-beta-programs/sfos-v170-beta/f/sfos-v170-beta-feedback/95909/fw-log-could-not-assocate-packet-to-any-connection-when-ips-enabled

Ian

XG115W - v20.0.2 MR-2 - Home

XG on VM 8 - v21 GA

If a post solves your question please use the 'Verify Answer' button.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 John Henry Vindas Carballo over 7 years ago in reply to BlackChart

Same here but in my case the destination IP is:

Name: c2resolver.ctmail.com
Address: 216.163.176.35
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 BlackChart over 7 years ago in reply to deeptibhavsar

And I get a sh*tload of these lines in the firewall log:

10.10.10.1 = Fiberbox IP
10.10.10.2 = Sophos WAN interface

Log files:

http://files.trab.dk/dgd.log

http://files.trab.dk/syslog.log

Regards,
Morten Trab
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel