Topic: CoovaChilli will not recognise thirt ethernet card

[ctimlin]

Hi All,

I have been having a problem with installing CoovaChilli on a new test machine. The target machine is a Dell OptiPlex GX280 with SMEServer 7.5.1.   I've switched off the onboard adaptor as it was causing other problems so I have used standard PCI cards:  RTL8139 as local (server / gateway) , ADMtek NC100 as external, and a good old fashioned 3c905B as the CoovaChilli addon.

When the machine is being configured I can see all 3 cards and have been able to mix the configuration to test each card.

But when the machine reboots only eth0 and eth1 are seen.  No eth2 or tun0 as per CoovaChilli HowTo. As a result CoovaChilli refuses to start.

Any ideas?

[cactus]

Any ideas?

Yes, SME Server only supports a maximum of two NICs, not more.

[Daniel B.]

As your 3rd NIC is different from the two others, you need to load the apropriate kernel module. For example, if this NIC is handled by the 3c59x kernel module, you can do the following:

Code: [Select]

cat <<'EOF' > /etc/sysconfig/network-scripts/ifcfg-eth2

TYPE=Ethernet
DEVICE=eth2
USERCTL=no
ONBOOT=no
PEERDNS=no
IPV6INIT=no
IPADDR=0.0.0.0

EOF

echo "alias eth2 3c59x" >> /etc/modprobe.conf

Then, the module should automatically load on boot, eth2 will be available, and chilli will be able to start and to create the tun0 interface.

Let me know.

Regards, Daniel

[ctimlin]

Spot on Daniel. 

I've moved over to an older FujitsuSiemens Scenic machine with the onboard Intel 80801EB/ER adapter as the local, and two 3C905C cards for external and coovachilli use.
I had that problem with the onboards for a number of Dells that I tried. Dev not found and some errr number, repeating for 20-30 minutes, very frustrating.

All seems well now.  I just have to get to grips with editing the home page and seeing what auditing can be done to stop the public misusing the service. 

Thanls again,
Colm

[johnp]

Be sure to do an advanced search of the forum on CoovaChilli. A lot of questions you may have, likely have been answered.

Thanks Daniel for your support of this community and all the work you've done on LDAP for our implementation in the future.