As posted by the doktor on the other thread: https://redmine.pfsense.org/issues/4437#note-2 Nothing to see here.  The perils of -current.

@Derelict: I wish Jim or Chris would chime in. https://redmine.pfsense.org/issues/4437#note-2 Move on…

enable SNMP in pfSense and have PRTG auto discover the services on the box.

I don't know what that output means but you might have better luck by posting this in the Traffic Shaping forum.

1.  Questions about the traffic shaper are best posted in the Traffic Shaping forum. 2.  I have no idea what you mean when you say "how many protocol or port that use on my traffic shaper such as (Skype, Hangout, SIP phone, Go to Meeting, Lync)"?

Limiters. You might want to post in the Traffic Shaping section with a descriptive title.

Just found the problem and made it work System>Advanced>Firewall/Nat uncheck "Disable reply-to on WAN rules" Now ping works and TCP and UDP.

imho it's best to use the system->patches addon to insert commits

Ok, the problem was the connected serial cable with the other end open for all the time, means without termination of a serial device or serial-usb adapter. May be some signal reflection/induction on the open end back to the serial port on the APU.1D4 board.

maybe its just me, but installing non security, or very basic network functionality features (dhcp, dns) on my firewall seems like bad juju to me. I would go the VM route - this allows you to use the same hardware for lots of thing, but still isolate from installing stuff on your firewall OS.

Thank you NOYB and grandrivers for the helpful information. When looking at the packets I captured on the WAN I do see many re-transmission because of "TCP  new fragment overlaps the old". This leads me to believe it is on Charters end since it is their IP throwing the error. I also see some inconstancy with Apinger which makes me question the data in RRD graph as well.

Thanks for the answers. When I reproduce the issue I will try few things and let you know @dgcom That seems to be a good workaround. If I can't troubleshoot the problem then I will go with that. Thanks

So the fix I posted earlier works, but apinger still crash sometimes, so I wrote a watchdog script to put in the crontab. The "watch_apinger.sh" shell script will look for apinger PID using ps CLI, look for apinger PID using its PID file (in case of SIG_KILL), compare both values, and run "restart_apinger.php" script if needed: #!/bin/sh RELAUNCH=0 CUR=$(ps xcopid,command | awk '/apinger/ {print $1}') PID=$(cat /var/run/apinger.pid) [ -z "$CUR" ] && RELAUNCH=1 [ -z "$PID" ] && RELAUNCH=1 [ "$CUR" != "$PID" ] && RELAUNCH=1 [ "$RELAUNCH" == 1 ] && ( killall apinger ; /root/restart_apinger.php ) Save it to "/root/watch_apinger.sh" and make it executable : chmod +x /root/watch_apinger.sh Then add it to root crontab: echo "* * * * * /root/watch_apinger.sh" | crontab -

Thank you guys! Maybe you are right,I have to buy a switch

Go to SSH shell and run squidclient -p 3128 mgr:info Look at the Median Service Times.  Look for something that stands out, like a DNS lookup times in the 1-10+ second range.

Then you don't have any unassigned interfaces available for assignment so the button doesn't appear.

Might it be you are mixing some things up here? pfSense is a full blown, enterprise grade router/firewall that runs on most any standard PC-based hardware. It has a WebGUI for configuration but by no means is it a replacement GUI for your DSL router. Given the feature set of this software and your statement that your "PLDT my web configuration is not so easy to use", chances are, that pfSense is overcharging your current capabilities. Expect a steep learning curve at least.

I enabled it once, so it must be a very intermittent bug…