Kitz Forum
Computers & Hardware => Networking => Topic started by: Chrysalis on June 07, 2023, 06:10:12 PM
-
Hi guys, I have added a section on the wiki with the link below, I have shared a lot of my patches, and hopefully you guys find them of some use. There is also some information on the patch system within pfSense.
The link is here.
https://wiki.kitz.co.uk/index.php?title=Pfsense
-
Thanks Chrys. Good job. :thumbs:
Ive made a duplicate post in the site announcement section so that it is visible from the main site.
-
Thank you.
I will post some more patches some time next week.
-
Are the patches still useful on 2.7.0 as they seem to have made a lot of fixes?
-
After I update to 2.7.0, if the patches no longer apply cleanly, I will make new one's.
-
I will probably update to 2.7.0 second weekend from now, just before i do so I will submit the remaining patches I have (they bit more complex than the existing which is why I didnt upload initially), then after will add a 2.7.0 section.
-
Looks like diagnostic Limiters patch needs "ipfw" changing to "dnctl".
-
Thanks Alex, as you said ipfw replaced with dnctl binary in the diagnostics layout patch.
I will update the wiki with that change and other changes probably tomorrow.
-
The other UI pages have had a fair amount of tweaking so I couldn't eyeball them.
Though it begs the question why the Firewall Rules page doesn't just have a setting you can pick to choose the default rule set to land on, it really shouldn't take a patch to make such a simple change.
-
The other UI pages have had a fair amount of tweaking so I couldn't eyeball them.
Though it begs the question why the Firewall Rules page doesn't just have a setting you can pick to choose the default rule set to land on, it really shouldn't take a patch to make such a simple change.
I got not so good news on that.
Last night I redid all of the patches I use, I also added a nice new patch, but the default rule set for the firewall page, they removed the old code where they specified a default (which is what I had patched), the new code from what I can tell just simply assigns the lowest interface ID but i didnt understand how it was being done. So that hasnt been changed yet, however just before going bed I think I found the code that can still change it by studying the patch that changed the behaviour, so if you still want it pushed to LAN, I will do a new patch for it.
All the rest of the patches on the wiki, either just still work, or only needed minor tinkering.
You wasnt wrong they fixed a lot as well, before IPv6 was a bit of a mess on the gateways on the dashboard, with the gateway often not there and it unable to do online/offline detection, I see they fixed 5 bugs related to that (mostly with local link gateways) and I now see my AAISP IPv6 L2TP gateway on the dash.
-
Ok page is updated, when I have made the new default to LAN patch on the firewall page, that link will start working. The 2.6.0 patches are still accessible as well.
--
New LAN patch is there now.
If you want to edit this patch for another interface you need to use the internal interface name, WAN is wan, LAN is lan, however any added interfaces are usually optX where X is a number, typically starting from 1. Easy way to find internal name is going to the interfaces assignments screen, and hover over the link to edit the interface and check the url, it will end with something like 'if=opt5' thats an easy way to find the internal name.
-
Darn it, how did I not see how obvious that change was? ;)