[Openswan Users] routing problem with netmask 255.255.255.255

[Alex, Wheeler]

Problem: ipsec0 routes do not appear in IP routing table

I have the following ipconfiguration:

Machine A
ifconfig eth0 w.x.y.z broadcast w.x.y.z netmask 255.255.255.255
route add 10.255.255.1 dev eth0
route add default gw 10.255.255.1

(ipsec config at bottom)

When ipsec is started, a encrypted connection is established.  All traffic 
from machineB to macineA is  encrypted. Traffic from machineA to machineB is 
not encrypted.

When looking at the route table, it shows that no ipsec routes have been 
added.

It looks as though openswan tries to determine the gateway, checks eth0, 
see's that there is only 1 host on the network (itself) and gives up.  But 
infact 10.255.255.1 is on the same physical network segment, which is the 
router for machineA, but openswan ignores this.

Has anybody had this problem?  What is the fix/workaround?


Thanks
Alex
alexdw1 at hotmail.com


and the following ipsec.conf of machineA:
version 2.0     # conforms to second version of ipsec.conf specification

config setup
        interfaces="ipsec0=eth0"
        klipsdebug=none
        plutodebug=none
        myid=@machineA

conn %default
        auto=start
        type=tunnel
        left=w.x.y.z
leftrsasigkey=soijcsoidcjsoicjsoicjdoijcosicjosidcjoisdcjpaoskxpaoxkfoobar

conn machineA-to-machineB
        auto=start
        left=w.x.y.z
        rightid=@machineB
        right=a.b.c.d
        rightrsasigkey=posidcpsodicpsodicpsocipsodicposdicfoobar

_________________________________________________________________
Express yourself with cool new emoticons http://www.msn.co.uk/specials/myemo