Messages

For example -- https://docs.opnsense.org/manual/how-tos/multiwan.html

When will topics like these be updated to reflect the changes in firewall rules in v26?
Can these be netered as rules under the old system and them migrated to new?

Thanks

If the devices managed use DHCP  ;)

I'm not sure what your response means.. The managed device shown does used DHCP, and also has a static mapping.  But that "DHCP Leases Status" link shown on the widget has a broken link to https://{Router_IP}/status_dhcp_leases.php  -- my thoughts are that if there is a static mapping to DHCP with the MAC address, the widget should be able to accurately show the online status -- if thats what the goal is.  Otherwise, Im not sure what the intent of the "Online" indicator is in the widget

I agree -- but there is a "status" for each host, as well as a broken link to "DHCP Leases Status", so I am assuming at some point there was some kind of ability to do an IP lookup on the DHCP table?

If you look at my screenshot, the widget is identifying this host as "Online" -- but its really off.  What I can do with the widget is wake the host.. But it would be helpful if I knew whether or not the host had already gone to sleep or not.

I noticed that the WOL widget always shows my WOL hosts as "online" instead of its true status.. I'm assuming this is because the widget is checking if the MAC is in the ARP table?  Is there any way to change this behavior to actually report if the host is up by pinging it?

Thanks

I'm apparently on the beta channel running AdGuard Home v0.108.0-b.17 and it fails when I update from the UI to AdGuard Home v0.108.0-b.18..  I'll give it a few days, the updates from the UI had been working fine for months.

When going to Interfaces: Diagnostics: ARP Table, there is a hostname column..  However, on my system - exactly one host of around 120 in the table show a hostname .  Is this column supposed to populate with hostnames from someplace? 

Is it possible to add a UI element to have the option of forcing the previous behavior?  IIRC, prior to 21.1 - if I tried to add a static mapping that was inside the designated pool ranges, I would get a warning that I couldn't do so.. Am I wrong here?  Apparently, I missed the "dhcp: removed the need for a static IPv4 being outside of the pool (contributed by Gauss23)" release note from back then -- and I have assigned MAC address to IPs in my pool range -- only to discover that other devices were grabbing reserved IPs when the original mapped devices were powered off.

I'm not even sure what the rationale was of removing this requirement if the underlying DHCP service didn't actually reserve it..  Now I'm in the process of remapping my static maps and setting up new pool ranges -- and in the future reminding myself that I have to make sure myself that I dont statically map in those pool ranges.

Thanks

Also experienced WAN issues with 22.1.2_1 here... I was using MAC spoofing on the WAN interface, but removed it for troubleshooting.  I am not using IPS on this device.  One of the issues I have is that if my upstream device (cable modem) reboots, the DHCP client does not appear to get an IP again once the link returns -- the GUI just displays "dhcp" -- I have to manually reboot the entire firewall in order to get an IP on the WAN interface again. 

Second -- on reboots, my Wireguard VPN fails and stays that way because the initialization for that takes place while the WAN is still broken -- and even when it returns, it doesn't attempt to fix itself.. So I have to manually disable Wireguard and re-enable it for it to work.

Hi,

clear the cache of your browser.
See: https://forum.opnsense.org/index.php?topic=23558.msg112182#msg112182

KH

That worked, thanks.

I just updated to 21.1.7_1 but now, when I try to check for updates or install a plug-in, the System:Firmware Updates tab just displays a spinning circle and displays no output.. What can I do to fix this?

Thanks
Rick

Is it possible to fix the sort order when viewing the ARP tables and sorting by IP?

Mine go something like this:

Hi all.. I've been using Cloudflare DNS using DNS over TLS with Opnsense for quite some time now.. In previous versions, I was using the "Custom" field to specify the Cloudflare directives.. Now, I have that empty and I am using the "Miscellaneous" section of Unbound and using the "DNS over TLS Servers" section to specify 1.1.1.1@853 and 1.0.0.1@853.  At random times, clients on the LAN will not be able to resolve DNS entries.. Currently I only have the log level set to '2', but when the clients cant resolve these certain addresses, I am seeing this in the logs:

2020-09-07T10:03:26   unbound[23196]   [23196:0] info: query response was THROWAWAY
2020-09-07T10:03:26   unbound[23196]   [23196:0] info: reply from <.> 1.1.1.1#853
2020-09-07T10:03:26   unbound[23196]   [23196:0] info: response for www.tivo.com. TYPE65 IN
2020-09-07T10:03:26   unbound[23196]   [23196:0] info: query response was THROWAWAY
2020-09-07T10:03:26   unbound[23196]   [23196:0] info: reply from <.> 1.0.0.1#853

This seems to be an issue that pops up for many people at random times - just wondering if anyone has run into it and found any reliable workarounds.  The events are random, and often after a few minutes, they resolve properly.

This has been a problem.. Was doing this in 20.1 as well, a couple of people posted (including me) about how to resolve it and received no responses.  I have NetFlow turned off.. With NetFlow off, the firewall hangs up on reboot with the following when shutting down for at least a minute:
Cannot 'stop' flowd_aggregate. Set flowd_aggregate_enable to YES in /etc/rc.conf or use 'onestop' instead of 'stop'.


How do I resolve this when not using NetFlow? 

Anything?

I also get these errors after turning off Netflow.. I also see that there have been no responses to any of the other users reporting the same error from the Opnsense team... Any ideas?