For ease of administration and easier hierarchical design, we want to use longer prefixes on our subnets.
For example, we want /120 subnets for small networks and so forth.
Cisco equipment seems to have no problem with this. However, Windows (XP, 2003, Vista, and 2008) all seem to want to use /64 only, which leads to routing problems. These machines can communicate fine on their local subnet, but cannot communicate with other hosts that would have otherwise been on the same /64 but are not on their local /120 vlan.
Example:
Subnet 1: AAAA:BBBB:CCCC::0/120
Subnet 2: AAAA:BBBB:CCCC::100/120
Router 1: AAAA:BBBB:CCCC::1/120
Router 2: AAAA:BBBB:CCCC::101/120
Host 1: AAAA:BBBB:CCCC::2/64
Host 2: AAAA:BBBB:CCCC::102/64
Routers are at separate sites, connected via a GRE tunnel.
The routers can ping each other's ethernet interfaces through the tunnel and both networks show up in both routers' tables (using EIGRP as routing protocol).
The routers can also ping the hosts local to them.
However, as expected, given the prefixes, the hosts cannot reach each other, since they do not bother to talk to the router.
When I try to set the addresses for the hosts as:
Host 1:AAAA:BBBB:CCCC::2/120
Host 2:AAAA:BBBB:CCCC::102/120
Windows just sets the prefixes back to /64.
How can I alter this behavior, or is it even possible on Windows?
Thanks