Comment A tale of two fibers. (Score 4, Insightful) 301
Screw whatever karma points I'm not going to get...I have nothing too insightful to say on this matter; but i'm going to talk anyway.
I, too, feel it's a trumped up way of making customers pay for a higher tier. I too wonder why they specifically are targeting web-servers than anything else. One part of me wants to say it's a "public" vs "private" aspect. Look at a device like a Slingbox for example. When you get down to it; it's a server. It's a little device that sends data over the internet. At the same time; it's "hidden" and not publically accessible. You need two individual logins to be able to connect to it; one for the slingbox website; another for the slingbox itself. It's not like *anyone* can drive by my IP and go "I think i'll stream some video". I don't know of a single ISP that's had issue with this. I'm sure there's a few people with google fiber running one. Verizon has never taken an attempt to block mine. or tell me I needed to stop running it. Hell, having this insane amount of bandwidth is what made me invest in one in the first place. Same goes for my remote SSH access. Yeah; that's a server alright; but again, it's not a "public" thing...and mine isn't even on a standard port. So, maybe there's a distinction between a "public" server; like an httpd; and "private" servers like SSH, games, torrents; etc. I run a VPN on my network...and that's not even raised any eyebrows by my ISP...and within that VPN I've got access to any server running on my LAN. Again, this is what leads me to believe they make a distinction between public servers pumping out data to everyone; and private servers that "just happen to use your residential" account.
But, let me focus on Verizon for just another minute; since it's the only ISP I've used for the last 11 years (12 if you count the year my DSL was technically GTEi). My original DSL TOS was on like...a 4"x4" leaflet...and said *nothing* about servers. I read that tiny piece of paper three or four times.....GTE (this was before they completely merged the networks sometime in '02) didn't care if you ran a server on your DSL. Therefore; I did. In fact, I ran a server a large majority of the time I was on a DSL connection. Verizon never blocked port 80....and I don't think they even scanned. Oddly enough; the only port they blocked was 25. It was for trying to reduce the amount of spam people's PCs were sending out; and they gave a TON of notice about it. I didn't have a business account...they probably didn't have to tell me; but they did. They even called me to make sure I knew about the upcoming block on incoming port 25. I ran web-servers; ftp; ssh; shoutcast, even an ircd; never had Verizon "get after me" or block any ports.
Ok, granted FiOS isn't offering a 1gpbs plan yet; and I don't know what ever happened to XG-PON...but even now, they don't forcibly prevent you from running a server by blocking ports. A buddy of mine up in MA has a residential FiOS account and has been running an httpd for who knows how long. I've tried running services that are public on standard ports and never had an issue.
There's...a lot I don' t know about how they handle; or even if they check. If google's blocking port 80 incomming (which is what I gathered from some of the comments); then how is it Verizon...whose been called extremely evil...not?
Maybe part of it is the "old" way of thinking it seems tech companies don't want to shake. Maybe they're lumping *anyone* who runs a server as a business; completely shunning the fact a home user might want to run a server as a hobby.
I, too, feel it's a trumped up way of making customers pay for a higher tier. I too wonder why they specifically are targeting web-servers than anything else. One part of me wants to say it's a "public" vs "private" aspect. Look at a device like a Slingbox for example. When you get down to it; it's a server. It's a little device that sends data over the internet. At the same time; it's "hidden" and not publically accessible. You need two individual logins to be able to connect to it; one for the slingbox website; another for the slingbox itself. It's not like *anyone* can drive by my IP and go "I think i'll stream some video". I don't know of a single ISP that's had issue with this. I'm sure there's a few people with google fiber running one. Verizon has never taken an attempt to block mine. or tell me I needed to stop running it. Hell, having this insane amount of bandwidth is what made me invest in one in the first place. Same goes for my remote SSH access. Yeah; that's a server alright; but again, it's not a "public" thing...and mine isn't even on a standard port. So, maybe there's a distinction between a "public" server; like an httpd; and "private" servers like SSH, games, torrents; etc. I run a VPN on my network...and that's not even raised any eyebrows by my ISP...and within that VPN I've got access to any server running on my LAN. Again, this is what leads me to believe they make a distinction between public servers pumping out data to everyone; and private servers that "just happen to use your residential" account.
But, let me focus on Verizon for just another minute; since it's the only ISP I've used for the last 11 years (12 if you count the year my DSL was technically GTEi). My original DSL TOS was on like...a 4"x4" leaflet...and said *nothing* about servers. I read that tiny piece of paper three or four times.....GTE (this was before they completely merged the networks sometime in '02) didn't care if you ran a server on your DSL. Therefore; I did. In fact, I ran a server a large majority of the time I was on a DSL connection. Verizon never blocked port 80....and I don't think they even scanned. Oddly enough; the only port they blocked was 25. It was for trying to reduce the amount of spam people's PCs were sending out; and they gave a TON of notice about it. I didn't have a business account...they probably didn't have to tell me; but they did. They even called me to make sure I knew about the upcoming block on incoming port 25. I ran web-servers; ftp; ssh; shoutcast, even an ircd; never had Verizon "get after me" or block any ports.
Ok, granted FiOS isn't offering a 1gpbs plan yet; and I don't know what ever happened to XG-PON...but even now, they don't forcibly prevent you from running a server by blocking ports. A buddy of mine up in MA has a residential FiOS account and has been running an httpd for who knows how long. I've tried running services that are public on standard ports and never had an issue.
There's...a lot I don' t know about how they handle; or even if they check. If google's blocking port 80 incomming (which is what I gathered from some of the comments); then how is it Verizon...whose been called extremely evil...not?
Maybe part of it is the "old" way of thinking it seems tech companies don't want to shake. Maybe they're lumping *anyone* who runs a server as a business; completely shunning the fact a home user might want to run a server as a hobby.