Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
05-28-2004, 11:23 PM
|
#1
|
LQ Newbie
Registered: May 2004
Location: Indianapolis, IN
Distribution: RedHat 9
Posts: 2
Rep:
|
"Error, some other host already uses address XXX.XXX.XXX.XXX"
Hello,
I am building a RedHat 9 box. I have configured the IP information however, on boot I receive the error message "Error, some other host already uses address 192.168.1.2" (Note: Not real address but should do for troubleshooting purposes)
If I log in and do the following commands, the network works fine:
ifconfig eth0 192.168.1.2 netmask 255.255.255.0 up
route add default gw 192.168.1.1
I have checked my dns servers and cannot find the address being used. If I ping the address, I do not get a reply.
Any ideas? Also, what other information would be helpful for troubleshooting purposes?
mwbb_support
|
|
|
05-29-2004, 06:08 PM
|
#2
|
LQ Newbie
Registered: May 2004
Location: Indianapolis, IN
Distribution: RedHat 9
Posts: 2
Original Poster
Rep:
|
Ok, I found the problem.
It seems that our firewall system "grabs" the entire subnet so that rogue machines cannot be either placed on the subnet without authorization or spoof themselves as one of ours.
Apparently, the firewall system detects the new machine then checks its list of authorized machines. Since my machine was not on the list, it essentially gets a DoS attack from the firewall system.
Pretty clever.
Anyway, I tried the machine on another subnet that the firewall system does not guard and it works great.
As to what type of firewall system we are using, I cannot say for security purposes however; I will say that it is open source.
mwbb_support
|
|
|
04-11-2007, 09:24 PM
|
#3
|
LQ Newbie
Registered: Apr 2007
Posts: 6
Rep:
|
Quote:
Originally Posted by mwbb_support
Ok, I found the problem.
It seems that our firewall system "grabs" the entire subnet so that rogue machines cannot be either placed on the subnet without authorization or spoof themselves as one of ours.
Apparently, the firewall system detects the new machine then checks its list of authorized machines. Since my machine was not on the list, it essentially gets a DoS attack from the firewall system.
Pretty clever.
Anyway, I tried the machine on another subnet that the firewall system does not guard and it works great.
As to what type of firewall system we are using, I cannot say for security purposes however; I will say that it is open source.
mwbb_support
|
I am having the exact same problem. Can you please give me some help? I am using 192.168.1.1 as my subnet. Should I change to 10.1.1.1 or something? Thanks. When I use DHCP, I dont have the problem. But I do need a static IP so I can forward the port out. I am just using a linksys wireless router by the way. This problem never happen on Windows.
Last edited by sfo_sc; 04-11-2007 at 09:32 PM.
|
|
|
04-30-2009, 08:09 AM
|
#4
|
LQ Newbie
Registered: Feb 2009
Posts: 1
Rep:
|
Error, some other host already uses address
I am also facing this same problem. But there is no firewall in our network. I checked in the network, none of the devices are using the IP. I changed the IP address and it started working.Previously also the same problem happened. If I log in and do the following commands, the network works fine:
ifconfig eth0 192.168.1.2 netmask 255.255.255.0 up
route add default gw 192.168.1.1
If i restart the network service then i will get the error
Error, some other host already uses address 192.168.1.2. If configure the IP using the above method it will work.
Can anyone please help me to resolve the issue.
|
|
|
11-15-2010, 01:03 AM
|
#5
|
LQ Newbie
Registered: Nov 2010
Posts: 1
Rep:
|
Resolved: "Error, some other host already uses address XXX.XXX.XXX.XXX"
I was receving this error on my CentOS 5 which I was running through VMWare. I resolved this error by deleting the Network Adapter from VMWare GUI and reinstalled the Network Adapter.
-- Aamir Hirani --
|
|
|
01-20-2014, 09:59 AM
|
#6
|
LQ Newbie
Registered: Jan 2014
Posts: 1
Rep:
|
Fix for CentOS 6.4
For me on CentOS, every time I tried ifup eth0 it would say: "Error, some other host already uses address 192.168.X.X" (even though no other host had that IP address).
The quick & dirty fix was editing /etc/sysconfig/network-scripts/ifcfg-eth0 and commenting out the following lines:
#HWADDR
#UUID
#USERCTL
And setting NM_CONTROLLED=no
After that, the interface came up just fine using ifup eth0.
|
|
|
All times are GMT -5. The time now is 06:45 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|