@PixieDust

No

@jrey said in pfblocker not downloading ASN list:

All I can say is that at 01:20:13 Eastern it was working fine

Ah, OK - thanks!

@johnpoz If ssh does complain about the ssh key cd to the .ssh folder and remove the known_hosts file.

@tecno-guac symlinks to the rescue 🤠

[23.09.1-RELEASE][root@fw]/root: ls -l /usr/local/www/apple-touch* lrwxr-xr-x 1 root wheel 55 Nov 10 12:33 /usr/local/www/apple-touch-icon-ipad-76x76-precomposed.png -> apple-touch/apple-touch-icon-ipad-76x76-precomposed.png lrwxr-xr-x 1 root wheel 43 Nov 10 12:41 /usr/local/www/apple-touch-icon-ipad-76x76.png -> apple-touch-icon-ipad-76x76-precomposed.png lrwxr-xr-x 1 root wheel 64 Nov 10 12:33 /usr/local/www/apple-touch-icon-ipad-retina-152x152-precomposed.png -> apple-touch/apple-touch-icon-ipad-retina-152x152-precomposed.png lrwxr-xr-x 1 root wheel 52 Nov 10 12:41 /usr/local/www/apple-touch-icon-ipad-retina-152x152.png -> apple-touch-icon-ipad-retina-152x152-precomposed.png lrwxr-xr-x 1 root wheel 57 Nov 10 12:33 /usr/local/www/apple-touch-icon-iphone-60x60-precomposed.png -> apple-touch/apple-touch-icon-iphone-60x60-precomposed.png lrwxr-xr-x 1 root wheel 45 Nov 10 12:41 /usr/local/www/apple-touch-icon-iphone-60x60.png -> apple-touch-icon-iphone-60x60-precomposed.png lrwxr-xr-x 1 root wheel 66 Nov 10 12:33 /usr/local/www/apple-touch-icon-iphone-retina-120x120-precomposed.png -> apple-touch/apple-touch-icon-iphone-retina-120x120-precomposed.png lrwxr-xr-x 1 root wheel 54 Nov 10 12:41 /usr/local/www/apple-touch-icon-iphone-retina-120x120.png -> apple-touch-icon-iphone-retina-120x120-precomposed.png lrwxr-xr-x 1 root wheel 44 Nov 10 12:33 /usr/local/www/apple-touch-icon-precomposed.png -> apple-touch/apple-touch-icon-precomposed.png lrwxr-xr-x 1 root wheel 32 Nov 10 12:41 /usr/local/www/apple-touch-icon.png -> apple-touch-icon-precomposed.png /usr/local/www/apple-touch: total 35 -rw-r--r-- 1 root wheel 3669 Dec 6 12:10 apple-touch-icon-ipad-76x76-precomposed.png -rw-r--r-- 1 root wheel 7260 Dec 6 12:10 apple-touch-icon-ipad-retina-152x152-precomposed.png -rw-r--r-- 1 root wheel 2965 Dec 6 12:10 apple-touch-icon-iphone-60x60-precomposed.png -rw-r--r-- 1 root wheel 5640 Dec 6 12:10 apple-touch-icon-iphone-retina-120x120-precomposed.png -rw-r--r-- 1 root wheel 5640 Jun 27 2023 apple-touch-icon-precomposed.png [23.09.1-RELEASE][root@fw]/root:

@jrey
👻 I know this an old thread....But, it appears that your statement, "Cable/DOCSIS Modem under load, and you've got a VPN on top of that", is spot on. I recently updated my Netgear DOCSIS 3.0 to a used/like new Motorola DOCSIS 3.1 from eBay for a few coins 😊 And thus far, I haven't received the frequent error messages, listed above in my first post, after ten days. It appears that this issues has been resolved, albeit it only has been 10 days with this new modem. I used to experience the error messages frequently almost daily and at least every couple days. My suspicion was always the cable modem since that particular Netgear cable modem uses the controversial Intel chipset instead of the Broadcom chipset, but the pfSense log confused the matter because it showed both the cable modem and my VPN were potential culprits. I pulled the trigger because the Motorola cable modem was such a good deal to pass up. Thanks for pointing out the cable modem was the most likely the culprit!👻

0

@Prokleon said in Submitted ticket to Netgate for access to Beta installer - 403 forbidden after refreshing portal page?:

@rtorres Your ticket was forwarded to the engineering team, it could take time to send you a download link.

Thank you kindly!

No rush, just wanted to see if all was well with my request.

Have an awesome day!

It will create a new cert if you run that command. It will be the same type of cert as the initial one but not actually the same so you would need to agree to allow it again as you do when you first connect.

@MakOwner said in CE 2.7.2 to CE 2.7.2 routing issue:

@Stewart
pfBlockerNG MaxMind - MaxMind now requires a License Key! Review the IP tab: MaxMind settings for more information. @ 2024-02-29 16:15:40

Once an hour.
I have turned off everything I can find about IP.

I think it now also requires an Account ID in addition to the License Key be provided to download updates. I think this new requirement took effect in January of this year.

I had to make a recent change in the Suricata IDS/IPS package because of the MaxMind authentication API change.

@Jhosin running some 10.x network on the same L2 network as your 192.168 network not really isolating them.. You need to physically isolate these networks.. Or you need to vlan them..

While you can run multiple IP ranges on the same L2 - this does not provide for actual isolation.. If you are worried about device X accessing device Y, they really need to be actually on different L2 network.. Not just different IP ranges.

There isn't really anything specific to that.

On the 2100 you would need to add the VLAN interface in pfSense. Then add that VLAN ID as tagged in the switch setup so it's passed through to the AP.

And of course add the VLAN to the AP but that's in the Unifi config.

Steve

Mmm, might not be possible then. If you had enabled Auto Config Backup that would have it.

You can purchase a Plus sub from the store:
https://shop.netgate.com/products/pfsense-software-subscription-tac-lite-support

BTW, reading that using VPN might be the safest way, perhaps one thought might be to set up dedicated raspberry Pi like devices on each network.
Just a thought either in addition to using the one of pfsense or as an alternative.
I haven't spent enough time learning more about VPNs even though I use the one on pfsense daily.

@Sasquatchv you neglected to mention what ISP you are with. For PPPoE you only require the Router in Bridge mode then configure PPPoE on pfsense. Let the Router pass thru the modem and don’t configure PPPoE on the Router itself as the PPPoE with have two Open Sessions and majority of ISPs in UK, Ireland and Europe uses RAS/RAAS which will cause the Auth on PPPoE Session to fail.

@MoonKnight oh I still have my cmd window open all the time.. But I also have the wsl prompt open - I use it for whois multiple times a week for sure..

@stephenw10 Actually we see this across multiple physical locations but all being run by the same hosting company. I'll keep an eye on it and come back to you, if we find another occurrence outside this scope.

Backtrace for reference:

db:0:kdb.enter.default> bt Tracing pid 12 tid 100127 td 0xfffff8000908b000 kdb_enter() at kdb_enter+0x3b/frame 0xfffffe02399d78f0 vpanic() at vpanic+0x19b/frame 0xfffffe02399d7950 panic() at panic+0x43/frame 0xfffffe02399d79b0 trap_pfault() at trap_pfault/frame 0xfffffe02399d7a00 trap_pfault() at trap_pfault+0x49/frame 0xfffffe02399d7a60 trap() at trap+0x29d/frame 0xfffffe02399d7b70 calltrap() at calltrap+0x8/frame 0xfffffe02399d7b70 --- trap 0xc, rip = 0xffffffff80f7eb95, rsp = 0xfffffe02399d7c40, rbp = 0xfffffe02399d7e40 --- pf_test() at pf_test+0x1ef5/frame 0xfffffe02399d7e40 pf_check_out() at pf_check_out+0x1d/frame 0xfffffe02399d7e60 pfil_run_hooks() at pfil_run_hooks+0x90/frame 0xfffffe02399d7ef0 ip_output() at ip_output+0xa53/frame 0xfffffe02399d8020 ip_forward() at ip_forward+0x2c3/frame 0xfffffe02399d80c0 ip_input() at ip_input+0x724/frame 0xfffffe02399d8150 netisr_dispatch_src() at netisr_dispatch_src+0xa2/frame 0xfffffe02399d81a0 ether_demux() at ether_demux+0x15b/frame 0xfffffe02399d81d0 ether_nh_input() at ether_nh_input+0x32c/frame 0xfffffe02399d8230 netisr_dispatch_src() at netisr_dispatch_src+0xa2/frame 0xfffffe02399d8280 ether_input() at ether_input+0x26/frame 0xfffffe02399d82a0 vmxnet3_rxq_eof() at vmxnet3_rxq_eof+0x752/frame 0xfffffe02399d8330 vmxnet3_legacy_intr() at vmxnet3_legacy_intr+0xe0/frame 0xfffffe02399d8360 intr_event_execute_handlers() at intr_event_execute_handlers+0xe9/frame 0xfffffe02399d83a0 ithread_loop() at ithread_loop+0xe7/frame 0xfffffe02399d83f0 fork_exit() at fork_exit+0x83/frame 0xfffffe02399d8430 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe02399d8430 --- trap 0, rip = 0, rsp = 0, rbp = 0 ---

But, yes, many many things have been fixed since 2.4.5 so test in a current version.

Also check the VMWare hypervisor and VM versions you are running.

Yup, someone probably has this working. Unfortunately I don't think I have any way to test it here.

Killing states by ruleID, or lack thereof, is probably a legacy option. pfctl has been extended a lot since pfSense was released.

Or it could be that the ruleID field itself is quite new. That used to be hidden so killing states by it would have been confusing at best.

It looks like pfctl can kill states by ruleID now so that could be a feature request.