Bug. Fail to detect IPv6 on the VPS server.

Submitted by Chris_C on Tue, 02/03/2015 - 15:22

Steps to reproduce:

  1. setup free ipv6 tunnel via hurricane electric tunnel broker.

  2. Go to System settings, Virtualmin Configuration, Network settings.

Default virtual server IPv6 address: enter a valid IPv6 from the tunnel public /64 allocation.

Network interface for IPv6 addresses: enter the interface name (for example, tb)

Netmask size for IPv6 addresses (Default 64) : Default.

Use default IPv6 address for new virtual servers: Yes.

Save.

  1. Go to Create Virtual Server, IP Addresses and Forwarding.

IPv6 address: Not supported on this system.

Why does Virtualmin fail to detect IPv6?

IPv6 is enabled on the System Settings, Virutalmin Config, Network settings.

And the IPv6 addresses work.

You can ping from the server, to outside ipv6 servers (ping6 www.apple.com).

And you can tracert and ping6, from your local notebook or desktop, over the IPv6 internet, to the virtualmin vps server's IPv6 address.

Status: 
Active

Comments

Submitted by JamieCameron on Tue, 02/03/2015 - 18:13

Can you post the output from the ifconfig -a and ip addr commands? It looks like Webmin may not be detecting that IPv6 is enabled on your primary IP address..

Submitted by Chris_C on Wed, 02/04/2015 - 12:00

Hi Jamie, Seems the assumption about where the IPv6 addresses are enabled, is not right.

IPv6 isn't enabled on the primary IP address's interface. IPv6 is enabled a separate net interface.

So IPv4 is on venet0:0 and venet0:1 and those work fine after having specified them in the config. And IPv6 is enabled on tb (multiple IPv6 addresses are on this one interface).

tb is an interface that is created after bootup by a script that automatically runs. it's a vpn tunnel connected to the he.net tunnelbroker service for providing IPv6. Very common.

In webmin , networking, network configuration, network interfaces, activated at boot, under "venet0", "IPv6 adddress", it says "From IPv6 discovery".

tb interface is listed only under "active now", not "activate at boot".

# ifconfig -a
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:18708557 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18708557 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9124530827 (8.4 GiB)  TX bytes:9124530827 (8.4 GiB)

tb        Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: aaaa:bbb:cccc:ddd::1/64 Scope:Global
          inet6 addr: aaaa:bbb:cccc:eee::2/64 Scope:Global
          inet6 addr: aaaa:bbb:cccc:ddd::2/64 Scope:Global
          inet6 addr: aaaa:bbb:cccc:ddd::3/64 Scope:Global
          inet6 addr: aaaa:bbb:cccc:ddd::4/64 Scope:Global
          inet6 addr: aaaa:bbb:cccc:ddd::5/64 Scope:Global
          inet6 addr: aaaa:bbb:cccc:ddd::6/64 Scope:Global
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1480  Metric:1
          RX packets:38307 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60731 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:13966703 (13.3 MiB)  TX bytes:10479478 (9.9 MiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:127.0.0.2  P-t-P:127.0.0.2  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:44533709 errors:0 dropped:0 overruns:0 frame:0
          TX packets:46319632 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:27382295126 (25.5 GiB)  TX bytes:10222920998 (9.5 GiB)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:aaa.bbb.ccc.ddd  P-t-P:aaa.bbb.ccc.ddd  Bcast:aaa.bbb.ccc.ddd  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1

venet0:1  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:aaa.bbb.ccc.eee  P-t-P:aaa.bbb.ccc.eee  Bcast:aaa.bbb.ccc.255  Mask:255.255.255.0
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1

# ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever

2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/void
    inet 127.0.0.2/32 scope host venet0
    inet aaa.bbb.ccc.ddd/24 brd aaa.bbb.ccc.255 scope global venet0:1
    inet aaa.bbb.ccc.eee/32 brd aaa.bbb.ccc.eee scope global venet0:0

5: tb: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1480 qdisc pfifo_fast state UNKNOWN qlen 500
    link/none
    inet6 aaaa:bbb:cccc:eee::2/64 scope global
       valid_lft forever preferred_lft forever
    inet6 aaaa:bbb:cccc:ddd::1/64 scope global
       valid_lft forever preferred_lft forever
    inet6 aaaa:bbb:cccc:ddd::2/64 scope global
       valid_lft forever preferred_lft forever
    inet6 aaaa:bbb:cccc:ddd::3/64 scope global
       valid_lft forever preferred_lft forever
    inet6 aaaa:bbb:cccc:ddd::4/64 scope global
       valid_lft forever preferred_lft forever
    inet6 aaaa:bbb:cccc:ddd::5/64 scope global
       valid_lft forever preferred_lft forever
    inet6 aaaa:bbb:cccc:ddd::6/64 scope global
       valid_lft forever preferred_lft forever

#

Submitted by JamieCameron on Wed, 02/04/2015 - 18:03

Ok, that's an interesting setup .... but it should work.

If you go to Webmin -> Networking -> Network Configuration -> Network Interfaces -> Active Now, does the tp interface show up, and does it have IPv6 addresses assigned?

Submitted by Chris_C on Sat, 02/07/2015 - 11:36

Yes they are on that screen "Active Now". The reason is because the addresses are created by a script on system start, which establishes the VPN tunnel to the he.net IPv6 tunnel broker service.

Submitted by JamieCameron on Sat, 02/07/2015 - 12:50

Ok, so it looks like Webmin it detected the IPv6 tunnel address.

If you SSH into the system as root and run virtualmin check-config , does it display a message like "Default IPv6 address for virtual servers is 2001:db8:0:f101::105" ? If not, does it mention IPv6 at all?

Submitted by Chris_C on Sat, 02/07/2015 - 17:07

Ran the command.

All that it says about IP addresses is:

Using network interface venet0:0 for virtual IPs.

Default IPv4 address for virtual servers is a.b.c.d.

Default IP address is set to a.b.c.d, but the detected external address is actually a.b.c.e. This is typically the result of being behind a NAT firewall, and should be corrected on the module configuration page.

Submitted by JamieCameron on Sun, 02/08/2015 - 12:40

Ok, I see the bug now - Virtualmin is ignoring interfaces that don't have an IPv4 address when checking for IPv6 support, which is wrong (and will be fixed). Until then, you can work around this by assigning an IP like 10.1.1.1 to your tb interface and then re-doing the configuration check.

Also, on the Virtualmin Configuration page under Networking settings, you should set "Network interface for IPv6 addresses" to tb