Fixed, thanks!

Yes it is working Thanks Jimp

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

for dhclient VLAN priority support :

https://github.com/opnsense/src/commit/b7307744e08bc601f1ae83773ee1afaa8b170f57

Looks like that only happens when you have zero patches in the list. I've just pushed an updated package to fix that, should show up with the next new round of snapshots later.

GOOD DAY I HOPE THAT IT IS WELL EFFECTIVELY UPDATE TO VERSION 2.4.4-DEVELOPMEN SNAPSHOTS 2.4.4.a.20180715.1209 AND THE PROBLEM RUN IN THE IPSEC, MANY THANKS

a probable fix in version 5.0.1 released on July 6

Fix crash with gif/tun/gre interface.

PR: 228643

0_1531653282987_41a7efe5-821a-48a0-a856-0bb5bcaaabce-image.png

https://www.freshports.org/net/frr5/

I haven't tried on other hardware or a VM but it does not even get recognised on 2 different models of Qotom systems set up for UEFI only booting when this img file is DDd to a USB drive. 2.4.3 non-hybrid image works fine.

This hybrid image might not be a great idea for 2.4.4 release if it has compatibility issues.

Solved by using -devel packages.

I rebooted it appears to have upgraded I assume all is well

This is my next step. I had to leave the router in place to have a working setup, but I'll try to test an other hardware to see if I can make it work and eliminate my pfSense hardware.

There are a couple open PRs for the gateway code:

https://github.com/pfsense/pfsense/pull/3955
https://github.com/pfsense/pfsense/pull/3956

It's possible you need one of those, the second one is likely especially if your WAN is PPP.

I tried again in GUI and same error. After running pkg update -f in the shell, the packages are all in the GUI now.

Thanks for your support. Late in the morning i could upgrade it to the latest dev version which fixed that problem. But now i'm facing problems with PPPOE via VLAN again. The not working PPPOE via VLAN was the reason why i had to switch to dev branch early this year. Now it is not working again with the latest dev :(

@pete35 said in OpenVPN GUI Problem with spaces in Remote networks field:

The route was in the routing table and so on, but it doesnt work.

If the route was correct in the routing table, there isn't anything else OpenVPN would have needed to do for it. Maybe the restart of the VPN helped more than removing the space?

The routes are definitely trimmed before they are put into the OpenVPN configuration. See https://github.com/pfsense/pfsense/blob/master/src/etc/inc/openvpn.inc#L2035 for a better example.

Maybe its just this specific request. It seems to work if i take the key and paste it into notepad, and then copy it into the key box on pfsense. It doesnt like it when i copy it from the webpage to pfsense, it wont generate the cert. Maybe theres a formatting error that is being removed when it goes into notepad...

It was the part in the "Reinstalling pfSense" instructions that said "Write the image to a USB memstick." My understanding is I have to do a bare metal install in order to format the eMMC as ZFS. For some reason I didn't think to install 2.4.3-release via USB then update via the development branch and restore config via ACB. Thanks.

@jimp so strange, it works perfectly now. I made sure that I reloaded all the feeds in pfblockerng before upgrading this time, there was a dnsbl database error last time I tried to upgrade because when I reboot (i emailed bbcan about this) the database gets wiped and I have to reload it as I am using ramdisk. I went back to june 7 snapshot (newer snapshot memstick iso won't boot in esxi 6.7, I saw some commit changes you made to how iso files work on github so I went with june 7 snapshot) and I can't do snapshots in esxi as I am using zfs and had to put the disk in physical raw disk mode.

error came back but went away when I uninstalled pfblockerng-devel, only caused issues with tcp connections

There may be better options than filebeat anyway…

Snort has a binary output which (as I understand it) can ship out to logstash without needing filebeat.

Suricata can output EVE data directly to a remote location via the 'redis' configuration.

dnsmasq and unbound support dnstap which gives the whole request & response in a single entry.

I'd expect more packages will have similar abilities if configured for it...  I'm going to set up an ELK VM to play with at some point soon (I wanted to set it up on an RPi2 but MongoDB won't build for FreeBSD/ARM unfortunately).