>
Thanks for the insight. I ended up changing to having the drivers loaded in
the kernel and adding the append statement into the lilo.conf file. I can now
communicate with both the internal and external networks.
I also removed my networking statements from the /etc/init.d/network file and
ad
On 2000-03-02 10:59:25, Doug wrote:
> I was under the impression that the append line was used when the
> networking is built into the kernel (not in modules).
You pass config info to modules via setings in /etc/modules.conf.
Perhaps, you need to "force settings" (opposed to relaying on pnp
confi
Thanks for the reply jeff. I was under the impression that the append line was
used when the networking is built into the kernel (not in modules). Should I
add this into lilo.conf even if I am using modules?
I guess an additional question would be if I should compile the networking into
the ke
The instructions I sent were for drivers compiled into the kernel. If you
are using modules, you'll have to do something like in the Ethernet howto,
in particular, you'll prob. have to pass the IO port and IRQ...
http://www.linuxdoc.org/HOWTO/Ethernet-HOWTO-3.html
On Thu, 2 Mar 2000, Doug wrote:
Read over the Linux Network Administrators Guide, you need to pass some
parameters to the kernel to let it know that it needs to look for 2
cards. The NAG is kinda old, but that piece of it still applies:
http://www.linuxdoc.org/LDP/nag/nag.html
For instance, I have a firewall w 2 3c503 cards in
Hello,
I hope this is the right area to ask this question. I have a system I plan to
use as a firewall eventually. Currently I am trying to get the networking
(using two 3C509 network cards) to work.
Originally my system was using the 2.0.36 kernel and everything seem to work
fine. eth0 con
6 matches
Mail list logo
