I've just completed tests… I let 2-3gb trough each port :)
Found 5 faulty on walls...

Probably answered a thousand times. I've no real clue about networking. I built a pfsense router. Pc connects, it works fine, Internet works. My TV can't get internet connection though connects to router. My phone connects also fine. Can get internal connection to devices like nas etc. Can use ookla speed app fine but can't use Netflix on it you tube on it or browse with Safari. Can anyone help me with this and also explain it for someone that has no real idea of networking. I'm very willing to learn. Thank you for any help

It would be nice to be able to run it on ARM devices if the hardware wasn't weak.

@NOYB:

Think you don't have anything to contribute to pfSense project?  Think again.

Probably everybody that uses pfSense has some skill that can be used to contribute to the pfSense project.

Here is just a very short list of examples.  Poke around and I sure you can find something you can contribute.
JavaScript
PHP
HTML
BASH
Language (spelling, grammar, tech writing, help page docs, etc.)

testing
testing
helping others on the forum
asking intelligent questions.
testing
more testing

Yes i agree with the new user interface and how much better the squid and snort packages are integrated it's fantastic!

OpenVPN

https://doc.pfsense.org/index.php/OpenVPN_Remote_Access_Server

Running squid with local ram cache?

Sounds like something snort could do. Not sure about other options.

@phil.davis:

Search for "Internet Guide" - and then you have to subscribe to it.
http://dyn.com/labs/dyn-internet-guide/

Thanks, It took a while , but i got to it:
https://account.dyn.com/labs/dyn-internet-guide/edit-defenseplan.html?new=1

Shameless plug for Ubiquiti.  Just pulled the trigger on one 2xAP SOHO setup and now have done a few more - all using the AC Pro APs.  Also love their 'cloud key' product.  Spend ~$80 once and get Meraki-esque remote access plus the bonus of having a local controller.  If only I could get back the hours of my life I spent configuring Cisco APs.

Good time to share this absolutely cool post by Grünsfröschli:

https://forum.pfsense.org/index.php?topic=107605.0

:-D

A long time ago, we had a quality specialist in to give a talk. His message went like this:

Software engineers are engineers who design and implement software. They need to think like engineers. When software doesn't work as intended it doesn't have "bugs." Bugs are cute, bugs are quirky, even funny. When software doesn't work as intended, it has defects, just like any other engineered solution. Think of it this way: if the anti-lock brakes on your car fail, it's not a bug, it's a defect. It doesn't matter if the root cause is hardware or software. People die either way.

Dramatically worded, but a great message nonetheless.

@phil.davis:

AFAIK there is nothing for that. I am thinking that you are wanting something like:

a) Daily, weekly or monthly check.
b) Check if there is a new version of pfSense (core) available.
c) Check if there are new version of any of the "real pfSense" packages available.
d) If (b) or (d) then notify - e.g. use file_notice so that an email or growl notify is sent and it shows on the dashboard notices.

That would help people with a lot of systems to find out automagically about systems they have not yet updated.

You could add a feature request in https://redmine.pfsense.org/projects/pfsense/issues

Spot, it's like any other system. why don't you wan't your system to be up to date?

Thanks

If something was trying to connect out and there was an Internet issue and say your ISP's router was responding with an error like Route not Found, then that something could have gone into a tight loop that kept attempting to create new states to establish a connection.

It could be just random noise generated by script kiddies. After all, you don't have to ask anyone's permission to send random UDP traffic to random IP addresses, you just do it and the recipient of that traffic sees just random unrelated UDP packets hitting his firewall if he has logging on it.

It was a private bug (potential security issue), it's closed now.

It's fixed. We often don't set % on any bug tickets, so it stays at the default of 0. The status is the only thing that matters.

i think policy based routing need it