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 - dumaresq

#1
Looks like your patch was merged and is in 25.1, but I haven't tried upgrading yet (I'm nervous after a kernel bug a month or two ago).  Thanks for doing that work!
#2
This resolved the problem for me, and is vastly better then my solution which was to get a shell on the box, and restart tailscale :)
#3
General Discussion / Re: Proper way to delay boot up
August 08, 2024, 10:39:21 PM
Quote from: Baender on August 06, 2024, 06:30:39 PM
Isn't it like most .d folders, that an additional file like 70-custom-delay with the same content would overwrite 20-misc? Like most of those files work in the Linux world? That way, the 20-misc can be overwritten from any update, but your setting would remain. I don't think, that the whole folder is overwritten/deleted at an update?

Edit: first found value prevails. You need your custom file to be lower than 20.
This worked great!  thanks so much!   I still think ti shoudl be a var in the GUI but at least this works!
#4
General Discussion / Proper way to delay boot up
August 06, 2024, 04:49:20 PM
Hi,

I have HA turned on.  if for some reason my whole network is down, on boot up, I want my secondary firewall to wait about 5 minutes (For my ISP to give me my IPs) and then boot.   After that I want the primary to come up about 1 minute later.   This is due to the complexities of having only a single wan IP and using CARP.  Anyway, the way I've done this is I have modified /usr/local/etc/rc.loader.d/20-misc so it contains autoboot_delay="400" on the primary and autoboot_delay="300" on the secondary.  Sadly every update causes this file to be overritten.  I Assume there must be a setting somewhere I can change to have this perist but I cannot figure it out.   What am I missing?

Thanks!
#5
Quote from: autone on December 18, 2021, 06:29:35 AM

Did you try rolling back the suricata version to the one before 21.7.6? It works wonderfully for me after a rollback.

Nope.  I tried to do it, but couldn't figure it out, and didn't care that much... Just wanted to report that it still seemed to be an issue.
#6
It has not been fixed in 21.7.7 for me.

Also I have only enabled suricata on my WAN interface which has no virtual interfaces, so I don't understand why I am impacted.  For now disabling suricata has solved the issue.