Hi! I have still problem with swaping eth0 and eth1 in SuSE 9.3 when i restart computer. I have 3com which is eth0 and i use for the Internet and D-Link which is eth1 and i don't use yet and is not connected. On each start of computer is different: once is 3com eth0 and next time eth1 but Internet works. What is wrong? Every time i must reconfigured KNemo... Thanks, Mitja
On Saturday 23 July 2005 06:50 pm, Mitja wrote:
Hi!
I have still problem with swaping eth0 and eth1 in SuSE 9.3 when i restart computer. I have 3com which is eth0 and i use for the Internet and D-Link which is eth1 and i don't use yet and is not connected. On each start of computer is different: once is 3com eth0 and next time eth1 but Internet works. What is wrong? Every time i must reconfigured KNemo...
Thanks,
Mitja
This is a known bug in 9.3. man ifrename It will allow you to set the name by mac address. -- _____________________________________ John Andersen
On Sat, 13 Aug 2005 12:13:17 +0200, you wrote:
John Andersen <jsa@pen.homeip.net> [Sat, 23 Jul 2005 19:27:30 -0800]:
This is a known bug in 9.3.
It's *not* a bug. A nuisance, yes, but not a bug.
Philipp
That's a matter of opinion - I call it a bug, and a huge one. 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.
[I *do* read the list, therefore additional private mail is unnecessary and unwanted] Michael W Cocke <cocke@catherders.com> [13 Aug 2005 11:35:28 -0400]:
That's a matter of opinion - I call it a bug, and a huge one.
Where is the bug? It has always been so that the kernel assigns network device names in the order that the devices appear. Before we used hotplugging for network devices, you could influence that by loading the drivers in a fixed order, but that didn't help you if you had multiple network cards of the same type. Use a tool like ifrename to change the names or use a persistent name in the respective if-up script if you need persistent names. Philipp
On Sun, 14 Aug 2005 17:19:29 +0200, you wrote:
[I *do* read the list, therefore additional private mail is unnecessary and unwanted]
Michael W Cocke <cocke@catherders.com> [13 Aug 2005 11:35:28 -0400]:
That's a matter of opinion - I call it a bug, and a huge one.
Where is the bug? It has always been so that the kernel assigns network device names in the order that the devices appear. Before we used hotplugging for network devices, you could influence that by loading the drivers in a fixed order, but that didn't help you if you had multiple network cards of the same type.
Just because it's always been possible to screw it up doesn't mean it's not a bug. Interface #1 should always be interface #1. Just for example, allowing the internal and external network interfaces to exchange places randomly on a firewall is either a major security hole or a networking failure looking for a place to happen - depending on your point of view. And pointing out how easy it is to work around just shows that it would have been very simple to correct the bug. 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.
On Monday 15 Aug 2005 20:22, Michael W Cocke wrote:
On Sun, 14 Aug 2005 17:19:29 +0200, you wrote:
[I *do* read the list, therefore additional private mail is unnecessary and unwanted]
Michael W Cocke <cocke@catherders.com> [13 Aug 2005 11:35:28 -0400]:
That's a matter of opinion - I call it a bug, and a huge one.
Where is the bug? It has always been so that the kernel assigns network device names in the order that the devices appear. Before we used hotplugging for network devices, you could influence that by loading the drivers in a fixed order, but that didn't help you if you had multiple network cards of the same type.
Just because it's always been possible to screw it up doesn't mean it's not a bug.
It's a valid and flexible solution a problem. Formerly, there was a "bug" which meant you couldn't change, add or rearrange the cards (network or otherwise) without potentially having your network interfaces change identities. This makes upgrading and mainenance more problematical. Now, because the adminstrator can assign the interface based on various criteria (like MAC address or text name) you can be sure that changing a card won't futz your setup.
Interface #1 should always be interface #1.
Just for example, allowing the internal and external network interfaces to exchange places randomly on a firewall is either a major security hole or a networking failure looking for a place to happen - depending on your point of view.
Indeed, but it's NOT a bug in the system, it is the admin's responsibility to use the tools correctly to ensure the security of the setup.
And pointing out how easy it is to work around just shows that it would have been very simple to correct the bug.
Just because you don't like the way it works does not make it a bug. It is the chosen and implemented method. Dylan
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.
-- "The man who strikes first admits that his ideas have given out." (Chinese Proverb)
On Monday 15 August 2005 12:46 pm, Dylan wrote:
It's a valid and flexible solution a problem. Formerly, there was a "bug" which meant you couldn't change, add or rearrange the cards (network or otherwise) without potentially having your network interfaces change identities. This makes upgrading and mainenance more problematical. Now, because the adminstrator can assign the interface based on various criteria (like MAC address or text name) you can be sure that changing a card won't futz your setup.
Wait a minute, you've got that totally backward. Previously, interfaces were constantly named, and did not change from one boot to the next. You call this a bug based on the fact that you couldn't re-arrange cards? That's bogus. If you re-arrange cards (do any physical maintenance) you expect problems. If you re-boot the machine, or have a power failure, you don't expect to have your entire network exposed to the world, and you don't expect to have to have your sysop standing there to fix this because SUSE NEVER WARNED anyone that this could happen. Had they documented it, they could call it a feature, but since they didn't its clearly a bug. Further, had they done the LEAST bit of testing in a firewall situation they would have run into this, its not something that happens RARELY. -- _____________________________________ John Andersen
participants (5)
-
Dylan -
John Andersen -
Michael W Cocke -
Mitja -
Philipp Thomas