Some person or people mentioned in here that @Home is too much money. I have a sad fact for them, Excite@Home only takes $20 at the most from your bill (leaving the rest for the cable service). From what I understand from this new Terms of Service from COMCAST and not any other cable provider (@Home sets a set of rules, and then each cable company has the ability to make there own set of rules as well, your best bet is to goto your cable provider's web page and look at the AUP/Terms of Service). When I worked for @Home, people would VPN into work and use there own DSN Servers for work, we would have to encourage the @Work service, because the @Home service does not encourage that kind of usage, it was ment for the home, and not working from the home. Using NAT/Proxy would be a viloation of AUP from @Home, but what they don't know, doesn't hurt them in any such way, thats what I would tell customers. All you have to do is setup a good firewall and block out anything from home.net, which is the corp domain for @Home, even the NOC, they used to have an hostname by the name of ops-scan.home.net doing port scans on customers to see if they are running something they shouldn't be, SMTP, POP3, IMAP4, HTTP, etc. Have a good day =-)
Former @Home Employee at 425 Broadway, Redwood City, CA
Slashdot Mirror
Some person or people mentioned in here that @Home is too much money. I have a sad fact for them, Excite@Home only takes $20 at the most from your bill (leaving the rest for the cable service). From what I understand from this new Terms of Service from COMCAST and not any other cable provider (@Home sets a set of rules, and then each cable company has the ability to make there own set of rules as well, your best bet is to goto your cable provider's web page and look at the AUP/Terms of Service). When I worked for @Home, people would VPN into work and use there own DSN Servers for work, we would have to encourage the @Work service, because the @Home service does not encourage that kind of usage, it was ment for the home, and not working from the home. Using NAT/Proxy would be a viloation of AUP from @Home, but what they don't know, doesn't hurt them in any such way, thats what I would tell customers. All you have to do is setup a good firewall and block out anything from home.net, which is the corp domain for @Home, even the NOC, they used to have an hostname by the name of ops-scan.home.net doing port scans on customers to see if they are running something they shouldn't be, SMTP, POP3, IMAP4, HTTP, etc. Have a good day =-)
Former @Home Employee at 425 Broadway, Redwood City, CA