From: "Denys" <denys@visp.net.lb>
To: "Denys" <denys@visp.net.lb>, netdev@vger.kernel.org
Subject: Re: strange TCP behaviour
Date: Tue, 8 May 2007 13:31:32 +0300 [thread overview]
Message-ID: <20070508103049.M75995@visp.net.lb> (raw)
In-Reply-To: <20070508094330.M22276@visp.net.lb>
I forgot to mention, latest tested kernel (for now)
2.6.21-rc5
It's just not easy to upgrade, is there any changes after rc5 related to that?
On Tue, 8 May 2007 12:49:36 +0300, Denys wrote
> Dear All
>
> I have application, thats accept redirected requests from squid
> (over iptables .... -j REDIRECT), getting ip over
> getsockopt/SO_ORIGINAL_DST and throwing data in to the tunnel.
>
> And i have strange behaviour, when i do
> sysctl net.ipv4.tcp_frto=0
>
> And i try any website with attachments (means a lot of data going to
> be sent to redirect), i am getting after 3-10 seconds message "Read
> error: Connection timed out". Thats a bit strange, possible it is
> related to application, but i guess kernel must not give error to
> recv/read (i dont know what squid is using). It is a bit difficult
> to reproduce the problem, but i can give a remote access to PC where
> all things installed. But i have no idea, who of TCP(?) maintainers
> can help me with this. I think there is no app problem, tcpdump
> looks normal, there is no reset(and message will be different in
> case of reset).
>
> --
> Denys Fedoryshchenko
> Technical Manager
> Virtual ISP S.A.L.
>
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
prev parent reply other threads:[~2007-05-08 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 9:49 strange TCP behaviour Denys
2007-05-08 10:31 ` Denys [this message]
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=20070508103049.M75995@visp.net.lb \
--to=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
/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).