Project

General

Profile

Actions

Bug #3969

closed

apinger configuration for DHCPv6 gateway is missing interface scope on source IP and target

Added by Jim Pingle almost 7 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
Normal
Category:
Gateways
Target version:
Start date:
10/31/2014
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:
All

Description

When using a DHCPv6 WAN, apinger sets the srcip to be the interface link-local address but it does not set the scope on the source IP or target, so apinger cannot reach the gateway.

Log message (IPv6 addresses masked):

Oct 31 08:25:13 pfs22 apinger: Could not bind socket on address(fe80::a00:27ff:xxxx:xxxx) for monitoring address fe80::240:48ff:xxxx:xxxx(WAN_DHCP6) with error Can't assign requested address

Broken configuration made currently (IPv6 addresses masked):

target "fe80::240:48ff:xxxx:xxxx" {
    description "WAN_DHCP6" 
    srcip "fe80::a00:27ff:xxxx:xxxx" 
    alarms override "loss","delay","down";
    rrd file "/var/db/rrd/WAN_DHCP6-quality.rrd" 
}

Working hand-edited version (IPv6 addresses masked):

target "fe80::240:48ff:xxxx:xxxx%em0" {
    description "WAN_DHCP6" 
    srcip "fe80::a00:27ff:xxxx:xxxx%em0" 
    alarms override "loss","delay","down";
    rrd file "/var/db/rrd/WAN_DHCP6-quality.rrd" 
}

Actions

Also available in: Atom PDF