Hi folks, I've recently bought a fujitsu siemens pa2548 laptop. Vista out Suse 10.3 in. The wireless lan is switched off. The network was initialy configured with dhcp everything worked fine. But I want to use fixed ip-addresses. In the Yast network setting screen I see 2 items. 1. Fujitsu iemens Ethernetcontroller Not configured Mac ....6d:43 2. Ethernet Network Card Not configured only a BusID The number 1 ethernetcontroller can be configured with a fixed ip adress. I configure then the existing eth4 device (wich was configd by dhcp) Then I get a third entry. 3. Fujitsu iemens Ethernetcontroller with its config data Than I can ping this fixed address. Now the problem: After a reboot. In yast there is still the same config data. The system is unreachable on the fixed address. Looking in the networkmanager I see the following: 1.A new ethernetdevice eth6 ( after 10 boots it is eth16) 2.A dhcp ip adress 3.A new mac-address (changes with every boot) I can make network connections but not the way I want. Additional info: If I start the network in traditional way with ifup then nothing happens nothing is started no network. Do's anybody have an idea whats wrong ??? Whats the maximum number of the eth devices and how can I reset it ? Thanks -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
Hans defaber schreef:
Hi folks, I've recently bought a fujitsu siemens pa2548 laptop. Vista out Suse 10.3 in. The wireless lan is switched off. The network was initialy configured with dhcp everything worked fine. But I want to use fixed ip-addresses. In the Yast network setting screen I see 2 items. 1. Fujitsu iemens Ethernetcontroller Not configured Mac ....6d:43 2. Ethernet Network Card Not configured only a BusID
The number 1 ethernetcontroller can be configured with a fixed ip adress.
I configure then the existing eth4 device (wich was configd by dhcp) Then I get a third entry. 3. Fujitsu iemens Ethernetcontroller with its config data Than I can ping this fixed address.
Now the problem: After a reboot. In yast there is still the same config data. The system is unreachable on the fixed address. Looking in the networkmanager I see the following: 1.A new ethernetdevice eth6 ( after 10 boots it is eth16) 2.A dhcp ip adress 3.A new mac-address (changes with every boot)
I can make network connections but not the way I want.
Additional info: If I start the network in traditional way with ifup then nothing happens nothing is started no network.
Do's anybody have an idea whats wrong ??? Whats the maximum number of the eth devices and how can I reset it ?
Thanks
Additonal info: An extract the file 70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. # PCI device 0x10de:0x054c (forcedeth) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:00:6c:6c:2e:9a", NAME="eth0" # PCI device 0x10de:0x054c (forcedeth) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:00:6c:c0:8a:d1", NAME="eth1" . . . . . # PCI device 0x10de:0x054c (forcedeth) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:00:6c:7d:3f:45", NAME="eth24" # PCI device 0x10de:0x054c (forcedeth) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:00:6c:86:5f:99", NAME="eth25" # PCI device 0x10de:0x054c (forcedeth) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:00:6c:3b:ea:94", NAME="eth26" I this gives the direction to the source of the problem. -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
On Saturday 16 February 2008 03:44:06 pm Hans defaber wrote:
Hi folks, I've recently bought a fujitsu siemens pa2548 laptop. Vista out Suse 10.3 in. The wireless lan is switched off. The network was initialy configured with dhcp everything worked fine. But I want to use fixed ip-addresses. In the Yast network setting screen I see 2 items. 1. Fujitsu iemens Ethernetcontroller Not configured Mac ....6d:43 2. Ethernet Network Card Not configured only a BusID
The number 1 ethernetcontroller can be configured with a fixed ip adress.
I configure then the existing eth4 device (wich was configd by dhcp) Then I get a third entry. 3. Fujitsu iemens Ethernetcontroller with its config data Than I can ping this fixed address.
Now the problem: After a reboot. In yast there is still the same config data. The system is unreachable on the fixed address. Looking in the networkmanager I see the following: 1.A new ethernetdevice eth6 ( after 10 boots it is eth16) 2.A dhcp ip adress 3.A new mac-address (changes with every boot)
I can make network connections but not the way I want.
Additional info: If I start the network in traditional way with ifup then nothing happens nothing is started no network.
Do's anybody have an idea whats wrong ??? Whats the maximum number of the eth devices and how can I reset it ?
Thanks
This is probably bug in network card driver that provides random MAC address when initialized. Search our bugzilla for that (there is one open bug for that). Sorry I can't do it myself now Michal -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
This is probably bug in network card driver that provides random MAC address when initialized. Search our bugzilla for that (there is one open bug for that). Sorry I can't do it myself now
This bug : https://bugzilla.novell.com/show_bug.cgi?id=339482 Michal -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
Michal Zugec schreef:
This is probably bug in network card driver that provides random MAC address when initialized. Search our bugzilla for that (there is one open bug for that). Sorry I can't do it myself now
This bug : https://bugzilla.novell.com/show_bug.cgi?id=339482
Michal
Thank you, but I think this s something different. Some investigation (under vista with all the correct drivers) that I have a NVDIA nforce networking controller. Googeling on the internet I found he same problem many times and always related to nvida netw controllers. At the end I found this piece of text:
The nvidia MAC has for many years now for some stupid reason had it's MAC address stored in reverse order on almost all boards that use it (not sure if the documentation was confusing or what). As a result the driver has had to reverse it before using it. A few months ago some board makers decided to "fix" the problem and start storing the MAC in the correct order which of course now breaks all existing drivers that "know" the MAC address is in reverse order.
The kernel developers are aware of this and are trying to come up with a way for the driver to detect which way the address is stored and do the right thing based on it. Any solution is going to appear at earliest in 2.6.24 as far as I can tell. You can do a search of lkml (linux kernel mailing list) to get more details on it.
Maybe can anybody tell me if this is known at opensuse ? Hans -- To unsubscribe, e-mail: opensuse-networking+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-networking+help@opensuse.org
participants (2)
-
Hans defaber -
Michal Zugec