[Voyage-linux] not all html pages are routed

[Gustin Johnson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Torsten Senf wrote:
> Hi,
> 
> i used voyage linux 0.5.2 for a while. I used the
> distribution on an alix 2d3 board. The hardware with the software works
> as a router. Behind the router is one client with debian (lenny) os. On
> the router i have only two eth[01] interfaces working. eth0 connects to the
> client, eth1 connects to the internet. I have my own firewall rules with
> iptables. Everything worked fine.
> 
> Now I installed the 0.6.2 version of voyage on an other CF-Card. I use the old 
> /etc/network/interfaces file, the old ppp-peer file and also my old
> firewall skript from 0.5.2 for the 0.6.2 distribution. It seems that
> everything work, but not all html sites where routed to the client. 
> I mean I can't browse every page from the client with firefox. 
> The most pages are working but not all e.g. www.mdr.de not
> work. I installed w3m on the router and from the router i get all html
> pages. When i boot windows on the client host, the same effect
> appear, not all pages can be browsed from the client. All other network
> protocols are correct working. 
> 
> Any ideas how can I solve the problem??
> 
A couple of things come to mind.  What are your MTU settings?  If you
are using PPP/PPPoE you should try something less than the ethernet
default to avoid fragmentation, which may cause some sites to fail.
IIRC the command is:
ip link set eth0 mtu 1492

Of course change the device to match your environment.

You may wish to investigate MSS clamping if this is an issue.  Read the
following link for more info:
http://lartc.org/howto/lartc.cookbook.mtu-mss.html

The other option that could be causing grief is window scaling.  Check
this on both the router and the workstation:
sysctl -a |grep tcp_window_scaling

To disable it try:
sysctl -w net.ipv4.tcp_window_scaling=0

If this works then the sites you are trying to get to have some broken
routers in the way.  Yes they really are broken, there have been a few
flame wars over this issue over the years.  Check the LKML for more
details (if you care).

Hth,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFKzw0WwRXgH3rKGfMRAjQ6AKCdMMwYbarswOkfYEm/D+wotigo3ACfV6/C
5LD9LUq8zkkyJvPDN0M+fpw=
=Riyz
-----END PGP SIGNATURE-----