From: Stephen Hemminger <stephen@networkplumber.org>
To: Tomas Agartz <tlund@nxs.se>
Cc: netdev@vger.kernel.org
Subject: Re: No longer able to add iptunnel interface to bridge?
Date: Mon, 15 Apr 2013 11:12:13 -0700 [thread overview]
Message-ID: <20130415111213.62c4d117@samsung-9> (raw)
In-Reply-To: <Pine.LNX.4.61.1304151757340.20041@envy.nxs.se>
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.
next prev parent reply other threads:[~2013-04-15 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 16:14 No longer able to add iptunnel interface to bridge? Tomas Agartz
2013-04-15 18:12 ` Stephen Hemminger [this message]
2013-04-16 23:22 ` Tomas Agartz
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=20130415111213.62c4d117@samsung-9 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=tlund@nxs.se \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox