Hi guys,
Not sure if this is a bug or something I'm doing wrong, but I've added IPv6 addresses to some of my domains and I'm getting reports in the validation emails that say things like:
IPv6 address : No active IPv6 address 2001:0ba8:01f1:f1de:0000:0000:00f5:0 found
When I run ifconfig to check however, they're definitely showing up (and I can definitely reach those sites on those IPs by telnetting to port 80 of each IP):
eth0 Link encap:Ethernet HWaddr 00:16:5e:00:02:51
inet addr:212.13.195.100 Bcast:212.13.195.255 Mask:255.255.254.0
inet6 addr: 2001:ba8:1f1:f1de::2/64 Scope:Global
inet6 addr: 2001:ba8:1f1:f1de::f5:2/64 Scope:Global
inet6 addr: 2001:ba8:1f1:f1de::f5:3/64 Scope:Global
inet6 addr: fe80::216:5eff:fe00:251/64 Scope:Link
inet6 addr: 2001:ba8:1f1:f1de::f5:0/64 Scope:Global
inet6 addr: 2001:ba8:1f1:f1de::f5:1/64 Scope:Global
inet6 addr: 2001:ba8:1f1:f1de::f5:4/64 Scope:Global
inet6 addr: 2001:ba8:1f1:f1de::f5:5/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13067108 errors:0 dropped:0 overruns:0 frame:0
TX packets:12533992 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1875189100 (1.8 GB) TX bytes:2550566138 (2.5 GB)
Interrupt:9
Did I forget to configure something? The IP range was added to Virtualmin, and then they were assigned to the domains, as I was instructed in a previous ticket about IPv6.
This isn't really urgent, things are indeed working fine it's just some extra lines in the validation emails, but thought I should check in with you guys all the same.
Comments
Submitted by JamieCameron on Wed, 04/20/2011 - 22:55 Comment #1
Looks like a mismatch between the long and short forms of the IPv6 address ..
How did you add the addresses to your domains?
Submitted by JamieCameron on Wed, 04/20/2011 - 23:54 Comment #2
Ok, I see the cause now .. Virtualmin is incorrectly comparing two different IPv6 address formats (long vs short). I will fix this in the next release (3.85).
Submitted by arussell on Thu, 04/21/2011 - 11:53 Pro Licensee Comment #3
Thanks! :)
Submitted by Issues on Thu, 05/05/2011 - 12:21 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.
Submitted by arussell on Mon, 05/30/2011 - 05:07 Pro Licensee Comment #5
Reopening: I'm still seeing this issue in 3.85, unfortunately.
Submitted by JamieCameron on Mon, 05/30/2011 - 13:07 Comment #6
Are you still getting the exact same validation error?
Submitted by arussell on Wed, 06/01/2011 - 05:08 Pro Licensee Comment #7
Hi Jamie, yeah exact same error in the nightly emails. Here's one from last night's email: IPv6 address : No active IPv6 address 2001:0ba8:01f1:f1de:0000:0000:00f5:0 found
Submitted by JamieCameron on Wed, 06/01/2011 - 15:53 Comment #8
Ok, I found another bug in Virtualmin's code for canonicalizing IPv6 addresses that causes this to still fail :-(
It will be fixed in the 3.56 Virtualmin release.
Submitted by Issues on Thu, 06/16/2011 - 01:22 Comment #9
Automatically closed -- issue fixed for 2 weeks with no activity.