----- Forwarded message from Paul P Komkoff Jr <[EMAIL PROTECTED]> -----
From: Paul P Komkoff Jr <[EMAIL PROTECTED]> To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Was change to ip_push_pending_frames intended to break udp (more specifically, WCCP?) 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. -- Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key This message represents the official view of the voices in my head - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ----- End forwarded message ----- - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
