Hello You say about replacing in bird or bird6 ?
if in bird6 than it does not help in my case, because router id is also the same as ip`s: Router ID Pri State DTime Interface Router IP 1.1.1.1 1 full/ptp 00:30 ng1 fe80::224:1dff:feb3:720 1.1.1.1 1 full/ptp 00:29 ng2 fe80::224:1dff:feb3:720 1.1.1.1 1 full/ptp 00:30 ng0 fe80::224:1dff:feb3:720 Thanks for your reply Ondrej. i don`t know "c" code as good as you, easier to say i don`t know "c" at all. you are you're talking about this string in bgp.c ? log(L_ERR "%s: Invalid remote address %I%J", p->p.name, cf->remote_ip, cf->iface); It is doubtful that I can by myself make patch proto/ospf/neighbor.c for right use of cf->iface in neigh_chstate() function. With best regards, Dmitry S. Nikolaev Moscow, Russia phone: +7 (499) 678 8007 [ext. 6003] fax: +7 (499) 678 8007 [ext. 7777] www: http://www.mega-net.ru mail: dnikol...@mega-net.ru On 07.12.2013 02:48, Ondrej Zajicek wrote: > Hello > > Although adding an iface scope to link-local addresses helps a bit, > link-local addresses are still confusing when there are many neighbors > on one iface. > > I am thinking about replacing IPs with router IDs as a primary neighbor > description in most OSPF log messages. Any comments/opinions to such > change? > > > BTW, you can use '%J' as a shorthand for %iface > (see e.g. bgp_start_locked() in proto/bgp/bgp.c). >