Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Possible solution</strong> (or kludge should I say).<br> The only way I can see of achieving this is to extend the network mask to 255.255.0.0 (class B network mask) for all the linuxpc boxes.<br> You will have to do that, however, on the DHCP server, in the same way you configure that linuxpc1 eth0 mac address will be assigned ip address 192.168.0.101.<br> This means merging all your Class C private sub-networks into a single class B chunk.</p> <p><strong>Detail</strong><br> Otherwise, I don't think you can do that with avahi straight out of the box. Here is why. </p> <p>Avahi uses mDNS to publicize hostnames.</p> <p><strong>In detail, things work like this:</strong><br> As part of it's processing logic, your linuxpc3's avahi daemon will send a DNS UDP datagram on port 5353 (?) on ip address 224.0.0.51.<br> This address is one of the multicast addresses reserved for zeroconf (see <a href="http://www.iana.org/assignments/multicast-addresses/multicast-addresses.xml" rel="nofollow">iana multicast addresses</a>). </p> <p>Assuming linuxpc3 address is 192.168.2.103 (following your naming convention), and assuming a standard class C network mask of 255.255.255.0, then only those boxes with addresses between 192.168.2.1 and 192.168.2.254 will receive the corresponding dns A update record (by which I mean the other avahi/bonjour daemons running in these boxes). </p> <p>As a result, neither linuxpc1 nor linuxpc2 will be made aware of the linuxpc3.local hostname/address pair.</p> <p>If instead the network mask of all these boxes is extended to 255.255.0.0 then the broadcast range will be extended to include all addresses in the 192.168/16 network.</p> <p><a href="http://tools.ietf.org/html/rfc1918" rel="nofollow">RFC1918</a>, the standard for <a href="http://en.wikipedia.org/wiki/Private_network" rel="nofollow">private networks</a> explicitly allows the 192.168.0.0 block to be configured as a single class B subnetwork.</p> <p><strong>Update</strong><br> Having seen your comments.</p> <p>First conclusion. Avahi has no solution for your combination of requirements.<br> Avahi relies on subnetwork broadcast.</p> <p>In a similar context in which avahi was not applicable either, I once resorted to automate the update of /etc/hosts files and DNS records through the detection of connection events changes. </p> <p>All PCs could see the internet and were detecting conection changes (Linux in <a href="http://linux.die.net/man/1/networkmanagerdispatcher" rel="nofollow">NetworkManager dispatcher hooks</a> - Windows through subscription to the <a href="http://msdn.microsoft.com/en-us/magazine/cc301850.aspx" rel="nofollow">System Event Notification Service</a>). </p> <p>All machines were reporting their connectivity status and ip addresses through messages in www.dropbox.com and were getting their updates from their respective local dropbox folder. </p> <p>If you want to implement this in stead, or a similar solution, I have to warn you this is quite a bit of work.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload