Log option (18) Interface-Id in DHCPv6 failed

Darko Bezjak darko.bezjak at t-2.com
Mon Feb 23 11:40:31 UTC 2015


Has somebody experience with logging configuration for option 18
Interface-Id, which is pushed by dhcp-relay. 

 

Related configuration:

 

deny bootp;

ddns-update-style none;

authoritative;

log-facility local5;

ping-check false;

one-lease-per-client off;

deny client-updates;

deny declines;

log(info,concat("Interface-ID: " , option dhcp6.interface-id));

..

 

Log: 

Feb 23 09:32:19 MB-DHCP-T-02 dhcpd: Sending Relay-reply to
2a01:260:8043:1007::1 port 547

Feb 23 09:33:03 MB-DHCP-T-02 dhcpd: Relay-forward message from
2a01:260:8043:1007::1 port 547, link address 2a01:260:8043:1007::1, peer
address fe80::883c:510a:267a:f0a6

Feb 23 09:33:03 MB-DHCP-T-02 dhcpd: Sending Relay-reply to
2a01:260:8043:1007::1 port 547

Feb 23 09:59:01 MB-DHCP-T-02 dhcpd: Relay-forward message from
2a01:260:8043:1007::1 port 547, link address 2a01:260:8043:1007::1, peer
address fe80::d6ca:6dff:fe2f:fd7c

Feb 23 09:59:01 MB-DHCP-T-02 dhcpd: Advertise PD: address
2a01:260:8043:1033::/64 to client with duid 00:03:00:01:d4:ca:6d:2f:fd:7c
iaid = 1 valid for 43200 seconds

Feb 23 09:59:01 MB-DHCP-T-02 dhcpd: Sending Relay-reply to
2a01:260:8043:1007::1 port 547

Feb 23 09:59:02 MB-DHCP-T-02 dhcpd: Relay-forward message from
2a01:260:8043:1007::1 port 547, link address 2a01:260:8043:1007::1, peer
address fe80::d6ca:6dff:fe2f:fd7c

Feb 23 09:59:02 MB-DHCP-T-02 dhcpd: Reply PD: address
2a01:260:8043:1033::/64 to client with duid 00:03:00:01:d4:ca:6d:2f:fd:7c
iaid = 1 valid for 43200 seconds

Feb 23 09:59:02 MB-DHCP-T-02 dhcpd: Wrote 2 NA, 0 TA, 2 PD leases to lease
file.

Feb 23 09:59:02 MB-DHCP-T-02 dhcpd: Sending Relay-reply to
2a01:260:8043:1007::1 port 547

 

 

Regards, Darko.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150223/6e4d3eb0/attachment.html>


More information about the dhcp-users mailing list