Hi to all,
We have a strange drop packets every one or two ours for about two minutes. From the lan we can't reach any destination on the WAN. Now we have XG 18MR1 and a Swithc layer 3 as Default gateway of the LAN. Also PortE0 ( LAN ) show many dropped packets.
Any idea to the question ?
Thank you for contacting the Sophos Community!
Does this happen only in one interface Port?
Like if you have Port1 and Port 3 sets as LAN does the traffic stops for both Ports or only one?
Can you please try running the following command and monitor if the issue persists, if it persists please reverse the command by adding default after Port1 (You can use Tab autocomplete)
console > system diagnostics interface-driver-settings set Port1 offload tso
Also if you run ifconfing from the Advanced Shell (5>4) does the interface with the issue shows any error?
Thnks, do you measn system diagnostics interface-driver-settings set PortE0 offload tso off ?
Port show dropped packet
PortE0 Link encap:Ethernet HWaddr 00:E0:20:11:0A:2E inet6 addr: fe80::2e0:20ff:fe11:a2e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3920156735 errors:0 dropped:9717308 overruns:581125 frame:0 TX packets:4157577655 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1747414760597 (1.5 TiB) TX bytes:2730760050319 (2.4 TiB)
Your dropped packets could be a a indicator of a hardware issue (maybe cable etc.). But its not that high. I would rather inspect the Switch and cable, maybe switch the cable.
I'm surprised LuCar Tonididn't suggest it himself but if you are using STAS checkout his post here: https://community.sophos.com/xg-firewall/f/discussions/123403/xg-firewall-v18-mr-3-feedback-and-experiences/450541#450541
Fixed my issue with regular traffic drops
Could be. But would first start with those packet drops.
Short answer is I don't know. You've supplied the answer to me before I have had to investigate further. The dropped packets may be unrelated or a separate issue. The pattern fits the STAS issue and it is a very quick fix so worth mentioning.
Yes sorry I forgot the off at the end of the command.
As Luca mentioned, however, it does seem that issue might be Layer 1 related, especially because of the overruns.