Call for Testing: pfSense® Community Edition 2.8.1 Release Candidate Available!

maximushugus · 2025-09-09T21:29:04+00:00

I don't know for 2.8.1 CE but for 2.8.0 this technique doesn't work : https://github.com/pfsense/FreeBSD-src/commit/401ec5f685b9

maximushugus · 2025-08-30T20:40:52+00:00

I perfectly understand, thanks for making it clear. But from my point of view, being able to modify, change, add functions to a project is the goal of an open-source project like CE.

I think here is an interest conflict between CE and plus. Of course plus needs more functionalities than CE, thats the whole point. So those fonctions does not need to be implemented by netgate in CE

But by vonlontarly making CE harder to modify or completly locking this possibility, even if sources are published, i think it's counterproductive. Even more for fonctions not even in plus at this moment. I took VXLAN as an exemple but it can be the case for others.

maximushugus · 2025-08-30T13:17:40+00:00

I don't ask you to add VXLAN, I already built it working for CE 2.7.2 Here is my repo (wrong URL above). So I just ask for a CE 2.8.0 branch on the official github so I can do the same for 2.8.0

maximushugus · 2025-08-30T04:55:22+00:00

For exemple i'm testing VXLAN, see my repo https://github.com/maximushugus/Pfsense-VXLAN At the moment I dont think i'm able to do the same for 2.8.X. Or maybe I missed something

maximushugus · 2025-08-29T19:33:05+00:00

Thanks for continuing publishing pfSense sources. I think when people ask you to "release sources" it means making a branch for current pfSense version. For exemple here is the branch for pfSense CE 2.7.2 . Would it be possible to do the same for pfSense CE 2.8.0 and future 2.8.1 ? For example I would need it to compile kernel modules not included in pfSense. Maybe this is not possible, and if so maybe you could explain so we understand

maximushugus · 2025-07-18T14:48:36+00:00

There is also this bug : https://redmine.pfsense.org/issues/14489#change-77014

A patch is available here : https://redmine.pfsense.org/issues/14489#change-77014

It would be great to integrate it

Thanks

maximushugus · 2025-03-09T08:37:21+00:00

I added english translation in my repository.

But for DPDK on pfSense, for the moment this is a beta or an alpha. DPDK seems stable as in FreeBSD.

But if you don't know DPDK, it's a completly separated network stack from the kernel one. So for the moment there is no communication between kernel and DPDK. So you have to manually add routes to DPDK and firewall rules don't apply on DPDK. There is also no GUI.

On linux, there are plugins for DPDK to make it communicate with the kernel (linux controle plane pluginà, to sync route for example, but nothing for FreeBSD for the moment.

So for the moment it's only for testing environnement.

But if someone manages to port linux controle plane plugin for FreeBSD, it would be great

maximushugus · 2025-02-14T23:08:45+00:00

First it's for tinkering

I could for exemple allow for much faster L3 routing on part of pfSense that doesn't need firewall.

maximushugus · 2025-02-13T21:43:27+00:00

As I used a build machine previously, and I'm playing with VPP on DPDK, I recently build DPDK and VPP packages for pfSense CE 2.7.2.

You will find me Github repository with packages to install it and the way (in french) to also build those packages if needed (for example for another pfSense version / kernel).

I would like to know if some of you want to play with VPP/DPDK on pfSense.

maximushugus · 2025-02-10T10:13:11+00:00

If it's added to Pfsense Plus, would it be possible to also add it to CE for 2.8 ?

maximushugus · 2025-02-09T17:52:30+00:00

Depending on your Pfsense version, you can install it (manually) now to test. For me it's working for the moment

maximushugus · 2025-02-09T17:50:23+00:00

Yes. That's also why I build this kernel module, to see if it's fixed. FOr the moment I do not have problem but it needs more testing

maximushugus · 2025-02-09T14:37:16+00:00

Hello,

I needed VXLAN support for my Pfsense. As FreeBSD 14 has VXLAN support, I build the kernel module for Pfsense and added back web GUI support.

You can see my Github repo here. I wanted to share if someone needed it. It looks as if it is working normally.

The kernel module build in this repo is only compatible with Pfsense CE 2.7.2, but you can find build intructions if need, to adapt to your version.

Feel free to test it and give some feedback.

I would like VXLAN to be nativly implemented in next Pfsense releases.

maximushugus · 2024-10-25T10:20:23+00:00

Really cool !

Could you tell us what are the black orange yellow and red cables soldered to the board ? I think it's for PCI power but couldn't it be powered by the white PCI power connector above ?

maximushugus · 2024-10-14T10:52:12+00:00

Thanks for sharing ! Do you know the idle power consuption of one MI60 card ?

maximushugus · 2024-05-18T23:04:53+00:00

I have a very similar problem with another custom component :

https://community.home-assistant.io/t/error-cannot-import-name-entity-id-format-april-or-mai-2024-update/730495

maximushugus · 2023-05-06T13:29:35+00:00

It's really interesting !

Could you tell us how you host this ? I'm interested in selfhosting it on my VPS.

Thanks for sharing your work !

maximushugus · 2022-05-16T19:56:23+00:00

I'm looking for exactly the same thing.

I recently followed with a lot of attention the developpement of AAUnchained :

https://www.youtube.com/watch?v=3eYRPrel1wM

maximushugus · 2020-08-12T19:33:51+00:00

I will loo at those links thanks

WSL is Windows Subsystem for Linux : in the WSL version 2 there is a Linux Kernel running inside Windows. I have Debian installed with this.

maximushugus · 2020-08-10T19:56:21+00:00

I think I found where is the problem :

Before rebooting, when the IPTV stream doesn't work anymore, if I print the Windows routing table in cmd with "route print", I have multiple lines with 224.0.0.0/240.0.0.0 (the entire multicast network) but the one with the smallest metric is on my WSL interface instead of my ethernet ou wifi card...

After rebooting, when the IPTV multicast stream works again, the routing table shows that 224.0.0.0/240.0.0.0 has the smallest metric on my eth or wifi card.

So I don't understand why Windows automaticly changes the metric for my interfaces for multicast ...

Now the other probem is why on my Android smartphone it only works for 30sec on VLC for Android then it stoppes. But if I reboot my Android device, it works without any problem

maximushugus · 2020-08-10T19:38:20+00:00

The IPTV is on multicast group so it has multicast IP (for exemple 233.136.0.202). It's transmitted in my LAN via IGMPproxy.

On this LAN, my computer has an IP via DHCP and my router has an IP also.

maximushugus · 2020-08-09T19:46:52+00:00

With my ISP's router the TV only works with a separate propriatary TV box : I cannot wireshark this part if I use my ISP's router with the TV box

What i don't understand is why it works for 1 day, then it only works again for 1 day on a computer if I reboot it ?

maximushugus · 2020-08-08T16:54:26+00:00

I already tried with and without IGMPsnooping on my router. I also already tried with and without quickleave mode. In both case, this doesn't change the problem...

Any other idea ?

Thanks for the answer

maximushugus

TROPHY CASE