Hi. I'm testing ipv6 routing on a 3750. I have two vlans set with a global /eui address but cannot ping a windows client attached to one of the vlans either from the router itself or another machine on the same vlan using the global address. I CAN ping no problem using the link-local.
Here is snippets of my config:
switchport access vlan 18
switchport mode access
ip address 10.1.2.1 255.255.255.0
ipv6 address 2001:DB9:C18:1::/64 eui-64
ipv6 route ::/0 Port-channel1
I do not have an uplink to anywhere.. i put the default ipv6 route thinking this was the problem but that had no effect. Channel-group 1 is applied to 2 ports that will eventually be the uplink, but they are currently not connected.
My windows client DOES get a global address - although it is currently duplicate. When it was preferred, it still didn't work, so I don't think this is related.
w32 [C:\WINDOWS] ipv6 if 8
Interface 8: Ethernet: Local Area Connection
zones: link 8 admin 5 site 2
uses Neighbor Discovery
uses Router Discovery
link-layer address: 00-1a-6b-67-82-df
duplicate global 2001:db9:c18:1:21a:6bff:fe67:82df, life 29d23h57m51s/6d23h57m51s (public)
preferred link-local fe80::21a:6bff:fe67:82df, life infinite
multicast interface-local ff01::1, 1 refs, not reportable
multicast link-local ff02::1, 1 refs, not reportable
multicast link-local ff02::1:ff67:82df, 2 refs
link MTU 1500 (true link MTU 1500)
current hop limit 64
reachable time 17500ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
default site prefix length 48
I'm unable to ping the global address from the router or another client on the same vlan. My goal is to be able to ping the global from another vlan, to prove that routing is working. Maybe this is a windows problem? Both clients are Win XP.
Maybe this is a problem with the windows client route table?
w32 [C:\WINDOWS] netsh interface ipv6 show route
Querying active state...
Publish Type Met Prefix Idx Gateway/Interface Name