OoO En ce début de soirée du dimanche 06 juin 2010, vers 21:45, Fabrice Lorrain <[email protected]> disait :
> After having read the documentation it is unclear what information lldpd > is sending on the wire. It is also unclear where it get its information from. > Documenting these would be appreciated (man 5 lldp ?). > I'm using lldp in a multi OS environnement... and the system name doesn't > seem to be "standardize" between Oses. Having a way (conf. file, conf. > variable) > to specify it would help. > The same goes for the SystemDescr... Providing OS + kernel version is not > always the saner choice. Having a way to choose what to send would > help. See: https://trac.luffy.cx/lldpd/ticket/19 https://trac.luffy.cx/lldpd/ticket/37 https://trac.luffy.cx/lldpd/ticket/37 And of course: https://trac.luffy.cx/lldpd/ticket/9 Moreover, recent version of lldpd does allow to set system description to your liking: https://trac.luffy.cx/lldpd/changeset/40ce835b083ccd31d34d716753e9d8aff058cfe6 System name should be the same than "hostname -f". It uses "uname -n" and asks the resolver for the full name. For example : $ uname -n neo $ getent hosts $(uname -n) 192.168.116.1 neo.luffy.cx neo This is a pretty common way to get the full system name. This is how "hostname -f" works. This usually means that you have something revelant in /etc/hosts. In recent Debian system, there is a line like this: 127.0.1.1 shortname longname The system name is one of the last thing I would have put in a configuration file because there is so many softwares that rely on this trick to get a correct hostname. -- printk("ufs_read_super: fucking Sun blows me\n"); 2.0.38 /usr/src/linux/fs/ufs/ufs_super.c
pgpYbYaSlEzJu.pgp
Description: PGP signature
