Unable to assign IP address to interface
Hi If my memory serves me correct this was covered in the last month on this group but I am unable to find it in the archives. I have two industrial single board computers with two onboard LAN cards each. Both are running SuSE 9.3 One machine is assigned a static IP (192.168.100.102) using yast. When entering the IP yast tells me that it detected a duplicate IP address. The IP is not used on our network and even with the flylead plugged out I still get the message. Yast gives me the option of continuing even though it believes the IP is duplicate. I saved the settings, quit yast and ran ifconfig. The interface didn’t show. I then ran: # ifconfig eth0 192.168.100.102 SIOCSIFFLAGS: Resource temporarily unavailable # ifup eth0 eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03) eth0 configuration: eth-id-... SIOCSIFFLAGS: Resource temporarily unavailable ERROR: Cannot enable interface eth0. ERROR: interface eth0 is not up /etc/sysconfig/network/ifcfg-eth-id-... contains the correct configuration for this card. I have disabled the second NIC and it still has the same problem. The other machine is working without a problem. Any ideas? Albert -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.14/128 - Release Date: 2005/10/10
Albert wrote:
I have two industrial single board computers with two onboard LAN cards each. Both are running SuSE 9.3
One machine is assigned a static IP (192.168.100.102) using yast. When entering the IP yast tells me that it detected a duplicate IP address.
The IP is not used on our network and even with the flylead plugged out I still get the message.
Yast gives me the option of continuing even though it believes the IP is duplicate. I saved the settings, quit yast and ran ifconfig. The interface didn’t show.
I then ran:
# ifconfig eth0 192.168.100.102 SIOCSIFFLAGS: Resource temporarily unavailable # ifup eth0 eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03) eth0 configuration: eth-id-... SIOCSIFFLAGS: Resource temporarily unavailable ERROR: Cannot enable interface eth0. ERROR: interface eth0 is not up
/etc/sysconfig/network/ifcfg-eth-id-... contains the correct configuration for this card.
I have disabled the second NIC and it still has the same problem.
The other machine is working without a problem.
I have now reinstalled SuSE 9.3 on the faulty machine and I still have the same issue. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.14/129 - Release Date: 2005/10/11
Albert wrote:
Albert wrote:
I have two industrial single board computers with two onboard LAN cards each. Both are running SuSE 9.3
One machine is assigned a static IP (192.168.100.102) using yast. When entering the IP yast tells me that it detected a duplicate IP address.
The IP is not used on our network and even with the flylead plugged out I still get the message.
Yast gives me the option of continuing even though it believes the IP is duplicate. I saved the settings, quit yast and ran ifconfig. The interface didn’t show.
I then ran:
# ifconfig eth0 192.168.100.102 SIOCSIFFLAGS: Resource temporarily unavailable # ifup eth0 eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03) eth0 configuration: eth-id-... SIOCSIFFLAGS: Resource temporarily unavailable ERROR: Cannot enable interface eth0. ERROR: interface eth0 is not up
/etc/sysconfig/network/ifcfg-eth-id-... contains the correct configuration for this card.
I have disabled the second NIC and it still has the same problem.
The other machine is working without a problem.
I have now reinstalled SuSE 9.3 on the faulty machine and I still have the same issue.
If both NIC's are the same, they would share the same module (eepro100 I think) without problems. Check the second NIC isn't also configured with the same IP address, YaST is probably seeing this. Also check dmesg and /var/log/messages for possible errors. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
On Wednesday 12 October 2005 04:13, Albert wrote:
Albert wrote:
I have two industrial single board computers with two onboard LAN cards each. Both are running SuSE 9.3
One machine is assigned a static IP (192.168.100.102) using yast. When entering the IP yast tells me that it detected a duplicate IP address.
The IP is not used on our network and even with the flylead plugged out I still get the message.
Yast gives me the option of continuing even though it believes the IP is duplicate. I saved the settings, quit yast and ran ifconfig. The interface didn’t show.
I then ran:
# ifconfig eth0 192.168.100.102 SIOCSIFFLAGS: Resource temporarily unavailable # ifup eth0 eth0 device: Intel Corporation 82801BA/BAM/CA/CAM Ethernet Controller (rev 03) eth0 configuration: eth-id-... SIOCSIFFLAGS: Resource temporarily unavailable ERROR: Cannot enable interface eth0. ERROR: interface eth0 is not up
/etc/sysconfig/network/ifcfg-eth-id-... contains the correct configuration for this card.
I have disabled the second NIC and it still has the same problem.
The other machine is working without a problem.
I have now reinstalled SuSE 9.3 on the faulty machine and I still have the same issue.
I did the same thing: reinstall, thinking it was something with the system. There is a lot of reference on this subject out there, but all points to BIOS assigning problem IRQ to device. I finally wound up fixing mine by restoring factory defaults in BIOS. Hope this helps! Bernd -- "If you want to build a ship, don't drum up the men to gather wood, divide the work, and give orders. Instead, teach them to yearn for the vast and endless sea." Antoine de St. Exupery
participants (3)
-
Albert -
Bernd -
Sid Boyce