OSPF: Cannot find next hop for LSA type

Hi, Recenly I occasionally found that one can define the OSPF area twice, like area 0.0.0.1 { interface "eth0"; } area 0.0.0.1 { interface "eth1"; } And this obviously erroneous configuration passes the bird configuration check, and starts causing unpredictable and wierd problems, including the one mentioned in subject. Since bird doesn't seem to have a bug tracker, this list seems to be an appropriate place to report this. Thanks. Eugene.