Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support vxlan unicast configuration #5145

Closed
1 of 2 tasks
joejulian opened this issue Jan 24, 2017 · 4 comments · Fixed by #12441
Closed
1 of 2 tasks

Support vxlan unicast configuration #5145

joejulian opened this issue Jan 24, 2017 · 4 comments · Fixed by #12441
Labels
network RFE 🎁 Request for Enhancement, i.e. a feature request

Comments

@joejulian
Copy link

Submission type

  • Bug report
  • Request for enhancement (RFE)

NOTE: Do not submit anything other than bug reports or RFEs via the issue tracker!

systemd version the issue has been seen with

232

NOTE: Do not submit bug reports about anything but the two most recently released systemd versions upstream!

Used distribution

Arch

Sometimes network providers do not allow multicast communication. In this instance, vxlans need to be configured using multiple unicast endpoints. This is done by appending additional zero MAC entries to the fdb.

Please add support for configuring these in netdev.
@ssahani
Copy link
Contributor

ssahani commented Jan 27, 2017

Could you please give a example for it ? Thanks !

@joejulian
Copy link
Author

https://joejulian.name/blog/how-to-configure-linux-vxlans-with-multiple-unicast-endpoints/

@joejulian
Copy link
Author

I would expect to configure it such as:

[VXLAN]
Id=42
Endpoint=10.0.0.1
Endpoint=10.1.0.1
Endpoint=10.2.0.1

@poettering poettering added network RFE 🎁 Request for Enhancement, i.e. a feature request labels Feb 1, 2017
ssahani pushed a commit to ssahani/systemd that referenced this issue Apr 30, 2019
networkd: Add support to configure bridge FDB.
732de3a 
Closes systemd#5145

```
[Match]
Name=vxlan1309

[BridgeFDB]
MACAddress=00:00:00:00:00:00
DestinationAddress=10.0.0.2

[BridgeFDB]
MACAddress=00:00:00:00:00:00
DestinationAddress=10.0.0.4

[BridgeFDB]
MACAddress=00:00:00:00:00:00
DestinationAddress=10.0.0.5

```
@ssahani ssahani mentioned this issue Apr 30, 2019
Merged
@ssahani
Copy link
Contributor

ssahani commented Apr 30, 2019

https://joejulian.name/blog/how-to-configure-linux-vxlans-with-multiple-unicast-endpoints/

since it's a bridge fdb I have added to the [BridgeFDB] section also Please see the example conf how to apply to vxlan.

yuwata pushed a commit to ssahani/systemd that referenced this issue May 3, 2019
@yuwata
networkd: Add support to configure destination address for bridge FDB
c2c2793 
Closes systemd#5145.

Example conf:
```
[Match]
Name=vxlan1309

[BridgeFDB]
MACAddress=00:00:00:00:00:00
Destination=10.0.0.2

[BridgeFDB]
MACAddress=00:00:00:00:00:00
Destination=10.0.0.4

[BridgeFDB]
MACAddress=00:00:00:00:00:00
Destination=10.0.0.5
```
edevolder pushed a commit to edevolder/systemd that referenced this issue Jun 26, 2019
@edevolder
networkd: Add support to configure destination address for bridge FDB
c039da6 
Closes systemd#5145.

Example conf:
```
[Match]
Name=vxlan1309

[BridgeFDB]
MACAddress=00:00:00:00:00:00
Destination=10.0.0.2

[BridgeFDB]
MACAddress=00:00:00:00:00:00
Destination=10.0.0.4

[BridgeFDB]
MACAddress=00:00:00:00:00:00
Destination=10.0.0.5
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
network RFE 🎁 Request for Enhancement, i.e. a feature request
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

networkd: add support for bridge fdb destination address. ssahani/systemd
4 participants
@ssahani @joejulian @poettering @yuwata