@ali-ilyas said in PFSense On 4G To Remotely Access PLC (Programmable Logic Controller): I tried using Pfsense to access a PLC over VPN without having to enter router or default gateway info into PLC but didn't work. Also you will need to have a route setup on your local machine or router to the remote LAN network that sends traffic to the pfsense box that is performing the outbound NAT to the remote LAN. Hopefully it will be using a subnet that is different from your local network.

This is targeted for CE-next in redmine but seems to have stalled. Does CE-Next mean 2.5.2 or 2.6.0 ?

If you are hitting that it mostly affects VPN tunnels using the interface address. Whatever nuance it is causes the interface to return a VIP as the primary address. However you will find it doesn't cause a problem for pf using the system alias 'WAN address' for firewall rules or outbound NAT for example. If you can use a VIP there instead of the interface address that will be unaffected. Steve

There were significant changes in pf after 2.5.1 which will be in 2.5.2, especially in state handling. That panic is unlikely to still happen on 2.5.2, or at least would have a different backtrace which would be more helpful.

@mfld ill do that.. thanks a lot!

A downgrade then upgrade in the UI worked for me.

Smoothing can cause stuff like this for sure.. Also filtering could come into play as well. And have not played much with the mode..

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.