th-lists at lf
Apr 8, 2011, 2:25 AM
Views: 229
Permalink
|
|
Multiple independent OSPF areas in on ethernet segment?
|
|
Hi,
I've found a quagga (0.99.10) instance continously logging the
following event:
OSPF: interface bond1:192.168.160.3: ospf_read invalid Area ID 192.168.160.42.
During my search for the source of this event I've discovered the
following network topology which causes this type of log entries:
quagga1 quagga2 } OSPF Area 192.168.160.0
192.168.160.3 192.168.160.4
| |
------+-------+-------+-------+------- } switched ethernet segment
| |
192.168.160.42 192.168.160.43
dialup router1 dialup router2 } OSPF Area 192.168.160.42
- The two quagga routers are running OSPF with the area id
192.168.160.0.
- The two dialup routers are running OSPF with the area id
192.168.160.42.
- These two OSPF areas are running indenpent from each other but they
share one ethernet segment and they use the same ip range
192.168.160.0/24.
After reading RFC1583 and other documentation I'm still unsure if this
type of OSPF setup is supported/allowed. So my questions are:
Does OSPFv2 allow multiple independent OSPF areas on one ethernet
segment?
Shouldn't quagga ignore OSPF packets from OSPF area 192.168.160.42
when not configured for area 192.168.160.42?
--
Gruss / Best regards | LF.net GmbH | fon +49 711 90074-414
Thorsten Huber | Ruppmannstrasse 27 | fax +49 711 90074-33
th [at] LF | D-70565 Stuttgart | http://www.lf.net
Handelsregister Stuttgart: HRB 18 189
Geschaeftsfuehrer: Norman Fuerst, Rodney Volz
_______________________________________________
Quagga-users mailing list
Quagga-users [at] lists
http://lists.quagga.net/mailman/listinfo/quagga-users
|
Multiple independent OSPF areas in on ethernet segment?