Hi Community,
given following scenario:
* a central IPSEC "server" (EdgeRouter 8 Pro) with one (of many) local subnets:
** 10.10.0.0/20: real local subnet
** 10.10.16.0/21: MPLS tunnel by provier to branch office in same country
** 10.10.24.0/21: MPLS tunnel by provide to branch office in same country
** quite some more of these MPLS tunnels.
* three sites are connected via IPSEC to the central server above
** site 1: 10.10.96.0/21
** site 2: 10.10.104.0/21
** site 3: 10.10.112.0/21
The MPLS is routed via static routes on the central EdgeRouter.
The IPSEC sites are connected via following tunnel scenarios:
tunnel 1 {
local {
prefix 10.25.96.0/21
}
remote {
prefix 10.25.0.0/16
}
}
(and with the appropriate subnet for the other two sites).
Our goal is, that the IPSEC branch offices can connect to the central subnet and also to the other subnet via MPLS (the routing on MPLS side OK).
But sadly, as soon as we start the above tunnel, all traffic (even to local subnets) on the branch side is not working anymore.
I assumed that the router can handle that automatically to handle local subnets prior to IPSEC subnets - but sadly it tries to route all traffic to IPSEC as soon as it's up.
Honestly, I have not yet tried this with a different Linux/IPSEC server, but according to my knowledge of kernel & routing the kernel should be able to handle this.
Is this now a "bug" on EdgeRouter or is my knowledge wrong and this is a design flaw?
Thanks upfront,
fips
/edit: just to inform: it's not a problem of the IPSEC tunnel, as soon as I try to tunnel 192.168.x.0/24 through the same config, everything works ;-)