1 |
>> >> Maybe run a ping to a destination which you are having problems |
2 |
>> >> with, then reproduce the problem (with the network idle |
3 |
>> >> otherwise). You should see ping packets dropped only then. |
4 |
>> >> |
5 |
>> >> You can also ping with increasing packet sizes (see ping --help) |
6 |
>> >> and see when the packet becomes too big for path MTU. But instead |
7 |
>> >> lowering your MTU then, you should allow icmp-fragmentation-needed |
8 |
>> >> come through reliably. Lowering MTU only makes sense to stop |
9 |
>> >> overly fragmentation in the first place and optimize for a |
10 |
>> >> specific packet path (like traffic through one or multiple VPN |
11 |
>> >> tunnels) where fragmentation would otherwise increase latency a |
12 |
>> >> lot, or where icmp-frag-needed does not correctly work. |
13 |
>> > |
14 |
>> > |
15 |
>> > I'll try pinging today once the issue pops up. |
16 |
>> |
17 |
>> |
18 |
>> I'm seeing the issue again as usual but ping response times come back |
19 |
>> normal at about 50ms. I'll keep trying. |
20 |
> |
21 |
> Not sure if this came after or before switching your router to modem |
22 |
> mode... But if it happened before and is solved now, your router really |
23 |
> doesn't well with icmp packets or has problems with mss clamping / pmtu. |
24 |
|
25 |
|
26 |
I did not try pinging before switching the device from router to modem. |
27 |
|
28 |
BTW, I read that setting CLAMPMSS=Yes in shorewall.conf is a necessity |
29 |
when using PPPoE but my connection is working fine without that |
30 |
setting. Should I set it anyway? |
31 |
|
32 |
- Grant |