On Thu, 28 Apr 2005 10:08:52 -0500, you wrote:
On Thursday 28 April 2005 9:40 am, Michael W Cocke wrote:
Ok - THIS is a bug in 9.3, thru and thru. Not a bug. What you need to setup is known as 'persistent name' and is not SUSE specific. This happens in other distros also.
Practically every time my system boots (not often, but still) eth0 and eth1 exchange their hardware assignments. Since one is connected to the internet and the other to my intranet, this is a problem!
After talking to some people on another list, I hear that SuSE knew about this during the beta and didn't fix it! Didn't they think anyone would want to run a firewall on 9.3? If you check the list archives you'll find this has been known for far longer than that. I've changed my system even though it hasn't exhibited this behavior but I don't want it to either.
I've got part of a workaround (Thanks John Sivak) Search the archives for 'persistent name' or PERSISTENT_NAME and you'll get the answer: add it to /etc/sysconfig/network/ifcfg-eth-id-[mac address] and re-do any firewall info that relies on them, then restart network or reboot. DO NOT name them eth0, eth1, etc because it will NOT work. Call them external, internal, internet, intranet, fred, wilma, whatever.
Mike-
Stan
Interesting - I've been using Suse on my firewall since 9.1 and I never encountered this problem before, nor did I have it with Redhat before that. Not saying you're not right, but that's a hell of a chain of cooincidences! Anyway, for the record, I figured out what I was missing and it works now. I did it differently. Mike- -- Mornings: Evolution in action. Only the grumpy will survive. -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments.