Oh, I see I misinterpreted the screenshot there.

Ok the first thing I would do here is spoof the Draytek's MAC address on the pfSense WAN. The modem or ISP is probably locked to that MAC.

Steve

@deanfourie said in ntopng on FreeBSD - Help with autostart:

So, ive gone ahead and installed ntopng from the website documents alongside pfSense as the pfSense package installer just never worked for me.

Its installed and running smoothly, the only thing I am unsure of how to do is to autostart redis and ntopng on boot. Upon every boot I need to run

service redis start
service ntopng start

Is there a way I can auto start these 2 services on boot?

Thanks

If you are on 22.01/2.6 and do not want to upgrade to 22.05/2.7, and can highly recommend installing NtopNG using my guide here instead:

https://forum.netgate.com/topic/172084/a-guide-to-current-ntopng-on-pfsense-2-6-22-01/24

That uses the NtopNG pfsense package wrapper to give you control and start/use NtopNG as intended.

But I just upgraded to 22.05/2.7, and the pfsense NtopNG package there contains a very recent release from the 5.2 stable branch - which works beautifully and is very stable. So I recommend using that approach instead of going “manually installed”

@johnpoz
Yes sir they said that I can disable that

It is a huge burden off my shoulders

Don't use Cron use scheduled rules:
https://docs.netgate.com/pfsense/en/latest/firewall/time-based-rules.html

You two rules with different schedules. Add the required gateway(s) to each one.

Steve

@johnpoz

Interesting, I’m in Nova Scotia, Canada

@johnpoz

Thanks

Yeah, it really depends on the system. On one CE test box here (Core2duo era) it caused the fans to spool up to max! Was really obvious.

@steveits

Just to complete this post, as I deleted some screenshots with IP in them.

This problem is SOLVED

"I ended up setting the WAN gateway to WAN_DHCP as it was set to none."

And then everything started working as it should.

Thanks to all that helped me out.

Have a great day!

@uscut out of the box nothing is blocked. I am accessing it just fine (just checked), are you using proxy, or pfblocker or snort or anything?

That seems more like a block on their end,

Your trying http vs https?

@mikev7896 said in 22.05 Upgrade question - ZFS/snapshots:

I assume that I'd need to download 2.7 CE and then re-upgrade to pfSense Plus?

For reference, currently you would need to re-install 2.6, upgrade to 22.01 and then update that again to 22.05.

At some point the CE > Plus upgrade repo will be switched to 22.05 and then it should be possible to update to it from either 2.6 and 2.7.

Steve

@neiltiffin said in pfSense 2.5.2 video stalling and buffering:

@stephenw10 I found in the last 10 years of using pfSense that being an early adopter is not wise. My experience with upgrades has not been good, often retreating to the command line and a reinstall even though I am on a Netgate Appliance.

Ok so I upgraded from 2.5.x to 2.6.0 using the ui this time, and it worked. Pleasantly surprised. I hope this is the future as I had given up on using pfSense. We'll see how the next few upgrade go.

@danlad sorted it, had to do an system update and it was listed in there.

I haven't seen that happen here and I've restored several dozen times during 22.05 development with all sorts of different configuration styles. I haven't seen either of the behaviors you describe thus far.

One thing you might want to check is the update branch in the saved configuration. Look for (and remove) the <pkg_repo_conf_path> tag(s) and contents before restoring and see if that makes a difference.

Also if you have extra data in the backup such as RRD, DHCP leases, etc, then it can greatly increase the size of the backup file and can cause it to take longer to upload and restore.

@bingo600 If you create a allow rule with their IP, then when they create traffic to whatever that is allowed that would be logged. But only first instance of such traffic, which seems like what your after..

@stephenw10 said in No log entries:

mber that opened a state.
Then you can check which rule that was using: pfctl -vvs

got it. ill do some testing today and report back.

Yes, that would leave you with the default sysctls.

It shouldn't just freeze. But if that's a real concern for you then setup an HA pair. Or maybe some OOB access to the console.

Steve

@stephenw10
Thank you Steve! Late last night I realized that VLAN10 needed to be tagged on port 5 but completely missed removing port 2 from VLAN1. This got Wifi sort of working. The Airport would get an IP and DHCP clients would get IPs but this would hold for about 20 seconds and then it would lose its IP for 20 seconds, then get another for 20 seconds, endlessly cycling. I kept thinking I must have the DHCP service misconfigured somehow. Once port 2 was removed from the VLAN1 list everything started working properly.

Thanks again Steve. As you can see I have the VLAN10 and VLAN1003 firewall rules set wide open while trying to figure this out, so the next step will be to lock them down more.

@jimp Ok, maybe. I actually went away to make breakfast and came back and was sitting at the login screen. So I don't think it was a timing related thing of being too trigger happy. I remember seeing this once before during the 22.05 betas and it's definitely just a cosmetic thing, so I won't worry about it.

Let's see if any other people report it.