XOA not responding on IPv6

bryonadams

I'm using the free version of the XOA appliance (not sources/paid/etc) and recently I've not been able to connect to XOA's web interface or SSH using v6 addresses. Not sure if it stopped working after a particular update, as I've only recently fixed my DNS in my lab and was using IPv4 addresses for a while.

[22:03 04] xoa@xoa:~$ ss -nl6tp | egrep "State|22|80|443"
State  Recv-Q Send-Q Local Address:Port  Peer Address:PortProcess
LISTEN 0      511                *:80               *:*          
LISTEN 0      128             [::]:22            [::]:*          
LISTEN 0      511                *:443              *:*

Curl attempt from my laptop, which is on the same VLAN as XOA.

bryon@blaptop:~$ curl -v -6 xo.ducknet.org
* Host xo.ducknet.org:80 was resolved.
* IPv6: 2603:xxxx:xxxx:1d02::11
* IPv4: (none)
*   Trying [2603:xxxx:xxxx:1d02::11]:80...
* connect to 2603:xxxx:xxxx:1d02::11 port 80 from 2603:xxxx:xxxx:1d02:e76a:cab:34ad:16f5 port 48918 failed: Aucun chemin d'accès pour atteindre l'hôte cible
* Failed to connect to xo.ducknet.org port 80 after 3073 ms: Could not connect to server
* closing connection #0
curl: (7) Failed to connect to xo.ducknet.org port 80 after 3073 ms: Could not connect to server

I'm not sure how to get tcpdump onto XOA in order to make sure the traffic is making it there, but I'm confident I was able to reach it via IPv6 previously. The only significant change I've made is upgrading xcp-ng to 8.3.

How can I troubleshoot this?

Andrew

@bryonadams Please try HTTPS (tcp port 443).

bryonadams

@Andrew It's the same. It should respond with a 302 to /signin as the login page. It is listening on :80 too, I just forgot it in my filter. I'll edit the correct filter in the post.

AtaxyaNetwork

I just tested, I can curl my XOA with v6 enforced, and ssh with the IPv6 address.

The XOA is a Debian 11 or 12 ?

bryonadams

@AtaxyaNetwork It is Debian 12. I found the problem and will post again if there's more issue. The VM stopped using its static IP, not sure how that happened, but I re-added it to /etc/network/interfaces and it's working again.