What does pfsense have to do with a switch port?  Come on think for a couple of seconds here..  How does pfsense tell the switch not to negotiate a connection "lights" on the switch?? "the printer refuses to accept any connection" Well again No Lightly No Worky!!! Is your printer 10/100 while your switch port is hard coded GIG?  You get NO Lights at all, not even a flicker when you first plug in the cord??  But your saying this printer works on another switch?  And your saying other stuff works when you plug it into the port on the switch printer doesn't work on? What is the printer, what is the switches involved.  What is the cable your using.  You changed cables right?

@artooro: For the record we have found the source of this issue, some of the code that was written for a linux environment doesn't seem to run quite as well on freebsd so we'll issue an update for users asap. And Mothra as a preview-release early tester we will personally contact and verify with you that the fix is working. Interestingly I didn't see this issue on my virtual machine. Thanks! Top notch service as usual ;) Update fixed the issue.

Thanks Jorge I stepped through the suggestions in your posted links, and nothing seemed to work until I got to Traffic Shaping.  The Traffic Shaping had been done on the original installation, so of course the speeds were off ! I reran the Wizard and tweaked it a bit, and voila - I get to keep this old box for a while longer. Appreciate the tips, they were right on :) Regards

YES!!! that worked..i logged in as admin and was able to make changes. Now to configure my group to be allowed to makes changes too.

@georgeman: https://atxfiles.pfsense.org/mirror/downloads/ Or any of the other mirrors. Still, I would suggest to troubleshoot the issue and get it fixed (if due to a bug) Thanks, i've been troubleshooting the issue for 2 weeks now and whilst i'm pretty sure it's a bug and will present it shortly, I need to get a working solution for my customer asap.

@cmb: That ATA error is likely because the drive is dying. Guessing it'll probably come back, might just not be hitting the part of the disk that's problematic post-reinstall for some reason. Maybe next power cycle or some future power cycle it comes back. Check SMART on the drive, though it being clean isn't necessarily indicative of no issue. I couldn't even check it, it has a output/input parse error. I believe my HDD died on it unfortunately. Every time I shut it down and try booting it backup I get a ton of errors and now when I tried turning it on I got kernel not found. I'm gonna replace the HDD/SATA cable and see what happens.

On #2, this is RRD objecting to time running backwards. The first timestamp is recent (May 10th), while the second timestamp is from back in January. It may be that the current time has not yet been set after boot. I see this happen with power cycling systems that do not have a battery backed clock. It goes away once NTP is synchronized.

up

Hello Fahim, Do your PPP logs give you any idea of the problem? can you post them here? Mike.

@coxhaus: I can run packet captures if it would help? Yes that would be telling. Filter on the IP of the TV.

Race conditions!

@dennypage: This might be of assistance for #2: https://forum.pfsense.org/index.php?topic=110043.0 Yep changing the ping payload fixed the issue.

@pfdigs: Working with the provider/carrier to provision fibre to building (upgrade from ADSL, yay!) and the initial question (before deployment) they've asked is "Can you confirm if a /31 will be compatible with your equipment for IP addressing?" We're using the SG-4860. Yes that would be fine.

I gave the answer to this in your other thread where you originally asked this question. https://forum.pfsense.org/index.php?topic=108668.msg605967#msg605967

After some time I have finally installed my ELK log system ( I need only to adjust the appearance ) and obviously  it doesn't log all traffic by default (states are not sent trough syslog) but you need to mark in every firewall rules "Log packets that are handled by this rule". I know that this thread is old, but it can be useful for those looking for logging states know this. PS: ELK seems hard to configure, but the result seems to be amazing  ;D

In PFSense 2.3.1 version, PHP have the updated time zones and the webConfigurator time is correct, but the console not, thus, the LOGs show the incorrect time…  :o I fix with this: mkdir zoneinfo cd zoneinfo wget http://pkg.freebsd.org/freebsd:11:x86:64/latest/All/zoneinfo-2016.d.txz xz -d zoneinfo-2016.d.txz tar xf zoneinfo-2016.d.tar cd usr/share/zoneinfo tar czf ../../../zoneinfo.tgz * cd ../../../ scp zoneinfo.tgz root@192.168.0.1:/usr/share ssh root@192.168.0.1 8 cd /usr/share/zoneinfo tar czf ../zoneinfo.bkp.tgz * mv ../zoneinfo.tgz . tar xzf zoneinfo.tgz After reboot… The file /usr/share/zoneinfo.bkp.tgz is a backup of original files.

For torrenting, since they'll use any and every port available, i'd specify the http/https ports in the floating firewall rules, and then traffic-shape the hell out of the subsequent catch-all.