Hi,
looking at
Time Message
Fri Sep 6 08:30:03 2013 dhcp6_ctl_authinit: failed to open /var/etc/dhcp6sctlkey: No such file or directory
Fri Sep 6 08:30:03 2013 Exiting, permissions on conf_file invalid.
Fri Sep 6 08:30:03 2013 can't open /var/run/radvd.LAN-6.conf: No such file or directory
Fri Sep 6 08:28:03 2013 main: failed to parse configuration file
Fri Sep 6 08:28:03 2013 yyerror0: /var/run/dhcps6.LAN-4.conf 7: fatal parse failure: exiting (1 errors)
Fri Sep 6 08:28:03 2013 yyerror0: /var/run/dhcps6.LAN-4.conf 7: syntax error
Fri Sep 6 08:28:03 2013 Exiting, failed to read config file.
Fri Sep 6 08:28:03 2013 error parsing or activating the config file: /var/run/radvd.LAN-4.conf
Fri Sep 6 08:28:03 2013 syntax error in /var/run/radvd.LAN-4.conf, line 23: -1
Fri Sep 6 08:28:03 2013 Exiting, sigterm or sigint received.
it is quite obvious, that for whatever reason the config files for both the radvd and dhcpv6 service are erroneous and hence unreadable which in turn produces syntax errors and parsing failures when the starting processes try to read them. As a consequence neither radvd nor the DHCPv6 server will start.
Given you use the
Autoconfiguration Type "
SLAAC+Stateless DHCP" when radvd is not running the router won't send any router advertisements into the LAN. That's why your LAN PCs won't learn any global IPv6 addresses from the /64 prefix your router has learned from your ISP by DHCP-PD. If in addition the DHCPv6 server is not running your LAN PCs won't learn any IPv6 DNS server addresses.
Given your router is still working in a correct manner concerning IPv6 routing you could circumvent the problem by configuring your LAN devices manually:
Look at the router's
IPV6 CONNECTION INFORMATION to see what is your present
IPv6 Network assigned by DHCP PD (for example according to one of your srceenshots: 2a02:2f0e:9031:4100::/64), what is the
LAN IPv6 Link-Local Address (for example: fe80::7a54:2eff:fefb:394c) and what are the
Primary and
Secondary IPv6 DNS Servers (for example: 2a02:2f01:30:2:0:405:465:1 and 2a02:2f01:30:201:0:405:465:1).
Go to your first PC and form a suitable global address for it, for example taking the present value 2a02:2f0e:9031:4100::/64 for
IPv6 Network assigned by DHCP PD you could choose the address 2a02:2f0e:9031:4100::1 with a prefix length of 64 to configure this PC manually. Configure the value fe80::7a54:2eff:fefb:394c (your router's
LAN IPv6 Link-Local Address) as the default gateway for your PC. Finally configure both the values 2a02:2f01:30:2:0:405:465:1 and 2a02:2f01:30:201:0:405:465:1 as primary and secondary DNS server.
This should work but has the disadvantage that you have to reconfigure your PC's global IPv6 address when after a reconnect of your router to your ISP it gets a new prefix value for its
IPv6 Network assigned by DHCP PD. To circumvent this you could ask your ISP for a fixed prefix that never changes...
Of course the real problem is a bug within your router, maybe the storage it uses to store its configuration files is defect. I would ask your vendor for a new device.
PacketTracer