Robert H. Merriman wrote:
> Connect the ethernet card directly to the cable modem OR
> if you are connecting a LAN be sure to use the uplink port
> of the hub to connect the modem to the hub. If your hub
> doesn't have an uplink port then use a cross over cable to
> connect it to the modem to the hub.
Be aware that some ISPs charge by the IP address. My ISP would complain if
I put more than one DHCP client on the cable modem by using a hub that way,
and ask that I cough up an extra $10-15/month for the priv.
Also, some ISPs who use cable modems use (or have used, in the case of RR
down here), authentication SW that runs only under Windows or MacOS.
Fortunately in my case, a Linux client was available. RR dropped the
requirement and are now doing just DHCP -- unless you need to edit your
account information and then they require the software.
I haven't tried, but i would think that the software might work under
vmware even on a masqueraded connection, as it doesn't handle the DHCP
side, it just passes authentication information to set up (what I suppose
to be) some kind of login session state on the server. (Authentication
will time out but TCP/IP keeps rolling along.)
-W-
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
