All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
help needed for proxmox to proxmox gre tunnel
recently I posted a discussion about the less amount of downtime when migrating customers from a proxmox node from a provider to another proxmox node in aother provider. (with moving the /24 ipv4 block between providers)
at the end of discussion with kind help from fellow let citizens the best way looks like creating a GRE TUNNEL between provider A and provider B and using ip addresess from provider A in provider B by the help of the GRE TUNNEL and after all the migrating done, Migrate the /24 from old AS# to new AS# in the new provider.
What I've done:
gre tunnel is easy. Is up and running in under 2 mins.
BUT to route ips currently used by KVM VM's in Provider A in Provider B gives a lot of headaches.
for not to mess up with the current production system I created a new debian Vm in provider A and set up the GRE tunnel between this VM and new Proxmox node on provider B (New proxmox node is empty)
created a vmbr2 bridge in Provider B proxmox node and assign the Gre Tunnel as bridge interfece to that.
After all the failed attempts ( Doing NAT with Real Ips etc, even Creating an openVPN tunnel instead of GRE, I am yet to be able to route any ip from Provider A VM to Provider B proxmox node)
I searched and searched, Trying to steer myself away of DUMB AI suggestions, Trying translating German, Russian, even Arabic ancient forum posts. But no Luck)
I failed miserably at the moment.
I need help about this.
Below is my current setup ( Ip addressess are imaginary) Can someone please point me to right direction?
Provider A:
Debian VM:
ip: 38.248.1.150
Gateway: 38.248.1.1
Provider B:
Empty proxmox Node:
ip: 185.17.1.2
Gateway: 185.17.1.1
Gre setup:
Debian VM:
ip tunnel add gre1 mode gre local 38.248.1.150 remote 185.17.1.2 ttl 255
ip link set gre1 up
ip addr add 172.18.185.57/30 dev gre1
Proxmox Node:
ip tunnel add gre1 mode gre local 185.17.1.2 remote 38.248.1.150 ttl 255
ip link set gre1 up
ip addr add 172.18.185.58/30 dev gre1
GRE TUNNEL UP AND RUNNING.
Proxmox Node:
auto vmbr2
iface vmbr2 inet static
address 38.248.1.151/24
gateway 38.248.1.1
bridge-ports gre1
bridge-stp off
bridge-fd 0
Promox Node: Migrated VM From Provider A:
Net0 Network Device: Bridge vmbr2
Migrated VM Ip: 38.248.1.152
Migrated VM Gateway: 38.248.1.1
Right here without any NAT nonsense I need to create a routing setup between my vmbr2 and and the GRE Interface.
This Is what I need help with.
Thank you all..
Comments
PROBLEM SOLVED:
SOLUTION:
for those who interested after my original post with more trial and error here is the solution for my use case.
On Provider A (Debian VM)
On Provider B (Proxmox Node)
edit /etc/network/interfaces
auto gre1 iface gre1 inet manual pre-up ip link add gre1 type gretap local 185.17.1.2 remote 38.248.1.150 ttl 255 up ip link set gre1 up mtu 1450 post-down ip link del gre1 auto vmbr2 iface vmbr2 inet manual bridge_ports gre1 bridge_stp off bridge_fd 0 mtu 1476 # see below for extra notesend edit and reboot
Migrate a VM to Provider A to Provider B
Migrated VM network settings - keep everything intact and original
IMPORTANT NOTE:
Because GRE uses more encapsulation overhead.
Lower the MTU in Provider B side
I set the MTU values as below and seems like working (may need a little bit more tweaking)
Provider B Proxmox node set vmbr2 MTU 1476 - already setup in /etc/network/interfaces
On Proxmox node side: Provider B Migrated VM: set net0 network device MTU 1400
EXTRA: Mandatory Tests:
From Migrated VM with ip address 38.248.1.152
From My own office connection to Migrated VM
Hmm
Nice, sincerely,
I would VXLAN it the next time, but if that works, +1