-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/21/2011 12:20 PM, Juliusz Chroboczek wrote:
I am sorry this reply has been so delayed, work has been rough lately. > Oh yeah, there should be no problem in a layer 2 mesh, if the mesh > implements broadcast (or hacks in some ad hoc smarts related to DHCP). > AHCP is only needed in a layer 3 mesh. We also have a solution worked out for layer 3 meshes. We will be using DHCP to configure clients, and our control panel application can pseudo-randomly choose RFC-1918 IP addresses for mesh interfaces if the user selects it. AHCP is still an option for configuring other mesh nodes, we have not yet implemented that. - -- The Doctor [412/724/301/703] PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1 WWW: http://drwho.virtadpt.net/ "Take back, take back, take back the dancefloor!" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5AM2cACgkQO9j/K4B7F8ERngCePSd8L2smWq5phMwX3ryy8ZFV j9AAnjcCwcJuq+kcfOlyb8caXYLlUupn =/kkF -----END PGP SIGNATURE----- _______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
