मेरी बीटी SmartHub से एक pfSense रूटर से स्विच करने के बाद मैं कुछ मामूली पेश आने वाली समस्याओं लिया है. One of which has been the squid proxy service causing a problem where I can’t access the BBC website with an error. जबकि मैं अंत में एक से थोड़ा अजीब विधि के माध्यम से इसे ठीक किया, मैं इस समस्या का संभावित स्रोत जो अपने आप पर फिक्सिंग के लायक था का सामना करना पड़ा
When I turned squid off I was immediately able to access the BBC website, but with it turned on I consistent received an error from squid that there had been a “Zero Sized Reply”. यह व्यंग्य लग रहा था बीबीसी से कोई जवाब प्राप्त करने में असमर्थ था. One possible cause of this could be fragmented packets being dropped, and the cause of fragmentation is normally MTU size.
The default MTU for Ethernet is 1500 and most modern operating systems manage things on the LAN automatically. It is possible to use sizes up to 9000 to increase throughput (थोड़ा) लैन के लिए. कैसे कभी, this was of less interest to me than making sure packets weren’t getting fragmented multiple times, or being fragmented after leaving the router.
pfSense के साथ वान MTU डिफ़ॉल्ट करने के लिए सेट (1500) I tried some pinging from windows to see what the maximum size was without fragmentation. The command to use is ping google.com -f -l 1500
, changing the last number to find the optimum. My BT Infinity connection uses PPPoE which typically has a maximum value of 1492 (यह वास्तव में सच में PPPoA उपयोग कर सकते हैं के रूप में PPPoE pfSense के लिए जो मेरे पाट मॉडेम पेश कर सकते हैं, different sources say different things about this), and when using ping it is necessary to take into account some overhead which has a value of 28, so I was expecting a ping MTU of 1464 सबसे बड़ा मैं इस्तेमाल कर सकते हैं होने के लिए. To my surprise this still resulted in fragmentation and I eventually found the maximum I could use was 1456.
मैं इस मान का उपयोग किया (साथ 28 पीठ पर जोड़ा) की एक MTU मान सेट करने के 1484 में वान interface settings of pfsense. Now the only fragmentation should be done by the router to LAN packets, with no risk of any later fragmentation from a router somewhere between me and any particular website. After clearing my browser cache and the squid cache I was then able to load the BBC website successfully. I suspect the issue was caused by a router blackholing issue somewhere between my आईएसपी and the BBC servers which was dropping the fragmented packets. A nice description of the phenomenon can be found on RCL के ब्लॉग
“Hi James I realise it has been a long while, but I just checked this on windows 11 (build 23H2)…”