[CentOS] Php package for Microsoft-SQL -- integrated layer 2 + layer 3 name services
Bryan J. Smith <b.j.smith@ieee.org>
thebs413 at earthlink.netMon Jun 13 19:50:37 UTC 2005
- Previous message: [CentOS] Php package for Microsoft-SQL -- integrated layer 2 + layer 3 name services
- Next message: [CentOS] CentOS-announce Digest, Vol 4, Issue 6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
From: Les Mikesell <lesmikesell at gmail.com> > But if it 'knows' which of two nodes claiming a name is the correct > one, then it must have been preconfigured in a way that wouldn't > have required listening to the broadcast in the first place. How > does centralizing the service help resolve a conflict correctly? Via several options: 1. First and foremost, those naming conventions 2. Reserved MAC address for blocks of the IP subnet 3. Historical MAC address assignment of the name/IP 4. Digital signatures of the client (both BIND 9 and reverse engineered ADS-DNS) These is just some of many approaches that can _only_ be accomplished in an unified layer 2 + layer 3 server. -- Bryan J. Smith mailto:b.j.smith at ieee.org
- Previous message: [CentOS] Php package for Microsoft-SQL -- integrated layer 2 + layer 3 name services
- Next message: [CentOS] CentOS-announce Digest, Vol 4, Issue 6
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list