Comments
 
posted on June 23rd 2010, at 17:14
by lunarg
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:

Quote
ipsec_setup: Starting Openswan IPsec U2.4.12/K2.6.26-2-amd64...
ipsec_setup: no default route, %defaultroute cannot cope!!!

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 solve  ...
 
 
« February 2020»
SunMonTueWedThuFriSat
      1
2345678
9101112131415
16171819202122
23242526272829
 
Links
 
Quote
« When a bird does poo poo in your eye, be happy elephants don't fly. »