Bufferbloat guide causes NAT bug
-
https://docs.netgate.com/pfsense/en/latest/recipes/codel-limiters.html
I used this guide to reduce bufferbloat and it works just fine. However, I noticed that when I perform a traceroute on any of my clients, I will see the destination IP address on every single hop. As soon as I disable the Traffic Limiter queues, traceroute works properly and shows the correct IP address on every hop.
Example:
Anyone else run into this problem? I'm running 22.01-RELEASE on a Netgate 3100.
-
@fused said in Bufferbloat guide causes NAT bug:
Anyone else run into this problem?
No. Next time show your command too.
-
@bob-dig all I typed was tracert 1.1.1.1 in command prompt but I get your point. This happens on all client types: smartphones, linux, windows, etc.
Here are the results from the router itself:
SOURCE: LAN INTERFACE
CODEL LIMITERS: ENABLED
SOURCE: LAN INTERFACE
CODEL LIMITERS: DISABLED
SOURCE: WAN INTERFACE
CODEL LIMITERS: ENABLED
-
@fused Next is to show your actual rule you made.
-
Hi @fused -
This is actually a known issue that has been worked on:
https://redmine.pfsense.org/issues/9263
https://docs.netgate.com/pfsense/en/latest/releases/22-05.html#traffic-shaper-limitersIt should be working better in pfSense 22.05 once it's released. I recently upgraded one my 22.01 systems to the 22.05 Beta version (22.05-RC) and can confirm that the traceroutes do work properly for me now.
Hope this helps.
-
@tman222 awesome! thanks for the information :)
