<div>Justin,</div>
<div> </div>
<div>I think I have multiple problems here. One of them being me. After talking to our network department they have stated that the setup is a 1 to 1 NAT. Unfortunately I provided the wrong address for System B since it is not on the same network. Its address is
<a href="http://100.100.109.3">100.100.109.3</a> as the public address. So my connection looks like this:</div>
<div> </div>
<div>SystemA (<a href="http://100.100.110.2">100.100.110.2</a>) --->(<a href="http://100.100.109.3">100.100.109.3</a>)NAT--->SystemB(<a href="http://192.168.1.3">192.168.1.3</a>)</div>
<div> </div>
<div>So I am trying to find a good example online that would mimic this setup so I could use their config file but I am confused when I so no explanation as to what the following key words mean:</div>
<div> </div>
<div>virtual_private</div>
<div> </div>
<div> </div>
<div>Also is it necessary to use the following command to get the tunnels to connect:</div>
<div> </div>
<div>ipsec auto --up systema-systemb</div>
<div> </div>
<div> </div>
<div> </div>
<div>If you could point me to a basic config example that I could use on systemA and systemB that would be awesome!</div>
<div> </div>
<div>Thanks for your help!<br><br> </div>
<div><span class="gmail_quote">On 2/8/07, <b class="gmail_sendername">Justin Fletcher</b> <<a href="mailto:jfletche@gmail.com">jfletche@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Sounds like SystemB has two interfaces with addresses of <a href="http://192.168.1.3">192.168.1.3</a><br>and
<a href="http://100.100.110.3">100.100.110.3</a>. If that's the case, it's correct for it to respond<br>to either address.<br><br>SystemA can talk to the <a href="http://100.100.110.3">100.100.110.3</a> address on SystemB because it's
<br>on the same subnet, thus directly connected.<br><br>If you really want to talk to the <a href="http://192.168.1.3">192.168.1.3</a> address, you'll have to<br>put in a static route so SystemA knows how to get to systemB.
<br><br>btw, eth0 has no priority - it's just a name.<br><br>This is speculation based on my guesses of your network configuration<br>- if it's not right, can you provide more details on your setup?<br><br>Best,<br>
Justin<br><br>On 2/8/07, Josh <<a href="mailto:jhcrowe@gmail.com">jhcrowe@gmail.com</a>> wrote:<br>> Everyone,<br>><br>> I have a configuration question for you. I am trying to connect two systems<br>> running openswan but am unable to do so because of some strange network
<br>> settings. Here are the details:<br>><br>> SystemA: <a href="http://100.100.110.2">100.100.110.2</a><br>><br>> The address that system A thinks system B has because of the network<br>> configuration :
<a href="http://100.100.110.3">100.100.110.3</a><br>><br>> SystemB's actual address for eth0: <a href="http://192.168.1.3">192.168.1.3</a><br>><br>> When I ssh or ping <a href="http://100.100.110.3">100.100.110.3
</a> system B responds.<br>><br>> When I setup the configuration file for system B and provide it the<br>> <a href="http://100.100.110.3">100.100.110.3</a> address and restart openswan it states it does not know that
<br>> network. When I change the configuration file and add <a href="http://192.168.1.3">192.168.1.3</a> it trys<br>> to connect but does not work either.<br>><br>> So...with this being said I am not sure how to setup the configuration file.
<br>> Any thoughts?<br>><br>> Thanks,<br>><br>> Josh<br>><br>> _______________________________________________<br>> <a href="mailto:Users@openswan.org">Users@openswan.org</a><br>> <a href="http://lists.openswan.org/mailman/listinfo/users">
http://lists.openswan.org/mailman/listinfo/users</a><br>> Building and Integrating Virtual Private Networks with Openswan:<br>> <a href="http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155">http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155
</a><br>><br>><br></blockquote></div><br>