Hi!<div><br></div><div>I ran into another problem with Openswan. My topology looks like this...</div><div><br></div><div><a href="http://192.168.140.0/24" target="_blank" style>192.168.140.0/24</a><span style> -> 192.168.140.20 -> 192.168.101.128 << switch to another machine >> 192.168.101.129 -> 192.168.105.1 -> </span><a href="http://192.168.105.0/24" target="_blank" style>192.168.105.0/24</a></div>
<div><br></div><div><a href="http://192.168.140.0/24">192.168.140.0/24</a> is routed through another Linux machine. Here's kind of like what it looks like...</div><div><br></div><div>[ Internet ] -> Linux Box doing IPTables/NAT/DNS -> (192.168.140.20) Openswan (192.168.101.128) -> switch -> 192.168.101.129 (another openswan) -> 192.168.105.1 -> <a href="http://192.168.105.0/24">192.168.105.0/24</a> (workstations)</div>
<div><br></div><div>Linux Box has multiple subnets, <a href="http://192.168.140.0/24">192.168.140.0/24</a>, <a href="http://192.168.102.0/24">192.168.102.0/24</a>. If I ping 192.168.140.20, I get responses. This is on the other side of the openswan box. If I ping 192.168.140.1, I can see that on the linux box doing iptables/nat/dns, I get the ICMP Echo Request from 192.168.105.1 to 192.168.140.1. However, I get no responses at this point.</div>
<div><br></div><div>I believe I don't because the linux box doing all the routing has no idea about the <a href="http://192.168.105.0/24">192.168.105.0/24</a> subnet and how to get there. I've attempted to add routes to that for 192.168.105.0, but I obviously have no clue what I'm doing because I couldn't get it to work. The route I tried was...</div>
<div><br></div><div>route add -net 192.168.105.0 netmask 255.255.255.0 eth1.140</div><div><br></div><div>I thought that it would tell the gateway to get to 105 through eth1.140, which is the interface the vlan is on. This failed.</div>
<div><br></div><div>Can anybody out there solve this dilemma?</div><div><br></div><div><br></div><div>Thanks!</div><div>Mike</div><div><br></div>