Hi,

On Sat, Mar 05, 2016 at 09:55:23AM -0600, Leroy Tennison wrote:
> I have been asked to set up a site-to-site OpenVPN instead of using 
> IPSec and there are some things I'm not sure about.  I'm mostly familiar 
> with "road warrior" implementations.  Assuming a tun implementation, how 
> does site-to-site work as far as routing is concerned?  I've searched 
> the web and, unless I searched for the wrong things, details are 
> non-existent.  Any documentation or illustrations?  Maybe an example 
> would clarify (I realize the use of the 10 network for OpenVPN is 
> wasteful, it's only an illustration):
> 
> "Site 1"
>          has 172.16... networks (172.16.1.0/24 through 172.16.10.0/24) 
> and "Site 2" has 192.168... networks, see below.
>          the OpenVPN server is 10.0.0.1/30
>          firewall routing is
>                  10.0.0.2 dev tun0 proto kernel scope link src 10.0.0.1
>                  192.168.1.0/24 via 10.0.0.2 tun0 proto static
>                                (through)
>                  192.168.10.0/24 via 10.0.0.2 tun0 proto static
> 
> "Site 2"
>          has 192.168.1.0./24 through 192.168.10.0/24 networks.
>          the OpenVPN client is 10.0.0.2/30
>          firewall routing is
>                  10.0.0.1 dev tun0 proto kernel scope link src 10.0.0.2
>                  172.16.1.0/24 via 10.0.0.1 tun0 proto static
>                              (through)
>                  172.16.10.0/24 via 10.0.0.1 tun0 proto static

Routingwise, this looks very reasonable.

> In both cases OpenVPN will run on the site's Internet-facing firewall 
> and all site subnets route through that firewall and systems at each 
> site have a default route being the IP address of the firewall for that 
> subnet.

Good start (because otherwise your default gateway would need to be taught
to send packets towards the openvpn machine).

> For remote site communications, do all "Site 1" systems have 10.0.0.2 as 
> the source IP address in packets from "Site 2" and "Site 2" systems have 
> 10.0.0.1 as the source IP address in packets from "Site 1"?

Not unless you tell it to - you can run iptables NAT rules on either
system to *make* it, but by default, OpenVPN will not mess with your
addresses.  So, a system on 172.16.1.x talking to a system on 192.168.10.y
will show up with its own address.

(If you connect *from the firewall* to the remote side, source address
selection will pick the 10.x address as source, because that's the address
belonging to the interface where the connection goes to - but this is
not relevant for other machines)

> Are the OpenVPN client and server tracking individual systems at their 
> sites using different ports or is it some other mechanism?  If I have it 
> all wrong then how does it work?  Anything else I should know?  Thanks 
> for any and all help.

If you want NAT, it's tracked like NAT would be - TCP/IP session state.

If not, no need to track individual systems :-)

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             [email protected]
fax: +49-89-35655025                        [email protected]

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
_______________________________________________
Openvpn-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openvpn-users

Reply via email to