On Thu, 5 Jul 2001 16:01:55 -0500
Jim Conner <[EMAIL PROTECTED]> wrote:
> I have @Home as well. I didn't have any trouble setting it up as a static
> ip.
Same here. I'm logged into comcast@home in Burlington County New Jersey. The
only problem I had was early on, with their pop servers. It took a while, like
5 or
6 hours, for all the pop servers to get to know me. I would get random invalid
user ID and Password until the servers all sync-ed up. No problems now. Also
chose the static setup as I doubt, very much I'll be needing the dhcp bull shit
on
my home lan connection.
> I've tried to set it up using dhcp and haven't had much luck. Probably
> a setting is off somewhere.
>
Initially I tinkered with it, never got it to work. So when the @home installer
gave
me the choice of static or dhcp... it was an easy decision.
> I've heard of people having problems with
> Linksys cards though.
.
It comes from the fact that LINKSYS distributed some old drivers with their new
hardware... didn't work. However... the cards are VERY good, will do duplex
100base transfers with a good (linksys) switch box. Through put is VERY good.
The best thing is... the newer kernels 2.4.x have drivers that work from the
get-go.
I am using nothing but Linksys on the home net, LNE100TX versions 4.1 and 4.0
with no problems.
One other upside with Linksys NIC's... everybody wants to get rid of them... I
have
a virtrual endless source of NIC's... :')
If you don't want to compile a new kernel, just to get a working driver...
visit SCYLD
and grab the tulip driver source and compile that. It works just as good as the
kernel
stuff already mentioned.
--
*****************************************************************************
* Registered Linux User Number 185956 *
*****************************************************************************
_______________________________________________
http://linux.nf -- [EMAIL PROTECTED]
Archives, Subscribe, Unsubscribe, Digest, Etc
->http://linux.nf/mailman/listinfo/linux-users
