<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I picked up an old and out-of-support FGS648P for my basement
(overkill, yes, but the PoE was nice for $110 CAD! Plus I wanted to
play with a managed switch). Software version 04.1.00aT7e1, Feb 19
2008 vintage.
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<br>
<br>
I used to have IPV6 enabled on the internal network based on my
ISP's allocated /56, which I advertise on my router's LAN interface
using radvd (/64). All this worked on my old, unmanaged switch.<br>
<br>
With the Foundry, I have found that non-link-local IPV6 traffic
internal to my home network won't transit the switch, or rather,
that neighbour discovery won't, saying that the destination was
unreachable. Link-local <i>does</i> transit the switch. Swapping
out the Foundry for the unmanaged switch, the neighbour discovery
works again, so that all IPV6 traffic can transit; it is definitely
the switch at fault. Can anybody suggest what I might be able to
correct? Do I need a new software image (and, where the heck could
I get a newer image given that I cannot even buy support if I wanted
to)?<br>
<br>
SSH@FGS648P Switch(config)#show flash <br>
Compressed Pri Code size = 2864799, Version 04.1.00aT7e1
(FGS04100a.bin)<br>
Compressed Sec Code size = 2864799, Version 04.1.00aT7e1
(FGS04100a.bin)<br>
Compressed BootROM Code size = 405217, Version 04.0.00T7e5<br>
Code Flash Free Space = 2424832<br>
<br>
SSH@FGS648P Switch>show ipv6<br>
Global Settings<br>
IPv6 is enabled<br>
Link-local address(es):<br>
fe80::212:f2ff:fe89:ef80 [Preferred]<br>
Global unicast address(es):<br>
2607:f2c2:f00e:b700:212:f2ff:fe89:ef80 [Preferred], subnet is
2607:f2c2:f00e:b700::/64<br>
Joined group address(es):<br>
ff02::1:ff89:ef80<br>
ff02::1<br>
MTU is 1500 bytes <br>
ND DAD is enabled, number of DAD attempts: 3<br>
ND reachable time is 30 seconds<br>
ND retransmit interval is 1 seconds<br>
Current Hop Limit is 64<br>
Hosts use stateless autoconfig for addresses<br>
No Inbound Access List Set<br>
No Outbound Access List Set<br>
IPv6 Domain Name: romanus.ca<br>
IPv6 DNS Server Address:<br>
2607:f2c0::1<br>
<br>
I can ping the switch on it's link-local address, but not the global
unicast that I manually assigned (out of my /64).<br>
<br>
SSH@FGS648P Switch(config)#ipv6 ?<br>
access-class Filter incoming/outgoing connections<br>
access-list Build ipv6 access lists<br>
address Assign IPv6 address to this switch router<br>
dns Set DNS properties<br>
enable Enable IPv6<br>
mld-snooping Set MLD snooping globally<br>
<br>
(There doesn't seem to be a lot I can configure here....)<br>
<br>
SSH@FGS648P Switch#debug ipv6 ?<br>
address Packet for ipv6 address<br>
cache IPv6 cache entry<br>
icmp ICMPv6<br>
mld MLD protocol activity<br>
nd Neighbor Discovery<br>
packet IPv6 packet<br>
ra Router Advertisement<br>
<br>
SSH@FGS648P Switch#show debug<br>
Debug message destination: Console<br>
Enabling ACL log<br>
IPv6 Routing:<br>
ipv6: address fe80::212:f2ff:fe89:ef80 debugging is on<br>
ipv6: icmp debugging is on<br>
ipv6: nd debugging is on<br>
ipv6: ra debugging is on<br>
ipv6: packet debugging is on<br>
<br>
<br>
I've turned these on, but I don't know where the debug messages go
to... if console, as implied by show debug, I see nothing even when
I successfully ping fe80::212:f2ff:fe89:ef80<br>
</body>
</html>