From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: Orgad Shaneh <orgads@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Netdev <netdev@vger.kernel.org>
Subject: Re: PROBLEM: networking - port 80 not accessible on eth0
Date: Fri, 9 Jan 2009 16:43:41 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.64.0901091637350.1889@wrl-59.cs.helsinki.fi> (raw)
In-Reply-To: <af2dae3d0901090401l19ea59b6j1812c9d16c843116@mail.gmail.com>
Added netdev though this is unlikely to end up being dev related.
On Fri, 9 Jan 2009, Orgad Shaneh wrote:
> ---------- Forwarded message ----------
> From: Orgad Shaneh <orgads@gmail.com>
> Date: Fri, Jan 9, 2009 at 8:20 AM
> Subject: PROBLEM: networking - port 80 not accessible on eth0
> To: linux-kernel@vger.kernel.org
>
>
> I have a "VIA Technologies, VIA Technologies, Inc. VT6102 [Rhine-II]"
> NIC connected to an ECI B-FOCuS 270PR ADSL model. I used fedora since
> version 5. On FC5 (using kernel 2.6.15) the modem functioned as a
> router, and it worked fine.
>
> When I upgraded to FC6 (which was published with kernel 2.6.18) I
> couldn't access any websites. I found out that I can access https, ftp
> etc. but not http. I figured out that for some reason, port 80 was
> blocked. When using VMWare with Windows, I could access websites.
>
> I configured the modem to be a bridge, and I'm connecting through
> pppoe. This way it works. Anyway, although I can access websites on
> ppp0, I cannot access the modem itself (for configuration), which is
> on eth0 port 80.
>
> I attached a tcpdump when trying to connect to the modem (the same
> applies for websites, when the modem is configured as a gateway):
>
> After trying some different distributions (fedora up to 9, ubuntu 8.04
> and 8.10), the problem remains. That's what leads me to the conclusion
> that the problem is in the kernel.
Unlikely so, more likely the router is broken and some kernel TCP settings
got changed in the newer kernels. I took a short look into the provided
tcpdump and the modem negotiates tcp connection ok but then goes dead
silent.
Your could try playing around with tcp_window_scaling sysctl,
most likely the modem has some problem related to it.
--
i.
parent reply other threads:[~2009-01-09 14:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <af2dae3d0901090401l19ea59b6j1812c9d16c843116@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0901091637350.1889@wrl-59.cs.helsinki.fi \
--to=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=orgads@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).