@johnpoz "dhcpleases kqueue error: unkown" @jimp there is a bug listed from Jim for 2.5 which seems to be the same as with 2.4.4_p2 https://redmine.pfsense.org/issues/9383 it appears on a vanilla install with only DHCP / DNS Resolver turned on on 2.4.4_p2 "DNS Query Forwarding" - Enable/Disabled - makes no difference to the error "Register DHCP static mappings in the DNS Resolver" - Enable/Disabled - makes no difference to the error the trigger for the error is "Register DHCP leases in the DNS Resolver" checked error occurs, unchecked no error Error first appears immediately after boot and any time unbound is re-started In 2.3.4 there was the same error, but for a different reason. But this can be ignored. https://redmine.pfsense.org/attachments/2097/unbound-stop.diff

If you edited the Limiters you may need to re-apply them in the rules. Unless you created that rule specifically there is not normally a way to edit the Negate Networks rule. I would still try disabling it as I said and then reload the rules in Status > Filter Reload and see if it comes back without errors. Steve

Yes, it looks like legacy, no efi partition. It's almost certainly fine to remove it but renaming first is always wise. If you think you may have created it yourself then nothing to worry about. Steve

I gave the bridge mode a try today. I believe I have the PFSense appliance properly configured. I was able to update firmware and download Snort but I think I had a conflict of some kind so I decided to abort for now. Everything went south on me so I stopped and backed out. It turns out I accidentally took down my whole network by accidentally plugging my Lan into the third expansion Wan port on the Balance 210 Router that is not activated. Stupid move! It took me an hour to realize the bone head move! Needless to say ...that port is now tapped over. Will read some more and go at it again in a few days ....

It still should work be default in 2.3.5 but, yeah, if you've found some edge case that somehow doesn't it's not going to be fixed there ever. Steve

Nice tip, be good to know if that fixes it. Otherwise I'd check the PCI IDs from pciconf -lv. Also look at the boot log for driver attach errors. Steve

If that's replicable I'd open a bug report for it, assuming one doesn't exist already. https://redmine.pfsense.org Edit: It does: https://redmine.pfsense.org/issues/8454 Steve

That user has been removed.

Maybe post to a Nagios forum?

it is normal , the message wont reset automatically.

@Jawhead said in MTU Settings: @JKnott Hi It's not working, the MTU I set on port 3 is 1400, but when I check on Status-->Interfaces It's still 1500. Take note I rebooted the firewall after changing the MTU. I expect that's due to the MTU being set on the NIC, not in FreeBSD. If so, you're trying to set the same hardware to different MTU. I don't know enough about the network stack to say for certain.

Hi, Great, I will check it out and revert back if I need additional help. Thanks.

Just an update here for anyone who's interested/following I seem too have fixed all my issues now the only thing i need too do too finish setup is move the the xboxs from a strict nat to a open nat What was the problem with the local upnp? Quote from Wikipedia "IGMP snooping and reliability If IGMP snooping is enabled on a switch, or more commonly a wireless router/switch, it will interfere with UPnP/DLNA device discovery (SSDP) if incorrectly or incompletely configured (e.g. without an active querier or IGMP proxy), making UPnP appear unreliable. Typical scenarios observed include a server or client (e.g. smart TV) appearing after power on, and then disappearing after a few minutes (often 30 by default configuration) due to IGMP group membership expiring." What was wrong with Network Discovery? im sorry i cant confirm what actually fixed this its been a combination of enabling different thigs and trial and error reading the net and watching videos it mainly seemed too be services stopped and features disabled (possibly from an windows update) What was wrong with xbox upnp? This was solved as soon as i fixed the upnp locally Thanks everyone for the replys and tips it might not have seemed like it but they helped alot

Why shouldn't they, what did you try to prevent it? Hint: use the "Block Ads" feature of modern browsers.

Post this issue to a new thread in either General pfSense Questions or Packages: Traffic Monitoring.