Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - TheLatestWire

#1
Just one additional troubleshooting thought would be to set the switch port to Gigabit rather than auto negotiate if that's possible.  Let us know if you find a solution.  I have a SFF PC with this card and I'd like to move my OPNsense install to it.
#2
Do you happen to know what the default value for "Firewall Maximum Table Entries" is?
#3
Thanks Franco, you were right.  I was able to upgrade to 21.1.9 without ending up on 21.7 yet.  Thanks for the help.
#4
I've installed a fresh copy of OPNsense 21.1 and restored from backup config file.  I'd like to update to just OPNsense 21.1.9 and hold off on 21.7 for a bit and stay at 21.1.9 but when I check for updates it wants to install 21.7 and I just can't seem to find a config setting to stay on 21.1.x Marvelous Meerkat series.  Any assistance would be greatly appreciated.
#5
Just wanted to say thanks to franco and the entire team for all their hard work and efforts on the incredible project.

The traffic graphs really look amazing.

#6
General Discussion / Re: How to enable log forwarding?
December 20, 2020, 12:13:07 AM
Where is the "SEM Console Settings page" ?
#7
General Discussion / Re: How to enable log forwarding?
December 19, 2020, 08:29:50 PM
Thanks.  I'm not sure how I managed to miss that   :-\   I'm guessing the "filter (filterlog)" would be the same stuff that's seen in the firewall live log view?
#8
General Discussion / How to enable log forwarding?
December 19, 2020, 04:31:42 AM
I'd like to forward logs to Alien Vault OSSIM but I can't seem to find the setting to do this anywhere in OPNsense.  Is this log forwarding possible?
#9
Any luck with this?  I'd like to configure OPNsense to use AlienVault OSSIM's SIEM as well.
#10
Hi,

I'm wondering if this is expected behavior or perhaps a bug.  I want to remove the domain line listed in my DHCPv4 clients' /etc/resolv.conf and have no domain line listed.  They were getting this value from my OPNsense DHCPv4 server.

I cleared/deleted the value in the domain field on my OPNsense DHCPv4 server, but it was never removed from the clients.  I tried releasing/renewing at the clients and also waited a day.  I ended up replacing the blank field with something a different value and then that new value was sent to the clients.

Is it not possible to entirely remove the domain value from DHCPv4 clients' /etc/resolv.conf?

Thanks.
#11
What's the number of that patch please?  Is there a page to see/watch for patches?
#12
19.7 Legacy Series / Re: Entering alias is not working
October 13, 2019, 11:02:58 PM
I've tried patching using "opnsense-patch 7a5a271" as well as manually editing the opnsense.js file with the changes but I'm still having issues with aliases.  I don't see any content in them when I first try to edit them and then when I do see their contents (after a 2nd attempt at editing one), I can't add any new networks to the alias.

I've had to roll back to 19.7.4 to get things working again using "opnsense-revert -r 19.7.4 opnsense".

#13
I'm having similar issues with aliases with 19.1.6.  I've added a CIDR to an existing alias that only has about 28 other CIDRs to in order to block continuous SPAM from the new CIDR I'm adding and it as if I didn't even add it.  I keep getting SPAM from an address in the CIDR block that I added to the existing alias.  CIDR's added to the alias prior to the 19.1.6 upgrade are blocked as expected.
#14
Thanks for the reply Ad.

I had that setting at 500000, but just now changed it to 1000000 and that seems to have resolved the issue.  I also noticed that after increasing it some of my other firewall rules, that I thought were working but really weren't, finally started working.

Many thanks for the assistance.

ObecalpEffect
#15
Hi,

I receive the popup error "Cannot allocate memory" after I hit apply in the Firewall/Aliases section.  I've discovered that I don't have to add/edit or change any of the aliases but if I even simply go to the Aliases section and hit "Apply" after making no changes, I still get the error.



I do have quite a few aliases that contain a large number of CIDRs but this error is something relatively new, maybe only started after that last two updates.

I'm using the current, up to date v19.1 production series:
OPNsense 19.1.4-amd64
FreeBSD 11.2-RELEASE-p9-HBSD
OpenSSL 1.0.2r 26 Feb 2019

Is there a tunable that I could adjust or should I start examining my large aliases perhaps?

Any assistance would be greatly appreciated.

Thanks,
ObecalpEffect.