Re: [cobalt-users] Qube 2 and @home networks

[Kris Dahl <kris@xxxxxxxxxxxxx>]

on 2/18/00 11:01 AM, Frank Johnson at frank@xxxxxxxxxxxxxxxxxxxx wrote:

> Did you give @home the nic information of your qube2?
> 
> On Wed, 16 Feb 2000,
> Mark Callahan wrote:
> 
>> I'm trying to get my Qube 2 to act as a line sharing on my @home network
>> connection.  However, @home has network scanners that only let you on their
>> network if you computer name matches one in their database.  I gave my Qube
>> 2 this computer name but I still can't get on the network.  I know other
>> cobalt users have Qubes on @home networks so how did you get around this?

Shouldn't matter.   Think of the logistics in keeping track of everyone's
MAC addresses.  A network card goes bad, then a customer has to get a new
NIC, call in the new address, etc.  That's be lunacy.  There is a deal with
the DHCP requiring identification.  DHCP isn't going to work for the Qube
more than likely due to their implementation.  I would quesiton any
implementation of dynamically assignment of static addresses.  Just one more
thing to complicate the situation.  THey also use some not oft-used parts of
DHCP to setup host name information, etc. so that you just have to type
'mail' or whatever into your email client for SMTP instead of (for example)
pop.sttl.uswest.net.  Although, I personally question the technical merits,
I can see how it would make things easier for other users.

If you go into the management interface utility thing that @home gives you
(I think its called @home assistant), it has a section somewhere where you
can get your IP information.  You actually get assigned a static.  You can
purchase more statics for about $4.95 a month up to 2 or 3.  This static
will also be labeled 'IP:' on your original work order/invoice (next to PD:,
etc.). 

PUnch that in and the router address, etc, and you'll be in business.

FYI: I have a Qube running on @home at my condo.  And I've set up another.
So I know it works.

-k