"Paul Adare" <[EMAIL PROTECTED]> writes: > So not exactly the same. As I said, even though the message says that > bringing up the interfaces fails, they are actually being brought up. I > don't need to manually bring them up at all.
I suspect it's a mii-tool issue. What it is the result if this command ? In this case you should set MII_NOT_SUPPORTED to yes in the /etc/sysconfig/network-scripts/ifcfg-eth(0 and 1) files ... and fire service network restart to check it again .. my 2 cts, > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Diego > Morato > Sent: Friday, January 07, 2005 10:29 AM > To: [email protected] > Subject: Re: [Security Firewall] Bringing Up Interfaces FAILED (MNF 2.0) > > With me happens the same. I initialize the interfaces manually via ifup > ethX. > > > On Sex, Janeiro 7, 2005 12:55 pm, Paul Adare disse: > > During the boot process, I'm getting the messages that both eth0 (LAN) > > and eth1 (WAN) failed when attempting to bring them up. However, when > I > > check with ifconfig after logging in, they are both actually up, and > > shorewall starts and seems to work perfectly well. Any ideas? In the > > interest of full disclosure here, I'm running the beta of MNF 2.0 > (with > > no updates from Florin's site yet) in a Virtual Server 2005 virtual > > machine. > > > > > > > > Thanks! > > > > > > > > Paul Adare > > > > > > -- Florin http://www.mandrakesoft.com http://people.mandrakesoft.com/~florin/
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
