| 1 |
>> I set up squid on a remote system so I can browse the internet from |
| 2 |
>> that IP address. It works but it stalls frequently. I had similar |
| 3 |
>> results with ziproxy. I went over this with the squid list but we got |
| 4 |
>> nowhere as it seems to be some kind of a system or network problem. |
| 5 |
>> |
| 6 |
>> http://squid-web-proxy-cache.1019090.n4.nabble.com/squid-3-3-5-hangs-the-en |
| 7 |
>> tire-system-td4660893.html |
| 8 |
>> |
| 9 |
>> Can anyone here help me figure out what is wrong? I'm not sure where to |
| 10 |
>> start. |
| 11 |
>> |
| 12 |
>> - Grant |
| 13 |
> |
| 14 |
> Just a quick pointer in case it applies to you: if you tunnel into the proxy |
| 15 |
> machine (using ssh, VPN, proxychains and what not) you would suffer from |
| 16 |
> packet fragmentation, which could quickly snowball. In this case try reducing |
| 17 |
> your mtu to lower values, than the default ethernet 1500 byte packets, to |
| 18 |
> cater for the overhead of the larger tunnelling headers. |
| 19 |
|
| 20 |
I've tried disconnecting from my SSH tunnel and changing the mtu on my |
| 21 |
laptop and on the remote proxy server via ifconfig and there is some |
| 22 |
kind of an improvement but I can't narrow it down. I've tried mtu |
| 23 |
down to 1000 on both systems but the proxy server still stalls |
| 24 |
sometimes. Any tips for narrowing this down further? |
| 25 |
|
| 26 |
- Grant |
Archives