1 |
Am 25.05.2011 21:45, schrieb Harry Putnam: |
2 |
> There must be a number of people who post here that have had to do |
3 |
> this problem. |
4 |
> |
5 |
> Discover the addresses of computers on a home network that have |
6 |
> connected by way of DHCP. For example: Several wireless connections. |
7 |
> |
8 |
> I've used static IPS for around 10 yrs, always seemed handier for |
9 |
> things like ssh between home lan computers. |
10 |
> |
11 |
> But recently started using DHCP for wireless connections. It must be |
12 |
> such a popular method for some reason. |
13 |
> |
14 |
> But when you do it that way, and say want to VNC or ssh or the like to |
15 |
> something connected by a dhcp serving WAP then how do you find the |
16 |
> address? |
17 |
> |
18 |
> That is, besides something like accessing the WAP and checking the IPs |
19 |
> connected to it. |
20 |
> |
21 |
> Is there some quick and sure way to discover any IPs on the home lan? |
22 |
> |
23 |
> Some kind of mapper tool? |
24 |
> |
25 |
> |
26 |
|
27 |
While I personally prefer a combined DHCP+DNS server like dnsmasq, you |
28 |
can also take a look at the whole Zeroconf/MDNS/Avahi/Bonjour stack. |
29 |
|
30 |
I'm not really sure if you can configure common devices and Linux PCs to |
31 |
use the DNS server for internet addresses and MDNS for local ones. In |
32 |
theory, it should be possible since you can distinguish them (local |
33 |
addresses should not be fully qualified _or_ have the domain .local). |
34 |
|
35 |
net-misc/mDNSResponder, sys-auth/nss-mdns and net-dns/avahi are probably |
36 |
good starting points. |
37 |
|
38 |
Hope this helps, |
39 |
Florian Philipp |