ConfigServer Community Forum

This is related to: https://forum.configserver.com/viewtopic.php?f=6&t=10378 We, and others, are seeing issues where CSF appears to incorrectly limit the MTU under certain circumstances. We're seeing this with a user making use of a VPN service. We're seeing this over multiple servers running CS...

Largest responses to tests: CSF enabled: 35 44.826188344 <host_tested> -> 141.138.203.105 ICMP 1495 Echo (ping) reply id=0x4b45, seq=1/256, ttl=64 (request in 34) 1481 MTU in effect, 14 bytes are for ethernet. CSF disabled: 18 0.269080556 <host_tested> -> 141.138.203.105 ICMP 1514 Echo (ping) reply ...

Yes, we've just been looking at a connectivity issue one customer has to a server running CSF and came to the conclusion it was an MTU issue. We're seeing it drop down to 1481 on several servers.

No errors related to dyndns in the logs, checked that. The IPs are in /var/lib/csf/csf.tempdyn - and it is being updated. But they aren't in the ALLOWDYNOUT chain when I do csf -g <ip> HOST = Is correct IPSET - No It does all the A records (we've a few hosts make use of the dyndns) fine, nothing wit...

It is, was the first thing I checked.

Forgot to add, that if I do:

csf -r

The rules appear, it's only when it comes round to the refresh interval that they disappear again, until I do csf -r again.

Hi, This has started happening since 10.04 as far as we can tell. We'll reload CSF (csf -r) and all is good, 5 minute later the v6 rules have gone. We have some rules: tcp|out|d=1234|d=host.example.org Where host.example.org has a single v4 and single v6 address. The v4 rules get created, the v6 rul...