Extra: according to chatgtp \ud83d\ude00
this also can be achieved using VXLAN setup
Below is this VXLAN setup ( did not tried or experiment this – just for extra information )<\/p>\n\n\n\n
Alright \u2014 here\u2019s the VXLAN version of your setup.
VXLAN is nice because it uses UDP (default port 4789), which almost always passes through firewalls\/NAT, and it\u2019s still Layer 2 capable like gretap.<\/p>\n\n\n\n
Network Recap
Provider A (Debian VM) Provider B (Proxmox Node)
Public IP: 38.248.1.150 Public IP: 185.17.1.2
\/24: 38.248.1.0\/24 (lives in Provider A)
\/24 Gateway: 38.248.1.1
Goal: VMs in Provider B keep using their old IPs + gateway over the tunnel<\/p>\n\n\n\n
On Provider A (Debian VM)<\/p>\n\n\n\n
apt install bridge-utils iproute2<\/p>\n\n\n\n
ip link add vxlan100 type vxlan id 100 \\
dev eth0 \\
remote 185.17.1.2 \\
dstport 4789 \\
local 38.248.1.150 \\
ttl 255<\/p>\n\n\n\n
ip link set vxlan100 up mtu 1450<\/p>\n\n\n\n
brctl addbr br0
brctl addif br0 eth0
brctl addif br0 vxlan100<\/p>\n\n\n\n
ip addr flush dev eth0
ip addr add 38.248.1.150\/24 dev br0
ip link set br0 up
ip route add default via 38.248.1.1<\/p>\n\n\n\n
On Provider B (Proxmox Node)
Edit \/etc\/network\/interfaces:<\/p>\n\n\n\n
auto vxlan100
iface vxlan100 inet manual
pre-up ip link add vxlan100 type vxlan id 100 \\
dev eth0 \\
remote 38.248.1.150 \\
dstport 4789 \\
local 185.17.1.2 \\
ttl 255
up ip link set vxlan100 up mtu 1450
post-down ip link del vxlan100<\/p>\n\n\n\n
auto vmbr2
iface vmbr2 inet manual
bridge_ports vxlan100
bridge_stp off
bridge_fd 0<\/p>\n\n\n\n
! Do not assign the \/24 to vmbr2. This bridge is purely for the VMs.<\/p>\n\n\n\n
On a Migrated VM in Provider B
Same config as if it were still in Provider A:<\/p>\n\n\n\n
IP: 38.248.1.152
Netmask: 255.255.255.0
Gateway: 38.248.1.1
<\/p>\n\n\n\n
Firewall \/ Networking Notes
Allow UDP\/4789 in both directions (between 38.248.1.150 \u2194 185.17.1.2).<\/p>\n\n\n\n
MTU must be reduced to ~1450 (or lower if path MTU is smaller).<\/p>\n\n\n\n
Some providers have \u201canti-MAC spoofing\u201d \u2014 if so, you may need to request that they disable it for the VXLAN tunnel endpoints.<\/p>\n\n\n\n
Testing
On Provider B:<\/p>\n\n\n\n
bridge link show
Should show vxlan100 as a port in vmbr2.<\/p>\n\n\n\n
From the migrated VM in Provider B:<\/p>\n\n\n\n
ping 38.248.1.1
If it works, you\u2019ve got transparent L2 connectivity over VXLAN.<\/p>\n\n\n\n
GRE vs VXLAN Quick Comparison Extra: according to chatgtp \ud83d\ude00this also can be achieved using VXLAN setupBelow is this VXLAN setup ( did not tried or experiment this – just for extra information ) Alright \u2014 here\u2019s the VXLAN version of your setup.VXLAN is nice because it uses UDP (default port 4789), which almost always passes through firewalls\/NAT, and it\u2019s […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1683","post","type-post","status-publish","format-standard","hentry","category-kategerisiz"],"_links":{"self":[{"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/posts\/1683","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/comments?post=1683"}],"version-history":[{"count":3,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/posts\/1683\/revisions"}],"predecessor-version":[{"id":1686,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/posts\/1683\/revisions\/1686"}],"wp:attachment":[{"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/media?parent=1683"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/categories?post=1683"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.shukko.com\/x3\/wp-json\/wp\/v2\/tags?post=1683"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/strong>Feature GRE\/gretap VXLAN
Layer 2 capable gretap only Yes
Encapsulation Protocol 47 (GRE) UDP
Likely to pass firewalls Lower Higher
Overhead ~24 bytes ~50 bytes
MTU impact Moderate Slightly more<\/p>\n","protected":false},"excerpt":{"rendered":"