Re: howto show IPv6 address lifetime?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Florian, On 04/20/17 12:45, Florian Ermisch wrote: > Hi Harri, > > until someone in the know replies you could take a look at the DHCPv6 traffic > to see if a lifetime is included in the replies (and maybe keep them handy > for a dev to look at). Maybe dhcpcd supports this feature but there's an > uncommon combination of flags it doesn't know about yet. > > Regards, Florian bash-4.4# dhcpcd -U pppoe0 dhcp6_client_id=00010001207921d480ee7395c10c dhcp6_ia_pd1_iaid= dhcp6_ia_pd1_prefix1=2003:dd:b3dd:aa00:: dhcp6_ia_pd1_prefix1_length=56 dhcp6_ia_pd1_prefix1_pltime=1800 dhcp6_ia_pd1_prefix1_vltime=14400 dhcp6_ia_pd1_t1=900 dhcp6_ia_pd1_t2=1440 dhcp6_server_id=000205834a4e3132353234354441 If I run "ifconfig pppoe0 down" and "... up", then I get another prefix, but the rest is unchanged, esp. client and server ID are the same. I have the impression, that this is a bug in dhcpcd. If I stop the service, then re1 is reconfigured accordingly: Apr 20 13:15:34 marvin dhcpcd[84654]: sending signal TERM to pid 7129 Apr 20 13:15:34 marvin dhcpcd[7129]: received SIGTERM, stopping Apr 20 13:15:34 marvin dhcpcd[7129]: re1: removing interface Apr 20 13:15:34 marvin dhcpcd[7129]: re1: deleting address 2003:dd:b3dd:aa00::1/56 Apr 20 13:15:34 marvin dhcpcd[84654]: waiting for pid 7129 to exit Apr 20 13:15:34 marvin dhcpcd[7129]: lo0: changing reject route to 2003:dd:b3dd:aa00::/56 via ::1 Apr 20 13:15:34 marvin dhcpcd[7129]: pppoe0: removing interface Apr 20 13:15:34 marvin dhcpcd[7129]: lo0: deleting reject route to 2003:dd:b3dd:aa00::/56 via ::1 Apr 20 13:15:34 marvin dhcpcd[7129]: pppoe0: deleting address 2003:dd:b3bf:1daa:665a:4ff:fe35:830a/64 Apr 20 13:15:34 marvin dhcpcd[7129]: dhcpcd exited Apr 20 13:15:41 marvin dhcpcd[99209]: DUID 00:01:00:01:20:79:21:d4:80:ee:73:95:c1:0c Apr 20 13:15:41 marvin dhcpcd[99209]: re1: IAID 73:95:c1:0d Apr 20 13:15:41 marvin dhcpcd[99209]: pppoe0: IAID 00:00:00:00 Apr 20 13:15:41 marvin dhcpcd[99209]: pppoe0: rebinding prior DHCPv6 lease Apr 20 13:15:41 marvin dhcpcd[99209]: pppoe0: soliciting an IPv6 router Apr 20 13:15:41 marvin dhcpcd[99209]: pppoe0: Router Advertisement from fe80::101:101:3e9b:f1ab Apr 20 13:15:41 marvin dhcpcd[99209]: pppoe0: adding address 2003:dd:b3bf:1daa:665a:4ff:fe35:830a/64 Apr 20 13:15:43 marvin dhcpcd[99209]: pppoe0: REPLY6 received from fe80::101:101:3e9b:f1ab Apr 20 13:15:43 marvin dhcpcd[99209]: pppoe0: renew in 900, rebind in 1440, expire in 14400 seconds Apr 20 13:15:43 marvin dhcpcd[99209]: lo0: adding reject route to 2003:dd:b3dd:aa00::/56 via ::1 Apr 20 13:15:43 marvin dhcpcd[99209]: pppoe0: delegated prefix 2003:dd:b3dd:aa00::/56 Apr 20 13:15:43 marvin dhcpcd[99209]: re1: adding address 2003:dd:b3dd:aa00::1/56 Apr 20 13:15:43 marvin dhcpcd[99209]: re1: changing route to 2003:dd:b3dd:aa00::/56 If I restart pppoe0, then the old address is not removed from re1, even though dhcpcd recognized that the old delegation has been withdrawn. It created a new default route, added a new IPv6 address to re1, etc. Apr 20 13:30:39 marvin dhcpcd[46072]: pppoe0: carrier lost Apr 20 13:30:39 marvin dhcpcd[46072]: pppoe0: deleting address 2003:dd:b3bf:2325:665a:4ff:fe35:830a/64 Apr 20 13:30:39 marvin dhcpcd[46072]: pppoe0: if_addrflags: 93.233.206.36: Undefined error: 0 Apr 20 13:30:39 marvin dhcpcd[46072]: pppoe0: if_addrflags: Undefined error: 0 Apr 20 13:30:54 marvin dhcpcd[46072]: pppoe0: carrier acquired Apr 20 13:30:54 marvin dhcpcd[46072]: pppoe0: IAID 00:00:00:00 Apr 20 13:30:54 marvin dhcpcd[46072]: pppoe0: rebinding prior DHCPv6 lease Apr 20 13:30:54 marvin dhcpcd[46072]: pppoe0: Router Advertisement from fe80::101:101:3e9b:f1ab Apr 20 13:30:54 marvin dhcpcd[46072]: pppoe0: adding address 2003:dd:b3bf:2336:665a:4ff:fe35:830a/64 Apr 20 13:31:04 marvin dhcpcd[46072]: pppoe0: failed to rebind prior delegation Apr 20 13:31:04 marvin dhcpcd[46072]: pppoe0: soliciting a DHCPv6 lease Apr 20 13:31:07 marvin dhcpcd[46072]: pppoe0: REPLY6 received from fe80::101:101:3e9b:f1ab Apr 20 13:31:07 marvin dhcpcd[46072]: pppoe0: renew in 900, rebind in 1440, expire in 14400 seconds Apr 20 13:31:07 marvin dhcpcd[46072]: lo0: adding reject route to 2003:dd:b3e3:3600::/56 via ::1 Apr 20 13:31:07 marvin dhcpcd[46072]: pppoe0: delegated prefix 2003:dd:b3e3:3600::/56 Apr 20 13:31:07 marvin dhcpcd[46072]: re1: adding address 2003:dd:b3e3:3600::1/56 Apr 20 13:31:07 marvin dhcpcd[46072]: re1: changing route to 2003:dd:b3e3:3600::/56 It just forgot to remove the old address. Regards Harri -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAlj4qXkACgkQCp4qnmbT gcvYgAf/RbVvuMPjtdgIsVNpJVSgGLJSsrD9t+dyE27HKDGtewahYvJEhF1ZXnWd LiWPAoo9OaWN9vIhewmHnXQRwSRDL7S63PPIw9T5XN8Fjhic1EeiSS9qsLgEfSeG tAFRPPMi2rxrjHPLy2ea6+nrw+IiuVzfDMuvts8/FXuMJS4yFwyITj8yfzjIh3VC jId3BNwknYd9I8vVgHoSOSDxlYJw8I/tlOFR2HUiDF+lqRHo6qD1po0mTRhIV/DC SAR9uMY3iKk+kfZmnl1hDQ05+pUPR4
Re: howto show IPv6 address lifetime?
Hi Harri, until someone in the know replies you could take a look at the DHCPv6 traffic to see if a lifetime is included in the replies (and maybe keep them handy for a dev to look at). Maybe dhcpcd supports this feature but there's an uncommon combination of flags it doesn't know about yet. Regards, Florian Am 20. April 2017 10:25:54 MESZ schrieb Harald Dunkel : >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 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 0xff00 broadcast 10.42.100.255 >inet6 fe80::82ee:73ff:fe95:c10d%re1 prefixlen 64 scopeid 0x3 >inet6 2003:::e500::1 prefixlen 56 >inet6 2003:::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= >iaid 0 >ia_pd 0 re1/0 > > >Every helpful hint is highly appreciated. >Harri
Re: howto show IPv6 address lifetime?
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 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 0xff00 broadcast 10.42.100.255 inet6 fe80::82ee:73ff:fe95:c10d%re1 prefixlen 64 scopeid 0x3 inet6 2003:::e500::1 prefixlen 56 inet6 2003:::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= iaid 0 ia_pd 0 re1/0 Every helpful hint is highly appreciated. Harri
Re: howto show IPv6 address lifetime?
On Wed, Apr 19, 2017 at 09:32:56AM -0400, Eike Lantzsch wrote: > On Wednesday, 19 April 2017 14:22:32 -04 Peter N. M. Hansteen wrote: > > On Wed, Apr 19, 2017 at 11:16:44AM +0200, Harald Dunkel wrote: > > > > Give a try to ifconfig as regarde privacy policy lifetime : pltime & > > > > vltime if i'm still right. You can also preset this two counters using > > > > the same command.> > > > ??? Sorry, but I don't understand this first sentence. > > > > > > I would like to see the address lifetime, which address is preferred, > > > which is deprecated, etc. On Linux a simple command like "ip a s" shows. > > As quoted above, ifconfig is your friend: > > > > [Wed Apr 19 14:19:35] peter@elke:~$ ifconfig iwm0 > > iwm0: flags=208943 > > mtu 1500 lladdr a0:a8:cd:63:ab:b9 > > index 1 priority 4 llprio 3 > > groups: wlan egress > > media: IEEE802.11 autoselect (HT-MCS4 mode 11n) > > status: active > > ieee80211: nwid we_collect_all_your_nasty-bits5 chan 36 bssid > > e0:3f:49:23:bb:2c 29% wpakey wpaprotos wpa2 wpaakms psk > > wpaciphers ccmp wpagroupcipher ccmp inet6 fe80::a2a8:cdff:fe63:abb9%iwm0 > > prefixlen 64 scopeid 0x1 inet 192.168.103.126 netmask 0xff00 broadcast > > 192.168.103.255 inet6 2001:470:28:658:a2a8:cdff:fe63:abb9 prefixlen 64 > > autoconf pltime 604759 vltime 2591959 inet6 > > 2001:470:28:658:54c6:1b6f:ee43:32b9 prefixlen 64 deprecated autoconf > > autoconfprivacy pltime 0 vltime 43 inet6 > > 2001:470:28:658:9039:71e4:30e2:a37e prefixlen 64 autoconf autoconfprivacy > > pltime 11955 vltime 530703 > > > > That's output from my laptop just now, with autoconfigured inet6 addresses. > > I believe the pltime and vltime values are given in seconds. > > can it be that ifconfig outputs pltime and vltime only if the values are set > but not in the case that they are forever? Or are the values not shown or in > case of using virtual interfaces? The man page does not say. > I'm asking because : > > $ doas ifconfig > [snip re0 and re1] > vether0: flags=8943 mtu 1500 > lladdr fe:e1:ba:d0:52:8d > index 8 priority 0 llprio 3 > groups: vether > media: Ethernet autoselect > status: active > inet 192.168.12.1 netmask 0xff00 broadcast 192.168.12.255 > inet6 fe80::fce1:baff:fed0:528d%vether0 prefixlen 64 scopeid 0x8 > inet6 2001:470:1f0b:ca9::1 prefixlen 64 You don't seem to have any autoconfigured addresses. Try ifconfig vether0 inet6 autoconf first.
Re: howto show IPv6 address lifetime?
On Wednesday, 19 April 2017 14:22:32 -04 Peter N. M. Hansteen wrote: > On Wed, Apr 19, 2017 at 11:16:44AM +0200, Harald Dunkel wrote: > > > Give a try to ifconfig as regarde privacy policy lifetime : pltime & > > > vltime if i'm still right. You can also preset this two counters using > > > the same command.> > > ??? Sorry, but I don't understand this first sentence. > > > > I would like to see the address lifetime, which address is preferred, > > which is deprecated, etc. On Linux a simple command like "ip a s" shows. > As quoted above, ifconfig is your friend: > > [Wed Apr 19 14:19:35] peter@elke:~$ ifconfig iwm0 > iwm0: flags=208943 > mtu 1500 lladdr a0:a8:cd:63:ab:b9 > index 1 priority 4 llprio 3 > groups: wlan egress > media: IEEE802.11 autoselect (HT-MCS4 mode 11n) > status: active > ieee80211: nwid we_collect_all_your_nasty-bits5 chan 36 bssid > e0:3f:49:23:bb:2c 29% wpakey wpaprotos wpa2 wpaakms psk > wpaciphers ccmp wpagroupcipher ccmp inet6 fe80::a2a8:cdff:fe63:abb9%iwm0 > prefixlen 64 scopeid 0x1 inet 192.168.103.126 netmask 0xff00 broadcast > 192.168.103.255 inet6 2001:470:28:658:a2a8:cdff:fe63:abb9 prefixlen 64 > autoconf pltime 604759 vltime 2591959 inet6 > 2001:470:28:658:54c6:1b6f:ee43:32b9 prefixlen 64 deprecated autoconf > autoconfprivacy pltime 0 vltime 43 inet6 > 2001:470:28:658:9039:71e4:30e2:a37e prefixlen 64 autoconf autoconfprivacy > pltime 11955 vltime 530703 > > That's output from my laptop just now, with autoconfigured inet6 addresses. > I believe the pltime and vltime values are given in seconds. can it be that ifconfig outputs pltime and vltime only if the values are set but not in the case that they are forever? Or are the values not shown or in case of using virtual interfaces? The man page does not say. I'm asking because : $ doas ifconfig [snip re0 and re1] vether0: flags=8943 mtu 1500 lladdr fe:e1:ba:d0:52:8d index 8 priority 0 llprio 3 groups: vether media: Ethernet autoselect status: active inet 192.168.12.1 netmask 0xff00 broadcast 192.168.12.255 inet6 fe80::fce1:baff:fed0:528d%vether0 prefixlen 64 scopeid 0x8 inet6 2001:470:1f0b:ca9::1 prefixlen 64 bridge0: flags=41 index 9 llprio 3 groups: bridge priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp vether0 flags=3 port 8 ifpriority 0 ifcost 0 athn0 flags=3 port 4 ifpriority 0 ifcost 0 re2 flags=3 port 3 ifpriority 0 ifcost 0 [snip] pflog0: flags=141 mtu 33144 index 12 priority 0 llprio 3 groups: pflog gif0: flags=8051 mtu 1280 index 13 priority 0 llprio 3 groups: gif egress tunnel: inet 181.121.5.112 -> 216.66.80.30 inet6 fe80::20d:b9ff:fe41:2214%gif0 -> prefixlen 64 scopeid 0xd inet6 2001:470:1f0a:ca8::2 -> 2001:470:1f0a:ca8::1 prefixlen 128 Greetings Eike
Re: howto show IPv6 address lifetime?
On Wed, Apr 19, 2017 at 11:16:44AM +0200, Harald Dunkel wrote: > > Give a try to ifconfig as regarde privacy policy lifetime : pltime & vltime > > if i'm still right. You can also preset this two counters using the same > > command. > > ??? Sorry, but I don't understand this first sentence. > > I would like to see the address lifetime, which address is preferred, which > is deprecated, etc. On Linux a simple command like "ip a s" shows. As quoted above, ifconfig is your friend: [Wed Apr 19 14:19:35] peter@elke:~$ ifconfig iwm0 iwm0: flags=208943 mtu 1500 lladdr a0:a8:cd:63:ab:b9 index 1 priority 4 llprio 3 groups: wlan egress media: IEEE802.11 autoselect (HT-MCS4 mode 11n) status: active ieee80211: nwid we_collect_all_your_nasty-bits5 chan 36 bssid e0:3f:49:23:bb:2c 29% wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp inet6 fe80::a2a8:cdff:fe63:abb9%iwm0 prefixlen 64 scopeid 0x1 inet 192.168.103.126 netmask 0xff00 broadcast 192.168.103.255 inet6 2001:470:28:658:a2a8:cdff:fe63:abb9 prefixlen 64 autoconf pltime 604759 vltime 2591959 inet6 2001:470:28:658:54c6:1b6f:ee43:32b9 prefixlen 64 deprecated autoconf autoconfprivacy pltime 0 vltime 43 inet6 2001:470:28:658:9039:71e4:30e2:a37e prefixlen 64 autoconf autoconfprivacy pltime 11955 vltime 530703 That's output from my laptop just now, with autoconfigured inet6 addresses. I believe the pltime and vltime values are given in seconds. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: howto show IPv6 address lifetime?
> On Apr 19, 2017, at 10:43, Eric Huiban wrote: > > Hi, > > Give a try to ifconfig as regarde privacy policy lifetime : pltime & vltime > if i'm still right. You can also preset this two counters using the same > command. ??? Sorry, but I don't understand this first sentence. I would like to see the address lifetime, which address is preferred, which is deprecated, etc. On Linux a simple command like "ip a s" shows. Regards Harri
Re: howto show IPv6 address lifetime?
Hi, Give a try to ifconfig as regarde privacy policy lifetime : pltime & vltime if i'm still right. You can also preset this two counters using the same command. Eric
howto show IPv6 address lifetime?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi folks, AFAIR IPv6 addresses have a lifetime and some other attributes. Is there some way to show? "sysctl -a", "ifconfig -a" and netstat don't. Probably I am just missing the right command. Every helpful hint is highly appreciated. Harri -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEH2V614LbR/u1O+a1Cp4qnmbTgcsFAlj3Bo4ACgkQCp4qnmbT gcvTvQf/VlNt8XHhVGNj9V0nS68w2nWrMlbMzaoofl1q0YppEVVrov4rYDH3EapC qbL3jOxjG5RbYfmuhMSt796F/R2vD/u40q7dv//CQoS8rhvYN3G6rnoOVGWz8WLU bVr4RrOZk8uBM4emX3jr+AxpUEU/PyQQXNpoQ2K98PNIlLXcpsh8V2Xwq4kQtbb5 g/flcJjUcKrXHeO+9jH052maymqLVu9Z+oUJPENyeNhWZvkvWIbZZgVA1BtiYRCr ZFIHaNoYiJy9qryzE4+Psrj4gDi+JSp/QDsA1E0KUA/M+FNLxv3TB9aZLI2p46H7 lwWWIuu0nv08a3GnMLiAQG2iWQBZKw== =aZGh -END PGP SIGNATURE-
