That Shellcmd worked great. Updated to the latest dev version 11/19 and had no issues with PFblocker this time.
Thanks!

That's a known issue with the new graphing style/library. I'm not sure how feasible a fix is though. I think I had opened a ticket for that a while back but I don't see it at the moment.

You are correct, we are going to continue with security/errata updates for 2.3.x for a while after 2.4 is released.

It looks like this issue is fixed now.  I put a note on the bug report you filed.

Thanks

Custom changes always go in loader.conf.local. Never change loader.conf.

Dropping a note here to match what I put on the bug report you opened:

I tried this a couple times and it always worked for me. If you can reproduce it again, take notes of the exact steps performed and exactly when contact was lost with the firewall and which parts of the process were saved and which had to be performed again.

Just started working all by itself after I came back an hour later. Did not add any rules. Strange.
Couldn't debug this since the firewall logs do not work yet.

Thanks Jim. I will keep an eye on that  :)

Yes jimp, thanks for the tip, I've checked with mount and found that it's RAM drive and it's UFS.
I don't know why but I was thinking that ramdisk for ZFS should be created with
zpool create RAM /dev/mdx "by design", but looks like it can be done in any way, if it does not matter like Harvy66 mentioned.

I tested and merged the PR, next snaps should have it.

announcement soon.

@blueduckdock:

Hey all,
Was wondering what the state of Realtek drivers are in 2.4. Reason I ask is I get the infamous "watchdog timeout" on 2.3 with my Realtek cards. I understand that 2.4 is based on FreeBSD 11 now so I was wondering if those drivers appear to fix any of the issues you normally see on the Realtek cards. It also made me wonder because the new SG-1000 has dual gigabit NICs but I'm not sure that they are Intel (I would venture to say they are Realtek too- just a hunch) but can't find any info on it.

I'd be more than willing to help test 2.4 if I could get stable ops with my Realtek card. Otherwise I might have to go down that custom driver solution.

Realtek - we don't sell anything with these in it, so we're not prioritizing same.

SG-1000 NICs are on-die (they're part of the SoC).  Clearly not "Intel" or "Realtek".

further to Realtek driver, nobody is really working on it: https://github.com/freebsd/freebsd/commits/master/sys/dev/re

last two changes there are post 11.0-RELEASE.

I have no idea what your "go down that custom driver solution" statement is about.

The thing is, like many VPNs these days, they often run over port 443, which also happens to be the port for SSL. You might do some research and see if maybe there are specific hosts on Opera's end that can be blocked to prevent the VPN connection from being made. Create an alias list of the hostnames, then create a firewall rule blocking communication with that alias list.

found it
problem with "ifconfig-push"
without it works fine

in server logs:
MULTI_sva: pool returned IPv4=10.0.7.2

but i push 10.0.7.100 and client gets 10.0.7.100

I think it's https://bugs.freenas.org/issues/16280
Confirmed. It boots after manually editing UEFI entries.

Updated by Grzegorz Krzystek 3 months ago

Bios Version: 2.90
Latest for C2750D4I
In particular it's not a bug, but proMicrosoft implementation, of uefi boot sequence, and well known problem of many UEFI Bios on many motherboards.

windows boot loader have path: EFI\Microsoft\Boot\bootmgr.efi

and there are bios implementation like Asus one that expecting Windows Boot loader on internal hard-drives, and respecting EFI/BOOT/BOOTX64.EFI only on removable devices.

all UEFI implementations allows user to manage bootentrys.
adding new entry by uefishell that subbort bcfg is one line, in my case was:
shell>bcfg boot add N fsV:\EFI\BOOT\BOOTX64.EFI "FreeNAS"
where N was number of entry nad V was number of Filesystems that efi was able to read (all fat partitions are numbered and are accessible from uefishell)
after adding this entry, i see FreeNAS in bios as Bootable device that can be selected in boot order menu.
same operation is done in some Linux distros when grub-efi is installed by invoking command efibootmgr, cause some distros placeing grub in different dirs in EFI_BOOT partition. so adding these record to UEFI boot order make them bootable.

I just did

bcfg boot add 10 fs0:\EFI\BOOT\BOOTX64.EFI "pfSense"

bcfg answers that entry 10 is 0000 (do not exists)  and corrected it with number 3

and on next boot selected new entry in UEFI settings boot priority.

All done!