At 03:58 PM 3/18/00 -0500, Kerry Blalock wrote:
>Dean,
>Thanks for the information. I have been battling this since 3:30 this
>morning. I went to to site, but could not find the driver in any foirm
>except an open text file. I haven't installed nay like that yet, so I
>went back to office d and picked up another kit that had two of the same
>cards I am now using, plus the other stuff for growth. :) I am trying to
>set this box up as a firewall for my ADSL line. Telocity instructions
>said to turn on DHCP(? not sure of letters) so I did in linuxconf or
>netcfg. Wehn I put the new card in, box did not see it either, so I
>turned the DHCP option off, and now ifconfig shows me both nics. After
>reinstalling the system, I can't get the network stuff to work with the
>other machines, and I haven't tried to get telocity working yet. So
>slowly, I will find the offending file , and get my pings, and telnet,
>ftp, nfs working, then proceed with the internet.
>
>Kerry
>
Kerry,
You need to turn on dhcp for the NIC connected to the DSL "modem",
but unless you are running a dhcp server on your network, you do not
want it for the NIC that connects to your local network. Also, be sure
you know which NIC connects where.
One thing that can help with the setup is to not have the interface
you are using for the DSL line come up on boot. That way you can get
the local network all set up first. If you try sending something out
on the local net, and you don't see any activity on the hug status lights,
but ifconfig shows the transmit count climbing, but not the receive count,
you know to try the other NIC.
I will be going through some of this Monday, if all goes well. But I
was able to check out the firewall by using a crossover cable to my laptop
to simulate the DSL connection...
Mikkel
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
