Messages

Currently running v25.1.1 upgraded from v25.1

When on v25.1 (pre-upgrade), IPv6 was working via the "Track Interface" mechanism on the WAN (igb0) interface.

Settings are the same as used in the v24 production series, which also worked.

The behavior (pre-upgrade) was:

Request a /56 allocation from Cox
Deploy the /56 as a /64 to:
LAN (igb1) with prefix "0"
IoT (opt1) with prefix "1"

With the 25.1.1 upgrade, this does not seem to work any more.

The log is filled with messages like:

Code Select Expand

RDNSS address 2001:579:4c:3700:a434:9a73:b10d:e091 received on igb1 from fe80::53bb:1ff4:f59c:40b3 is not advertised by us
AdvPreferredLifetime on igb1 for 2001:579:4c:3700:: doesn't agree with fe80::53bb:1ff4:f59c:40b3
AdvValidLifetime on igb1 for 2001:579:4c:3700:: doesn't agree with fe80::53bb:1ff4:f59c:40b3
I also spot that both internal interfaces (LAN and IoT, which are physical interfaces) end up with the same IPv6 address: 2001:579:4c:3700:2e0:67ff:fe1f:2529/64 which is apparently not a "reachable" address.

Rolling back to 25.1, IPv6 works as expected once again, internal systems are assigned IPv6 from the allocation, etc.

Not sure what else might be needed to troubleshoot /debug, but I'm game to deliver as requested...

[UN]

I had spotted the other thread, but when I checked the file I found:

Code Select Expand

# grep offloading /conf/config.xml
    <disablechecksumoffloading>1</disablechecksumoffloading>
    <disablesegmentationoffloading>1</disablesegmentationoffloading>
    <disablelargereceiveoffloading>1</disablelargereceiveoffloading>

The natives were getting restless in the household, so I girded my loins and moved the `eastpect` file out of `/usr/local/etc/rc.d`.

That worked and the WebUI came up on reboot.

Oddly, when I checked the system config I noticed that all the "offload" boxes were UNchecked.

Moving the `eastpect` file back where it started and rebooting worked as I would have expected before this evolution.  WebUI, SSH, etc. working.

Checking those boxes didn't change anything in the `/conf/config.xml` file, so maybe that's controlled /set somewhere else these days?

At any rate, I'm back up and running and managed to remove Zenarmor (it didn't work since it's missing the database).

Thanks for the pointers, it got me moving (even if I had a flop-sweat moment moving files around).

Not sure if anyone can help, but I screwed up and thought I'd try Zenarmor.

Unfortunately, I didn't read far enough into the "gotchas" to discover that turning on checksum offloading is a "Bad Idea (tm)" with Zenarmor.

Now my firewall is stuck with no WebUI, no SSH and no Serial/TTY console (spamming the "drop mbuf that needs checksum offload" message).

I built a NomadBSD USB and can mount up the correct partition - but can't find where the config files live to either:

1) Turn checksum offload "Off"
-or-
2) Disable Zenarmor so the WebUI starts and I can change the checksum offload there

Can anyone point me in the right direction?

Or have I just blown up my firewall and need to re-image from bare metal?

Here's my config.

For me the widget is titled "Interfaces" and is one of the default widgets on the Lobby/Dashboard page.

I'm on 24.7_9 and can confirm that the widget only displays the link-local IPv6 addresses, though via command line I can see that public IPv6 addresses are assigned to devices, which is confirmed by https://ip6only.me.

This is a follow-on to a prior post:
https://forum.opnsense.org/index.php?topic=39145.0

It looks like in order to fully meet https://www.rfc-editor.org/rfc/rfc4890, I need to create specific rules for some ICMPv6 types versus the "wide open everything" rule I have at the moment.

Digging into the available OPNSense and FreeBSD IPFW /PF documentation, this should be possible if I create rules from the command line by editing pf.conf?  ipfw.conf?  ipfw?  pfctl?  Something else?

But where, what syntax (since OPN seems to mix IPFW and PF), how to ensure that it's accepted by the system, etc. is still pretty darn foggy to me.

If my current understanding is correct, somewhere in the file structure I should be able to create a new file /rule something like:

pass in log quick inet6 proto ipv6-icmp all icmp6-type 4 code 2 keep state
pass out log quick inet6 proto ipv6-icmp from (self) to fe80::/10 icmp6-type 4 code 0

along with the other types /codes as listed in RFC4890

But how? And where?

Can anyone point me in the right direction so I don't self-inflict a breakage?

Oddly, I just ran across a forum topic from 2019 that looked like it was going to help /maybe resolve the issue - but then the author got distracted and never tested /implemented the update code..

https://forum.opnsense.org/index.php?topic=14891.0

[Transit through the Firewall:]

Wow - yup.

Hadn't tried the "hover" reveal, but the list of ICMPv6 types is not at all complete per RFC 4890.

I've been searching and can't find where OPNSense defines ICMP /ICMPv6 Types or how to build PF rules where a type is not named (the "Undefined" numerics).

The only ICMPv6 types that I can see in-use are:

• Type 1 Destination Unreachable (unreach)
• Type 2 Packet Too Big (toobig)
• Type 128 Echo Request (echoreq)
• Type 129 Echo Reply (echorep)
• Type 133 Router Solicitation (routersol)
• Type 134 Router Advertisement (routeradv)
• Type 135 Neighbor Solicitation (neighborsol)
• Type 136 Neighbor Advertisement (neighboradv)

With a few more pre-defined in the "drop-down" but those look more like they are comingled with ICMPv4 from a strict "Human readable name" perspective.

I see an array in /usr/local/www/firewall_rules.php, but I'm not willing to edit that and I don't see any of the icmp6types showing up in the WebUI.

Anyone have a good link /doc where I can use the WebUI or command line (pfctl) to define types /codes, add them by number to a table, or otherwise build correct rules?

It feels like the WebUI is not robust /flexible enough (unless I've missed something) so I am likely stuck adding rules via command line...

If my read is correct, then the "Automatic" rules for ICMPv6 should encompass:

Transit through the Firewall:
Must Not Drop (§4.3.1):
  Type 1, Type 2, Type 3 Code 0, Type 4 Code 1, Type 4 Code 2, Type 128-129
Should Not Drop (§4.3.2):
  Type 3 Code 1, Type 4 Code 0, Type 144-147
Needs a rule (§4.3.4):
  Must Allow:
   Seamoby
    Type 150
   Undefined Error Messages:
    Type 5-99, 102-126
   Unallocated Informational Messages:
    Type 154-199
    Type 202-254

Not sure about these - maybe a "checkbox" somewhere to turn them on?
Should Drop barring defined need (§4.3.5):
Type 100-101, Type 127, Type 138-140, Type 200-201, Type 255

Local Traffic (LAN, WAN, Link Local, etc.):
Must Not Drop (§4.4.1):
Type 1, Type 2, Type 3 Code 0, Type 4 Code 1, Type 4 Code 2, Type 128-136, Type 141-143, Type 148, Type 149, Type 151-153
Should Not Drop (§4.4.2):
Type 3 Code 1, Type 4 Code 0
Needs a Rule (4.4.4):
  Must Allow:
   Type 137
  If Experimental:
   Type 139-140
  Undefined Error Messages:
   Type 5-99
   Type 102-126

Not sure about these - maybe a "checkbox" somewhere to turn them on?
Should Drop barring defined need (§4.4.5):
Type 100-101, 127
Type 154-199
Type 200-255

The Automatically Generated Rules for ICMPv6 are present in my 24.1.2 system:


But for whatever reason, IPv6 does not work without the custom /manual ICMPv6 rule.

I've reverted to 24.1.1 and re-upgraded to 24.1.2 twice, with a "Factory Default" reset each time and on 24.1.2 IPv6 does not work until I put the ICMPv6 rule in place.

If there's further debug /troubleshooting data that would help isolate the issue, I'm game to track /search and post...

It's the most basic and simple of rules:

Code Select Expand

pass in quick on igb1 inet6 proto ipv6-icmp all keep state (LAN)

Code Select Expand

pass in quick on igb0 inet6 proto ipv6-icmp all keep state (WAN)

or



I thought about trying to build out a duplicate of the RFC4890 "Automatic" rules, but once I read a bit more and realized that since, by design, ICMPv6 doesn't pose the same sort of Command and Control /data leakage risk that ICMPv4 does, I used a "blanket" rule.

If you know of any reason why that might be "bad", let me know and I'll build the duplicates...

In order:

1 - At least for my deployment, I think I've solved the problem.
2 - Yes, it was happening across all platforms (Windows, Linux, MacOS, Android, Network /Switch gear, etc.)
3 - Yes, I restarted radvd and dhcpdv6 after each "Save /Apply".

I got frustrated last night and rolled back to v24.1.1.

As expected, IPv6 worked "normally".

I did find that (from the web console):
1 - The ISC DHCPv6 configuration did not need to have the range configured to function
2 - Router Advertisements was not enabled
3 - There was a set of "Automatically generated rules" that allowed ICMPv6 for LAN and WAN

So I went back to v24.1.2 (still no IPv6 connectivity) and made one change.

I created a rule for both LAN and WAN that allowed all ICMPv6.

Even though there are "Automatically generated rule"(s) that look identical to the ICMPv6 rules in place in v24.1.1 on both interfaces, once I created the Custom rule, IPv6 started working.

Disable the Custom ICMPv6 rule - IPv6 "breaks" again...

Maybe it's my hardware - maybe I'm just unlucky, but with all the great help and ideas /guidance /troubleshooting here at least it's now working...

It's a pretty simplistic network:



I say the "Provided" gateway as in the LAN 2009:... which is from the Cox allocation.

The two fe80: IP's on the WAN side are "Unreachable".

Code Select Expand

C:\Windows\System32>ping 2001:579:4c:3700:2e0:67ff:fe1f:2529

Pinging 2001:579:4c:3700:2e0:67ff:fe1f:2529 with 32 bytes of data:
Reply from 2001:579:4c:3700:2e0:67ff:fe1f:2529: time<1ms
Reply from 2001:579:4c:3700:2e0:67ff:fe1f:2529: time<1ms
Reply from 2001:579:4c:3700:2e0:67ff:fe1f:2529: time<1ms
Reply from 2001:579:4c:3700:2e0:67ff:fe1f:2529: time<1ms

Ping statistics for 2001:579:4c:3700:2e0:67ff:fe1f:2529:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Windows\System32>ping fe80::2e0:67ff:fe1f:2528

Pinging fe80::2e0:67ff:fe1f:2528 with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for fe80::2e0:67ff:fe1f:2528:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Windows\System32>ping fe80::2ef8:9bff:fe9d:b419

Pinging fe80::2ef8:9bff:fe9d:b419 with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for fe80::2ef8:9bff:fe9d:b419:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Windows\System32>

[DHCPDv6]

Here is the DHCPDv6 stanza.

I did "turn on" Default Gateway during the troubleshooting (checkbox selected and the "ranodefault" no longer appears in conf/config.xml), but it did not make a difference.

Troubleshooting over the weekend:
1 - Set up an additional Microsoft Windows 11 system from scratch (same IPv6 problem)
2 - Completely reset the Network Interfaces and the Network Stack on the original Microsoft system (no change)
3 - Tested a MacOS system (same IPv6 problem) borrowed from a friend

All LAN systems can see /ping the "IPv6 Default Gateway" provided by my ISP (fe80::2ef8:9bff:fe9d:b419) and other LAN systems using both the Private and Public IPv6 addresses, but cannot reach any system on the Public Internet.

DHCPDv6

Code Select Expand

<dhcpdv6>
  <lan>
    <ddnsdomainalgorithm>hmac-md5</ddnsdomainalgorithm>
    <enable>1</enable>
    <range>
      <from>2001:579:4c:3700::</from>
      <to>2001:579:4c:3700:ffff:ffff:ffff:ffff</to>
    </range>
    <prefixrange>
      <from/>
      <to/>
      <prefixlength>64</prefixlength>
    </prefixrange>
    <dnsserver>fde4:b3e2:db9e:1000::11</dnsserver>
    <ntpserver>fde4:b3e2:db9e:1000::11</ntpserver>
    <numberoptions>
      <item/>
    </numberoptions>
    <ramode>assist</ramode>
    <rapriority>medium</rapriority>
    <ramininterval>200</ramininterval>
    <ramaxinterval>600</ramaxinterval>
    <radomainsearchlist/>
    <radnsserver/>
    <rasamednsasdhcp6>1</rasamednsasdhcp6>
  </lan>
</dhcpdv6>

Microsoft Windows IPv6 Route

Code Select Expand

C:\>route print -6
===========================================================================
Interface List
22...f0 2f 74 d3 b8 d0 ......Realtek PCIe 2.5GbE Family Controller #2
29...00 15 5d 58 33 d0 ......Hyper-V Virtual Ethernet Adapter #5
15...f0 2f 74 d3 b8 52 ......Intel(R) I211 Gigabit Network Connection #2
19...0a 00 27 00 00 13 ......VirtualBox Host-Only Ethernet Adapter
  5...00 ff 15 55 9b 77 ......TAP-Windows Adapter V9 for OpenVPN Connect
25...........................OpenVPN Data Channel Offload
30...b4 0e de f7 4d 41 ......Bluetooth Device (Personal Area Network)
  1...........................Software Loopback Interface 1
36...00 15 5d 8f c9 29 ......Hyper-V Virtual Ethernet Adapter
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
  1    331 ::1/128                  On-link
15    281 2001:579:4c:3700::/64    On-link
15    281 2001:579:4c:3700:5be9:bf0:9b9f:3923/128
                                    On-link
15    281 2001:579:4c:3700:cc03:b286:53d8:a7fb/128
                                    On-link
15    281 fde4:b3e2:db9e:1000::/64 On-link
15    281 fde4:b3e2:db9e:1000:5555::6b1e/128
                                    On-link
15    281 fde4:b3e2:db9e:1000:c08d:7634:5276:2feb/128
                                    On-link
15    281 fde4:b3e2:db9e:1000:cc03:b286:53d8:a7fb/128
                                    On-link
19    281 fe80::/64                On-link
15    281 fe80::/64                On-link
36   5256 fe80::/64                On-link
19    281 fe80::6b4e:bc42:6225:64b2/128
                                    On-link
36   5256 fe80::7ce3:8317:eb17:da67/128
                                    On-link
15    281 fe80::e0be:a038:5030:f7f2/128
                                    On-link
  1    331 ff00::/8                 On-link
19    281 ff00::/8                 On-link
15    281 ff00::/8                 On-link
36   5256 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

C:\>netsh interface ipv6 show route

Publish  Type      Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ---  ------------------------  ---  ------------------------
No       System    256  ::1/128                     1  Loopback Pseudo-Interface 1
No       Manual    256  2001:579:4c:3700::/64      15  Ethernet 4
No       System    256  2001:579:4c:3700:5be9:bf0:9b9f:3923/128   15  Ethernet 4
No       System    256  2001:579:4c:3700:cc03:b286:53d8:a7fb/128   15  Ethernet 4
No       Manual    256  fde4:b3e2:db9e:1000::/64   15  Ethernet 4
No       System    256  fde4:b3e2:db9e:1000:5555::6b1e/128   15  Ethernet 4
No       System    256  fde4:b3e2:db9e:1000:c08d:7634:5276:2feb/128   15  Ethernet 4
No       System    256  fde4:b3e2:db9e:1000:cc03:b286:53d8:a7fb/128   15  Ethernet 4
No       System    256  fe80::/64                  29  vEthernet (Default Switch (Wi-Fi))
No       System    256  fe80::/64                  19  Ethernet 3
No       System    256  fe80::/64                  25  OpenVPN Connect DCO Adapter
No       System    256  fe80::/64                   5  Local Area Connection
No       System    256  fe80::/64                  22  Ethernet 5
No       System    256  fe80::/64                  15  Ethernet 4
No       System    256  fe80::/64                  30  Bluetooth Network Connection
No       System    256  fe80::/64                  36  vEthernet (Default Switch)
No       System    256  fe80::42cc:5baf:e39e:6a0f/128   30  Bluetooth Network Connection
No       System    256  fe80::493c:96ef:b3b1:1fae/128   29  vEthernet (Default Switch (Wi-Fi))
No       System    256  fe80::6b4e:bc42:6225:64b2/128   19  Ethernet 3
No       System    256  fe80::7ce3:8317:eb17:da67/128   36  vEthernet (Default Switch)
No       System    256  fe80::b847:d5ca:dbb3:ee08/128   22  Ethernet 5
No       System    256  fe80::d18b:9f01:61a2:2f2e/128    5  Local Area Connection
No       System    256  fe80::e0be:a038:5030:f7f2/128   15  Ethernet 4
No       System    256  fe80::ff59:d680:5693:b9e4/128   25  OpenVPN Connect DCO Adapter
No       System    256  ff00::/8                    1  Loopback Pseudo-Interface 1
No       System    256  ff00::/8                   29  vEthernet (Default Switch (Wi-Fi))
No       System    256  ff00::/8                   19  Ethernet 3
No       System    256  ff00::/8                   25  OpenVPN Connect DCO Adapter
No       System    256  ff00::/8                    5  Local Area Connection
No       System    256  ff00::/8                   22  Ethernet 5
No       System    256  ff00::/8                   15  Ethernet 4
No       System    256  ff00::/8                   30  Bluetooth Network Connection
No       System    256  ff00::/8                   36  vEthernet (Default Switch)


C:\>C:\>ping 2001:4860:4860::8888

Pinging 2001:4860:4860::8888 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

Ping statistics for 2001:4860:4860::8888:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>

Very relevant to the thread (in my opinion anyhow).

Something changed about how OPNsense is handling IPv6 between the 24.1.1 and the 24.1.2 releases and it's causing me issues.

I did check my IPv6 neighbors on Windows 11 and have the same "Unreachable" results that you have (different ranges of course).

I read through the most recent doc page on "Router Advertising" - nothing stands out as being "different", though just having to enable it is new in the 24.1.2 release (either it was "automagickal" in 24.1.1 or DHCPv6 was handling the RA part as well).

Hopefully wiser and more experienced folks here can help us provide enough data to troubleshoot and resolve...

Just for grins - here's what a Microsoft Windows system sees.

Interface

Code Select Expand

Ethernet adapter Ethernet 4:

   Connection-specific DNS Suffix  . : lan.local.us
   Description . . . . . . . . . . . : Intel(R) I211 Gigabit Network Connection #2
   Physical Address. . . . . . . . . : F0-2F-74-D3-B8-52
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:579:4c:120:8bf1:529:2289:3504(Preferred)
   IPv6 Address. . . . . . . . . . . : fde4:b3e2:db9e:1a29::eb1e(Preferred)
   Lease Obtained. . . . . . . . . . : Friday, March 1, 2024 09:38:41
   Lease Expires . . . . . . . . . . : Saturday, March 2, 2024 09:38:40
   IPv6 Address. . . . . . . . . . . : fde4:b3e2:db9e:1a29:bfcb:42c0:7157:544b(Preferred)
   Temporary IPv6 Address. . . . . . : 2001:579:4c:120:7c17:d9fb:7c25:26cf(Preferred)
   Temporary IPv6 Address. . . . . . : fde4:b3e2:db9e:1a29:7c17:d9fb:7c25:26cf(Preferred)
   Link-local IPv6 Address . . . . . : fe80::e0be:a038:5030:f7f2%16(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.144.21(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Friday, March 1, 2024 09:37:55
   Lease Expires . . . . . . . . . . : Saturday, March 2, 2024 09:37:55
   Default Gateway . . . . . . . . . : fe80::2e0:67ff:fe1f:2529%16
                                       192.168.144.1
   DHCP Server . . . . . . . . . . . : 192.168.144.11
   DHCPv6 IAID . . . . . . . . . . . : 703606644
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2A-D5-E4-3E-B4-0E-DE-F7-4D-3D
   DNS Servers . . . . . . . . . . . : fde4:b3e2:db9e:1a29::11
                                       192.168.144.11
   NetBIOS over Tcpip. . . . . . . . : Enabled

Routes

Code Select Expand

C:\>route print -6
===========================================================================
Interface List
22...f0 2f 74 d3 b8 d0 ......Realtek PCIe 2.5GbE Family Controller #2
30...00 15 5d 58 33 d0 ......Hyper-V Virtual Ethernet Adapter #5
16...f0 2f 74 d3 b8 52 ......Intel(R) I211 Gigabit Network Connection #2
19...0a 00 27 00 00 13 ......VirtualBox Host-Only Ethernet Adapter
  7...00 ff 15 55 9b 77 ......TAP-Windows Adapter V9 for OpenVPN Connect
26...........................OpenVPN Data Channel Offload
32...b4 0e de f7 4d 41 ......Bluetooth Device (Personal Area Network)
  1...........................Software Loopback Interface 1
24...00 15 5d 8f c9 29 ......Hyper-V Virtual Ethernet Adapter
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
  1    331 ::1/128                  On-link
16    281 2001:579:4c:120::/64     On-link
16    281 2001:579:4c:120:7c17:d9fb:7c25:26cf/128
                                    On-link
16    281 2001:579:4c:120:8bf1:529:2289:3504/128
                                    On-link
16    281 fde4:b3e2:db9e:1a29::/64 On-link
16    281 fde4:b3e2:db9e:1a29::eb1e/128
                                    On-link
16    281 fde4:b3e2:db9e:1a29:7c17:d9fb:7c25:26cf/128
                                    On-link
16    281 fde4:b3e2:db9e:1a29:bfcb:42c0:7157:544b/128
                                    On-link
19    281 fe80::/64                On-link
16    281 fe80::/64                On-link
24   5256 fe80::/64                On-link
19    281 fe80::6b4e:bc42:6225:64b2/128
                                    On-link
24   5256 fe80::7061:9fd4:cd1f:fa4f/128
                                    On-link
16    281 fe80::e0be:a038:5030:f7f2/128
                                    On-link
  1    331 ff00::/8                 On-link
19    281 ff00::/8                 On-link
16    281 ff00::/8                 On-link
24   5256 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

C:\>netsh interface ipv6 show route

Publish  Type      Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ---  ------------------------  ---  ------------------------
No       System    256  ::1/128                     1  Loopback Pseudo-Interface 1
No       Manual    256  2001:579:4c:120::/64       16  Ethernet 4
No       System    256  2001:579:4c:120:7c17:d9fb:7c25:26cf/128   16  Ethernet 4
No       System    256  2001:579:4c:120:8bf1:529:2289:3504/128   16  Ethernet 4
No       Manual    256  fde4:b3e2:db9e:1a29::/64   16  Ethernet 4
No       System    256  fde4:b3e2:db9e:1a29::eb1e/128   16  Ethernet 4
No       System    256  fde4:b3e2:db9e:1a29:7c17:d9fb:7c25:26cf/128   16  Ethernet 4
No       System    256  fde4:b3e2:db9e:1a29:bfcb:42c0:7157:544b/128   16  Ethernet 4
No       System    256  fe80::/64                  30  vEthernet (Default Switch (Wi-Fi))
No       System    256  fe80::/64                  19  Ethernet 3
No       System    256  fe80::/64                  26  OpenVPN Connect DCO Adapter
No       System    256  fe80::/64                   7  Local Area Connection
No       System    256  fe80::/64                  22  Ethernet 5
No       System    256  fe80::/64                  16  Ethernet 4
No       System    256  fe80::/64                  32  Bluetooth Network Connection
No       System    256  fe80::/64                  24  vEthernet (Default Switch)
No       System    256  fe80::42cc:5baf:e39e:6a0f/128   32  Bluetooth Network Connection
No       System    256  fe80::493c:96ef:b3b1:1fae/128   30  vEthernet (Default Switch (Wi-Fi))
No       System    256  fe80::6b4e:bc42:6225:64b2/128   19  Ethernet 3
No       System    256  fe80::7061:9fd4:cd1f:fa4f/128   24  vEthernet (Default Switch)
No       System    256  fe80::b847:d5ca:dbb3:ee08/128   22  Ethernet 5
No       System    256  fe80::d18b:9f01:61a2:2f2e/128    7  Local Area Connection
No       System    256  fe80::e0be:a038:5030:f7f2/128   16  Ethernet 4
No       System    256  fe80::ff59:d680:5693:b9e4/128   26  OpenVPN Connect DCO Adapter
No       System    256  ff00::/8                    1  Loopback Pseudo-Interface 1
No       System    256  ff00::/8                   30  vEthernet (Default Switch (Wi-Fi))
No       System    256  ff00::/8                   19  Ethernet 3
No       System    256  ff00::/8                   26  OpenVPN Connect DCO Adapter
No       System    256  ff00::/8                    7  Local Area Connection
No       System    256  ff00::/8                   22  Ethernet 5
No       System    256  ff00::/8                   16  Ethernet 4
No       System    256  ff00::/8                   32  Bluetooth Network Connection
No       System    256  ff00::/8                   24  vEthernet (Default Switch)

ICMP Ping test to OPN RA Gateway

Code Select Expand

C:\>ping -6 fe80::2e0:67ff:fe1f:2529

Pinging fe80::2e0:67ff:fe1f:2529 with 32 bytes of data:
Reply from fe80::2e0:67ff:fe1f:2529: time<1ms
Reply from fe80::2e0:67ff:fe1f:2529: time<1ms
Reply from fe80::2e0:67ff:fe1f:2529: time<1ms
Reply from fe80::2e0:67ff:fe1f:2529: time<1ms

Ping statistics for fe80::2e0:67ff:fe1f:2529:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

ICMP Ping to Public IPv6

Code Select Expand

C:\>ping -6 2001:4860:4860::8888

Pinging 2001:4860:4860::8888 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

Ping statistics for 2001:4860:4860::8888:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),