[SLE] multiple nics in SuSE 6.1
![](https://seccdn.libravatar.org/avatar/a8f23670c313bcfe6a972088c009d1ba.jpg?s=120&d=mm&r=g)
Hello everybody! I'm trying to set-up multiple network cards to work under S.u.S.E. 6.1. I had to re-compile my kernel in order to use my machine as a gateway/firewall and wish to enable bridging between the two nic's. They are both 3 Com 509's, but for some reason the kernel will only recognise one under the new "experimental (to me)" kernel 2.2.16. My original kernel (2.2.5) will recognise both nics and seems to use modules for the driver. On the newer kernel I loaded the nic driver as a builtin and therefore there is no module. Should I recompile the kernel and use modules for the nic cards instead? Thanks for listening! Mark -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
![](https://seccdn.libravatar.org/avatar/eedd9fb4827a9e56684e129940ceb863.jpg?s=120&d=mm&r=g)
Hi Mark Personally I prefer modules since I can load and unload as required. The in my init script for the firewall I have: # Enable chaining echo "1" > /proc/sys/net/ipv4/ip_forward echo "1" > /proc/sys/net/ipv4/ip_dynaddr # Chain timing /sbin/ipchains -M -S 7200 10 160 # Forward Dialup connections /sbin/ipchains -P forward DENY /sbin/ipchains -A forward -s 10.0.0.0/24 -j MASQ # Forward the 2nd ethernet through the gateway ipchains -A forward -i eth1 -j MASQ Chris On Wed, 14 Jun 2000 07:11:31 -0400, Mark B Withers wrote:
Hello everybody!
I'm trying to set-up multiple network cards to work under S.u.S.E. 6.1.
I had to re-compile my kernel in order to use my machine as a gateway/firewall and wish to enable bridging between the two nic's. They are both 3 Com 509's, but for some reason the kernel will only recognise one under the new "experimental (to me)" kernel 2.2.16.
My original kernel (2.2.5) will recognise both nics and seems to use modules for the driver. On the newer kernel I loaded the nic driver as a builtin and therefore there is no module.
Should I recompile the kernel and use modules for the nic cards instead?
Thanks for listening!
Mark
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
![](https://seccdn.libravatar.org/avatar/a3b15f16f00f828656bd0cb497c3655a.jpg?s=120&d=mm&r=g)
start yast system administration > network configuration > Network Base Configuration add the second nic card, activate it, give it an ip address then go to system administration > Integrate new hardware > Configure networking device > and let it know that eth1 is a 3com 509. Since the code is compiled in the kernel, it shouldnt have to load any other mods or anything. I have always had better luck using two different kinds of nics for this, but I know it will work using the same nics. Heck I have seen a box that has 5 nics in it (all the same) On Wed, 14 Jun 2000, Mark B Withers wrote:
Hello everybody!
I'm trying to set-up multiple network cards to work under S.u.S.E. 6.1.
I had to re-compile my kernel in order to use my machine as a gateway/firewall and wish to enable bridging between the two nic's. They are both 3 Com 509's, but for some reason the kernel will only recognise one under the new "experimental (to me)" kernel 2.2.16.
My original kernel (2.2.5) will recognise both nics and seems to use modules for the driver. On the newer kernel I loaded the nic driver as a builtin and therefore there is no module.
Should I recompile the kernel and use modules for the nic cards instead?
Thanks for listening!
Mark
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- Chad Whitten cwhitten@intop.net http://whitten.dhs.org -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
![](https://seccdn.libravatar.org/avatar/f2066a7dab9943f04b659f6d86a3436c.jpg?s=120&d=mm&r=g)
A mié, 14 jun 2000, Mark B Withers va escriure: Hi Mark, this is my configuration for my two ne nics. /etc/conf.modules ------------- alias etho ne alias etho ne options ne io=0x300,0x320 irq=5,10 (you should change ne (novell eagle) for 3c509) Lilo only try to detect one nic card, for this reason, you must put this line in /etc/lilo.conf: append= "ether=0,0,eth1" Hope it helps. Bye ---------------- Simeó Reig simeo@tinet.org Barcelona (SPAIN) -----------------
Hello everybody!
I'm trying to set-up multiple network cards to work under S.u.S.E. 6.1.
I had to re-compile my kernel in order to use my machine as a gateway/firewall and wish to enable bridging between the two nic's. They are both 3 Com 509's, but for some reason the kernel will only recognise one under the new "experimental (to me)" kernel 2.2.16.
My original kernel (2.2.5) will recognise both nics and seems to use modules for the driver. On the newer kernel I loaded the nic driver as a builtin and therefore there is no module.
Should I recompile the kernel and use modules for the nic cards instead?
Thanks for listening!
Mark
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
![](https://seccdn.libravatar.org/avatar/f2066a7dab9943f04b659f6d86a3436c.jpg?s=120&d=mm&r=g)
A mié, 14 jun 2000, Simeó va escriure:
A mié, 14 jun 2000, Mark B Withers va escriure:
Hi Mark, this is my configuration for my two ne nics.
/etc/conf.modules ------------- alias etho ne alias etho ne
Sorry, the second alias must be : alias eth1 ne -- ---------------- Simeó Reig simeo@tinet.org Barcelona (SPAIN) ----------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
![](https://seccdn.libravatar.org/avatar/5574a2ad242ba2f4d5387bb040330bd9.jpg?s=120&d=mm&r=g)
At 00:47 15-06-00, you wrote:
A mié, 14 jun 2000, Simeó va escriure:
A mié, 14 jun 2000, Mark B Withers va escriure:
Hi Mark, this is my configuration for my two ne nics.
/etc/conf.modules ------------- alias etho ne alias etho ne
Sorry, the second alias must be : alias eth1 ne
and the first one should be: alias eth0 ne It should be the number zero, not the small letter o. Regards Ole Kofoed Hansen okh@post.cybercity.dk ICQ# 25773325 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
![](https://seccdn.libravatar.org/avatar/f2066a7dab9943f04b659f6d86a3436c.jpg?s=120&d=mm&r=g)
A jue, 15 jun 2000, Ole Kofoed Hansen va escriure:
At 00:47 15-06-00, you wrote:
A mié, 14 jun 2000, Simeó va escriure:
A mié, 14 jun 2000, Mark B Withers va escriure:
Hi Mark, this is my configuration for my two ne nics.
/etc/conf.modules ------------- alias etho ne alias etho ne
Sorry, the second alias must be : alias eth1 ne
and the first one should be: alias eth0 ne It should be the number zero, not the small letter o.
Wow, yes! Sorry again, fucking exams !! -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
![](https://seccdn.libravatar.org/avatar/a8f23670c313bcfe6a972088c009d1ba.jpg?s=120&d=mm&r=g)
Well that's ok. I think I'm also running into trouble because on the first nic (eth0) I need to run the dhcp client while on the second nic (eth1), I do not. I wish to use the two nics for bridging between the asdl router and my internal intranet. It seems like the router needs for a machine to inquire upon it for an ip address. Of course I may be wrong about this. Mark On Wed, 14 Jun 2000, [ISO-8859-1] Simeó wrote: | A mié, 14 jun 2000, Simeó va escriure: | > A mié, 14 jun 2000, Mark B Withers va escriure: | > | > Hi Mark, this is my configuration for my two ne nics. | > | > /etc/conf.modules | > ------------- | > alias etho ne | > alias etho ne | | Sorry, the second alias must be : alias eth1 ne | | -- | ---------------- | Simeó Reig | simeo@tinet.org | Barcelona (SPAIN) | ----------------- | | -- | To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com | For additional commands send e-mail to suse-linux-e-help@suse.com | Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ | | -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
![](https://seccdn.libravatar.org/avatar/3c08eb5bb345f55e353570ed99a6e03e.jpg?s=120&d=mm&r=g)
It may work out if you tell the kernel where both cards live. You would do
this with an "append" line in /etc/lilo.conf.
The 3c509 is an ISA card correct? If I remember right it is, in which case
you'll probably need to find out the cards' resources (I/O space and
interrupt) with a DOS utility. One you have this info you do something
like:
append="ether=irq0,base_addr0,if0 ether=irq1,base_addr1,if1"
where irq0 is the IRQ of card #1, base_addr0 is the I/O base address of card
#1, and if0 is the interface (probably eth0). The second "ether" is, you
guessed it, for the second card.
Better yet you can have the kernel autodetect the first card, then tell it
where the second card is with the append line:
append="ether=irq1,base_addr1,if1"
In this case you have to make sure the kernel doesn't find the second card
first, otherwise it won't find the first card at all. To make sure the
kernel doesn't find the second card first, use a reserve in the append line.
A reserve prevents the kernel from probing the given I/O base (and a given
range from that base) until it is explicitly told to do so (via the ether
parameter):
append="reserve=base_addr1,32 ether=irq1,base_addr1,if1"
As an example,
append="reserve=0x300,32 ether=9,0x300,eth1"
Would prevent the kernel from probing from 0x300 to 0x31f and then tells the
ethernet drivers to look at interrupt 9 and I/O base 0x300.
More info on these boot parameters in the Ethernet-HOWTO. They are also
covered in more detail in the BootPrompt-HOWTO.
Regards,
kw
/* Keith Warno
** Developer & Sys Admin
** http://www.HaggleWare.com/
*/
----- Original Message -----
From: "Mark B Withers"
participants (6)
-
admin@brevsville.com.au
-
Anonymous User
-
cwhitten@intop.net
-
k01164@ko.sdu.dk
-
keith@HaggleWare.com
-
simeo@nil.fut.es