forum.ipfire.org

After a lot of search, it turned out that our problem affected mainly our sites that are behind VDSL lines and that it was not related only to core-update 126. It seems that ipfire after core-update 119 or 120 disabled the "path-mtu discovery" feature. After commenting out the line "net.ipv4.ip_no_p...

I fully agree, my setup is very "manual" and not optimum. However, my
problem is not related to this.
We will consider moving to a more effective and flexible way, possibly with a central pac file per site.
Many Thanks.

Our browser is Firefox Quantum 65.0 (64-bits)
and the proxy settings:

Yes, on the browser, I use the proxy for "all protocols". Today, I did a test: On one specific PC, I changed the browser settings to point to another ipfire i586 ver124 (not updated yet), which is located in another building (within our intranet). All worked fine (slower but successfully), uploading...

Thank you for your feedback.
With my local network setup, I can not avoid the proxy. Both the ipfire proxy and firewall are in the data path.
I use "IPFire 2.21 (i586) - Core Update 126" with usual-standard settings.
My problem persists and I keep on checking and testing,
Best Regards

We use the site https://wetransfer.com to upload files to colleagues, so that they can download them by using a link provided by the site after the upload completes. We use the free option which allows files sizes upto 2G, but our files are always below 300 Mbytes. Up to core update 124, we could up...

In setups with more than two interfaces, it would be very useful to be able to specify entry or exit interface for forward or SNAT rules (only exit interface) via the GUI. Is there any plan to add such a feature ?? Alternatively, the possibility to negate IP source or destination networks could some...