@stephenw10 said in How to scroll the backup restore list?:

The Scroll-Lock button should work for that on a directly attached keyboard/monitor.

Hit ScrollLock then use the cursor up/down keys. Retro-tastic! 😉

Steve

Amazing thank you !

@Proton

Check when the daily upload happens (If you have the pfSense Cron package, you can see this ) :

9d1fb2da-ac30-4d0b-84e8-717a95fa685a-image.png

So for me, at 47 minutes past midnight.

You could change your cron timing ?!

Btw : example : as you can see, the cron services page lists a lot of timed processes.
If one of these has as a side effect that unbound gets restarts - and close at that moment the execacb starts, then for a short moment (a coiuple of seconds), DNS won't be working.
That would explain your issue.
You could see this : in the resolver logs, you'll see the stop and moments later the start of the resolver.
In the system log, around the same time, you see abc start, and fail ... and now you know why.

Again : this is just an example.

@wifi-will said in Ruckus vSZ-H and 1 public IP:

I guess I would setup a rule for every site using a source rule right?

That would not be necessary, an alias can have lot's host aliases. You would add all the FQDN that go to one vSZ into one alias and the others in another alias.
And host alias can be a list of FQDN and IPs.

The FQDN get resolved by pfSense at a certain interval - not sure right now, every hour every 5 minute?

Addition: pfSense Doc: Hostnames in Aliases:

"The firewall periodically resolves and updates hostname entries in host or network type aliases. The default interval is 300 seconds (5 minutes). This behavior can be changed by adjusting the Aliases Hostnames Resolve Interval."

@stephenw10 I did another packet capture after this android effort so that previous capture is gone since it appears the GUI only maintains one copy. However, Everything is now working fine. I didn't fix this...it all just seems to work now after 2 weeks of pulling my hair out trying to figure it out. If/When it happens again, I'll get a better capture but I wanted to give you an update just so I didn't leave you hanging. Thanks for your help.

@Gertjan 😊

Hi,

i tried that, but that did not work. But now comes the catch: After doing so, it shows Version 2.8.0.1500029 on the start screen, updating to that actually works, without changing the branch, because then it selects 2.8.0 from the get-go and it does the job. I just havent tried this sequence.

Strange, but hey ist works!

Kind regards,

Jens

@stephenw10 @johnpoz
as for the vlan names on my sisters i guess i could just left out saying i made the same on her network since its not in use.. guess i make more confusion adding in stuff

i going to get my sister to test her network tommorow with the extra TP link antenna and remove the round disc version to see if its just a faulty AP maybe

as for my cable.. ya ive re terminated both ends still get 100mbp at half speed but since i been around a while i remember and still have my BNC coaxal network cable and cards for 10mbp when i used to host BBS Lan partys 80s 90s and 1200 baud and 33k modem even the modem for the Texas Instrument I99 i still have kicking around take ur phone and jam it on the suction cups.. 40+ years of networking of just standard LAN i only started using Vlans last couple years as my LAN was getting too cluttered...

so ya about the VLANs i was curious ya so VLAN 10 even though its embedded on 2 networks a few switchs apart will still be able to access even with pfsense down.. as i figured might go down too as i was going to move then the shinobi recording computer to the same switch as the cameras but then wouldnt solve for the 2nd switch of cameras at 2nd location..

i still playing around with pfsense high availability and had those questions about it above.. but i going to play around with it more.. pfsense pretty stable as long as hardware is good had it running on my sisters computer a dell from 15-20 years ago but it just started glitch now so i built a newer version as i thought also maybe the glitching computer for the AP issues .. but didnt solve it.. but i do love the verstile use of any computer pfsense will install on..

i appreciate the help so far
oh and i still have my 1 server thats still plugged in my network from 26 27 years ago running windows 98 and i ran Microsoft Wingate thats how we supplied dhcp internet for a lan party on 28.8k modem for 10 guys in a basement for a week at a time.. memories lol and that comp still works to this date but i dont miss dip switch networking

im just hoping i can test out what 1gb internet speed is before i dead.. as 3mbps speed is like dial up for the 80s 90s all over again now a days lol

@stephenw10 Yes, every time. I get an email notification every morning at 04:50, same error is OP.

That happens if the rule is no longer present in the ruleset when the log page is displayed. So commonly for old logs if it was something dynamically created like a UPnP rule or a scheduled rule.

Those look like reply traffic though so it could just be an expired state and the ruleset changed since.

If it's already registered and you have NDI you can just purchase a subscription against that NDI:
https://shop.netgate.com/products/pfsense-software-subscription-tac-lite-support

But if you applied one of the home or lab free subscriptions against it then you probably don't need to do that yet.

@stephenw10 Thanks!

@patient0 Thanks!

The client device will usually renew the lease at half the lease time but it doesn't have to. It could choose to renew it every 15mins. There are limits though. The server will refuse if clients try to renew too rapidly.

Check the client config. Or run a pcap for it and see if it's actually requesting it.

@stephenw10 It is static locked on mac address so I tried another android ping app and it works when the wan interface goes down so it must be a crappy ping app that I was using

What IP are you using to connect to pfSense over OpenVPN?

If you have firewall rules to allow it you should be able to use the pfSense LAN address to do so.

If that works then you must have the correct route in OpenVPN and probably have the correct firewall rules.
Most likely the host VMs in the LAN are blocking connections from outside their own subnet. In which case ypu can fix the hosts to allow it or use outbound NAT in pfSense to hide the source IP.

@stephenw10 said in Remote syslog using WAN interface.:

In the mean time that local gateway workaround should work if you can't switch to a route based tunnel.

VTI resolved the issue.

Thanks again.

https://redmine.pfsense.org/issues/16286

I included a code i made it in the github.

It was probably just pkg upgrade or some variation of it. That will offer to upgrade any remaining pkgs that didn't get upgraded during the normal pfSense upgrade.

@pfsjap glad you got it sorted.