1 |
Grant Edwards <grant.b.edwards@×××××.com> writes: |
2 |
|
3 |
[...] |
4 |
|
5 |
>> But when you do it that way, and say want to VNC or ssh or the like to |
6 |
>> something connected by a dhcp serving WAP then how do you find the |
7 |
>> address? |
8 |
> |
9 |
> The best thing to do is to use a DHCP server and DNS server that are |
10 |
> "connected" somehow. Then hostnames "just work". Or you can |
11 |
> statically assign IP addresses in the DHCP server so that DHCP clients |
12 |
> always get hard-wired IP addresses that match up with the /etc/hosts |
13 |
> file on the DNS server. |
14 |
> |
15 |
> I use OpenWRT for WAP, DNS, and DHCP, and it all pretty much "just |
16 |
> works". When a DHCP client is assigned an IP address, the DNS server |
17 |
> knows about it and you can access it by it's hostname just the way you |
18 |
> would with a static setup. |
19 |
> |
20 |
> For various reasons, I assign static IP addresses to a number of |
21 |
> devices, but I do it via the DHCP server's configuration, not by |
22 |
> configuring each individual device. |
23 |
|
24 |
That sounds like a good plan... and worth some thought. However I was |
25 |
only asking to find IPs on the home lan after the fact. Not the |
26 |
general question of how to setup the lan (though I welcome the ideas |
27 |
you present). |
28 |
|
29 |
I seem to have latched onto a tool by a bit more googling, and getting |
30 |
lucky, called netdiscover that is in portage now. |
31 |
|
32 |
Just one simple command found all machines active on the home lan |
33 |
including those with DHCP served addresses: |
34 |
|
35 |
netdiscover -i eth0 <ENTER> |
36 |
|
37 |
Oddly a similar command but aimed at a range misses a few: |
38 |
|
39 |
netdiscover -i eth0 -r 192.168.0.0/24 <ENTER> |
40 |
|
41 |
I guess the tool may use some heuristics if you give it less info. |
42 |
|
43 |
And for one reason or another a plain `arp' command misses several of |
44 |
those discovered with `netdiscover -i eth0' |
45 |
|
46 |
So I found what I needed... thanks. |