Allows to add more interface patterns to one common 'options'
section like:
interface "eth3", "eth4" { options common to eth3 and eth4 };
Also removes undocumented and unnecessary ability to specify
more interface patterns with different 'options' sections:
interface "eth3" { options ... }, "eth4" { options ... };
values for MD5 password ID changed during reconfigure, Second
bug is that BIRD chooses password in first-fit manner, but RFC
says that it should use the one with the latest generate-from.
It also modifies the syntax for multiple passwords.
Now it is possible to just add more 'password' statements
to the interface section and it is not needed to use
'passwords' section. Old syntax can be used too.
Bad as when bird e.g. was running for two weeks and then restarted it
would take another two weeks until the peers of this router would accept
data again from this router, as the sequence number would be too low.
Changed to use the the current system time as the starting sequence
number which is a more sane start value.
(by Andreas, cleaned up by me)
equal to a local address, just ignore the route (as it is usually just an
external route exported by us echoed by some RIP peer), when given an
invalid next hop, moan to the log.
o Use FIB_ITERATE_INIT instead of calling the function fit_init()
which is explictly marked as private in route.h.
o When printing trace messages, don't spit out protocol name twice.
o Some messages are a bit more verbose.
o Added a bunch of FIXME's.
o When running in broadcast mode, don't forget to bind the local
end of the socket to the same broadcast address, so that we don't
get the broadcasts looped back via different interface. I'm just
going to look up the same problem for multicasts.
