Topics

Any solution to this problem?

***GOT REQUEST TO UPDATE***
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.

flowd-0.9.1_3 is locked and may not be modified
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
Nothing to do.
Nothing to do.
Starting web GUI...done.
Generating RRD graphs...done.
Fetching base-21.7.7-amd64.txz: ............................... failed, no signature found
***DONE***

I'm looking for help trying to troubleshoot IPv6 issues.  All of this is done FROM an SSH/console login to OpnSense (e.g. the shell; forget about what happens on the LAN side).

When OpnSense is rebooted, IPv6 works for a couple minutes, then it just stops working.  By working I mean ping6 or traceroute6 from OpnSense on the WAN interface.

For example, reboot OpnSense, then login to the console (or ssh).  From the shell, I can successfully ping6 google.com.  Wait a couple minutes, retry the command and it fails.  This has been happening for a couple months (ever since my ISP did some maintenance a few months ago).  I haven't been able to get them to reveal what those changes were or really say anything.  So what I'm looking for is a way to troubleshoot what might be happening where it works only for a couple minutes after a reboot.  This is repeatable.  Are there any commands I can use to try and diagnose what's happening?

I did read that someone suggested using 'netstat -rn6' to check the routing table.

root@OPNsense:~ # netstat -rn6
Routing tables

Internet6:
Destination                       Gateway                       Flags     Netif Expire
default                           fe80::224:45ff:fe8e:cbd3%vmx0 UGS        vmx0
::1                               link#4                        UH          lo0
2605:9480:10b:4000::/50           link#1                        U          vmx0
2605:9480:258:ff10::/64           link#2                        U          vmx1
2605:9480:258:ff10:250:56ff:fea0:fe73 link#2                    UHS         lo0
fe80::%vmx0/64                    link#1                        U          vmx0
fe80::250:56ff:fea0:c131%vmx0     link#1                        UHS         lo0
fe80::%vmx1/64                    link#2                        U          vmx1
fe80::250:56ff:fea0:fe73%vmx1     link#2                        UHS         lo0
fe80::%lo0/64                     link#4                        U           lo0
fe80::1%lo0                       link#4                        UHS         lo0

Sample of the issue (the following is a single copy/paste where the commands were run just a couple minutes apart after a reboot):

root@OPNsense:~ # ping6 google.com
PING6(56=40+8+8 bytes) 2605:9480:258:ff10:250:56ff:fea0:fe73 --> 2607:f8b0:4006:802::200e
16 bytes from 2607:f8b0:4006:802::200e, icmp_seq=0 hlim=117 time=9.095 ms
16 bytes from 2607:f8b0:4006:802::200e, icmp_seq=1 hlim=117 time=9.187 ms
16 bytes from 2607:f8b0:4006:802::200e, icmp_seq=2 hlim=117 time=9.324 ms
^C
--- google.com ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 9.095/9.202/9.324/0.094 ms
root@OPNsense:~ # ping6 google.com
PING6(56=40+8+8 bytes) 2605:9480:258:ff10:250:56ff:fea0:fe73 --> 2607:f8b0:4006:81a::200e
^C
--- google.com ping6 statistics ---
25 packets transmitted, 0 packets received, 100.0% packet loss

I've been using OpnSense for a few years now and it's worked well.  However, it's become quite unreliable as of lately.  The current symptom is that every 1-5 days it starts to fail rather suddenly.  The exact symptom is network throughput from the LAN starts to fail (~50% packet loss when pinging google.com or 8.8.8.8).  At the same time that happens the web login interface from the LAN also fails (just stops responding completely).  From the console, when I login ping rates out the WAN seem consistent (~50% packet loss).  Restarting the services (11 in the menu) doesn't resolve the problem.  The only resolution is to reboot (again, you'd have to do this from the console since the web login interface has stopped responding entirely).  This is all ipv4.

For a couple versions now in the 2.7.x releases, the web proxy (squid) doesn't work anymore.  It was working then after an upgrade fails.  The error showing up in the system log (system > log files > general), is "FATAL: No valid signing certificate configured for HTTP_port <ip address>".  I don't have any custom certs installed.  Squid was working a couple releases ago.

The ntopng plugin doesn't seem to be able to start.  I've got it and the redis package installed.  I'm running 19.7.2.  I also searched the forum and didn't really find anything that seemed helpful to me.  Is this a known issue?