[NTLUG:Discuss] can not bring up all eth* on boot time?

[George E. Lass]

m m wrote:
> 
> I have 3 questions, please help.
> 
> 1. my 3 NICa can not bring up at boot time, here is what I did:
> 
> I add
> insmod ne
> insmod 3c509
> in the /etc/rc.d/init.d/network at very beginning of the file.
> 
> my /etc/conf.module file:
> 
> alias eth0 ne
> options ne io=0x300
> alias eth1 3c509
> options eth1 -o 3c509-0 io=0x320 irq=5
> alias eth2 3c509
> options eth2 -o 3c509-1 io=0x340 irq=10
> 
> the 2 3com NIC has been set io=320,340 irq=5,10
> 
> on boot time only the eth0 bring up.
> I have to run /etc/rc.d/init.d/network restart to bring these 2 3com NICs.
> my bos is compacq 486, run RH 6.2 All NICs are isa.

You *may* need a line like:

append="ether=5,0x320,eth1 ether=20,0x340,eth2"

in /etc/lilo.conf

This is what I had to do, but I'm not using modules for
my ethernet drivers.

Also, don't forget to run lilo after modifying lilo.conf.


> 
> 2. how do I know if the ip_fordward has been enabled?
> 
> there is a way to check something like ...
> 
> cat /proc/ksys... | grep ip_fordward

Try: cat /proc/sys/net/ipv4/ip_forward


> 
> and should get response, if don't get any response, that means the
> ip_fordward do not enabled.
> on RH 6.2 it says that you can enable ip_fordward by
> 
> echo "1" > ....
> 

Try echo "1" > /proc/sys/net/ipv4/ip_forward

> but this seems do not work to me.
> 
> 3. There are 2 boxes. A 192.168.1.1, B 192.168.1.2, they are connected.
> The problem I have is:
> A can ping B ( no packet lose) but B almost can not ping A (96% packet lose)
> any one has the idea?
> 
> any one have idea?

Sorry can't help on this one.


George

-- 
... Unix IS a user friendly O/S ...
(It's just picky about its friends)