How do I see my DHCP clients list on my new Airport Extreme AC?

Actually..... I can't believe my eyes but I now see all DHCP clients under the "DHCP Clients" tab.

I did what "Pelicani" suggested above:

1. Started Airport Utility 5.6.1 on PC

2. Waited for the device "scan" to complete then <Alt>double-click on the Airport Extreme

3. Went to Advanced > Logs and Statistics > DHCP Clients

And there it is.... even the IP address of the system I am currently working from!

Now to try it on the MacOS side.....

OK, on MacOS Airport Utility 6.3.1 it is as Bob T. states above.... only wireless clients. How terribly short sighted of Apple to take something so rudimentary from their networking devices... oh well at least it works on the PC side..... ;-)

Thanks again to Pelicani and Bob Timmons!!!

Has anyone noticed that Aairport Utility 5.6 doesn't work on the latest version of OSX??

Does the "double-click" replace the stuff that we lost in 5.6? I am guessing not. Wonder if there is a 3rd party app out there that could help. It seems possible if the PC version has it.

Thanks a bunch for the pointer to Fing, that is a great tool! It worked for me. Shows every host (wired or wireless) on my network, allows you to scan for services on those hosts, etc. . Very handy.

WELCOME HOME 5.6.1 !! *** SOLUTION ***

Ahrg! I've been so frustrated by Apple on this. Apple took away my ability to manage our office (ALL Mac /Apple) network!!

Apple wants us to use and BE ALL ... Apple - yet takes away our ability to use it!

You want to snub your noses at Apple on this?! A simple Apple Script that makes Terminal AirPort Utility 5.6.1 work under Mavericks!

At least an immediate and very workable solution can be found at:
http://coreyjmahler.com/2013/10/24/airport-utility-5-6-1-on-os-x-10-9-mavericks/

RIGHT NOW... I'm looking at ALL my hardwired clients, including our network printers,

print severs, all our Airport Express's, mobiles and more!

It's good to see an old friend. Welcome home Airport Utility 5.6.1 !! WELCOME HOME!

And be sure to thank Corey J. Mahler who came up with the solution!

BTW - I'm using this script and Airport Utility with:

iMac 3.4ghz i7 /32gb, with the latest Mavericks version.

Thought that would be an easy solution to remember so I tried it.

Umm... yea... that didn't work.

That command didn't show anything but our gateway IP address.

Maybe it didn't work for me because I have our modem set up on the front side of our Airport Extreme in bridge mode?

However, if this command is really supposed to work - our set up is shouldn't matter because our Extreme is still handling all our network traffic.

The terminal command would querying our Airport extreme, so even though I would like this as a simple solution - it really doesn't seem to work.

Is the command missing some text? I'd use it if this would work.

FYI:

I do know the solution I posted and mentioned previously works flawlessly. You're able to use a familar Apple tool, too - Airport Utility 5.6.x, which I like better, still, than any other revisions since.

Works for me just fine. I can't possibly know all possible situations you might have on your network, however, you can read this for more help on the arp command:

http://hints.macworld.com/article.php?story=20130821063020920&query=arp+-na

Our small office network consists of a modem, server, 4 -5 switches (technically another switch -our Extreme) and even with that - I would consider it a simple network, all of which equates to only a few possible factors that 'might' affect this issue..

But regardless...I was going to say that just reiterating "it works for me" and pasting a link to a convoluted article with multiple suggested options won't show or solve anything - UNTIL... I saw someone's response at the link.

The author of the article explained that no "friendly" names would appear, meaning only the actual IP number would show in Terminal's results ( unlike in Airport Utility - shows device names) The response to the article begins by explaining why you won't see the "friendly" names,

BUT THE REAL POINT you missed - shows why this really is not an actual viable solution to see what's currently on your network.

FROM THE LINK YOU PROVIDED:

Authored by: stevebr on Aug 21, '13 10:31:53AM

It's the

-n

But the arp utility is only looking up entries in a cached table of machines yours has had some kind of connection with. This means that may see names/addresses of machines that have shut down or left the network but are still cached, and machines that yours has had no contact with may not show up at all.

Some of your other suggested methods are probably more suitable for getting an accurate list.

MEANING: To the issue and subject of this particular discussion - those who need /want to see an accurate and current list of client machines on a network - this Terminal command line is not a viable option, or really... even a solution.

I couldn't see any other IP's on our network because I haven't looked at them by any means because I'm running on a brand new Mac, so I wouldn't have any cached IP information. So that's why the command line only showed the beginning and end of our possible addresses. But this shows why this is not really an option, nor an accurate representation of what's currently on your network.

While you think this may have worked for you - most likely you're simply looking at old "cashed" data.

I'm familiar and aware of the responses in the link provided. For 99% of home users using their home computer on their home network, that command as well as several others from Terminal, will work just fine, for most situations. The command line is a powerful tool.

I'm sorry that my contribution to this thread "missed the point". I don't care for the adversarial tone of the previous comments and will therefore allow others who volunteer their time to help out. Sheesh.

For anyone finding this thread in the future, here's an example of how the arp command was able to help me find a device on my network, even though the previous poster said "it's not a viable solution".

I bought a new TiVo and wanted it setup with a static IP. It initially got a dynamic IP from the Airport. I typed the arp command and found the newest IP address ending in the dynamic range 201-255 in my setup, and bingo, there was my TiVo Mac address and IP. It was the only one in the dynamic range, so it ended with 201, so I knew that had to be the TiVo. I copied the Mac address and pasted that into Airport Utility 6 and gave it a new static IP ending in 53. This is also helpful when setting up new devices, like IP cameras.

Good luck all, and hope this helps.

Sorry you feel my reply was... "adversarial." Don't be mad at me because your post suggestion ... "really" doesn't work or not relevant to 'heart' of the topic.

On the contrary - you're accusatory comment about me.... "missing" the point" - couldn't be further from the truth. The entire reason I know about this post and contributed an actual viable, working solution myself - because at the time I was researching and looking for a solution to this issue.

I'm very familiar with Terminal and it's ability, and was excited to learn of this being a possible, easy option. And I mentioned I had in fact tried it, however, found that it was not only, not a personal option, but also through research of your own link you posted - that it really isn't a working option.

And if you have kids, you'll know even better, home networks are no longer a 99% "norm". Nowadays, our home networks can look like they qualify for corporate support. Have a family, add several iPhones, Airport Extremes & Expresses, iPads, Macs, MacBooks, iTV, and a plethora of other miscellaneous mobile devices, and before you know it - we look like we have to upgrade our tech support options.

And because this method really doesn't work in "real world" networking conditions it absolutely needs to be cautioned as such. Yes, the method "can" display IP address data,, but it's old data that your computer has seen before, already existing on your network, that may in fact changed, which then, is not the best data available, most current.

It should be known to, that Airport Utility as it stands, only sees wifi DHCP client lists and IP addresses - not wired, and the entire reason a viable and reliable "hard wired" option has been sought for. Running Apple's own Airport Utility with the previously mentioned Apple script will do what Airport Utility use to do - see ALL IP addresses, wired and wireless.

But seriously.... don't be mad at me because the method you posted doesn't work, especially where the link you gave says so as well.

The method absolutely CAN work, otherwise I wouldn't have been able to set up my TiVo's and IP cameras. Will it work in every situation? Like most things, probably not. As another poster warns, please know that at the arp command may not work in all cases! Be forewarned and be careful!! 🙂 However, just like I did, feel free to give it a try and see if it works for you in your situation. It's often easiest to try simple methods before moving on to other ideas. If it works, great. If not, try some other methods that have been suggested.

Dude, it really seems you don't understand exactly what data that command line is gathering?

I never said it didn't work! Did you completely miss the part of my last post where I said - it "can" work?

I am NOT saying you can't get a list of IP addresses using arp. Do you want me to say it again in black and white?

YOU CAN. THERE!! I said it. I'm just saying you can't get a completely reliable list.

Despite how loud you yell - aint going to change the fact that the terminal arp command method only produces and shows basically, OLD data - or nothing at all as in my situation using a new mac. But whenever I need to find IP addresses it's because I need to know accurate info at that moment - not later.

You're right - the method "may" or "may not" work for someone, but according to your own link - the data gained from this specific terminal method within many cases - will not be accurate in any one specific time will not be accurate, or possibly completely incorrect. One iPhone away from your network for the day, and by using arp - and your data is incorrect.

So if someone has time to waste and an inkling to do extra, unnecessary trouble shooting in order to simply obtain potentially, unreliable, outdated IP addresses, some of which may not even still exist on your network at all ?? Then by all means - use the arp method.

BUT YES... the arp method ALONE, without any other extra trouble shooting will "work" to produce... "a list" of IP addresses.

Accuracy and reliability... optional.

arp command worked for me. On Yosemite, I filtered it further with a grep:

arp -na | grep -v '(incomplete)'

Then just looked for first instances of unique (MAC address?) lines. I was able to locate my hardwired device relatively quickly. Yes,the data might be dated, but worked none the less. In the face of no other useful or easy suggestion, this worked swell. Thanks tobylaura for the USEFUL reply!

:-)

Awesome, hooray! Exactly - it works, I said that.

But I stand correct regarding this method & the caution in using it.

*** C A U T I O N ***

This method works only if a client machine has previously scanned and seen the network, and even then, data obtained may still not be accurate. Further, this method can provide an inaccurate "false-positive.".

* Example: your looking for your Ethernet, network printer, but it powered off or died. This method will still show the printer. I don't think that's very useful.

* Example: If you put a new Mac on a network, as we did, and this method won't work as this method relies on previous data that may not exist. A new mac wnot see anything but the gateway IP and the last IP.

It works... sort of. Useful? That's questionable. Definitely not accurate.