I found this page that describes the fix which corrected my issue. Mostly, set to the current distribution, in my case 2.4.5 DEPRECATED and run "sudo pkg-static install -f pkg" https://agent31.net/blog/2021/03/10/fixing-stalled-package-manager-in-pfsense-2-4-5-p1-easily-in-5-minutes/ This procedure fixed the package manager on my 2.4.5-p1.

looks like everything is working now! many thanks to everyone who gave their input!

Use Captive Portal along with FreeRadius. Create a user and restrict no of simultaneous devices to 3. Share the username and password with all the users.... at a time only 3 will be able to connect. Regards, Ashima

For everyone's reference: apparently the notification methods are mutually exclusive. I had to first disable the SNMP notification method to have the Telegram one work. It looks like a bug to me. At the very least it is a behavior worth documenting.

If you create a new column in Wireshark and add the field vlan.id you'll be able to see the vlan ID otherwise look in the data. [image: 1624298101833-screenshot-2021-06-21-at-18.50.46.png]

@terminalhit Hy, Were you able to perform this configuration between PfSense + Syslog + OMS Azure + PowerBI?

@mer Okay, will wait some days and then do so. Thanks a lot.

@openwifi That link shows you how to integrate a script using the cron package. What step isn't clear for you ? Btw : The real solution would be to understand why this happens : @openwifi said in Script for Automatic Reboot of my pfsense box: where my WAN 1 connections seem to stop working The interface is bad ? The other side's interface is bad ? What is the other side ? DHCP re-negotiation is failing ? Etc.

@mewsense said in 504 Gateway Time-out: Not sure if it's related to a recent release Hi, There would be a lot of crying people here, if it was new release dependent... this is a very basic function, we agree?

@james2432 said in IPTV Bell FTTH: I was following this guide Hi, It will never work , because of the ISP's unique FW(s), -you can try, but it won't work. (it is not ISP-dependent, but they are all implementing their own ideas) We played with it for a long time, but it wasn't up to us .... Pls. let me know if it works: https://community.ui.com/questions/SOLVED-USG-Altice-Meo-Fibra-Data-IPTV-Portuguese-ISP/a0fb840b-8aad-4072-bf0e-279c53244475 it looks like this for us, but it never works properly.....

@steve_b Im on the newest version an its not fixed.

@g-shaffer Looking at /usr/local/lib/libldap* not sure how the symbolic links got changed. lrwxr-xr-x 1 root wheel 21 Apr 19 05:18 libldap-2.4.so.2 -> libldap-2.4.so.2.11.6 -rwxr-xr-x 1 root wheel 306248 Feb 5 12:12 libldap-2.4.so.2.11.5 -rw-r--r-- 1 root wheel 613160 Apr 19 05:18 libldap.a -rw-r--r-- 1 root wheel 816 Apr 19 05:18 libldap.la lrwxr-xr-x 1 root wheel 21 Apr 19 05:18 libldap.so -> libldap-2.4.so.2.11.6 lrwxr-xr-x 1 root wheel 23 Apr 19 05:18 libldap_r-2.4.so.2 -> libldap_r-2.4.so.2.11.6 -rwxr-xr-x 1 root wheel 332440 Feb 5 12:12 libldap_r-2.4.so.2.11.5 -rw-r--r-- 1 root wheel 670626 Apr 19 05:18 libldap_r.a -rw-r--r-- 1 root wheel 830 Apr 19 05:18 libldap_r.la lrwxr-xr-x 1 root wheel 23 Apr 19 05:18 libldap_r.so -> libldap_r-2.4.so.2.11.6 Basically deleted libldap and reinstalled the openldap-client-2.4.57 package.

I think that's what my issue was - hitting the public-facing ip from my LAN.

@stewart yeah I might give it a shot anyway since it's RC and this is non-prod. Not sure yet though as stability does still matter to me quite a lot.

thanks both @johnpoz & @JKnott! understood!!

It just happened again. This time the VoIP did not work while the WAN was not accessible. Makes me think it is the cable modem itself. Jun 17 11:05:08 php-fpm 1189 /rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. '' Jun 17 11:05:07 check_reload_status 1226 Reloading filter Jun 17 11:05:07 check_reload_status 1226 Restarting OpenVPN tunnels/interfaces Jun 17 11:05:07 check_reload_status 1226 Restarting ipsec tunnels Jun 17 11:05:07 check_reload_status 1226 updating dyndns WAN_DHCP Jun 17 11:05:07 rc.gateway_alarm 11702 >>> Gateway alarm: WAN_DHCP (Addr:24.166.168.1 Alarm:0 RTT:12.451ms RTTsd:4.459ms Loss:5%) Jun 17 11:03:16 php-fpm 85733 /rc.openvpn: Gateway, none 'available' for inet6, use the first one configured. '' Jun 17 11:03:15 check_reload_status 1226 Reloading filter Jun 17 11:03:15 check_reload_status 1226 Restarting OpenVPN tunnels/interfaces Jun 17 11:03:15 check_reload_status 1226 Restarting ipsec tunnels Jun 17 11:03:15 check_reload_status 1226 updating dyndns WAN_DHCP Jun 17 11:03:15 rc.gateway_alarm 3595 >>> Gateway alarm: WAN_DHCP (Addr:24.166.168.1 Alarm:1 RTT:12.474ms RTTsd:3.470ms Loss:22%) Jun 17 11:00:02 php 82382 [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload Jun 17 11:00:00 php 82382 [pfBlockerNG] Starting cron process. Jun 17 10:00:02 php 18110 [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload

No. The captive portal part of that is what allows pfSense to know which users are connected. You might be able to do it using 802.1x authentication at the APs. That's not something I've ever tried. Steve