Code:
79/tcp filtered finger
111/tcp filtered sunrpc
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
449/tcp filtered as-servermap
513/tcp filtered login
514/tcp filtered shell
515/tcp filtered printer
555/tcp filtered dsf
2049/tcp filtered nfs
4045/tcp filtered lockd
6969/tcp filtered acmsoda
7000/tcp filtered afs3-fileserver
7100/tcp filtered font-service
12345/tcp filtered NetBus
12346/tcp filtered NetBus
27665/tcp filtered Trinoo_Master
31337/tcp filtered Elite
These ports are blocked for good reasons. If you can give me a good enough reason to unblock them, I'll consider it. But, fingerd for IRC isn't going to cut it.
With all of the existing Linode customers, a good number have been with us for more than a year and a half, and no one has complained thus far makes me inclined to keep things how they are...
-Chris[/quote]
Basically I am looking for a UML provider that offers an open pipe as a policy. This way I am confident than in the future they will not block any ports that I am relying on. This has currently happened with by cable supplier.
I would like to define my own network access policy using iptables based on the services I will be offering. These may or may not be the ones you have blocked, but I think it should be left to the user to decide. Considering that you recommend running a service on a different port if the port is currently blocked, it doesn't really offer any additional security. The cases where these port blocks may provide extra security is when a user enables every server on a Linux distributions and neglects to keep it up to date with security patches.