IPv6 routed configuration

dauphintordu

New Member
Dec 29, 2023
4
0
1
Hello,

I've some issues regarding a routed ipv6 configuration that I've setuped.
What I want to do: host virtual machine with ipv6 public ips and access those vm from anywhere.

Here is what I've setuped so far:

Bash:
auto lo
iface lo inet loopback

iface eno2 inet manual

iface eno3 inet manual

iface eno4 inet manual

iface enp5s0f0np0 inet manual

iface enp5s0f1np1 inet manual

iface eno1 inet static
        address xxx.xxx.100.36/25
        gateway xxx.xxx.xxx.126
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward
        post-up echo 1 > /proc/sys/net/ipv4/conf/eno1/proxy_arp

iface eno1 inet6 static
        address xxx:e300::36/48
        gateway xxx:e300::126

auto vmbr1
iface vmbr1 inet static
        address 192.168.1.1/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0
#LAN

auto vmbr2
iface vmbr2 inet static
        address 192.168.9.1/24
        bridge-ports none
        bridge-stp off
        bridge-fd 0
#Private LAN

auto vmbr0
iface vmbr0 inet manual
        bridge-ports none
        bridge-stp off
        bridge-fd 0

auto vmbr3
iface vmbr3 inet6 static
        address xxx:e300:9::1/48
        bridge-ports none
        bridge-stp off
        bridge-fd 0

Here is the conf of systctl.conf:
Bash:
# Uncomment the next line to enable packet forwarding for IPv4
net.ipv4.ip_forward=1
net.ipv4.conf.all.proxy_arp=1

# Uncomment the next line to enable packet forwarding for IPv6
#  Enabling this option disables Stateless Address Autoconfiguration
#  based on Router Advertisements for this host
net.ipv6.conf.all.forwarding=1

Here are the route:

Bash:
default via xxx.xxx.100.126 dev eno1 proto kernel onlink
xxx.xxx.100.0/25 dev eno1 proto kernel scope link src xxx.xxx.100.36
192.168.1.0/24 dev vmbr1 proto kernel scope link src 192.168.1.1
192.168.9.0/24 dev vmbr2 proto kernel scope link src 192.168.9.1

Bash:
xxxx:e300::/48 dev eno1 proto kernel metric 256 pref medium
xxxx:e300:9::/48 dev vmbr3 proto kernel metric 256 pref medium
fe80::/64 dev fwpr100p0 proto kernel metric 256 pref medium
fe80::/64 dev fwpr108p0 proto kernel metric 256 pref medium
fe80::/64 dev fwpr108p1 proto kernel metric 256 pref medium
fe80::/64 dev fwpr100p1 proto kernel metric 256 pref medium
fe80::/64 dev eno1 proto kernel metric 256 pref medium
fe80::/64 dev fwpr111p1 proto kernel metric 256 pref medium
fe80::/64 dev fwpr111p0 proto kernel metric 256 pref medium
fe80::/64 dev fwpr106p0 proto kernel metric 256 pref medium
fe80::/64 dev vmbr1 proto kernel metric 256 pref medium
fe80::/64 dev vmbr2 proto kernel metric 256 pref medium
fe80::/64 dev vmbr0 proto kernel metric 256 pref medium
fe80::/64 dev vmbr3 proto kernel metric 256 pref medium
default via xxxx:e300::126 dev eno1 proto kernel metric 1024 onlink pref medium

I tried to host a vm with the ip address xxx:e300:9::10/48 and gateway xxx:e300:9::1
When I try to access it from somewhere else, it failed instantanetly and I get an NS_ERROR_CONNECTION_REFUSED

I clearly don't understand what I'm doing wrong here to be honest...

If you have any idea how to troubleshoot deeper, be my guest

Thank you in advance !
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!