From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs 1/2] pvesdn: add evpn Advertise Subnets && Exit Nodes Local routing options
Date: Mon, 6 Sep 2021 05:57:19 +0200 [thread overview]
Message-ID: <20210906035720.4123158-2-aderumier@odiso.com> (raw)
In-Reply-To: <20210906035720.4123158-1-aderumier@odiso.com>
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
---
pvesdn.adoc | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/pvesdn.adoc b/pvesdn.adoc
index 3b3fd8f..d26c6b9 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -233,6 +233,15 @@ Exit Nodes:: This is used if you want to define some proxmox nodes, as exit
gateway from evpn network through real network. The configured nodes will
announce a default route in the EVPN network.
+Advertise Subnets:: Optional. If you have silent vms/CT (for example, multiples
+ ips by interfaces, and the anycast gateway don't see traffic from theses ips,
+ the ips addresses won't be able to be reach inside the evpn network). This
+ option will announce the full subnet in the evpn network in this case.
+
+Exit Nodes local routing:: Optional. This is a special option if you need to
+ reach a vm/ct service from an exit node. (By default, the exit nodes only
+ allow forwarding traffic between real network and evpn network).
+
MTU:: because VXLAN encapsulation use 50 bytes, the MTU needs to be 50 bytes
lower than the maximal MTU of the outgoing physical interface.
--
2.30.2
next prev parent reply other threads:[~2021-09-06 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 3:57 [pve-devel] [PATCH pve-docs 0/2] sdn: evpn && vxlan improvments Alexandre Derumier
2021-09-06 3:57 ` Alexandre Derumier [this message]
2021-09-10 12:56 ` [pve-devel] applied: [PATCH pve-docs 1/2] pvesdn: add evpn Advertise Subnets && Exit Nodes Local routing options Thomas Lamprecht
2021-09-06 3:57 ` [pve-devel] [PATCH pve-docs 2/2] sdn: add vxlan encryption notes Alexandre Derumier
2021-09-10 13:01 ` [pve-devel] applied: " Thomas Lamprecht
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=20210906035720.4123158-2-aderumier@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
/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.