Thanks for the reply, jow. I followed your suggestion but I still can't get a global v6 address on br-lan.
I'm a bit confused regarding the dhcpv6 client configuration. I gather that the client should talk to a dhcpv6 server to get the information, right? Which server would that be? A wide-dhcpv6-server I should run on the wan? Or the dhcpv6 server that (I guess) my ISP runs?
In the former case, I don't know how to configure the wide-dhcpv6 server on the wan because all examples I found need a static address range. Since my ISP gives me a different v6 address every time pppoe is established, I don't have a static range. Can I configure it so that it gets the range from the prefix of the wan interface? If so, how?
In the latter case, I'm not sure but I don't think that my ISP runs a dhcpv6 server since I was able to get the v6 address on wan even before I installed the wide-dhcpv6 server and client packages. Is dhcpv6 involved when I get the v6 address on pppoe? I didn't think so. If so, do I need any special configuration for the dhcp client?
I've disabled the wide-dhcpv6 server and left only with the client. I have a global v6 address on the wan interface but only a link-local on the br-lan. Just for reference, here's my dhcpv6 client configuration:
config 'dhcp6c' 'basic'
option 'enabled' '1' # 1 = enabled; 0 = disabled
option 'interface' 'lan' # This is the interface the DHCPv6 client will run on
option 'dns' 'dnsmasq' # Which DNS server you run (only dnsmasq currently supported)
option 'debug' '0' # 1 = enable debugging; 0 = disable debugging
# Send options (1 = send; 0 = do not send)
option 'pd' '1' # Prefix Delegation
option 'na' '0' # Non-Temporary Address
option 'rapid_commit' '1' # Rapid Commit
# Request options (1 = request; 0 = do not request)
option 'domain_name_servers' '1'
option 'domain_name' '0'
option 'ntp_servers' '0'
option 'sip_server_address' '0'
option 'sip_server_domain_name' '0'
option 'nis_server_address' '0'
option 'nis_domain_name' '0'
option 'nisp_server_address' '0'
option 'nisp_domain_name' '0'
option 'bcmcs_server_address' '0'
option 'bcmcs_server_domain_name' '0'
# Override the used DUID, by default it is derived from the interface MAC
# The given value must be uppercase and globally unique!
#option 'duid' '00:03:00:06:D8:5D:4C:A5:03:F2'
# Script to run when a reply is received
#option 'script' '/usr/bin/dhcp6c-state'
# Define one or more interfaces on which prefixes should be assigned
config 'interface' 'loopback'
option 'enabled' '1' # 1 = enabled; 0 = disabled
option 'sla_id' '0' # Site level aggregator identifier specified in decimal (subnet)
option 'sla_len' '1' # Site level aggregator length (64 - size of prefix being delegated)
# e.g. /60 from ISP -> 64 - 60 = 4
config 'interface' 'lan'
option 'enabled' '1'
option 'sla_id' '1'
option 'sla_len' '1'
Here's the only relevant output I could find from logread after doing a reboot and then a restart of the dhcp6c:
root@OpenWrt:/etc/config# logread | grep 6c
Mar 27 02:44:03 OpenWrt user.notice dhcp6c: starting dhcp6c
Mar 27 02:44:04 OpenWrt user.notice dhcp6c: Using MAC address DUID 00:03:00:06:00:18:xx:xx:xx:xx
Oct 23 07:42:24 OpenWrt user.notice dhcp6c: stopping dhcp6c
Oct 23 07:42:24 OpenWrt user.notice dhcp6c: starting dhcp6c
Oct 23 07:42:24 OpenWrt user.notice dhcp6c: Using MAC address DUID 00:03:00:06:00:18:xx:xx:xx:xx
root@OpenWrt:/etc/config#
At the bottom of the kernel log I noticed a line that says "no IPv6 routers present" for eth1, which is the wan interface. I'm not sure why, I used to connect with IPv6 so I guess the ISP's configuration is ok.
(...) device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
eth1: no IPv6 routers present
ar71xx-wdt: enabling watchdog timer
Maybe there's some configuration I'm missing?
(Last edited by mikem4600 on 23 Oct 2011, 09:10)
