Here you are just capturing all packets on the WAN to what, if anything, is there. I expect to see either the gateway monitoring pings or ARP requests at least. Probably not much else.
But if you see the upstream gateway sending ARP requests for example that gives us a clue.
You can run the packet capture from the webgui:
https://docs.netgate.com/pfsense/en/latest/diagnostics/packetcapture/webgui.html

You can add the gateway status widget. If you have the monitoring for gateways set to something external, like 8.8.8.8, then that's a pretty definitely indication.

Steve

Yes, our offering there is still in development. There are some third party tools for doing this but we don't endorse any of them.

It's that OBN rule bug as shown in the report above. Almost certainly.

That's expected on a 2100.

@johnpoz Thank you for the information. I will wait for a fix.

@c0ff33h4x

Thanks for the feed back.
Be assured : I would have also fallen into the trap.

It is (was) easy for me to say : as soon as we know a newer pfSense is out, only upgrade packages after I've upgraded pfSense.
Packages repositories should be 'per pfSense version', or, way easier : package upgrading (using the GUI) should show a warning (or even block ?) if this information is isn't 'current' and/or not showing the green "The system is on the latest version".

e7f89436-7e5a-42ff-89df-cbd9261e87f7-image.png

@johnpoz looks like you nailed it....thanks !

Colors should convey some kind of meaning. Choosing a random color just to have it be a color seems like a bad idea.

The grey color already has a well-known intended meaning of something being inactive/disabled. I don't see the need to change it.

@stephenw10

I haven't seen it since I put on the maint patches, come to think of it. Hmmmmm.

I'll post back if I see it again. I do tend to review the logs every few days.

Yup, we are discussing what we can do.

Bug to track it: https://redmine.pfsense.org/issues/15019

@stephenw10

I agree 100%. the E2140 will not.

Just a little update there were several other issue other than the CPU.

The Netgear R6220 under powered - disabled Traffic Meter and every thing else, but Access Control, DHCP, port forwarding and WIFI. The RealTek NIC;s conflict with drivers and version(s), just downloaded updated driver package and replaced drivers.

After fixing those items I decided to pull the trigger and move this setup to the i7 NUC, just unplugged the hard disk and plugged it into the i7 NUC, ran the installer but select recover previous configuration from the menu, the followed the installation prompts.

Everything came back configured except the NIC;s just reassigned and set the ip address and bang done.

I am now hitting 1.1 GBPS on downloads and 940 MBPS on uploads. CPU utilization is between 2 - 5% on average and never peaks above 6%. Still using the Netgear but that is another can of woms I will tackle later (too much configuration) need to document and test the document that it is correct as I have allot of Home Smart Devices (i.e cameras, smart plugs, door bells, door locks, etc,,,,) they were a nightmare to setup and get working, do not want to repeat that.

But thank you for replying, as I am I noob with pFsense I can offer little help but if you have question for me just ask I will try my best to answer

DarkKnight

@stephenw10
Seems reasonable. Thanks for the advice on this. I will think about this a bit more. Appreciate it Stephen

@azureadministrator Sounds like it's a question for your host provider...

@stephenw10 We will try to find out. Thank you very much for your effort.

@michmoor That's a really nice looking flow chart/graph. Is that something you have as a plugin on pfSense? I've been looking for a way to get that for a long time.

I too agree with your statements on NtopNG being useless for anything other than realtime flows.

Hello,
Sorry about the delay.

In fact the problem did not come from the configuration but simply from a DNS problem. I hadn’t paid attention, but the ping test was coming back to me from the IPs which does not concern my Network. The domain I thought was not used on the web is used. To make a test I tried to clamp PFSENSE so that it only gets my DNS from the AD without success.
I changed the name of my domain and this time I made sure it was mine.
Now it works out.

thank you for your help.

@stephenw10 said in SSL termination, traffic forwarded to varnish cache:

I would expect that work yes. There any many people using HAProxy on pfSense pretty much exactly like that.

Just wondered if I was overlooking something or maybe someone had written a nice article on putting this together.

Thanks for your input folks.