QNAP Disk On-line Server NAS-2100 Uživatelský manuál stáhnout pdf (Strana 12)

Deploy Rsync across network boundaries

The next scenario we’ll examine is deploying Rysnc across network boundaries. In particular,

we’ll examine its operation when a firewall exists between two networks. The two networks

could be distinct subnets on your LAN (e.g. different departmental workgroups), or they could

be a WAN-LAN pair (e.g. a business site and a home office).

In the topology shown in Figure I, the remote network is sitting behind a NAT router with an

integrated firewall. As you can see, the Rsync server’s IP address and the NAT router’s internal

IP address are on the same subnet, namely 10.0.200.0/24. You can also see that the IP address of

the Rsync client and the NAT router’s external IP address are on an entirely different subnet,

namely 192.168.100.0/24. It’s worth noting that the latter subnet could also be a WAN segment

with a public rather than a private IP address.

In order for the Rsync client to connect to the Rsync server, the NAT router must forward

incoming Rsync requests to the appropriate ReadyNAS device on the remote network. So, you

must open TCP/UDP port 873 on the NAT router, and forward Rsync requests to 10.0.200.x in

this example.

Figure I: You must open port 873 on the NAT router to support Rsync across network

boundaries.

1 2 ... 7 8 9 10 11 12 13 14 15 16 17 ... 20 21

Žádné komentáře

QNAP Disk On-line Server NAS-2100 Uživatelský manuál Strana 12