Project

General

Profile

Bug #7176

IPv6 Monitor IP does not seem to propagate

Added by Chris Palmer 25 days ago. Updated 7 days ago.

Status:
New
Priority:
Normal
Category:
Gateway monitoring
Target version:
Start date:
01/30/2017
Due date:
% Done:

0%

Affected version:
2.4
Affected Architecture:
amd64

Description

2.3.3 snaps work. This particular install uses a 6to4 tunnel from the ISP.

Setting "Gateway Monitor IP" in 2.4 snaps at System/Routing/Gateways/Edit shows the IPv6 address.

Looking at Status/Gateways/Gateways Monitor IP does not show up.

Dashboard GUI continually shows "Pending".

:)

History

#1 Updated by Jim Pingle 15 days ago

  • Target version set to 2.4.0

#2 Updated by Chris Palmer 8 days ago

Got to play a little today- This is the error in the log when restarting dpinger.

Feb 16 18:23:01 php-fpm 73948 /status_services.php: Removing static route for monitor 2002:c058:6301::1 and adding a new route through 2002:c058:6301::
Feb 16 18:23:13 php-fpm 73948 /status_services.php: The command '/usr/local/bin/dpinger -S -r 0 -i WAN_6TO4 -B 2002:1871:323b:: -p /var/run/dpinger_WAN_6TO4~2002:1871:323b::~2002:c058:6301::1.pid -u /var/run/dpinger_WAN_6TO4~2002:1871:323b::~2002:c058:6301::1.sock -C "/etc/rc.gateway_alarm" -d 0 -s 500 -l 2000 -t 60000 -A 1000 -D 500 -L 20 2002:c058:6301::1 >/dev/null' returned exit code '1', the output was ''
Feb 16 18:23:13 php-fpm 73948 /status_services.php: Error starting gateway monitor for WAN_6TO4

#3 Updated by Denny Page 8 days ago

The bind address appears to be invalid.

#4 Updated by Luiz Otavio O Souza 7 days ago

  • Assignee set to Renato Botelho

Also available in: Atom PDF