Project

General

Profile

Bug #5631

Gateway monitor not started for 6RD connections

Added by Will Wainwright almost 4 years ago. Updated over 3 years ago.

Status:
Duplicate
Priority:
Low
Assignee:
-
Category:
Gateway Monitoring
Target version:
Start date:
12/12/2015
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.3
Affected Architecture:

Description

Hi guys,

I just set up a 2.3 (amd64 Sat Dec 12 14:06:02) vm & noticed that the gateway monitor widget displays my 6RD gateway as "pending".

I have verified that ipv6 is working & I can ping the monitor IP from an ssh session. I took a look at gateways.log & I can see connections to my ipv4 gateway\monitor ip, but there are no entries for the 6RD connection.

-Will

History

#1 Updated by Phillip Davis almost 4 years ago

How many dpinger processes do you have?
There should be 1 for each monitored gateway.
Maybe some of the logic that starts each dpinger process is missing out 6RD gateways.

#2 Updated by Will Wainwright almost 4 years ago

Hi Phillip,

I have one dpinger process that is connecting to my ipv4 gateway.

-Will

#3 Updated by Chris Buechler almost 4 years ago

  • Subject changed from Gateway monitor of 6RD connection "pending" to Gateway monitor not started for 6RD connections
  • Category set to Gateway Monitoring
  • Status changed from New to Confirmed

#4 Updated by Jim Pingle almost 4 years ago

I'm not getting dpinger instances for any of my IPv6 gateways, which are all static or DHCPv6

#5 Updated by Chris Buechler almost 4 years ago

Jim P wrote:

I'm not getting dpinger instances for any of my IPv6 gateways, which are all static or DHCPv6

I've seen multiple systems missing dpinger instances for IPv6 gateways, but my home system on DHCP6 has a proper instance and works correctly so it's not universally broken. Haven't gotten to the bottom of what the difference is yet. There is some more widespread issue with IPv6 gateways though, this probably applies to more than just 6rd.

#6 Updated by Chris Buechler over 3 years ago

  • Status changed from Confirmed to Duplicate

root issue in #5696, closing in favor of that.

Also available in: Atom PDF