netdev - Re: No longer able to add iptunnel interface to bridge?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.1304170119280.20041@envy.nxs.se>
Date:	Wed, 17 Apr 2013 01:22:13 +0200 (CEST)
From:	Tomas Agartz <tlund@....se>
To:	Stephen Hemminger <stephen@...workplumber.org>
Cc:	netdev@...r.kernel.org
Subject: Re: No longer able to add iptunnel interface to bridge?

On Mon, 15 Apr 2013, Stephen Hemminger wrote:

> On Mon, 15 Apr 2013 18:14:32 +0200 (CEST)
> Tomas Agartz <tlund@....se> wrote:
>
>> After rebooting my router/firewall (Debian Wheezy with debian 3.2.41-2 
>> kernel), I am no longer able to add an iptunnel to a bridge interface.
>
>
> You created a network level (L3) tunnel, which starts with IP header. 
> Bridging requires an Ethernet like (L2) tunnel, where packets start with 
> Ethernet header.

Yeah, looking further into this, i figured out a different (unrelated) 
problem that was the real root cause. The fact that the tunnel was never 
added to the bridge (and it has never been) was not related.

Sorry for bothering you guys :)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html