Some ideas
You could consider using IPv6 which was designed to operate over vast and barren address spaces.
To work by name instead of address, DNS, netbios and mDNS are 3 popular name resolution services likely present on most network hosts.
mDNS also includes DNS-SD, which is a service discovery protocol using the equivalent of TXT records in unicast DNS. Android won’t like it, but anybody else would.
If you prefer rolling your own protocol, communicating over a dedicated multicast address is less intrusive than broadcasting.
Finally, the expected behavior of a DHCP server is to lease back the same address to the same host, as much as possible. So in theory, the machine could enter client mode, record the IP address it obtains on the LAN, and later display it once in AP mode.
Should work as long as the DHCP server behaves and its address pool doesn’t run dry. Quite sketchy though.
You could consider using IPv6 which was designed to operate over vast and barren address spaces.
To work by name instead of address, DNS, netbios and mDNS are 3 popular name resolution services likely present on most network hosts.
mDNS also includes DNS-SD, which is a service discovery protocol using the equivalent of TXT records in unicast DNS. Android won’t like it, but anybody else would.
If you prefer rolling your own protocol, communicating over a dedicated multicast address is less intrusive than broadcasting.
Finally, the expected behavior of a DHCP server is to lease back the same address to the same host, as much as possible. So in theory, the machine could enter client mode, record the IP address it obtains on the LAN, and later display it once in AP mode.
Should work as long as the DHCP server behaves and its address pool doesn’t run dry. Quite sketchy though.
Statistics: Posted by epoch1970 — Sat Feb 03, 2024 10:27 pm