Are we close to an RC release?
-
welcome to RC . . .
-
@herozero Yay!
-
Yup!
-
This RC took a long time to upgrade - even from the most recent beta! I even took my laptop to the rack since I couldn't SSH in! Whew!
-
Really? Mine was really fast. No issues on my 6100.
-
@behemyth It took almost 10 minutes on my 6100 MAX when each incremental beta took less than a few miinutes. Suricata was the only package that had an upgrade and that one appeared to take a while for whatever reason. Interestingly enough I never got a boot verification. I'll have to see if this RC version flipped this back to an opt-in feature.
UPDATE: I never got a boot verification this time:
-
Hmm, that's odd. Anything logged?
-
@stephenw10 said in Are we close to an RC release?:
Hmm, that's odd. Anything logged?
I haven’t looked yet and my dog is looking at me wanting to know why we haven’t left for the dog park yet. I’ll check when I get back home!
-
I noticed that this RC version did not clear my package cache. You can run this command to reclaim the disk space:
pkg clean -a -
@stephenw10 said in Are we close to an RC release?:
Hmm, that's odd. Anything logged?
What should I look for specifically? Thanks!
-
@DefenderLLC said in Are we close to an RC release?:
I noticed that this RC version did not clear my package cache.
I saw the same.
-
@DefenderLLC said in Are we close to an RC release?:
What should I look for specifically? Thanks!
Something that shows it verifying the boot automatically when it should have been manual for example.
-
@stephenw10 Can you do the boot verification from the console? I may have inadvertently pressed enter s bunch of times when I was trying to establish a session via USB cable. Things appeared to have been locked up before the terminal refreshened with new text.
-
Hmm, not sure I've ever tried!
-
@stephenw10 I'll to the upgrade from the console on the released version and report back! I have a feeling that's what happened because I admittedly got impatient after 10 minutes of not being able to SSH in. Normally the 24.03 upgrades were really quick (like < 2 min).
There's another 6100 MAX users that experienced the same slow upgrade. The main difference is that he is running Snort vs Suricata. He did paste some log failures in his post. Take note of the last line:
Performing automatic boot verification...done.https://forum.netgate.com/topic/187308/24-03-rc-install-long-delays/
-
Hmm, it really is actually before the WAN is configured then....
-
@stephenw10 In my case, I have pfSense setup as a transparent firewall now, so there are no IP addresses on my WAN, LAN, or BRIDGE interfaces - only the MGMT interface. Not sure if that is related to my slow upgrade. I doubt it as everything is working perfectly fine pre and post upgrade.
-
As long as it has a default route via that interface it should be fine. But obviously not if that interface hasn't been configured yet when it does.
-
@stephenw10 said in Are we close to an RC release?:
As long as it has a default route via that interface it should be fine. But obviously not if that interface hasn't been configured yet when it does.
I can't put an IP on my BRDIGE interface because my 6100 MAX is sitting between the AT&T Fiber Gateway (which is in bridge mode itself) to my UDM-SE, so a LAN IP can't be assigned to it since the public IPs are being managed by UniFi.
-
Managed on the WAN side of the Unifi? The bridge would be in the same layer 2 as that if so so should be able to use one.
But that wouldn't matter for the update traffic. As long as pfSense has a valid default route from any interface it should be able to update.
