Malingering eth devices

[DThor]

We have a dual NIC system with SUSE 10.2 on it, the motherboard died, so that was replaced and when restarted by default the system assigned eth3 to the new primary NIC. That would be OK, except we want to run FlexLM on this system, which has a restriction that it *must* talk to eth0 only to get the licensing host ID. What happens when requested is that it comes back with 'host id is "" ', which makes sense because for some reason SUSE thinks the old devices are there, but the response is nothing.

ifconfig returns:

eth3      Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX
          inet addr:XXX.XXX.XXX.XXX  Bcast:XXX.XXX.XXX.XXX  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5245606 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4977750 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3177091168 (3029.9 Mb)  TX bytes:4683069106 (4466.1 Mb)
          Base address:0xd000 Memory:fca80000-fcaa0000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:7920 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7920 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:636015 (621.1 Kb)  TX bytes:636015 (621.1 Kb)

with some XX's in there cuz I'm paranoid.

So SUSE doesn't seem to acknowledge the old NICs are configured, when you run the Yast configuration tools, it simply doesn't offer up eth0 and eth1 as options. I've grepped around for config files containing those entries and can't find them. I can't figure out where this piece of information is being stored.

Any suggestions, thoughts? I need to be able to get the new NIC configured as eth0.

Thanks,

DT

[gogalthorp]

Check this thread

http://www.linuxforums.org/forum/sus...ethx-ethy.html

[DThor]

Looks like that's it - thanks!

DT