State of the Union (in pfSense land) - Opinions?

keyser

@cool_corona I hear you, but the point of my post is not that pfSense is generally useless/pointless.

I think it’s a great - really great product - that just suffers some “black holes” in features/fixes. So my point of the post is not to create a complaint thread - I would prefer we actually ended up commending the developers for the hard work they do.
I am pretty happy overall with pfSense and think they deserve a lot a credit - A LOT :-)

I would like this thread to revolve around what we can do to have pfSense “pick up” on the missing/dead feature ends it has. Any ideas?

Creating redmine requests seems to have little effect unless it’s a bug or you can create the codeedits yourself and actually make a pull request.
This forum is more or less dead in the areas where the functionality have been missing for years - a good indication of my point - so posting here has equally little effect.
There’s even quite a few posts that very heavily attempts to persuade users that those features are not needed, and they should actively try and do something else/use workarounds.

Perhaps a voting system with some kind of “product manager” that actively seeks out posts/threads that actually makes a good point for a feature/fix? The product manager could then clean up and formalize it as a feature request that could be voted on for popularity?

aduzsardi

@keyser
so what do you think we should do to have a more active development commitment from Netgate ?
I'm a systems administrator , not sure what or how could i help in the development area since i don't know anything about software development, otherwise i would gladly help in any way i can.

keyser

@aduzsardi said in State of the Union (in pfSense land) - Opinions?:

@keyser
so what do you think we should do to have a more active development commitment from Netgate ?
I'm a systems administrator , not sure what or how could i help in the development area since i don't know anything about software development, otherwise i would gladly help in any way i can.

Yeah that is the question - I'm in the same situation as you, and would also like to help.
PfSense really is a very very good and easy to use product, with the most intuitive GUI of all the Firewalls I have ever worked with. But there are these feature caveats.

The most problematic thing is probably "turning things around" for the dead branches of pfSense.
It will first require some development to actually bring it to a working and dependable state.
Then it will take a lot of time for users/the world to actually start using and believing in those features again on pfSense.

My experience is that Netgate/pfSense have improved on their communication skills, but they are still very hard to get out of the bushes. So the first point on the agenda would be to get them to talk about how we can help.
I have no insights into how they select what to fix/change/add to pfSense, but it seems to me that process is broken, because of the heavy focus on parts of the product and complete negligence of other parts. I'm not even arguing for new major features - just more feature completeness in the already included services.
22.05 is at the brink of release, but that seems to be bug fixes/security updates only, so that's not going to change any of the dead areas.

Perhaps persuade them to do a focused next release that aims to make already included services in pfSense more fully functional/dependable across platforms?

gabacho4

So quick question for the group here as I’ve wanted to know this for some time. You compare pfsense to other commercial products but how many of you are actually using it on Netgate hardware (PfSense+) or paying for a license/support plan versus using the CE version?

Development requires people and people require payment. It’s entirely possible that the things you want are valid but Netgate’s paying customers aren’t asking for it. If paying customers are making these requests, I wonder if the number who have made that request is large enough for Netgate to dedicate resources/money to? If large enough, Netgate should justify why they are ignoring that need. But first and foremost, you can’t compare free PfSense (CE) with very much not free alternatives.

I’m not a troll. I’m not affiliated with Netgate. I am a former CE user who went to Netgate hardware to help support the company and development. I’ve seen so much entitlement expressed since the announcement for Plus was made, by people who seem to forget that nothing in life is truly free (one way or another it has a cost), that I’ve struggled to see where the line between ungrateful whiners, and those who are actually contributing to the longevity of the product, lies.

Edit: not accusing anyone in this thread of being a whiner. Just asking an earnest question and expressing my observations.

Cool_Corona

@gabacho4 But if a product lacks the basic things, would you pay for it or look elsewhere?

First and formost, you deliver a solid and modern product with a little to no issues. Thats the basic requirement nowadays.

When things like VPN, reporting and monitoring is a hazzle, then people are hesitent to pay. Because they are not promised to get it done. as @keyser mentioned... it has been dormant for years.

Thats what bounties are for. Get a package going. Like pfblocker in the early with Marcello, snort and suricata with @bmeeks asf.

If you eliminated Snort, Suricata, zeek and pfblocker, what would make pfsense a great FW??

Exactly. :)

aduzsardi

@gabacho4
why do you assume that the people who are requesting these bug fixes/feature completeness are not running pfSense on netgate hardware ?

I think @keyser stated above that he is a paying customer with fairly large organizations. I'm also using netgate hardware as i stated a few replies above. And probably others as well. Anyway, it's not like anybody is asking for outrageous things ... mostly bug fixing and feature completeness for the features that are already included in pfSense.

gabacho4

@cool_corona I would agree with you. I think with the new business model and some time, we might start to see some movement on some of these issues. I think the previous model of pretty much 100% free unless you wanted to donate to Netgate definitely had an impact. I do find the argument that Palo Alto or Cisco or a namedPaidService can do X or Y better to be a dead one. Have fun paying an arm and a leg for all the licenses just to get the basic functionality that pfsense offers, let alone the extras.

I also think Netgate could do a better job being transparent about things they are working on or intend to implement and perhaps engage their user base more. The redmine shows issues being worked but I’ve seen it mentioned a few times that they have an internal “to do” list with Plus. Understand their need to keep new and exciting developments under wraps until they can excitedly announce them, but don’t see a reason that they can’t come out and say “your desire for request/feature X has been heard and is being worked on” or something to that extent. And of course, they can also just tell us when there’s no chance in hell. Reminds me of the much wanted and long broken UPnP and multiple game consoles issue they just got fixed. The hold up? They didn’t have any consoles to replicate the issue with and troubleshoot. To the user, it seemed they were hopelessly unable to do what a cheap D-link can do, while all the while they just lacked the gear or data to fix things. So yeah, I get where you’re coming from.

I wish I had development skills so that I could help kickstart things I would like to see advance. Like others have said, I don’t know how I can actively help contribute without those skills in hand.

Cool_Corona

We could pay cheap guys from India to develop the packages we need.

Outline the scope and specs and they are done quickly.

mcury

Since this topic was opened, I have been trying to configure framed-ip-pool in radius (sqlippool) to use with ipsec mobile road warrior in pfsense.

Unfortunately, no joy yet.

stephenw10

@cool_corona said in State of the Union (in pfSense land) - Opinions?:

If you upgraded to 2.6.0 youre stuck with errors and VLAN performing bad unless you run a script when the damn thing boots or disable RSC.

Just for clarity that only affects the hn(4) driver in Hyper-V. So a pretty small minority of users.
It is fixed now in 2.7 though.

@keyser said in State of the Union (in pfSense land) - Opinions?:

I understand - but for the record I have now created a simple hack to pfSense, that allows you to use the IPSec Mobile User VPN with group based authentication and group based IP Pools (Firewall rules for group of users).
It works with the OS native VPN client on all the major client OSs, and a feature pfSense has been lacking for FAR FAR FAR to long.
It works beautifully at a costumer with about 500 Mobile VPN Users :-)
I have created a redmine request to have it fixed...

What's the redmine?

Steve

keyser

@mcury You can't. The Framed-ip-pool attribute is not supported by pfSense IPSec (Strongswan).
You can only return Framed-ip-address - ie: static IP addresses pr. user.
That works just fine, but does not scale beyond 5 - 10 users unless lots of manual labor and lots of reserved addresses is your thing ;-)

What you can do is returning the "class" attribute with a groups name that strongswan can use for IP pool Selection. But it's not supported in pfSense now, so you have to apply my "hack":

https://forum.netgate.com/topic/172476/a-guide-to-assign-vpn-group-and-user-ip-pool-from-radius-in-22-01-2-6

stephenw10

This I assume? https://redmine.pfsense.org/issues/13227

keyser

This post is deleted!

NogBadTheBad

@keyser said in State of the Union (in pfSense land) - Opinions?:

@mcury You can't. The Framed-ip-pool attribute is not supported by pfSense IPSec (Strongswan).
You can only return Framed-ip-address - ie: static IP addresses pr. user.
That works just fine, but does not scale beyond 5 - 10 users unless lots of manual labor and lots of reserved addresses is your thing ;-)

What you can do is returning the "class" attribute with a groups name that strongswan can use for IP pool Selection. But it's not supported in pfSense now, so you have to apply my "hack":

https://forum.netgate.com/topic/172476/a-guide-to-assign-vpn-group-and-user-ip-pool-from-radius-in-22-01-2-6

I put the following in for a FreeRadius copy & paste in 2017 and its still open, it would help if you had loads of user to add.

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

stephenw10

Ok, that doesn't seem unreasonable. Obviously we are all hands on deck working on 22.05 right now but once that's released we can look at other things.

How would you anticipate that feature appearing?

What would you do for mobile IPSec if you could have anything? What are the common scenarios you see that could be solved?

If, for example, we added a mobile IPSec wizard of some sort to simplify the setup what should it cover? Given that it could probably only accommodate a few scenarios.

Steve

mcury

Its working, just tested...
Edited the ipsec.inc as indicated by @keyser

Observations:

test is the name of the identify created in preshared keys (pfsense), pool 172.16.98.128/25
test2 is the second identify created in preshared keys (pfsense), pool 172.16.98.0/25
freeradius is not running in pfsense, only ipsec road warrior is.
I had to enable accounting in ipsec tab.
member of AD group pfsense_admins get an IP from the pool (172.16.98.128/25)
member of AD group vpn_access gets an IP from the pool (172.16.98.0/25)

Unlang code used:

        if (LDAP-Group == "pfsense_admins" && NAS-Port-Id == "con-mobile") {
         update  {
                reply:Class := "pfsense_admins"
#                reply:Framed-IP-Address := "172.16.98.100"
#                reply:Framed-Netmask := "255.255.255.0"
                 reply:Class := "test"
        }
                noop
        }
        elsif (LDAP-Group == "vpn_access" && NAS-Port-Id == "con-mobile") {
          update {
              reply:Class := "vpn_access"
              reply:Class := "test2"
        }
                noop
        }

keyser

@mcury said in State of the Union (in pfSense land) - Opinions?:

Its working, just tested...
Edited the ipsec.inc as indicated by @keyser

Excellent proof that I was contemplating writing myself - to make sure people trusted my tests. It does work perfectly.

The only real “caveat” is that you are forced to also assign the default users/default pool on the “Mobile Client” tab a groups id (enable group authentication and select a group name to use - and return from Radius).
If you dont, everyone would land in the default pool because that is the first connection test (top of connection entires) in Strongswan, and everyone would qualify for that if there is no group restrictions on it. If it was the last connection test (bottom of entries), you could actually have all users NOT assigned a class attribute from radius belong to the pool created in the “Mobile Clients” tab.

mcury

Here its working like this:
The default pool is never used, if it fails the AD auth (not group member), the connection is dropped.

freeradius -X is generating a lot of stuff, I won't be able to post it here, but if you want, I can send a DM with it..

keyser

@mcury Yes, exactly as I described - only I think you misunderstood my posting.

You have enabled “Group Authentication” which is needed for this to work as intended. If you didn’t enable that, users in AD groups could pass Auth and even though you return the right groups ID with “Class” for a pool you created, they would still get an IP from the default Pool.
This would happen because the default pool is located in the first strongswan “mobile-con” connection selection (higher priority than those created with the EAP IP Pool identity fix). So all users would match the default Mobile-con connection selection if it did NOT have a groups restriction applied to it - regardless of any groups attribute that was returned with the accept message by radius.

You can have the default pool brought to use. In your setup, if you only return a Class = pfsense_admins or Class = vpn_access, then they would fall into that pool.
And that’s the major reason why the optimal solution to this fix would require a new UI design: Because the current “fix” mixes pfsense groups, IP Pool Identifiers and the Radius Class atrribute and causes them at times to be “the same thing”

PS: Right now you are attempting to return two Class attributes in one accept message, and strongswan only supports returning one. In your case it seems the last one becomes the one used for groups selection in strongswan (Test and Test2 in your case)

@stephenw10 - I’ll get back to you with a proper answer tommorrow.

mcury

@keyser Perfect
Thanks for the insight... =) One more tool in my Swiss army knife (I'm from Brazil by the way)

Blame the globalization for that comment hahaha :)