Brief description eurogard ServiceRouter V2 3/23
eurogard GmbH Kaiserstraße 100 D-52134 Herzogenrath T.: +49/2407/9516-0 F: +49/2407/9516-23 www.eurogard.de
Ensure accessibility –Target network and DynDNS
Integration into target network (End customer LAN)
Operation as Server in the target network
The ServiceRouterV2 has to be integrated by forwarding the ports described below.
Additionally it has to accessible via DynDNS through updating of its IP.
The port numbers listed below are available.
UDP 1194: For the tunnelled connection to the PLC network (VPN)
OPTIONAL:
TCP 443: for access to the configuration interface(SSL)
Only provisionally: TCP 22 for emergency support through manufacturer
eurogard.
Ports 443 and 22 in the Router can be blocked after first start-up and do
not have to be forwarded after this point.
Since the public IP of our customers is normally dynamic, the public IP of
the ServiceRouters is also dynamic.
For external access to the ServiceRouter, the local IP must be updated
through the provider DynDNS.com.
In order to do this, the Router must be able to communicate via Port 80.
The Router requires access to an NTP server in order to update its system
clock. If an internal NTP is not available, Port 123 outgoing has to be open
for accessing an Internet NTP.
The battery-backed real-time clock of the ServiceRouter bridges offline-
times and allows the Router to be accessed without interruption.
Operation as Client in the target network
If the ServiceRouter V2 is operated as client in the target network, port forwarding
does not apply –along with many a discussion with local IP administrators.
The ServiceRouter V2 only requires an IP in the network and access to the Internet,
just as with any other PC in this network.
Access to an NTP server is required.
DynDNS is only required once at the central server.
