Messages

Agreed, the graphs look great. It would be nice if they could display both IPv4 and IPv6 traffic.

I have three different OPNsense VMs running on windows server 2019 hyper-v (not all at the same time, but different versions). It's correct that the installer still requires being interrupted in two places, but aside from that, it installs and runs fine. The installer problem is not a show-stopper.

As for your other problem, I haven't experienced it. I occasionally encounter a message that OPNsense cannot communicate with the update server, but it usually works if I try again.

Worst case you borked your ABI mirror link...

Try this first:

# opnsense-revert -r 20.1.9 opnsense-devel

If that doesn't download...

# opnsense-update -sn "20.1\/latest"

And try again.


Cheers,
Franco

Thank you for the reply.

I tried opnsense-revert -r 20.1.9 opnsense-devel. It completed without any apparent issues. I rebooted after that and it's working. However, after that, I did opnsense-update and opnsense code core.

Here is the output:

Code Select Expand

root@OPNsense:/usr/core # opnsense-code core
Fetching origin
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

  git config pull.rebase false  # merge (the default strategy)
  git config pull.rebase true   # rebase
  git config pull.ff only       # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.

Already up to date.
ABI 20.1 is no longer supported
Fetching origin
Already up to date.


After that, I tried opnsense-update -sn "20.1\/latest" and then did opnsense-update and opnsense code core. There was no difference. Something seems to be borked, alright.

Do you have any other suggestions or should should I reinstall it?

I tried git config pull.rebase true before opnsense-code core. The same message appeared as I posted previously.

The system is now at:

OPNsense 21.1.a_15-amd64
FreeBSD 11.2-RELEASE-p20-HBSD
OpenSSL 1.1.1g 21 Apr 2020

Is there any way to fix the issue that's causing the message?

I'm running this version:

OPNsense 20.7.b_244-amd64
FreeBSD 11.2-RELEASE-p20-HBSD
OpenSSL 1.1.1g 21 Apr 2020

I updated using the following"

opnsense-update

This results in:

Nothing to do.

opnsense-code core

This result in the following:

Fetching origin
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

  git config pull.rebase false  # merge (the default strategy)
  git config pull.rebase true   # rebase
  git config pull.ff only       # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.

Already up to date.
ABI 20.1 is no longer supported
Fetching origin
warning: Pulling without specifying how to reconcile divergent branches is
discouraged. You can squelch this message by running one of the following
commands sometime before your next pull:

  git config pull.rebase false  # merge (the default strategy)
  git config pull.rebase true   # rebase
  git config pull.ff only       # fast-forward only

You can replace "git config" with "git config --global" to set a default
preference for all repositories. You can also pass --rebase, --no-rebase,
or --ff-only on the command line to override the configured default per
invocation.

Already up to date.

What is the recommended next step?

Remember to install the new dhcp6c...

I didn't update anything. dhcp6c seems to be working fine as-is.

I installed it in a generation 2 vm on a windows 2019 hyper-v server. The installer hung a couple of times at the same places as have been reported before. Like before, I was able to get past by interrupting it using CTRL-C and re-logging in.

Every time I executed /sbin/rtsol, there was an RS and an RA, observed using wireshark.

Here is the output from the command line:

Code Select Expand

root@OPNsense:~ # /sbin/rtsol -a
root@OPNsense:~ # /sbin/rtsol -d -a
probing hn0
root@OPNsense:~ # /sbin/rtsol -D -a
probing hn0
checking if hn0 is ready...
hn0 is ready
set timer for hn0 to 0s
New timer is 0s
timer expiration on hn0, state = 1
send RS on hn0, whose state is 2
set timer for hn0 to 4s
New timer is 4s
received RA from fe80::ea4:2ff:fe29:5001 on hn0, state is 2
Processing RA
ndo = 0x1b285594c20
ndo->nd_opt_type = 1
ndo->nd_opt_len = 1
rsid = [hn0:slaac]
stop timer for hn0
there is no timer
root@OPNsense:~ #


pretty sure we've been down this road before with your system. I think we have to manually add a gateway for dpinger to use.

There is hn0_router and hn0_pdinfo, but no hn0_routerv6. We've done a lot of hacking over the past few years, but I don't recall ever having to manually add a gateway. The default route points to the gateway so the system already knows about it. Why would it have to be manually created?

can you look in /tmp/ and see if you have a file called ***_defaultgw6 ?

There is no such file.

ok, re-Read the message.  that's pretty odd... can you email me an image of the gateways single page.

Here are some screen captures.

In the main gateways page the address is under 'Gateway'. Are you saying there's no entry for your WAN dhcp6 in gateways at all?

No, that's not what I meant. System: Gateways: Single shows both gateways. Interfaces: Overview WAN shows information about both gateways, but it does not report an address for the IPv6 gateway. The address isn't blank or ~, there is not even a line for it.

Hmm.. I think I might know why.  If you look at system->gateways->single, is that showing an entry?

System / Gateways / Single shows both the IPv4 and IPv6 gateways.

So it it's only the lobby widget that's missing the IPv6 gateway then?

The lobby widget is reporting the IPv6 gateway address as ~ and there is no reported IPv6 gateway address in Interfaces / Overview / Wan. It's not blank or ~. There isn't a line for the address.

Can you send me the output of netstat -6rW please.

Here you go:

Code Select Expand

root@OPNsense:~ # netstat -6rW
Routing tables

Internet6:
Destination        Gateway            Flags       Use    Mtu    Netif Expire
default            fe80::ea4:2ff:fe29:5001%hn0 UG     9025   1500      hn0
localhost          link#1             UH            0  16384      lo0
node-1w7jr9ql8gh2x5hajvvh1dr7k.ipv6.telus.net link#6 U          2894   1500      hn1
OPNsense           link#6             UHS           0  16384      lo0
fe80::%lo0/64      link#1             U             0  16384      lo0
fe80::1%lo0        link#1             UHS           0  16384      lo0
fe80::%hn0/64      link#5             U         83596   1500      hn0
fe80::215:5dff:fe67:5b19%hn0 link#5   UHS           0  16384      lo0
fe80::%hn1/64      link#6             U        128314   1500      hn1
fe80::215:5dff:fe67:5b1a%hn1 link#6   UHS           0  16384      lo0
root@OPNsense:~ #


Hmm.. I think I might know why.  If you look at system->gateways->single, is that showing an entry?

System / Gateways / Single shows both the IPv4 and IPv6 gateways.