[Openswan Users] Configuration Help

[Justin Fletcher]

Sounds like SystemB has two interfaces with addresses of 192.168.1.3
and 100.100.110.3.  If that's the case, it's correct for it to respond
to either address.

SystemA can talk to the 100.100.110.3 address on SystemB because it's
on the same subnet, thus directly connected.

If you really want to talk to the 192.168.1.3 address, you'll have to
put in a static route so SystemA knows how to get to systemB.

btw, eth0 has no priority - it's just a name.

This is speculation based on my guesses of your network configuration
- if it's not right, can you provide more details on your setup?

Best,
Justin

On 2/8/07, Josh <jhcrowe at gmail.com> wrote:
> Everyone,
>
> I have a configuration question for you.  I am trying to connect two systems
> running openswan but am unable to do so because of some strange network
> settings.  Here are the details:
>
> SystemA: 100.100.110.2
>
> The address that system A thinks system B has because of the network
> configuration : 100.100.110.3
>
> SystemB's actual address for eth0: 192.168.1.3
>
> When I ssh or ping 100.100.110.3 system B responds.
>
> When I setup the configuration file for system B and provide it the
> 100.100.110.3 address and restart openswan it states it does not know that
> network.  When I change the configuration file and add 192.168.1.3 it trys
> to connect but does not work either.
>
> So...with this being said I am not sure how to setup the configuration file.
> Any thoughts?
>
> Thanks,
>
> Josh
>
> _______________________________________________
> Users at openswan.org
> http://lists.openswan.org/mailman/listinfo/users
> Building and Integrating Virtual Private Networks with Openswan:
> http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155
>
>