CUPS 1.6 shaking up Linux printing
Posted Mar 11, 2012 5:01 UTC (Sun) by khim
In reply to: CUPS 1.6 shaking up Linux printing
Parent article: CUPS 1.6 shaking up Linux printing
>auto-discovery has the problem that if any node is mis-configured (either accidentally or deliberately), it can break the entire network.
How? Autodiscovery mechanism generally work by flooding the network with broadcast/multicast updates.
A misconfigured node should just be silently ignored.
Only if you disable autodiscovery (how else can you prevent flood organized by misconfigured node from affection configuration of the rest of the network) - but then what's the point of the whole exercise?
I assume you're not talking about DHCP/RA.
Actually DHCP is not any different: if a single node hogs all available IPs from a DHCP pool then other nodes will be unusable.
All autodiscovery mechanisms have this problems - and DHCP is not an exception. It also shows that on practice problems are rare: sure, DHCP autodiscovery may fail too and it even happens from time to time but if you'll consider how ubiquitous it is and how rare are such failures… I think we should not fear autodiscovery mechanisms all that much. 99% of users use [limited] version of autodiscovery with TCP/IP and sky have not fallen so why can't we use somewhat more advanced version and get the convenience offered by proprietary networks 20 years ago?
to post comments)