To 2.5.0 or not ? that is the question :)
-
Installed fresh from 2.5 image.
restored 2.4.5p1 .xml.
Everything works again, EXCEPT LAN Traffic Graph.Bummer, something in my .xml config?
I can't seem to find the reason...@buggz said in To 2.5.0 or not ? that is the question :):
Hmm, well, cleared the error, but still no traffic for LAN shown on the Traffic Graph...
-
What is your LAN interface? Anything special?
-
@pfworker79 said in To 2.5.0 or not ? that is the question :):
V2.4.5 configuration is not compatible with v2.5.0.
In what way? You can import a 2.4.5 config into 2.5.
Steve
-
@stephenw10
No special LAN settings that I know of.
LAN is set to IPV4 ONLY.
IPV6 is turned OFF on BOTH the WAN and LAN.
WAN Traffic Graph works good. -
Hmm, the only place I have seen that is odd interface types, like wireguard, where there is a known issue.
-
@stephenw10 Didn't work here. Importing the whole config resulted in no internet, GUI or SSH access. Only pinging the firewall worked.
-
Hmm, must be something specific in your config then. In general that should always be possible.
Steve
-
@buggz said in To 2.5.0 or not ? that is the question :):
@stephenw10
No special LAN settings that I know of.
LAN is set to IPV4 ONLY.
IPV6 is turned OFF on BOTH the WAN and LAN.
WAN Traffic Graph works good.POOF, and now on reboot, the WAN interface is out, not updating.
Hard to believe I am the only one with this problem...
-
This post is deleted! -
What is your WAN type?
How is it failing? The actual link goes down? Not pulling an IP?
Steve
-
@stephenw10
EVERYTHING, EXCEPT the LAN Traffic Monitor works.
I changed the time on my Win10 box, it has the Chrome interface to the pfSense box, and the WAN Traffic Monitor recovered, now works. That was strange.
LAN Traffic Monitor is still NOT working.
Though, worked great in the previous release.
Tried Firefox, still no go. -
Like the traffic graphs? Can we see a screenshot?
We have seen problems there before with a bad timezone.
Steve
-
-
Ah, yes sorry I conflated some topics there
Hmm, do you see the interface stats incrementing for LAN? What driver is it?
Steve
-
@stephenw10
Yes, Interface Statistics is updating.Intel OEM I350-T4
dmesg shows it is using:
igb0: <Intel(R) PRO/1000 PCI-Express Network Driver> mem 0xf7b00000-0xf7bfffff,0xf7c0c000-0xf7c0ffff irq 16 at device 0.0 on pci2Hmm, I can't remember what driver the former release used...
-
@buggz I'm facing issues using VLAN's with v2.5.0, where all VLAN tagged interfaces reports some output errors. Seems it has something to do with the 'igb' driver and IPv6. It doesn't affect the performance in any noticeable way, but it wasn't present in v2.4.5. After some research, it seems to do with the Intel 'igb' driver bundled with FreeBSD 12.2-STABLE. Following is a link to others facing the same problem:
https://github.com/opnsense/src/issues/74
I'm not experiencing problems with the traffic graphs, but maybe this got something to do with it. Hope this gets fixed in the next release.
-
Hmm, that doesn't seem to be generally the case. I have a whole bunch of boxes with igb NICs and VLANs and haven't noticed anything . Of course now I'm going to go digging....
But that seems unlikely to be related to this graphing issue.
Steve
-
Wow, and now LAN Traffic Graph magically works for the first time.
I did update ntopng to the latest, but it didn't work then.
Does now on reboot. -
Still in 2.5.0 or 2.5.1-RC snapshots?
Steve
-
Is wireguard being pulled from 2.5.1? I wasn’t able to update to latest RC (2.5.1.r.20210320.0824 ) due to having 'wireguard tunnels enabled'. I understood it was being pulled from the kernel until the version Jason is currently developing is integrated into FreeBSD (13.2?), but I assumed the Netgate funded version would remain in pfSense until that swap could be made as the security implications were only a concern if admin access had already been compromised?
0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option: 13 ERROR: There are WireGuard tunnels enabled on your config. Please remove or disable them before proceed.
