Messages

1

22.1 Legacy Series / ARP table hostname column?

« on: April 02, 2022, 03:20:56 pm »

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? 

2

General Discussion / Re: Problem with DHCP Static Mappings

« on: April 02, 2022, 02:48:34 pm »

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

3

22.1 Legacy Series / Re: WAN interface flapping with 22.1.2

« on: March 06, 2022, 03:45:42 pm »

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.

4

21.1 Legacy Series / Re: After upgrade to 21.1.7_1, Updates tab spins no output

« on: June 28, 2021, 05:27:26 pm »

Hi,

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

KH

That worked, thanks.

5

21.1 Legacy Series / After upgrade to 21.1.7_1, Updates tab spins no output

« on: June 24, 2021, 04:58:31 pm »

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

6

20.7 Legacy Series / Sort order by IP in ARP table

« on: January 26, 2021, 02:03:37 am »

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

Mine go something like this:

7

20.7 Legacy Series / Unbound random THROWAWAY responses

« on: September 07, 2020, 04:42:06 pm »

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.

8

20.7 Legacy Series / Cannot 'stop' flowd_aggregate -- Delays boot/reboot significantly

« on: August 05, 2020, 01:51:36 am »

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? 

9

20.1 Legacy Series / Re: Yet again about flowd_aggregate

« on: July 21, 2020, 04:23:47 pm »

Anything?

10

20.1 Legacy Series / Re: Yet again about flowd_aggregate

« on: July 17, 2020, 11:43:11 pm »

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?

11

20.1 Legacy Series / Viewing shaper status

« on: June 05, 2020, 03:26:08 pm »

You used to be able to monitor the full status of the traffic shaper in the GUI which would dynamically display the queues along with how many packets were dropped, etc - similar to running ipfw sched show on the command line.. Is there any way to duplicate that functionality from the command line where it automatically refreshes, similar to how top works?

12

20.1 Legacy Series / Request - zoom options on Health graphs

« on: June 05, 2020, 02:52:46 pm »

Is it possible to provide better options for zooming in to time periods on the Health graphs?  Especially on something like the quality graphs - being able to zoom in closer than a 20 hour period would be very helpful.. Or am I missing something? 

13

20.1 Legacy Series / Re: Damaged tar message after upgrade

« on: February 05, 2020, 02:17:46 pm »

So, what I ended up doing was taking a full config backup, and then doing a clean install of 20.1 on my RCC-VE 2440.. One of the things that stood out was that even when I got the firewall back up and running, it was taking a very long time to initiate a reboot, which typically completes in about 60-90 seconds.  After this happened, it was taking 3-4 minutes for a reboot.  Much of that time was spent during the shutdown process -- if I issued a reboot command from the GUI, the webpage would reload before the router even started rebooted.

I cant be 100% certain, but if I recall, the messages I was seeing about the damaged tar were showing up right when the router was attempting to start flowd_aggregate or flowd on the reboot.
tar: Damaged tar archive
    tar: Retrying...
    tar: Damaged tar archive
    tar: Retrying...
    tar: Damaged tar archive
    tar: Retrying...

Looking back at syslog messages from when this started around 3:20 AM on 2/4, it looks like my ISP remotely rebooted my modem, there was a WAN IP change via DHCP, and dpinger started complaining constantly about the gateway being down, and when I woke up around 6:00 AM, there was no internet connection and the serial console was just spitting out those tar messages.  It looks like dpinger didn't pick up the new gateway to monitor. 

Is it possible that archived logs from flowd became corrupt or something?  Why didn't dpinger change the gateway monitoring address after the WAN IP change?  Is it possible this could be related to the similar issue with flowd reported here?  https://forum.opnsense.org/index.php?topic=15698.0 -- if so, should I apply that patch?

In the end, I think the clean install and config restore was best.  My ISP does not change WAN IPs very often, maybe 2 or 3 times a year.  Now a reboot is taking about 60 seconds.

14

20.1 Legacy Series / Damaged tar message after upgrade

« on: February 04, 2020, 01:27:45 pm »

I upgraded my system from 19.7 to 20.1, I believe - on Friday last week.  Last night around 3:30 AM, it looks like the firewall rebooted for whatever reason and got stuck with these repeating "Damaged tar" messages.  I tried rebooting a couple more times with the same results.. I discovered that pressing CTRL-C allowed it to continue the boot and the firewall came back up.  I did one or two more reboots - but still got stuck with the damaged tar messages that required CTRL-C to finish booting.  I was getting ready to clean install and restore from a config backup when I rebooted one more time from the GUI, and this time it made it through the entire boot without issue. 

Any way I can figure out what this was/is?  I'm running on a Netgate RCC-VE2440 x64/serial with an Intel 30GB SSD.


Thanks
Rick

15

19.1 Legacy Series / Re: DDNS error since 19.1.4

« on: March 19, 2019, 12:35:08 pm »

Ended up being able to post a message to the DNS-O-Matic community about this.. I'll update this if anyone responds over there.. DNS-O-Matic is working within OPNSense -- its just the Cloudflare service when updated through DNS-O-Matic is failing.. I have a couple other services in the DNS-O-Matic account that are updating properly (Tunnelbroker, DSLReports, Zoneedit)