![](https://seccdn.libravatar.org/avatar/f4cd8e2cd103e0e97af0d11a5c6dfa9f.jpg?s=120&d=mm&r=g)
OS: SuSE 9.1 with kernel 2.6.5-7.111 WE have two identical systems built using the ASUS A7N8X-X motherboard with an Athlon 2500+ processor. The bulit in NIC is detected fine but the following errors appear in the boot.msg log concerning the second NIC: SIOCGIFFLAGS: No such device interface eth1 does not exist However, if I go into YaST => Network Devices => Network Card, both NICs appear in the top window as detected but not configured. (We are using both as part of a bridging firewall based on Shorewall, hence do not set them up in YaST.) At this point I can abort out of YaST and manually execute the /etc/init.d/bridge script and both NICs are found. Question: What does YaST use to detect NICs? Thank you, Lucky Leavell
![](https://seccdn.libravatar.org/avatar/712247edfbb995e02cdedf69464c3d17.jpg?s=120&d=mm&r=g)
Lucky Leavell wrote:
OS: SuSE 9.1 with kernel 2.6.5-7.111
WE have two identical systems built using the ASUS A7N8X-X motherboard with an Athlon 2500+ processor. The bulit in NIC is detected fine but the following errors appear in the boot.msg log concerning the second NIC:
SIOCGIFFLAGS: No such device interface eth1 does not exist
However, if I go into YaST => Network Devices => Network Card, both NICs appear in the top window as detected but not configured. (We are using both as part of a bridging firewall based on Shorewall, hence do not set them up in YaST.) At this point I can abort out of YaST and manually execute the /etc/init.d/bridge script and both NICs are found.
Question: What does YaST use to detect NICs?
Thank you, Lucky Leavell
Well, my version of Yast is not up to speed (I'm on SUSE Pro 8.0). That said, where you see Yast recognizes the cards, there should be a button that says "Configure". Click that (after selecting a NIC) to actually configure the cards. I am, of course, assuming you need to either manually assign them IP addresses, or tell them to use DHCP. If the Yast module doesn't allow you to configure the cards, or that's not what you need, then I'll leave you in the hands of the more experienced gurus. Don -- DC Parris http://matheteuo.org/ http://chaddb.sourceforge.net/ "Free software is like God's love - you can share it with anyone anytime anywhere."
![](https://seccdn.libravatar.org/avatar/f4cd8e2cd103e0e97af0d11a5c6dfa9f.jpg?s=120&d=mm&r=g)
Thank you, Lucky Leavell On Fri, 22 Oct 2004, Don Parris wrote:
Lucky Leavell wrote:
OS: SuSE 9.1 with kernel 2.6.5-7.111
WE have two identical systems built using the ASUS A7N8X-X motherboard with an Athlon 2500+ processor. The bulit in NIC is detected fine but the following errors appear in the boot.msg log concerning the second NIC:
SIOCGIFFLAGS: No such device interface eth1 does not exist
However, if I go into YaST => Network Devices => Network Card, both NICs appear in the top window as detected but not configured. (We are using both as part of a bridging firewall based on Shorewall, hence do not set them up in YaST.) At this point I can abort out of YaST and manually execute the /etc/init.d/bridge script and both NICs are found.
Question: What does YaST use to detect NICs?
Thank you, Lucky Leavell
Well, my version of Yast is not up to speed (I'm on SUSE Pro 8.0). That said, where you see Yast recognizes the cards, there should be a button that says "Configure". Click that (after selecting a NIC) to actually configure the cards. I am, of course, assuming you need to either manually assign them IP addresses, or tell them to use DHCP. If the Yast module doesn't allow you to configure the cards, or that's not what you need, then I'll leave you in the hands of the more experienced gurus.
The scripts I am using take care of assigning the IP address but the problem is the failure to even see eth1 until after YaST does. (The process of seeing both NICs and configuring them into a bridge needs to happen at boot time without manual intervention. The only missing part is whatever YaST uses to detect the NICs. The first step in invoking YaST to configure a NIC is detecting the NICs present in the system and that is the only part I need to make it happen at boot time.) Thank you, Lucky Leavell
![](https://seccdn.libravatar.org/avatar/dcefdbf1fbe7737b010a3a806d826ae2.jpg?s=120&d=mm&r=g)
The scripts I am using take care of assigning the IP address but the problem is the failure to even see eth1 until after YaST does. (The process of seeing both NICs and configuring them into a bridge needs to happen at boot time without manual intervention. The only missing part is whatever YaST uses to detect the NICs. The first step in invoking YaST to configure a NIC is detecting the NICs present in the system and that is the only part I need to make it happen at boot time.)
It doesn't sound like the kernel module for your NIC is loading on boot. Also I'm not sure why you are using a script to load the IP address for the interface when you can configure this easily though YaST. Try disabling your script then re-configuring the card through YaST which should automatically set your system to load the required module at boot. If YaST doesn't detect the correct module for your NIC (rare) you may need to install the driver (if there is one) by hand. Jeff Why am I online reading/writing mail on a Friday night? Better check vitals... no life signs present...
participants (3)
-
Don Parris
-
Jeffrey Laramie
-
Lucky Leavell