PLEASE let @Home now this our ((*&*$) cable partners own the last mile and as such control the splitting and recombining of nodes. Your connection to the CMTS is through a 8Mhz channel that will carry 39Gms but if they don't split and add more lines on to congested areas the service degrades... The cable partners are required to uphold a level of service to customers of themselves and @home.
Ok a little insight into Cable Modems and @Home
1. Cable modems are configured via a downloaded boot file and set using SNMP strings, none of this "Replace the chip" crap. The CMTS (Cable Modem termination server will not recognize your modem and grant an IP if the file does not configure it.
2. A cable modem is not even a modem at all it is a HFC router point.
3. Rate limiting is done on the CMTS and the Cable Modem. @Home is instructed by our cable partners to limit the speed as to our contract. They own the customer not us, I'm sorry.
3. Your QOS (Quality of Service) is dictated by your start date the cable partners set that twice a year and they are becoming stricter... again sorry
~E
P.S. your talking about the SB2100 Vs. the SB3100, actually the 3100 transmits faster
Your posting is interesting,
I work at @Home, specifically I manage the @Lab (or the server QA division) and I know intimately the internal workings of cable modems and your statement of sustained speeds of 5mps is very interesting... the current winner of the fastest modem contest is the Best data a2123 you may know it by another name, regardless this modem transmits a MAX of 4.8MBS and has only been in manufacture for three months. I have no idea how you were able to make you modem perform that fast, you should sell the secret;-)
As a technical side note the 8Mhz channel that Docsis cable modems transmit on can only transit a maximum of 39Gbs to the CMTS (cable modem Termination server or a router if you will.
I agree with the sentiments... I will se if we could make the port route out an option you can set yourself.
Granted... 1 and 2 are a take at face value problem.
Alas our Email administration group is how shall I say this delicately... plain stupid. A spammer just read our LDAP email store and sold your account. We are not perfect but I will try to admit our flaws openly.
Email has surprisingly remained our single largest problem. In security alone we fail to protect our users rights to confidentiality. Hopefully changes are in place to replace what has been so lacking in our support of users.
No not at all, your computer name is not set up by @Home, your DNS name (the other tab) is. @Home does not monitor users site hits or any other aspect of your usage. Period end of story.
on a side note, how would you possible monitor and log 2.7mil customers each pulling 800 to 4,000 pages a day? You just can't do it the way we work.
You and me agree but Richard (why they interview him I don't know he barley understands what we do for a living) doesn't want to scare the less informed user's. I think like-minded managers and myself here at @Home are winning...
Correction, Digital Phone Service is a cable modem based Telephony service, so you're a little misinformed:-) If a word sounds like it does not mean it is:-).
On the optional (or not) http proxy note... you may want to turn them on because
1. Our proxies do not log so unlike AOL and smaller ISP's we do not resell your site hits to others.
2. We mainly store graphical information files of large content on the proxies to save from you having to (again) waste your connection and @Homes backbone on repeating the same request another user just did. Again is saves bandwidth and is saves Us/You in the end with hopefully soon a reduction in cost.
AT&T has little to do with it they give @Home the copper is all. We (@Home) ate the technology that makes this work... even for roadrunner they copied our model easy sense we believed in open standards.
Ok, why does @Home use DHCP when you seem to get a static IP address...
Another small background on Cable modem technology, your cable modem is not a brain dead network bridge with a little compression thrown in like you typical Telco modem or DSL device. A cable modem works as a kind of mini router and DHCP server, as a DHCP server it can be configured to issue IP addresses and allow them to route back to the backbone.
Q: why did we do this?
A: Part 1. This allowed @Home to dynamically manage its IP blocks and routing tables, how does this help you the user? With this you can hit a web page and get more IP addresses for your home network (up to 5 in most area's). In addition all our devises can also be dynamically readdressed allowing an infinite (or close to it) growth of the @home network.
Part 2. Security is another consideration it is hard to hack a moving target a user can call or email @Home that they are under fire and we can first move them off to a new IP address if the attacker finds our user again we can port capture there address and call them up (if they are a fellow user) or block the IP at the cable modem for a few weeks.
Actually your Cable modem is your DHCP server (you could hit it to make yourself feel better). DHCP is a lousily defined RFC and allows for May interpretations http://www.ietf.org/rfc.html our's does have problems with some Linux releases. Our RDC based DHCP software was written by @Home because no other company's DHCP implementation could handle the load... 120 request a second.
Imagine what happens when a city louses power... that's right. Every cable modem comes up and asks for its IP address and boot file and like a bunch of hungry chicks this server has to manage to service all the chicks, rather a daunting task huh?
On behalf of @Home I'm sorry for the problems you had. @Home is a partnership with many cable company's like Cox, AT&T and Comcast we can not control their performance or their ability to keep there cable understructure clean... I will say that is you want to try us again I can arrange a 30-60 day trial fr free...
if your up to it email me and try us again. @Home is working very hard to make up for its faults in the past.
Really Mobil DSL... I got to get me one of those:-) Digital subscriber Line or DSL is a hardwired copper connection to your home, there is nothing mobile about a DSL line... So you work for marketing?:-)
Strange your @Home jargon is almost correct... I'm not to certain to believe you? please type "the" into atlas and give me a call I can shed some light on your problems..
OK, I work as SW engineer at @Home
Item 1.) "I know that news feeds take up a lot of bandwidth" , They at one time used 32% of our bandwidth for a bunch of data that no one even looks at. You are so correct we have kept our own News servers unfiltered in the vain hope that users would refrain from running there own and use the shared server. This has not worked and we are forced to hunt down and ask people to use the shared server.
Item 1.) I do agree on the firewall, @home can help you after the fact but your going to have to keep your own system secured. The port scanning has been a much-discussed problem that we have not found a good answer for.
Not necessarily Naster, your DNS address is also dynamically linked to your IP address. You can get a new IP address if we need to renumber a massive section of our network... as a rule we inform you long before even considering doing so but you are far safer to rely on your DNS name (which is a user based ID) then your IP address.
Erik
@Home
Only if your running a business off of it... other than that @Home welcomes people to use NAT's and routers it saves the massive overhead of managing millions of IP addresses and there associated router configuration.
Ok, why does @Home use DHCP when you seem to get a static IP address...
Another small background on Cable modem technology, your cable modem is not a brain dead network bridge with a little compression thrown in like you typical Telco modem or DSL device. A cable modem works as a kind of mini router and DHCP server, as a DHCP server it can be configured to issue IP addresses and allow them to route back to the backbone.
Q: why did we do this?
A: Part 1. This allowed @Home to dynamically manage its IP blocks and routing tables, how does this help you the user? With this you can hit a web page and get more IP addresses for your home network (up to 5 in most area's). In addition all our devises can also be dynamically readdressed allowing an infinite (or close to it) growth of the @home network.
Part 2. Security is another consideration it is hard to hack a moving target a user can call or email @Home that they are under fire and we can first move them off to a new IP address if the attacker finds our user again we can port capture there address and call them up (if they are a fellow user) or block the IP at the cable modem for a few weeks.
Strange you would rant @Home over Pac-bell, but I digress...
No @Home is not your mommy and will not "protect you". We do monitor our network for mass connections also called "tribe attacks". An alarm is triggered by a mass (for us this it 13,000 connections a second) network jump from multiple points on the network. A real "tribe attack" is very distinctive on a utilization map, one-minute 6,000 connections and wham! 14,000. To stop the madness we take the site off the route tables till it passes and then put it on line again.
Again this is not blocking our customers or restricting them, this is keeping one of the Internets largest backbones from being used as a weapon buy an uncreative wan bee hacker.
Not at all @home was founded by people who do not believe in the "Walled Gardens" like AOL or Pac-bell. your connection is never tampered with, we only stop the modem from routing requests or broadcast on 2 known ports, that were never meant to be passed onto the backbone in the first place. To be honest if you don't know how to close your own ports (like 1054) you deserve it;-)
From another post of mine:
" A small background on Cable modem technology, your cable modem is not a brain dead network bridge with a little compression thrown in like you typical Telco modem or DSL device. A cable modem works as a kind of mini router and as a router can be configured to filter out traffic that broadcasts across your network. Like the infamous Windows file and print sharing broadcasts...
Q: "Why do we do this" you ask?
A: Well think of it this way... you network you are connected to is a data steam, do you really want someone spewing dirt into your clean stream and Rivers... NO. Additionally unsuspecting users systems could be damaged by a uncreative wan bee hacker, remember not all or half our users are techno savvy folk.
This does not mean we are firewalling you in it means we are keeping data that was never meant to go out of the users home networks off your broadband connection. It is wasteful and drives up the cost of your connection"
Slashdot Mirror
PLEASE let @Home now this our ((*&*$) cable partners own the last mile and as such control the splitting and recombining of nodes. Your connection to the CMTS is through a 8Mhz channel that will carry 39Gms but if they don't split and add more lines on to congested areas the service degrades... The cable partners are required to uphold a level of service to customers of themselves and @home.
Ok a little insight into Cable Modems and @Home 1. Cable modems are configured via a downloaded boot file and set using SNMP strings, none of this "Replace the chip" crap. The CMTS (Cable Modem termination server will not recognize your modem and grant an IP if the file does not configure it. 2. A cable modem is not even a modem at all it is a HFC router point. 3. Rate limiting is done on the CMTS and the Cable Modem. @Home is instructed by our cable partners to limit the speed as to our contract. They own the customer not us, I'm sorry. 3. Your QOS (Quality of Service) is dictated by your start date the cable partners set that twice a year and they are becoming stricter... again sorry ~E P.S. your talking about the SB2100 Vs. the SB3100, actually the 3100 transmits faster
Another Technical note: DSL generally is 128kbs up and down... if you post your Zip plus four I will take a look into your problem. Erik
Your posting is interesting, I work at @Home, specifically I manage the @Lab (or the server QA division) and I know intimately the internal workings of cable modems and your statement of sustained speeds of 5mps is very interesting... the current winner of the fastest modem contest is the Best data a2123 you may know it by another name, regardless this modem transmits a MAX of 4.8MBS and has only been in manufacture for three months. I have no idea how you were able to make you modem perform that fast, you should sell the secret ;-)
As a technical side note the 8Mhz channel that Docsis cable modems transmit on can only transit a maximum of 39Gbs to the CMTS (cable modem Termination server or a router if you will.
your free time but I thank you for using the shared server.. Erik @Home
I agree with the sentiments... I will se if we could make the port route out an option you can set yourself.
Granted... 1 and 2 are a take at face value problem.
Alas our Email administration group is how shall I say this delicately... plain stupid. A spammer just read our LDAP email store and sold your account. We are not perfect but I will try to admit our flaws openly.
Email has surprisingly remained our single largest problem. In security alone we fail to protect our users rights to confidentiality. Hopefully changes are in place to replace what has been so lacking in our support of users.
Erik
@Home
No not at all, your computer name is not set up by @Home, your DNS name (the other tab) is. @Home does not monitor users site hits or any other aspect of your usage. Period end of story.
on a side note, how would you possible monitor and log 2.7mil customers each pulling 800 to 4,000 pages a day? You just can't do it the way we work.
Your lie and logic are a wee flawed my friend,
Erik
@Home
I just checked the CMTS and routes,,,, your not blocked... try again
Erik
@Home
Are you that guy? Hats off to you :-)
Erik
@Home
You and me agree but Richard (why they interview him I don't know he barley understands what we do for a living) doesn't want to scare the less informed user's. I think like-minded managers and myself here at @Home are winning...
We will see,
Erik
@Home
Correction, Digital Phone Service is a cable modem based Telephony service, so you're a little misinformed :-) If a word sounds like it does not mean it is:-).
Please go to...
broadband.att.com
Erik
On the optional (or not) http proxy note... you may want to turn them on because
1. Our proxies do not log so unlike AOL and smaller ISP's we do not resell your site hits to others.
2. We mainly store graphical information files of large content on the proxies to save from you having to (again) waste your connection and @Homes backbone on repeating the same request another user just did. Again is saves bandwidth and is saves Us/You in the end with hopefully soon a reduction in cost.
Erik,
@Home
AT&T has little to do with it they give @Home the copper is all. We (@Home) ate the technology that makes this work... even for roadrunner they copied our model easy sense we believed in open standards.
Erik
@Home
sorry not how we (@Home) run it...
Ok, why does @Home use DHCP when you seem to get a static IP address...
Another small background on Cable modem technology, your cable modem is not a brain dead network bridge with a little compression thrown in like you typical Telco modem or DSL device. A cable modem works as a kind of mini router and DHCP server, as a DHCP server it can be configured to issue IP addresses and allow them to route back to the backbone.
Q: why did we do this?
A: Part 1. This allowed @Home to dynamically manage its IP blocks and routing tables, how does this help you the user? With this you can hit a web page and get more IP addresses for your home network (up to 5 in most area's). In addition all our devises can also be dynamically readdressed allowing an infinite (or close to it) growth of the @home network.
Part 2. Security is another consideration it is hard to hack a moving target a user can call or email @Home that they are under fire and we can first move them off to a new IP address if the attacker finds our user again we can port capture there address and call them up (if they are a fellow user) or block the IP at the cable modem for a few weeks.
Erik
@home
Actually your Cable modem is your DHCP server (you could hit it to make yourself feel better). DHCP is a lousily defined RFC and allows for May interpretations http://www.ietf.org/rfc.html our's does have problems with some Linux releases. Our RDC based DHCP software was written by @Home because no other company's DHCP implementation could handle the load... 120 request a second.
Imagine what happens when a city louses power... that's right. Every cable modem comes up and asks for its IP address and boot file and like a bunch of hungry chicks this server has to manage to service all the chicks, rather a daunting task huh?
Erik
@Home
On behalf of @Home I'm sorry for the problems you had. @Home is a partnership with many cable company's like Cox, AT&T and Comcast we can not control their performance or their ability to keep there cable understructure clean... I will say that is you want to try us again I can arrange a 30-60 day trial fr free...
if your up to it email me and try us again. @Home is working very hard to make up for its faults in the past.
Erik
@Home
Really Mobil DSL... I got to get me one of those :-) Digital subscriber Line or DSL is a hardwired copper connection to your home, there is nothing mobile about a DSL line... So you work for marketing? :-)
Erik
Strange your @Home jargon is almost correct... I'm not to certain to believe you? please type "the" into atlas and give me a call I can shed some light on your problems..
Erik
@Home
OK, I work as SW engineer at @Home
Item 1.) "I know that news feeds take up a lot of bandwidth" , They at one time used 32% of our bandwidth for a bunch of data that no one even looks at. You are so correct we have kept our own News servers unfiltered in the vain hope that users would refrain from running there own and use the shared server. This has not worked and we are forced to hunt down and ask people to use the shared server.
Item 1.) I do agree on the firewall, @home can help you after the fact but your going to have to keep your own system secured. The port scanning has been a much-discussed problem that we have not found a good answer for.
Erik
@Home
Not necessarily Naster, your DNS address is also dynamically linked to your IP address. You can get a new IP address if we need to renumber a massive section of our network... as a rule we inform you long before even considering doing so but you are far safer to rely on your DNS name (which is a user based ID) then your IP address. Erik @Home
Only if your running a business off of it... other than that @Home welcomes people to use NAT's and routers it saves the massive overhead of managing millions of IP addresses and there associated router configuration.
Look in your policy guild off of members central.
Erik
@Home
You it the nail on the head, but there are more technological and management facts for using DHCP in the manor you describe... read my other post
Erik
@Home
Hello Erik again
Ok, why does @Home use DHCP when you seem to get a static IP address...
Another small background on Cable modem technology, your cable modem is not a brain dead network bridge with a little compression thrown in like you typical Telco modem or DSL device. A cable modem works as a kind of mini router and DHCP server, as a DHCP server it can be configured to issue IP addresses and allow them to route back to the backbone.
Q: why did we do this?
A: Part 1. This allowed @Home to dynamically manage its IP blocks and routing tables, how does this help you the user? With this you can hit a web page and get more IP addresses for your home network (up to 5 in most area's). In addition all our devises can also be dynamically readdressed allowing an infinite (or close to it) growth of the @home network.
Part 2. Security is another consideration it is hard to hack a moving target a user can call or email @Home that they are under fire and we can first move them off to a new IP address if the attacker finds our user again we can port capture there address and call them up (if they are a fellow user) or block the IP at the cable modem for a few weeks.
Erik
@Home
Strange you would rant @Home over Pac-bell, but I digress...
No @Home is not your mommy and will not "protect you". We do monitor our network for mass connections also called "tribe attacks". An alarm is triggered by a mass (for us this it 13,000 connections a second) network jump from multiple points on the network. A real "tribe attack" is very distinctive on a utilization map, one-minute 6,000 connections and wham! 14,000. To stop the madness we take the site off the route tables till it passes and then put it on line again.
Again this is not blocking our customers or restricting them, this is keeping one of the Internets largest backbones from being used as a weapon buy an uncreative wan bee hacker.
Erik
@Home
Not at all @home was founded by people who do not believe in the "Walled Gardens" like AOL or Pac-bell. your connection is never tampered with, we only stop the modem from routing requests or broadcast on 2 known ports, that were never meant to be passed onto the backbone in the first place. To be honest if you don't know how to close your own ports (like 1054) you deserve it ;-)
From another post of mine:
" A small background on Cable modem technology, your cable modem is not a brain dead network bridge with a little compression thrown in like you typical Telco modem or DSL device. A cable modem works as a kind of mini router and as a router can be configured to filter out traffic that broadcasts across your network. Like the infamous Windows file and print sharing broadcasts...
Q: "Why do we do this" you ask?
A: Well think of it this way... you network you are connected to is a data steam, do you really want someone spewing dirt into your clean stream and Rivers... NO. Additionally unsuspecting users systems could be damaged by a uncreative wan bee hacker, remember not all or half our users are techno savvy folk.
This does not mean we are firewalling you in it means we are keeping data that was never meant to go out of the users home networks off your broadband connection. It is wasteful and drives up the cost of your connection"
Erik @home