Question (about an IP address warning)

[frenchbluehour]

Hi,

I opened my MacBook earlier and connected to WiFi and a warning box appeared!

Advising that another device was using my IP address.
There was also other info about it resetting my IP address if required!

Is this something to be concerned about? :shrug:

[Octane]

Hey Nic!

It just means one of your iDevices has taken over the IP address that your MacBook had. It's nothing to worry about. :)

H

[killswitch]

One of the devices in your network likely has a static IP set and its creating a conflict with the IP address that DHCP gave your Macbook.

[04Stefan07]

You should be able to do similar commands in iOS like in Windows (release and renew through ipconfig).

[dannat]

Open network pref's
click on advanced (under WiFi)
in the TCp/IP tab click renew lease

as others have said its not a problem

[acropolite]

Tell that to the people who have to endure network crashes from this iQuirk.

Ios devices have a nasty habit of resuming leases that have long expired, I've seen the problem on several sites.

The best answer is to make static dhcp assignments, if possible, for any idevices operating on your network.

Here is one explanation of the problem, although I have to disagree with the author who claims the problem only happens when the device goes in to lock screen mode, I've seen cases where idevices crash the network as soon as they re-connect to a previously utilised wifi network after being off site for some time. http://www.simonblog.com/2010/04/24/ipads-dhcp-flaws-and-possible-workarounds/

[Tandum]

Mac is just an enhanced version of BSD unix so something like dhclient eth0 will reset the client. ifconfig will tell you the interface name.

[Camelopardalis]

Network crashes? Seriously :screwy:

If your equipment does this, you need to start using more robust equipment. I've worked with computers and networks all my life and never had a "network" crash because two devices wasted cycles fighting over an IP address...

[el_draco]

Absolutely.... You have a Mac..:lol::D.

[Steffen]

That is correct, well observed.

A Mac, which can normally be expected to be working without problems, would be affected insofar as networking will not function reliably.

If it was a Windows PC it would not matter either way, you wouldn't be able to tell the difference ;)

Cheers
Steffen.

[el_draco]

Precisely.... A consistent response. Always preferable :rofl::rofl:

[acropolite]

yes crashes, I've seen it on quite a few sites, we usually get called in to "check the cabling" usually to find the switch locked up with packet collision problems. Not everyone has high end gear, nor do they need it. You may be right in assuming it's associated with budget switches though. Equipment aside, there's no excuse for this particular iBug. I've seen quite a few network crashes due to Ip conflict, one we chased for months until we found the IT maintainers had forgotten to exclude a couple of Static assignments from their DHCP table (despite them supplying the static assignment after being given the mac of the PABX) and had assigned a printer on the same ip as our PABX voip traffic. The resultant conflict brought down the entire remote network, bridged radio link and voip traffic. I only found the problem by doing a network scan and finding a different mac address responding on the IP to what was expected.

[Camelopardalis]

I'm not defending the iBug specifically, but if a network switch is crashing because of a few packet collisions then the switch is not adhering to countless networking specs, and it doesn't need to be high end kit these days to be solid and reliable. Cheap tat on the other hand...there's no excuse for IT deploying that either ;)