On 04/19/17 15:38, Dimitris Papastamos wrote:
> 
> You don't seem to have any autoconfigured addresses.
> Try ifconfig vether0 inet6 autoconf first.
> 

Here is the output of ifconfig on my gateway:

# ifconfig re1
re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 80:ee:73:95:c1:0d
        index 3 priority 0 llprio 3
        groups: intern
        media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
        status: active
        inet 10.42.0.2 netmask 0xffffff00 broadcast 10.42.100.255
        inet6 fe80::82ee:73ff:fe95:c10d%re1 prefixlen 64 scopeid 0x3
        inet6 2003:xxxx:yyyy:e500::1 prefixlen 56
        inet6 2003:xxxx:yyyy:4200::1 prefixlen 56

There is no "inet6 autoconf". Both IPv6 addresses have been assigned to
re1 by dhcpcd during prefix delegation via pppoe0.

Point is, the address with "e500" is not valid anymore, since
Deutsche Telekom gave me the new prefix a few days ago. I had
expected some kind of "expiration procedure" here.

Is this a bug with my dhcpcd.conf or is this feature simply "not in"?
Should I set re1 to "inet6 autoconf", even though it is not? (I will
try, but let me send this EMail first.)

# cat /etc/dhcpcd.conf
ipv6only
persistent
option rapid_commit
require dhcp_server_identifier
nohook lookup-hostname, resolv.conf
allowinterfaces re1 pppoe0
noipv6rs

interface pppoe0
        ipv6rs
        # static static domain_name_servers=<nameserver IPs>
        iaid 0
        ia_pd 0 re1/0


Every helpful hint is highly appreciated.
Harri

Reply via email to