I checked @home about 6 months ago, i didnt like them (they wanted to
touch my colon...) The cost was prohibitively expensive for me ($200/month
for business type account, which is necessary for running a server) and to
do what i wanted to do they wanted $300 or $400/month!
I belive they do block service, do not support linux, and
provide "network security and diagnostics" for your network (meaning they
snoop on what your doing and your equipment). I asked how much to not get
the security, and they said "its free!" i said, ok, how much more to not
get the "Free security and diagnostics", i got silence for a while, then
she said uhh... we cant do that. so... i figure if they cant do that, then
they must have some reason, and im not interested in their service... she
then continued to try to sell me their stuff... so i said goodbye :)
Now... about the technology. I dont know what hardware they use, however
if its an internal device (the cable modem), you will likely have a lot of
trouble getting it to work, if you can! If the device is external, and
connects to the PC via standard communication devices(ethernet, serial,
...), and standard protocols(tcp/ip, ...), then you should be able to run
linux, and possibly ip masqing.
Jamie
On Sun, 2 Apr 2000, Dennis Soper wrote:
> On 2 Apr 00, at 20:31, [EMAIL PROTECTED] wrote:
>
> > Good luck - I know that their policy is that they don't
> > allow servers, and that they don't "support" linux. I've
> > never quite understood if that meant linux was impossible
> > or that they just won't give you linux help. Or if they even
> > check if you actually have a server running.
>
> Whether they "support" it or not, isn't the problem-- probably
> means you won't get help. I would find out what kind of cable
> modem is supported and then look in the how-tos to see if it will
> work. There have also been a number of posts on the suse-linux-e
> mailing list about getting it to work. If you can get a static IP (and
> hopefully a domain name) out of them and a DNS server address, it
> shouldn't be much of a problem, provided you can get the cable
> modem to work.
>
> The big thing that can be a problem (so I've been told) is if they're
> using Exchange for the mail server. I would assume that @home
> uses *nix, as Dennis Ritchie, Ken Thompson, and David Korn work
> for them. ;) Also, because NT wouldn't scale to a network that size.
>
> As for the server, I doubt they can do much about that, unless they
> don't allow incoming requests for certain services into some
> network segments. This could be a *real* drag for telecommuting,
> whether you want a full-on server or not-- think of that file you forgot
> to email, etc.
>
> If you think you can get it to work, you might ask real specifically
> about which ports are open for inbound network traffic in your
> network segment. They'll probably get real upset if people start
> doing ftp linux installs from your box. I've got a server stuffon one
> of my home boxes, with the explicit knowledge of clipper. I also
> had to agree that if inbound traffic got too high, I would have to pay
> more money or find a different ISP, but it's just for development, so
> it's no big deal.
>
> > What would be really great to figure out is how to get DSL
> > and Cable working together. DSL for the server, Cable for the
> > fast surfing speeds, downloads, multimedia. You think that's
> > possible? (Forgetting about the cost factor for now?)
> >
> > Let me think... an ethernet interface for each network into
> > the same computer... specify the Cable network as your gateway
> > but make your DNS resolve to your DSL ip address...? Yikes,
> > my brain just tied itself in a knot.
>
> Yeah, you need at least one router, and I'm not sure Linux has what you
> need to do the job-- might be a job for Cisco or Cyclades.
>
> Cheers,
> Dennis
> "Custard pies are a sort of esperanto: a universal language."
> --Noel Godin
>
