From: Paul P Komkoff Jr <i@stingr.net>
To: Vlad Yasevich <vladislav.yasevich@hp.com>
Cc: Rick Jones <rick.jones2@hp.com>, Paul P Komkoff Jr <i@stingr.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Was change to ip_push_pending_frames intended to break udp (more specifically, WCCP?)
Date: Tue, 23 May 2006 00:21:13 +0400 [thread overview]
Message-ID: <20060522202113.GA8196@stingr.net> (raw)
In-Reply-To: <1148324083.15323.325.camel@galen.zko.hp.com>
Replying to Vlad Yasevich:
> /* This is only to work around buggy Windows95/2000
> * VJ compression implementations. If the ID field
> * does not change, they drop every other packet in
> * a TCP stream using header compression.
> */
Unfortunately, cisco IOS also complains that packets are "duplicate".
And, regarding to your previous message on how to fix this - IIRC, if
I do connect() on this socket, it will refuse to receive datagrams
from hosts other than specified in connect(), and I will be unable to
bind another socket to the same port on my side.
That said, the only solution which is close to what been before, will
be to keep one socket for receive, and create socket for each router I
am communicating with, right?
--
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
This message represents the official view of the voices in my head
next prev parent reply other threads:[~2006-05-22 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060520191153.GV3776@stingr.net>
2006-05-20 21:04 ` Was change to ip_push_pending_frames intended to break udp (more specifically, WCCP?) Andrew Morton
2006-05-22 18:22 ` Vlad Yasevich
2006-05-22 18:48 ` Rick Jones
2006-05-22 18:54 ` Vlad Yasevich
2006-05-22 20:21 ` Paul P Komkoff Jr [this message]
2006-05-22 21:10 ` Vlad Yasevich
2006-05-22 21:11 ` Alan Cox
2006-05-22 21:06 ` Rick Jones
[not found] ` <20060522.161951.92584947.davem@davemloft.net>
2006-05-23 8:13 ` Paul P Komkoff Jr
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=20060522202113.GA8196@stingr.net \
--to=i@stingr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=vladislav.yasevich@hp.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).