I'd first try using address ranges that are appropriate. It looks like you are trying to adapt RFC1918 addresses (for IPv4) into IPv6 addresses. For RFC1918 equivalent addresses in IPv6, you probably want RFC4193 addresses. You can use something like https://unique-local-ipv6.com/ to generate your own prefix, that way you are using address space that won't get unusual treatment by the IP stack itself. Second, when using intervals, I always specify an explicit mask. In v6, that means a /128 mask for a single host. I tend to not use intervals unless they fall on a CIDR boundary. That might not work for your needs, but it makes the rules easier, and there's so much address space available in IPv6 that you can usually use CIDR boundaries without issue. I don't know that either of these would change the behavior of your examples, but they might make it easier to identify the problem. Also, be careful about trying to apply IPv4 logic to IPv6 addresses. One is in decimal, the other is in hex. Respectfully, ~Bradley Hook, J.D. Director, Information Systems Google Certified Project Manager Kansas State Schools for the Deaf and the Blind bhook@xxxxxxxxxxxxxx Mobile: 913-275-9982 -- *Kansas State Schools for the Deaf and the Blind Confidentiality Notice**:* The information contained in this e-mail transmission is confidential and legally protected. It is intended for the sole use of the individual(s) entity named in the message header. If you are not the intended recipient, you are hereby notified that any dissemination or copying of this information is strictly prohibited. If you received this message in error, please notify the sender of the error and delete this message and any attachments.
