@jonathanlee I don't see it, but, I suspect 23.05 is not available to test yet. It's not on other hardware, either.

@jimp Thank you! That worked!

@steveits Perfect. Thanks!

It's all typical subnet math, nothing special about it. The code for checking that is in util.inc, like check_subnets_overlap() but you might also look at things like gen_subnet() and get_subnet_mask() and the v4/v6 specific ones.

The question is very vague, though. We need more context to know what you're attempting to do that the current checks aren't allowing to know if it's valid.

While nothing stops something from using the network/broadcast addresses of a subnet (e.g. if it's routed to the firewall, all can be used for NAT so long as they aren't defined on an interface), you still can't force things to work that are not valid at a subnet level when used directly on an interface.

When using larger subnets, there is indeed nothing special about those addresses either. Such as when using a /23, it's valid to have clients use the .254 and .0 addresses in the middle of the /23.

@heper nice!

or can I just rebuild a kernel outside and replace the kernel on a running pfSense ? I would like to disable ALTQ

That's something we want to standardize eventually but it's a much bigger task than anyone realizes, and very easy to introduce new bugs in the process. Easy to think/suggest, but much more complicated to implement.

Overall we'd like to eliminate confusing/negative actions in options and move to a standard type of toggle control that makes it more obvious when things are on/off rather than checkboxes, too.

But for now we've at least been trying to do the right thing for new functions that get added when it's feasible.

@mephmanx
Can you edit and re-import the config?

If so, there is an <ssh> section within <system>.
You can add a port line there:

@aligator638 yeah see my edit, maybe I needed more coffee ;) Not sure what I was thinking - sorry about that.

I did some research this morning - and it seems there is a way to use it, but not with the official versions as of yet, I saw talk of compiling your own version and or manually doing some settings.

While that might be possible in pfsense, until its a standard feature in the released versions you most likely will not see it available in the pfsense openvpn settings.

So you would like to see a single page firewall view because that would enable drag-and-dropping a selection of rules between interfaces?

Steve

Hello,

I think I have solved all issues. The version I will upload in a moment to the bug-tracker-side does have the same functionality as the original NetGate version.

However, on my system and setup, it is nearly 20-times faster and does process a maximum of 250 lines from the firewall log in opposite to only 50 in the original version (which is relevant if you e.g. would like to select alarms from one specific interface).

I also shorted the timestamps printout, since I did not like it and assume nearly any one is interested to see the micro seconds.

If you want to use or test it, you can download it from
https://redmine.pfsense.org/issues/12673

@jimp said in Questions about DHCPd: new service on the agenda? DHCP pool restrictions?:

Yes, it's EOL. We'll be working on moving to Kea but not for this release. We've been using Kea with much success on TNSR, so we are hopeful that is the best path forward. That said, we still need to look into how it does things like failover pools.

Oh really exciting to read. I almost assumed it's a OpenBSD like situation that FreeBSD runs its own fork and will do so further down the road but I see that I now have to read on and check out Kea myself :)

@jimp said in Questions about DHCPd: new service on the agenda? DHCP pool restrictions?:

I'm not sure how Kea handles that second part but if they are actually reservations there then we can obviously lift that restriction after moving to Kea.

Oh then I'm sorry and "my bad" for assuming they actually were reservations. I just followed a similar discussion where ISC-dhcpd was concerned and either there was some misconception or they weren't aware, that preferences weren't really reservations.

But thanks for the update that gives additional input if that question pops up in the future again. Have to read Kea docs, if that is actually supported there (just for informational purpose).

Thanks again,
Jens

@jimp

One other reaction to add. I do not know which security measures / precautions Netgate makes with packages, e.g. with which authorization level they are running, however adding whatever 'external' code to your system is always a risk and surely if the involved system is a firewall.

So, but if you allow that whatever package to be installed, than you trust that package and an installed package does IMHO technically have the capability to do all kind of unwanted things with your platform.

If one of those more or less trusted packages generates fixed html code, it sounds strange to me to see that html code from one of your own packages as ^dangerous^ where the fact that the package is installed is again in my feeling is far more dangerous.

So, I do not need the htmlspecialchars() protection replacement for this case, but I do scratch my head why it is dangerous 😥

This long thread from earlier this year should help kickstart your effort: https://forum.netgate.com/topic/169749/pfsense-compile-requirements-for-3rd-party-software. This thread was about a different binary package, but the information is directly applicable to your iperf3 work.

You will first need to create a FreeBSD package builder environment based on the pfSense version you are targeting. Today that is FreeBSD 12.3-STABLE for pfSense CE and pfSense Plus RELEASE, and FreeBSD-14.0-CURRENT for the DEVEL snapshot branches.

You will find the binary pieces of iperf3 here: https://github.com/pfsense/FreeBSD-ports/tree/devel/benchmarks/iperf3.

The PHP GUI component of the package is here: https://github.com/pfsense/FreeBSD-ports/tree/devel/benchmarks/pfSense-pkg-iperf.

There is very little documentation of the process. Be prepared to draw upon your experience (or else you will have to spend a good deal of time on Google searching for clues and tips).

We're already looking into that. We were aware about it before it went in, it's something we've been keeping a close eye on.

@watermirror said in how to start?:

[00:00:46] [01] [00:00:11] Finished devel/libffi | libffi-3.3_1: Failed: fetch

This is the only error that matters. The others that followed it are just a symptom as they have libffi listed as a dependency, so when that port fails to build the others with a dependency on it will also fail to build.

To see why libffi is failing, you will need to examine its Makefile and perhaps the Poudriere build log for that package. The error says it failed to fetch the source code. That could be because the repo referenced in the Makefile is offline, or it might be that the source file location has been customized to some place not publicly accessible (like a private GitHub, for instance).

And lastly, I will say that trying to build a custom pfSense image is not for the faint of heart. It requires quite a bit of patience to track down and correct some weird errors, and it also demands a lot of experience with using and maintaining FreeBSD build environments.

@stephenw10 said in FreeBSD 13:

Yup, so does main/14. 😉

This does sound as a very very interesting deveolpment for pfSense. However, I’m not a FreeBSD user/follower apart from on my SG-xxxx boxes, so a few questions arise:

1: How big is the difference between 12/Stable and 14/Main in the bits pfSense use/exploit? IE: What will be the most noticable news for pfSense users?

2: Is it a huge leap in additional drivers availability and supported hardware? I’m thinking mainly NICs and especially 4G/5G dongles/hardware support.

3: Is 22.11/2.7’s only focus to change FreeBSD base and PHP build, or will there be other new features/requests included?

Leaving this here in case it's useful to anyone...

github.com/luckman212/pfsense-temp-alert