Ok a few things. I haven’t seen a non blind friendly router in probably 5
years. Everybody lately has been playing nicely.
Next, most users do have access to this information especially on home
networks. If not then one could use something like an intermediate router that
you do have access to. They make small pocket sized devices that can grab on
to a WiFi signal and then redistribute it to your devices. It has built in NAT
and DHCP so you could easily grab what you need from your interface on the
small box.
On your Mac I’m not sure. I think this is a cool solution but haven’t
tried this myself. There is definitely in there a list of leases that you
should be able to query from dhcpd. This would be most likely accomplished via
logging in to the Mac with ssh and issuing the proper command but I don’t know
what server variant you're using to help with specifics.
Typically this type of thing is best gotten from the router as far as most
consumers go. Most do not use a Mac or intermediate home brew setup. Nothing
wrong I’m just probably stating the obvious but giving the lay of the land a
little.
On Feb 20, 2020, at 4:45 AM, Rich Morin <rdm@xxxxxxxx> wrote:
On Feb 20, 2020, at 01:11, Scott Granados <scott.granados@xxxxxxxxx> wrote:
Just log in to your router that’s handing out IP addresses, look for the Pi
in your leases and then pull the IP address from that. Should be as simple
as reading a page or the output from a command depending on what kind of
router you have and how you're setup. I assume your router for example is
your DHCP server and you’re not running your own domain controller etc.
Well, in our case the router defers to a Mac which handles DHCP allocations,
so we'd probably have to send a request to the Mac. Is there a portable,
network-based way to get this sort of information from a router and/or the
DHCP server?
Logging into the router, as you suggest, may not be an option for the user.
For example, they might be a student living in a dormitory or a client in a
coffee shop. Also, there's no guarantee that the router's administrative
interface is blind-accessible.
So far, this doesn't seem like a very general solution, but I'm certainly
willing to keep the discussion open...
-r
===========================================================
The raspberry-vi mailing list
Archives: //www.freelists.org/archives/raspberry-vi
Administrative contact: <mike.ray@xxxxxxxxxxxxxx>
-----------------------------------------------------------
Raspberry Pi and the Raspberry Pi logo are trademarks of the Raspberry Pi
Foundation.
This list is not affiliated to the Raspberry Pi Foundation and the views and
attitudes expressed by the subscribers to this list do not reflect those of
the Foundation.
Mike Ray, list creator, January 2013
