Balance One is connected to two hubs - Primary (costs 10) and DR (costs 20).
If I reboot the Primary hub, PepVPN-Status shows: Route Conflict.
The goal is to have a hub-redundancy.
Can you give me a hint, what happens? The tunnel that shows “route conflicts” does handle traffic!
I think, I have a problem with OSPF.
The only thing, I have changed is: I added the LAN-interface to Area 0.0.0.0, as on the LAN-Interface, there is a second router that need to know the OSPF-routes of the two Peplink-Hubs (Balance 710).
Usually ‘Route Conflict’ means that two routers have the same IP address range or overlapping IP ranges. Please check your DHCP Settings to make sure that the routers aren’t overlapping.
DHCP is not activated, but my two “head-quarter balance 710” have both one leg in the same network and are both connected to the branch-office-balance-one.
We are still investigating this issue, and have sent an update to the Peplink Distributor who logged a ticket with support. Can you share what learned routes the Fortigate has learned?
fg200e_HZ_1_1 (root) # get router info ospf database router adv-router 10.9.49.2
Router Link States (Area 0.0.0.0)
LS age: 1556
Options: 0x2 (*|-|-|-|-|-|E|-)
Flags: 0x2 : ASBR
LS Type: router-LSA
Link State ID: 10.9.49.2
Advertising Router: 10.9.49.2
LS Seq Number: 8000027c
Checksum: 0x57d3
Length: 48
Number of Links: 2
Link connected to: a Transit Network
(Link ID) Designated Router address: 10.9.49.3
(Link Data) Router Interface address: 10.9.49.2
Number of TOS metrics: 0
TOS 0 Metric: 10
Link connected to: another Router (point-to-point)
(Link ID) Neighboring Router ID: 10.10.248.1
(Link Data) Router Interface address: 5.192.104.49
Number of TOS metrics: 0
TOS 0 Metric: 10
fg200e_HZ_1_1 (root) # get router info ospf database router adv-router 10.9.49.3
Router Link States (Area 0.0.0.0)
LS age: 7
Options: 0x2 (*|-|-|-|-|-|E|-)
Flags: 0x2 : ASBR
LS Type: router-LSA
Link State ID: 10.9.49.3
Advertising Router: 10.9.49.3
LS Seq Number: 800006fd
Checksum: 0xb317
Length: 36
Number of Links: 1
Link connected to: another Router (point-to-point)
(Link ID) Neighboring Router ID: 10.10.248.1
(Link Data) Router Interface address: 5.192.3.177
Number of TOS metrics: 0
TOS 0 Metric: 110
fg200e_HZ_1_1 (root) # get router info ospf neighbor all
OSPF process 0:
Neighbor ID Pri State Dead Time Address Interface
10.9.49.2 1 Full/Backup 00:00:31 10.9.49.2 TransferPepl949
10.9.49.3 1 Full/DR 00:00:37 10.9.49.3 TransferPepl949
That is all we need for now.
James is in the process of replicating this in our test-lab as we speak.
Hopefully we can give you a workaround or solution by tomorrow.