From: Mihail Dakov <mihail@ng4t.com>
To: netdev@vger.kernel.org
Subject: fou: udp encapsulation - how to configure multiple ports per tunnel
Date: Mon, 30 Jan 2017 15:52:00 +0100 [thread overview]
Message-ID: <d7f24185-46c4-d038-7a5e-a0bd3ee4ec58@ng4t.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 802 bytes --]
Hi there,
I am having trouble setting up the following tunnels on the tx path.
#!/bin/bash
sudo ip link add name fou11 \
type ipip \
remote 192.168.1.1 \
local 192.168.2.1 \
encap fou \
encap-sport 21001 \
encap-dport 21001
sudo ip link add name fou21 \
type ipip \
remote 192.168.1.1 \
local 192.168.2.1 \
encap fou \
encap-sport 21002 \
encap-dport 21002
this script returns:
RTNETLINK answers: File exists
which tells me that the kernel doesn't use sport and/or dport to
identify a tunnel.
Is it possible to configure a tunnel with different dport and/or sport?
If so how?
P.S. On the other hand if this was possible then the kernel would need
some policy to decide which dport and/or sport to use for each packet
arriving in this tunnel.
br,md.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2017-01-30 15:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d7f24185-46c4-d038-7a5e-a0bd3ee4ec58@ng4t.com \
--to=mihail@ng4t.com \
--cc=netdev@vger.kernel.org \
/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