Working on implementing Multi-WAN at our office (more about that later), in which we use a rather special routing setup, we got this error message on our IPSEC tunnels:
While the reason was obvious to me (there's indeed no default route in the main routing table, this is by design), fixing the problem was not.
I tried adding options like leftnexthop=ip-address but it did not really matter; the error persisted.
After searching around Google, I came across a post with a similar error, along with an unusual solution: adding the following line solves the issue.
config setup
interfaces="ipsec0=eth0"
The unusual about it is that I'm running a 2.6 kernel and IPSEC interfaces no longer exists. However, adding this option regardlessly overrides the implicit %defaultroute value for all interfaces.
Source: http://lists.openswan.org/pipermail/users/2005-June/005447.html
| « ‹ | December 2024 | › » | ||||
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 | 31 | ||||
