From: Andrew Morton <akpm@osdl.org>
To: Paul P Komkoff Jr <i@stingr.net>
Cc: 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: Sat, 20 May 2006 14:04:34 -0700 [thread overview]
Message-ID: <20060520140434.2139c31b.akpm@osdl.org> (raw)
In-Reply-To: <20060520191153.GV3776@stingr.net>
Paul P Komkoff Jr <i@stingr.net> wrote:
>
> Hello!
>
> I have a userspace application, which talks WCCP2 with cisco routers.
> It sends and receives UDP packets on port 2048. After I've updated my
> server to 2.6.16, it stopped working.
>
> Examining logs and packet dumps of previous (2.6.15 kernel) vs.
> current, I found, that cisco will not understand packets generated by
> 2.6.16. The only difference in that packets was IP id field, which was
> increasing (1, 2, ...) with old kernel, and always 0 with 2.6.16.
>
> Looking thru the changelog, I've found a suspect. It was this commit:
> http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1a55d57b107c3e06935763905dc0fb235214569d
>
> Reverting this patch fixes my problems - the router understands
> packets again.
>
> I took a look through the code and ip_select_ident codepath but still
> don't understand why it setting id to 0.
(netdev cc added)
next parent reply other threads:[~2006-05-20 21:04 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 ` Andrew Morton [this message]
2006-05-22 18:22 ` Was change to ip_push_pending_frames intended to break udp (more specifically, WCCP?) 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
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=20060520140434.2139c31b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=i@stingr.net \
--cc=linux-kernel@vger.kernel.org \
--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).