Bug #7176
closed
IPv6 Monitor IP does not seem to propagate
Added by Chris Palmer almost 8 years ago.
Updated about 7 years ago.
Category:
Gateway Monitoring
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".
:)
- Target version set to 2.4.0
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
The bind address appears to be invalid.
- Assignee set to Renato Botelho
edit to say- shows pending no matter if gateway ip is used to monitor or if a "monitor IP" is chosen. My original report seems confusing to me.
2.4.0-RC (amd64)
built on Wed Aug 23 05:47:05 CDT 2017
FreeBSD 11.0-RELEASE-p12
This now seems resolved.
- Status changed from New to Resolved
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by