InformAction Forums

Posted: **Fri Feb 11, 2011 6:08 pm**

Giorgio Maone wrote:
therube wrote:I thought that was an IPv6 address?
(Searches say, "www.exactaudiocopy.de has two IP numbers ...".)
Yes, it's an IPV6 address that looks like belonging to an address range reserved for private (LAN) usage.
However I've looked more closely into this issue, and it seems to actually be a subnetting issue in ABE's local IP checking code.
In fact, while fe80::::feeb:816e would have been a proper link-local address, fe80::21d:92ff:feeb:816e is not, because it falls out the fe80::/64 range set aside for autoconfiguration.

This is going to be fixed in next dev build.

So does that mean that this problem IS with NS/ABE and I should wait for the next update?

Posted: **Fri Feb 11, 2011 8:17 pm**

> So does that mean that this problem IS with NS/ABE and I should wait for the next update?

Yes.

Posted: **Fri Feb 11, 2011 9:09 pm**

/me wonders when this bug would have been found if sites weren't be preparing for IPv6 day.

Posted: **Sat Feb 12, 2011 3:22 am**

dhouwn wrote:/me wonders when this bug would have been found if sites weren't be preparing for IPv6 day.

I recall that I recently added/enabled IPv6 support to WinXP SP3. I wonder if that had anything to do with my problem with EAC site?

Posted: **Sat Feb 12, 2011 11:55 pm**

Fixed in latest development build, thanks.

InformAction Forums

Blocking of EAC

Re: Blocking of EAC

Re: Blocking of EAC

Re: Blocking of EAC

Re: Blocking of EAC

Re: Blocking of EAC