Well stated, but...
My usage is minimal and the modem/router has 4 ports. I was just trying to get a 150MB file to my buddy without slicing it into 15 pieces, spending all day emailing and clogging smtp servers, just so he can stitch them back together only to find one chunk got rotten in transit. He lives in another city.
Most ISP's are either blocking or starting to block ports ranges 1-1024. The reason for this is because you signed up as a private user and as a private user you should not be running any services and if you want to run services then you should be paying the higher price for your usage. I am sure if you look at your contract it might even state that you are only allowed to connect 1 PC to the internet also.
And running services is not a privilege. It's a right. And it's how the internet came to be. Remember Bulletin Boards and Usenet?
But that's like saying I'm only paying for the right to use my house. The guys who cut the lumber actually own it. They did their job and went home to their houses.
You are only paying to utilize the connection you do not own it. Same as the software you use on your computer. You are paying for the right to use it it is not yours and someone else owns it. As is the with GNU software. You don't own it but you are normally given the right to do with it as you see fit.
No no. This was that website recommended earlier that made me all paranoid.
I take it you run this scan locally and not from the outside.
Yes, indeed. I could tell by the perfect spelling. It was a Live Chat session from their website.
This is a standard answer to which 99% of the users would agree to as they do not have a clue what they are doing or how to protect themselves.
Yes. I tried that. It's my belief that my modem/router filters _types_ of packets, not just the ports. Some types get through, and other types don't. I've been bouncing packets around here all week.
Example I will use is SSH. SSH normally listens on port 22 but we know that is blocked so we need to change that port to something over 1024, so lets chose 22022. Now you need to configure SSH to listen on that port
And thank you for the example, others will surely appreciate it. Well said.