Re: route table behind router
Andrei Popescu a écrit :
> On Vi, 11 feb 11, 19:20:40, Mike McClain wrote:
>> root@/deb40a:~> wget -v google.com
>> --16:28:14-- http://google.com/
>> => `google.com/index.html'
>> Resolving google.com... 126.96.36.199, 188.8.131.52, 184.108.40.206, ...
>> Connecting to google.com[220.127.116.11]:80... failed: Connection timed out.
>> Connecting to google.com[18.104.22.168]:80... failed: Connection timed out.
>> Connecting to google.com[22.214.171.124]:80... failed: Connection timed out.
> Hmm, is the router using PPPoE to connect to your ISP? Try this:
> ifconfig eth0 mtu 1400
MTU issues should only affect "big" packets containing data, not the
establishement of the connection. But it is worth the try. Adapt the
interface name to the one connected to the router.
At this point, I have two ideas : either a problem with TCP connections
or specifically with HTTP connections. I would first try to connect to
other TCP-based services such as SMTP, POP3, FTP... If it fails too,
then the problem is with TCP, likely with some TCP option not supported
by the router or the ISP. The usual suspects are window scaling,
timestamps, ECN, SACK, which can be enabled or disabled via sysctl
variables in /proc/sys/net/ipv4/. Try to enable and disable each of them
and see what happens.
You can also use tcpdump to capture the packets on the interface while
trying to connect.
Another useful tool is tcptraceroute, it can help to see where something