Am Mon, 2003-08-11 um 21.57 schrieb Chad Graham: > Aug 11 16:07:29 rockhopper1 pluto[30848]: "thetunnel"[2] 4.4.4.4 #100: > route-client output: /usr/local/lib/ipsec/_updown: `route add -net > 192.168.0.0 netmask 255.255.255.0 dev ipsec0 gw 1.1.1.4' failed > Well, the gw 1.1.1.4 is not reachable from 2.2.2.2/24 which is the ip address assigned to the ipsec0 interface. > > If I do the same config but I make left eth0 1.1.1.1”” I can get the > tunnel up with no problems. Of course. Because 1.1.1.1/29 and 1.1.1.4/29 are in the same subnet. > > I think my problem is that left eth0:1 2.2.2.2 doesn’t have a gw on > it’s own network but how can I get around this? What are you trying to achieve? The gateway will not know how to route back to 2.2.2.2? Even if you could get ipsec up, you could only send packets but not receive them ?!?
Could you just explain why you are trying this setup? Cheers, Ralf -- Ralf Spenneberg RHCE, RHCX Book: Intrusion Detection für Linux Server http://www.spenneberg.com IPsec-Howto http://www.ipsec-howto.org Honeynet Project Mirror: http://honeynet.spenneberg.org _______________________________________________ FreeS/WAN Users mailing list [EMAIL PROTECTED] https://mj2.freeswan.org/cgi-bin/mj_wwwusr
