Project

General

Profile

Actions
Copy link

Bug #11764

closed

IPv6 link local gateway default status not indicated in GUI

Added by Jim Pingle about 3 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Viktor Gurov
Category:
Gateways
Target version:
2.7.0
Start date:
03/31/2021
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
22.05
Release Notes:
Default
Affected Version:
2.5.x
Affected Architecture:

Description

In certain cases an IPv6 link-local gateway is not marked as default in the Dashboard widget or on status_gateways.php even when it is default.

This appears to be due to the gateway entry lacking the scope on the LL address, which is present in the routing table.

It is up and working, monitoring shows it as online. GUI status shows the gateway address without scope, but the Monitor address includes the scope (see attached image)

: cat /tmp/vmx0_routerv6
fe80::208:a2ff:fe09:95b5

: route -n6 get default
   route to: ::
destination: ::
       mask: ::
    gateway: fe80::208:a2ff:fe09:95b5%vmx0
        fib: 0
  interface: vmx0
      flags: <UP,GATEWAY,DONE,STATIC>
 recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0      1500         1         0
: netstat -rWn6 | grep default
default                           fe80::208:a2ff:fe09:95b5%vmx0 UGS         269   1500     vmx0

Since it's cosmetic only, it's minor and can wait.

Files

gwstatus_v6.png (27.1 KB) gwstatus_v6.png Jim Pingle, 03/31/2021 11:00 AM
Actions
Copy link
 #1

Updated by Jim Pingle about 3 years ago

In this case, the gateway is from the WAN interface which is set to DHCPv6.

Actions
Copy link
 #3

Updated by Viktor Gurov over 2 years ago

Actions
Copy link
 #4

Updated by Jim Pingle over 2 years ago

  • Status changed from New to Pull Request Review
  • Assignee set to Viktor Gurov
  • Plus Target Version set to 22.05
Actions
Copy link
 #5

Updated by Viktor Gurov about 2 years ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by Jim Pingle about 2 years ago

  • Target version changed from CE-Next to 2.7.0
Actions
Copy link
 #7

Updated by Daryl Morse about 2 years ago

I was running 2.7.0-dev up to around mid-January, then I shut it down to test the 2.6.0 release candidate and release. When I returned to 2.7.0-dev 10 days ago, I updated it to the latest snapshot and found that dpinger is not running for the DHCP6 gateway and DHCPv6 is also not running. Otherwise IPv6 is working properly. The DHCP6 gateway has a link-local address. The file /tmp/hn0_defaultgwv6 is missing. I manually created the file and then restarted dpinger and dhcp, but it did not make any difference. It may be that this fix caused a regression.

Actions
Copy link
 #8

Updated by Jim Pingle about 2 years ago

  • Status changed from Feedback to New
Actions
Copy link
 #9

Updated by Viktor Gurov about 2 years ago

Daryl Morse wrote in #note-7:

I was running 2.7.0-dev up to around mid-January, then I shut it down to test the 2.6.0 release candidate and release. When I returned to 2.7.0-dev 10 days ago, I updated it to the latest snapshot and found that dpinger is not running for the DHCP6 gateway and DHCPv6 is also not running. Otherwise IPv6 is working properly. The DHCP6 gateway has a link-local address. The file /tmp/hn0_defaultgwv6 is missing. I manually created the file and then restarted dpinger and dhcp, but it did not make any difference. It may be that this fix caused a regression.

may be related: https://forum.netgate.com/topic/170445/wan_dhcp6-pending-unknown-and-dhcpv6-server-not-working

Actions
Copy link
 #10

Updated by Daryl Morse about 2 years ago

Viktor Gurov wrote in #note-9:

Daryl Morse wrote in #note-7:

I was running 2.7.0-dev up to around mid-January, then I shut it down to test the 2.6.0 release candidate and release. When I returned to 2.7.0-dev 10 days ago, I updated it to the latest snapshot and found that dpinger is not running for the DHCP6 gateway and DHCPv6 is also not running. Otherwise IPv6 is working properly. The DHCP6 gateway has a link-local address. The file /tmp/hn0_defaultgwv6 is missing. I manually created the file and then restarted dpinger and dhcp, but it did not make any difference. It may be that this fix caused a regression.

may be related: https://forum.netgate.com/topic/170445/wan_dhcp6-pending-unknown-and-dhcpv6-server-not-working

I started that thread. I think it's very likely that these issues are related.

Actions
Copy link
 #11

Updated by Viktor Gurov almost 2 years ago

  • Status changed from New to Feedback

Daryl Morse wrote in #note-7:

I was running 2.7.0-dev up to around mid-January, then I shut it down to test the 2.6.0 release candidate and release. When I returned to 2.7.0-dev 10 days ago, I updated it to the latest snapshot and found that dpinger is not running for the DHCP6 gateway and DHCPv6 is also not running. Otherwise IPv6 is working properly. The DHCP6 gateway has a link-local address. The file /tmp/hn0_defaultgwv6 is missing. I manually created the file and then restarted dpinger and dhcp, but it did not make any difference. It may be that this fix caused a regression.

There is no changes in DHCP code in January.
This may be due to the "don't wait for RA" option,
see https://forum.netgate.com/topic/170445/wan_dhcp6-pending-unknown-and-dhcpv6-server-not-working/13

Actions
Copy link
 #12

Updated by Hayden Hill almost 2 years ago

I might be having the same issue here. 22.05/2.07 Beta, IPV6 is "working" but gateway monitor always shows "pending". No issues with 22.01

Actions
Copy link
 #13

Updated by Hayden Hill almost 2 years ago

Hayden Hill wrote in #note-12:

I might be having the same issue here. 22.05/2.07 Beta, IPV6 is "working" but gateway monitor always shows "pending". No issues with 22.01

Disabled "don't wait for RA" and it worked just fine. I honestly don't know if I need that flag or not anymore but my guess is this will be an issue for people that do.

Actions
Copy link
 #14

Updated by Jim Pingle almost 2 years ago

  • Status changed from Feedback to Resolved

The problem here as exactly stated is solved. If we can reproduce a different (albeit similar) problem along a separate set of options/different code path it can be handled as its own separate Redmine issue.

The change here would not lead to a missing gateway file, the only difference is whether or not the gateway in that file gets the scope appended, which appears to be happening properly now.

Actions
Copy link
 #15

Updated by Daryl Morse almost 2 years ago

Hayden Hill wrote in #note-13:

Hayden Hill wrote in #note-12:

I might be having the same issue here. 22.05/2.07 Beta, IPV6 is "working" but gateway monitor always shows "pending". No issues with 22.01

Disabled "don't wait for RA" and it worked just fine. I honestly don't know if I need that flag or not anymore but my guess is this will be an issue for people that do.

If it makes no difference whether you have selected "do not wait for RA", then you don't need it. If your ISP requires the DHCP solicit to take place before the ICMP router solicit, IPv6 will not work at all unless you select "do not wait for RA".

Actions
Copy link
 #16

Updated by Daryl Morse almost 2 years ago

Jim Pingle wrote in #note-14:

The problem here as exactly stated is solved. If we can reproduce a different (albeit similar) problem along a separate set of options/different code path it can be handled as its own separate Redmine issue.

The change here would not lead to a missing gateway file, the only difference is whether or not the gateway in that file gets the scope appended, which appears to be happening properly now.

I created a new bug in redmine, Bug #13238.

Actions
Copy link

Also available in: Atom PDF