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.

Thank you for the inputs guys really appreciate it, for the meantime, I just disable the public access and push to use OpenVPN instead.

@Grimson Thanks, that did it, I had forwarding mode on pfsense but not actually configured.

None of these warrant individual threads. I merged them all. None of these are specific to pfSense. They are between your hardware and FreeBSD. Take this to FreeBSD.

Move VPN server A out of the LAN onto a different interface. Avoids asymmetric routing problems. Have pfSense connect directly to VPN server B would also do that. Remove VPN server A entirely and use pfSense for that. Steve

@stephenw10 yep, change to mbr and it is responding per the instructions. vesa error gone, with 1280 after initial boot pass