Bug #5695: dpinger doesn't work with source IPs specifying a scope ID - pfSense - pfSense bugtracker

Actions

Copy link

Bug #5695

closed

dpinger doesn't work with source IPs specifying a scope ID

Added by Chris Buechler almost 9 years ago. Updated almost 9 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Renato Botelho

Category:

Gateway Monitoring

Target version:

2.3

Start date:

12/24/2015

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.3

Affected Architecture:

Description

In the default DHCP6 WAN scenario where you're monitoring a link local gateway, the source IP passed to dpinger includes the scope ID. dpinger exits with "Invalid source IP address". It also fails and exits with "Invalid destination IP address" if the gateway IP includes the scope ID. That seems to get omitted from the monitor IP passed to dpinger in every circumstance, but should be permissible.

ping6 works with such source and destination addresses, such as:

ping6 -S fe80::250:56ff:feac:dd8c%vmx0 fe80::250:56ff:fea7:f865%vmx0
PING6(56=40+8+8 bytes) fe80::250:56ff:feac:dd8c%vmx0 --> fe80::250:56ff:fea7:f865%vmx0
16 bytes from fe80::250:56ff:fea7:f865%vmx0, icmp_seq=0 hlim=64 time=0.506 ms

Actions

Copy link

Updated by Renato Botelho almost 9 years ago

Opened an issue upstream to track it - https://github.com/dennypage/dpinger/issues/15

Actions

Copy link

Updated by Denny Page almost 9 years ago

I will add the ability to specify scope id as part of IP parameters.

Actions

Copy link

Updated by Denny Page almost 9 years ago

IPv6 scope IDs are now supported.

https://github.com/dennypage/dpinger/commit/00229f717db1212cdfa0cb0644d206e897ac6f4d

Actions

Copy link

Updated by Renato Botelho almost 9 years ago

Status changed from Confirmed to Feedback
% Done changed from 0 to 100

dpinger was updated to 1.2

Actions

Copy link

Updated by Jim Pingle almost 9 years ago

Status changed from Feedback to Confirmed
% Done changed from 100 to 90

dpinger runs now but the target also needs to be scoped, not just the source. Looking at the running dpinger command it does not appear to be using a scoped address for the target, and the gateway shows offline:

/usr/local/bin/dpinger -S -r 0 -i WAN_DHCP6 -B fe80::20d:b9ff:fe33:f71%re1 -p /var/run/dpinger_WAN_DHCP6_fe80::20d:b9ff:fe33:f71%re1_fe80::290:bff:fe37:a324.pid -u /var/run/dpinger_WAN_DHCP6_fe80::20d:b9ff:fe33:f71%re1_fe80::290:bff:fe37:a324.sock -C /etc/rc.gateway_alarm -s 250 -l 1000 -t 25000 -A 1000 -D 500 -L 20 fe80::290:bff:fe37:a324

If I kill that and start it with the target also scoped, it works:

/usr/local/bin/dpinger -S -r 0 -i WAN_DHCP6 -B fe80::20d:b9ff:fe33:f71%re1 -p /var/run/dpinger_WAN_DHCP6_fe80::20d:b9ff:fe33:f71%re1_fe80::290:bff:fe37:a324.pid -u /var/run/dpinger_WAN_DHCP6_fe80::20d:b9ff:fe33:f71%re1_fe80::290:bff:fe37:a324.sock -C /etc/rc.gateway_alarm -s 250 -l 1000 -t 25000 -A 1000 -D 500 -L 20 fe80::290:bff:fe37:a324%re1

Actions

Copy link