search

nsg / nsg

0 stars 0 forks source link

Couldn't find an email addr so I hope I can ask this question here. #1

Open bmullan opened 1 week ago

bmullan commented 1 week ago

In your Blog title:

LXD and VxLAN

You said:

Configure LXD

server1

Configure a new network bridge called br-vxlan, I disabled IPv6 because I do not need it.

What would the config steps be if I did want to use IPv6 ?

nsg commented 1 week ago

I have not tested it, but omitting the ipv6.address=none and then use ipv6 addresses should work. I think.

nsg commented 1 week ago

For reference, this is the output of the config section on my server:

$ lxc network show br-vxlan
config:
  bridge.mtu: "1370"
  ipv4.address: none
  ipv6.address: none
  tunnel.edge.id: "10"
  tunnel.edge.local: 10.0.1.2
  tunnel.edge.protocol: vxlan
  tunnel.edge.remote: 10.0.1.1

Note that both ipv4 and ipv6 are set to none. That's because I did not need LXD to manage IP:s for me on the interface. I have instead manually configured addresses inside the containers and vm:s. The VXLAN will just forward any layer two traffic like any classic network.

In the blog post I initially enabled DHCP assignments (via ipv4) on one system (server1). I do not remember why I stopped with that. Overall, this setup has been really stable and zero trouble for me. Let me know it you need any help and I will try to remember!

bmullan commented 1 week ago

@nsg

Trying to describe my use-case will be tough in a github "issue" & email would be preferred.

But I did some work a few years ago you may find interesting

I'd like to toss a couple ideas by you.
So my email can be found at the above in the How-To Install link.

bmullan commented 4 days ago

Stefan

fyi... I've been using Wireguard/VxLAN together with LXD & Incus for quite a while in different uses. VxWireguard-Generator https://github.com/m13253/VxWireguard-Generator is a great tool to help with configuration and its easy to use.

On Sun, Jun 30, 2024 at 11:18 AM Stefan Berggren @.***> wrote:

For reference, this is the output of the config section on my server:

$ lxc network show br-vxlan config: bridge.mtu: "1370" ipv4.address: none ipv6.address: none tunnel.edge.id: "10" tunnel.edge.local: 10.0.1.2 tunnel.edge.protocol: vxlan tunnel.edge.remote: 10.0.1.1

Note that both ipv4 and ipv6 are set to none. That's because I did not need LXD to manage IP:s for me on the interface. I have instead manually configured addresses inside the containers and vm:s. The VXLAN will just forward any layer two traffic like any classic network.

— Reply to this email directly, view it on GitHub https://github.com/nsg/nsg/issues/1#issuecomment-2198595419, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM23J4SWW3ZX27LAW55NTTZKAOU7AVCNFSM6AAAAABKEFQZX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGU4TKNBRHE . You are receiving this because you authored the thread.Message ID: @.***>