From: Patrick McHardy <kaber@trash.net>
To: Andrew Hall <temp02@bluereef.com.au>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: Dead loop on Virtual interface
Date: Mon, 18 Apr 2005 00:26:21 +0200 [thread overview]
Message-ID: <4262E28D.1080900@trash.net> (raw)
In-Reply-To: <0b8801c54001$bb029220$5001010a@bluereef.local>
Andrew Hall wrote:
> Hi,
>
> We've been using the native ipsec implementation in a routed environment
> with no real problems. We have now tried it with a combined
> bridging/routed setup and we see the message "dead loop on virtual
> interface BR0'. The endpoint is configured to be the bridge interface.
> We have tried 2.6.10 and 2.6.11.5 with the same effect. If we disable
> the ipsec transport the message goes away. Does anyone know if this is
> this a problem/bug with the way netfilter, the bridging code and ipsec
> interrelate? Or could there be some other issue.
Probably a misconfiguration, this message occurs when a virtual
device's hard_start_xmit() function tries to transmit a packet using
itself as output device.
Regards
Patrick
prev parent reply other threads:[~2005-04-17 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 8:21 Dead loop on Virtual interface Andrew Hall
2005-04-17 22:26 ` Patrick McHardy [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=4262E28D.1080900@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=temp02@bluereef.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.