3.9 i386 build #617 snapshot: I have an ipsec.conf at one end of a tunnel- ike esp from 192.168.1.0/24 to 192.168.0.0/24 peer 61.95.94.130 ike esp from 138.130.27.231 to 192.168.0.0/24 peer 61.95.94.130 ike esp from 138.130.27.231 to 61.95.94.130
One of the machines on 192.168.1.0/24 wants to connect to 61.95.94.139 but an attemp to do so is unsuccessful as there is nothing in the routing table that idicates a route to that host and so it tries going via the default. 61.95.94.130 is a router that "knows" 61.95.94.136/29 as well as 61.95.94.128/29 but I cannot figure a way to make that router known as a route to the destination we need to reach. Adding ike esp from 192.168.1.0/24 to 61.95.94.136/29 peer 61.95.94.130 doesn't generate any error message but neither does it add flows and ipsecctl -s f shows the same as without it. route add .... doesn't want to know either. Cluestick? >From the land "down under": Australia. Do we look <umop apisdn> from up over? Do NOT CC me - I am subscribed to the list. Replies to the sender address will fail except from the list-server.
