@vjizzle Thanks! Regretfully, I did not keep my config from previous versions. I'll know to do that going forward!

@chudak said in What is IP 169.254.178.43 ?: emails from pfsense It's an email? That implies something in pfSense is triggering an alert that is sending you a notification email. What is in the logs at that time? By itself the text shown seems rather meaningless...as noted an APIPA address is self-assigned by the default when DHCP isn't functioning. But then why would pfSense even know about the IP in a subnet that's not its own? And what is the alert that is triggering...there is no alert or error as written? What is the email subject? re: Private Address, that is for creating a unique MAC address not IP address.

@stephenw10 I just had this exact same issue and registered here to say thank you. This solved my problem.

The mail server (exchange 2019) is behind pfsense, the way it's setup, my mx is pointing at duo circle (primary scannig and queue in case of server failure) then it sends it to my exchange server if i enable pfblocker duocircle gives me connection refused (network erre) on numerous emails, the odd part is......... the same IP on the pfblocker will show as pass or fail, I do not use dnsbl, just ip In my pf logs when i do add that ip to my pass list the emails coming from that ip flow through problem is.....There's a sh**** load of them.... I know.... gotta do it

@balanga said in Logging to loghost: @bmeeks said in Logging to loghost: Yes, you can configure a remote syslog server on the system logging tab. Here is a link to the official documentation: https://docs.netgate.com/pfsense/en/latest/monitoring/logs/remote.html describing how to configure this. I don't see a system logging tab. The docs mention :- @bmeeks said in Logging to loghost: Yes, you can configure a remote syslog server on the system logging tab. Here is a link to the official documentation: https://docs.netgate.com/pfsense/en/latest/monitoring/logs/remote.html describing how to configure this. I don't see a system logging tab. The docs mention: The Remote Logging options under Status > System Logs on the Settings tab allow syslog to copy log entries to a remote server. I don't have a System Logs entry under Status. I'm using 2.4.5_1 You should see exactly the same screens as user @Gertjan posted earlier. This basic menu and screen layout has not changed for several pfSense versions.

@wmheath586 you might also want to drill down further to the MAC address tables in your router. If you are using a managed switch you should be able to telnet into your router and inspect the MAC address table. This would be relevant if you are running multiple VMs and have left the MAC addresses at their defaults.

abrupt power loss and UFS has always been bad mix.. You should be on a ups for sure to prevent such events. ZFS is better at handling them from my understanding, but would still suggest ups. I recently changed to using zfs in the lastest release of pfsense. But I have personally not tested abruptly removing power ;) And have no plans of doing that either - better to make sure it doesn't happen then to test what happens when it does if you ask me ;)

@piersciclark said in User Manager only allows password reset of local user?: Yes, I had the same question In 2019. ..... 2.4.4-p3 had a user manager bug. Why is that, today, important ?

@alanhjames check and see if your gateway is in the 169.254.x.x range. if it is, go back to 2.5.0 to fix. I hear there is a patch for 2.5.1 to fix as well, but do not know where that is.

@gertjan Interesting ... I have a cable modem (Motorola) and when the service is down or disrupted, I get WAN n/a however, I have no RF1918 checked on WAN. Thanks for sharing, I learn something new today.

@tgimagine What do you have for an outbound NAT rule?

@twiztddwg See if they boot up without a network error then make some calls. Fingers crossed.

@viragomann connected only show in the ethernet under network & internet settings. PPPoE (OPT1) did not get any IP

Well not by anything that counts! But, OK, not in the way 169.254 is non-routable. Anyway the fact RFC1918 IP destinations are sent out of the WAN is not a problem and is required in some situations. Steve

@mrhub Hello the updated repositories to install Netdata in pfsese 2.5.1 pkg install -y pkgconf bash e2fsprogs-libuuid libuv nano pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/Judy-1.0.5_2.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/json-c-0.15_1.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-certifi-2020.12.5.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-asn1crypto-1.4.0.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-pycparser-2.20.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-cffi-1.14.5.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-six-1.15.0.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-cryptography-3.3.2.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-idna-2.10.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-openssl-20.0.1.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-pysocks-1.7.1.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-urllib3-1.25.11,1.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/py37-yaml-5.3.1_1.txz pkg add https://pkg.freebsd.org/FreeBSD:12:amd64/quarterly/All/netdata-1.29.2.txz

Yup, that. Or have a transport subnet between the two routers with static routes over it so each has a route to the subnets on the other. That could be a separate VLAN between them. 'Two routers, one subnet' is almost always a bad idea. You can work around it with outbound NAT rules like that but it's much cleaner to avoid it. Steve

@akegec In the meanwhile the ISP has been changed and the problem solved, but thank You, it could help me in the future.

@kiokoman is J1900 4GB Ram, new appliance. bios is updated with a version of 2018. i have same appliances working with no issues