David S. Miller wrote:
> From: Andi Kleen <[EMAIL PROTECTED]>
> Date: Fri, 20 Jan 2006 08:15:39 +0100
>
>>Sorry for the delay in testing. Looks good so far. I'm running with SNAT
>>and the patch and the messages haven't appeared. Will keep it running
>>for longer, but previously they would have st
From: Andi Kleen <[EMAIL PROTECTED]>
Date: Fri, 20 Jan 2006 08:15:39 +0100
> On Tuesday 17 January 2006 10:42, Patrick McHardy wrote:
>
> > You're absolutely right. Using ip_route_output for local outgoing
> > packets in POST_ROUTING should fix this problem.
> >
> > Andi, can you please try this
On Tuesday 17 January 2006 10:42, Patrick McHardy wrote:
> You're absolutely right. Using ip_route_output for local outgoing
> packets in POST_ROUTING should fix this problem.
>
> Andi, can you please try this patch?
Sorry for the delay in testing. Looks good so far. I'm running with SNAT
and th
Herbert Xu wrote:
On Mon, Jan 16, 2006 at 08:08:19AM +0100, Patrick McHardy wrote:
I can't figure out how this can happen. If a local outgoing multicast
packet would have been SNATed to a non-local IP, ip_route_input would
have been used by ip_route_me_harder. In that case we should see
ip_outp
On Mon, Jan 16, 2006 at 08:08:19AM +0100, Patrick McHardy wrote:
>
> I can't figure out how this can happen. If a local outgoing multicast
> packet would have been SNATed to a non-local IP, ip_route_input would
> have been used by ip_route_me_harder. In that case we should see
> ip_output instead
Herbert Xu wrote:
Andi Kleen <[EMAIL PROTECTED]> wrote:
Badness in ip_finish_output2 at /home/lsrc/quilt/linux/net/ipv4/ip_output.c:203
Call Trace: {ip_finish_output2+419}
{ip_fragment+1512}
{ip_finish_output2+0}
{ip_mc_output+521}
{ip_push_pending_frames+877}
{udp_push_pendin
Andi Kleen <[EMAIL PROTECTED]> wrote:
> On Friday 13 January 2006 11:45, Patrick McHardy wrote:
>
>> I'm going to look into this. Andi, do you have any SNAT rules?
>
> Yes, a single one. I disabled it now and let's see what will happen.
BTW, here is a related discussion:
http://www.ussg.iu.edu/
On Friday 13 January 2006 11:41, Herbert Xu wrote:
> However, this is yet to be confirmed.
I tried to test yesterday. It ran for some short time, but then eventually
all hung (I think in IDE) because I didn't apply all workarounds for the
countless
bugs in current -git [Didn't have such an inst
On Friday 13 January 2006 11:45, Patrick McHardy wrote:
> I'm going to look into this. Andi, do you have any SNAT rules?
Yes, a single one. I disabled it now and let's see what will happen.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMA
Herbert Xu wrote:
Andi Kleen <[EMAIL PROTECTED]> wrote:
Badness in ip_finish_output2 at /home/lsrc/quilt/linux/net/ipv4/ip_output.c:203
Call Trace: {ip_finish_output2+419}
{ip_fragment+1512}
{ip_finish_output2+0}
{ip_mc_output+521}
{ip_push_pending_frames+877}
{udp_push_pendin
Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> Badness in ip_finish_output2 at
> /home/lsrc/quilt/linux/net/ipv4/ip_output.c:203
>
> Call Trace: {ip_finish_output2+419}
> {ip_fragment+1512}
> {ip_finish_output2+0}
> {ip_mc_output+521}
> {ip_push_pending_frames+877}
> {udp_push_pen
FYI,
Since -git7 my workstation spews a lot of these messages in the kernel log.
I added a WARN_ON to see the backtrace. I suspect it's related
to either broadcast or multicast - normal network operation works,
but the icecream daemon (which either broad or multicasts on the local networks)
doesn
12 matches
Mail list logo
