Guest User!

You are not Sophos Staff.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 1800 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can't ping outside WAN - Firewall-acceleration

Ste

Dear Community,

we have a new installation of an XG310 with the firmware (SFOS 18.0.4 MR-4) and we are experience random ping timeout to WAN:

Example ping 8.8.8.8 works from some computer and didn't work on others. Later pings stop work from the previos pc and start work on the otherone.

To solve we have to disable Firewall-acceleration option.

Is this a bug issue? Are you working on it?

What are the feature of the Firewall-acceleration option?

Thank you



This thread was automatically locked due to age.
Parents
  • 0

    Hello Ste,

    this is definitely a bug.

    We have the same issue on a XG550 after the migration from 17.5.12 to 18.0.4 MR-4.

    The thing is not reproducable. We had it right after the migration on 9th of january. Then it vanished for some weeks and probably came back a couple of days ago.

    Disabling the firewall-acceleration also helped in our case but we decided to leave the acceleration on as sophos support never told us to disable it and we wanted to find the root cause. This is diffcult as running tcpdump also will let the error go away.

    We have another issue with UDP Packets and Teams Communication which might be related in some way. However this issue is older and we have seen it also on 17.5.x.

    For me it looks like some packets are dropped under certain circumstances.

    Regards
    BeEf

Reply
  • 0

    Hello Ste,

    this is definitely a bug.

    We have the same issue on a XG550 after the migration from 17.5.12 to 18.0.4 MR-4.

    The thing is not reproducable. We had it right after the migration on 9th of january. Then it vanished for some weeks and probably came back a couple of days ago.

    Disabling the firewall-acceleration also helped in our case but we decided to leave the acceleration on as sophos support never told us to disable it and we wanted to find the root cause. This is diffcult as running tcpdump also will let the error go away.

    We have another issue with UDP Packets and Teams Communication which might be related in some way. However this issue is older and we have seen it also on 17.5.x.

    For me it looks like some packets are dropped under certain circumstances.

    Regards
    BeEf

Children