No longer able to add iptunnel interface to bridge?

No longer able to add iptunnel interface to bridge?

[Tomas Agartz]

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.

The iptunnel is configured like this:

iptunnel add TUNNEL mode ipip remote x.x.x.x local y.y.y.y ttl 32
ifconfig TUNNEL z.z.z.z netmask 255.255.255.254 up

and this is what strace shows when I try to do "brctl addif test TUNNEL":

ioctl(3, SIOCBRADDIF, 0x7fffafba64c0)   = -1 EINVAL (Invalid argument)
ioctl(3, SIOCDEVPRIVATE, 0x7fffafba64c0) = -1 EINVAL (Invalid argument)

I have no idea if I might have changed something in userspace by misstake, 
or if there has been a change in the kernel since last reboot. The same 
machine has a different bridge with an L2TPv3 tunnel added, this works 
fine.

I understand that the info here is not much to go on, but I am unsure what 
else to attach. Plese ask for further info and I shall provide it!

Best regards,
Tomas

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

[Stephen Hemminger]

On Mon, 15 Apr 2013 18:14:32 +0200 (CEST)
Tomas Agartz <tlund@nxs.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.
> 
> The iptunnel is configured like this:
> 
> iptunnel add TUNNEL mode ipip remote x.x.x.x local y.y.y.y ttl 32
> ifconfig TUNNEL z.z.z.z netmask 255.255.255.254 up
> 
> and this is what strace shows when I try to do "brctl addif test TUNNEL":
> 
> ioctl(3, SIOCBRADDIF, 0x7fffafba64c0)   = -1 EINVAL (Invalid argument)
> ioctl(3, SIOCDEVPRIVATE, 0x7fffafba64c0) = -1 EINVAL (Invalid argument)
> 
> I have no idea if I might have changed something in userspace by misstake, 
> or if there has been a change in the kernel since last reboot. The same 
> machine has a different bridge with an L2TPv3 tunnel added, this works 
> fine.
> 
> I understand that the info here is not much to go on, but I am unsure what 
> else to attach. Plese ask for further info and I shall provide it!
> 
> Best regards,
> Tomas
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

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.

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

[Tomas Agartz]

On Mon, 15 Apr 2013, Stephen Hemminger wrote:

> On Mon, 15 Apr 2013 18:14:32 +0200 (CEST)
> Tomas Agartz <tlund@nxs.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 :)