I'm not @ikus060 but I tried following the guide and it worked!
I was using a 20GBs disk size LXC container just for a simple Docker container + PostgreSQL, because anything less than that Docker would complain about "disk quota exceeded".
First, some "gotcha"'s that I found while following...
Sorry for the necro but @Vengence did you end up figuring out what was the issue? I have exactly the same issue as you and I just can't figure out *why* restarting the VM/LXC container breaks the IPv6 network.
Changing the IPv6 IP to a new one ends up fixing it but, you know, that's not a good...
What I ended up using is what I said in the third post: I used the experiemental SDN support in Proxmox with VXLAN. It works pretty well without any drawbacks and I haven't found any issues with it (and if I did find any problems, spirit helped me in the SDN thread he has here on the Proxmox...
I will try that later, thanks! :)
I'm not sure how it could be implemented on the GUI tho, because you would need to do a way of "okay, this node will use this IP for VXLAN connections but everyone else will use the default vmbr0 IP"
Also a small issue that I've noticed (which isn't a huge...
Hey @spirit, first off: Thanks for creating this plugin, I'm using it since November in production without any issues and this plugin made me learn so much about how SDN works (way more than my internship, which is also related to sdn, heh) and it works so well!
And now here's a question: Is it...
Today my Backup Job executed again and... no issues happened again!
Maybe that's why everyone stops replying to those threads, because it seems that it only happens very rarely... or maybe it only happens the first time you try backing up a container that has a shared storage or something...
Something that I forgot to mention is that I'm using suspend mode, snapshot doesn't work due to the storage used (damn you, SoYouStart/OVH default Proxmox settings that for some reason doesn't use lvm-thin by default!)
So, this is weird, this happened to me once today (on a automatic scheduled...
@Moayad while I'm not @Frenshow, I'm having the same issue with one of my containers, and both threads (this one too: https://forum.proxmox.com/threads/backups-exit-code-11.77342/ ) no one shared the container configuration or they stopped replying, so the solution was never found.
arch: amd64...
Only vmbr1 and vxlan1 are used for VMs/containers. vmbr1 traffic is forwarded to vmbr0 with a iptables rule.
I may be wrong (not really too good with networking haha) but the vmbr0 is used to ask OVH/SYS servers to get the machine IP, if you remove the vmbr0 interface, you are not able to...
VXLAN, however I think that this issue is not related to the SDN plugin, if I recall correctly this was happening even without any SDN network. (heck, even containers that do not use any SDN network (uses only the local network, "vmbr1" in this case, is breaking). When I installed "ifupdown"...
This is a very strange issue that I'm having on some of my dedicated servers.
Every time I reload the network interfaces with ifupdown2 installed (Example: When applying changes to the SDN network) all traffic in the VMs and containers break.
However there is a fix to this...
echo 0 >...
Okay, so I decided to try it again today:
I have a NAT (10.0.0.1/8) on my dedicated machines, this is used for internet connectivity. (and what I was using for connections between containers/VMs in the same dedicated server)
(Before I was using the 10.0.0.1 net for VXLAN *and* internet...
Thank you! I found out that after I thought "well *maybe* there is a way to change it" and decided to search on Google. I did that change and it worked fine :3
I also fixed the "Next Hop": The issue is that I was using IPs with "/24" for containers (example: "10.0.11.1/24" instead of...
Yes, currently it is over an external IP. And yes, I know that you should encrypt your transport layer when using VXLAN, I was already doing that because I was communicating between my VM/containers via the public IP (by port forwarding) :p
About the network card: Currently I'm using LXC...
I'm not sure if I'm going to be able to check the MTU size, because... well, I'm not the one that has the switch. :P
One of the machines are hosted at OVH, another is hosted at SoYouStart.
Also, the issue that I've mentioned (PostgreSQL failing) is on a container *on the same machine* as the...
When you mean "IP on the bridge", do you mean the "address 10.0.0.1/8" part? If yes, then how can I connect to my VMs/LXC containers from the Proxmox host?
Thanks for helping :), I will try decreasing the MTU, I only increased it because when using 1450 any PostgreSQL clients (example...
Hey, I was testing SDN (with VXLAN) and while it works fine in one single machine, everything *breaks* after I add another machine.
After I added the other machine, connections weren't working... okay, so I allowed connections to "4789" on both machines (via "ufw allow 4789") and, after I did...
Yeah the issue is the "Note that the physical network interface on each node should be connected physically, meaning cabled directly or via a switch.", because in my case the dedicated servers, while they are in the same datacenter, they aren't directly connected between them. :/ (I just rent...
I've also seen a suggestion to use tinc before, but for now I've decided to test out the experimental Software Defined Network feature with VXLANs just to see if it would work. (Because, if it does, then it would fit my use case!)
And... it seems to work pretty well! However I haven't tested in...
I'm not really a networking guy, so forgive me if this is a very stupid question :(
I have two dedicated machines (let's call them Machine1 and Machine2), both of them are running Proxmox, both of them are in the same datacenter (so the latency is very small betweem them) and they are in a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.