Quote:
Originally Posted by Lord of the Rings  How do you define "Firewalled"?
Do you mean simply UDP firewalled, or TCP firewalled, or other protocol? Or do you mean blocking via other means?
I suspect UDP or TCP firewalling would be a legal breach of services offered, potentially making an entity at risk of being sued be it the ISP or government being the target of such action.
You also need to consider proxy use and VPN's (although probably not so many people want to invest in VPN use, which costs, but can be very good.) |
Both UDP and TCP.
Essentially you have outgoing capacity, with your only incoming connectivity being based on your outgoing requests to an exposed ip/port.
This is pretty much the way browsing works. A host has a port (usually 80 or 443) exposed on their IP. Your browser makes a request to that port via a random outgoing port (regenerated every request). Your data is returned to that port and that port is then closed to incoming traffic (listening).
So to be clear, I am saying that the forced firewall would be rendering non-commercial clients incapable of listening on any port aside from outgoing requests made to exposed hosts. All data retrieved from the internet would have to be requested from an exposed port and returned to the exact port that requested it (after which the requesting port closes).