RV50 Port Forwarding Setup: Difference between revisions
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
[[category:RV50]] | [[category:RV50]] | ||
<div style=""> | <div style="">All devices on the LAN are configured as follows: </pre>All devices on the LAN are configured as follows: </div> | ||
All devices on the LAN are configured as follows: </pre>All devices on the LAN are configured as follows: | |||
<div style="font-weight: 400;"><p>APU #1 (and singles) 192.168.1.101 </p></div> | <div style="font-weight: 400;"><p>APU #1 (and singles) 192.168.1.101 </p></div> | ||
<div style="font-weight: 400;"><p>APU #2 192.168.1.102 </p></div> | <div style="font-weight: 400;"><p>APU #2 192.168.1.102 </p></div> | ||
Latest revision as of 18:48, 1 October 2024
APU #1 (and singles) 192.168.1.101
APU #2 192.168.1.102
APU #3 192.168.1.103 etc
Cloudgate 192.168.1.200
COM1000 192.168.1.200
Remote connection is to the RV50’s IP (or url) and appropriate port #. Ports are standardized so no changes to modem are required if the site is upgraded. This is done with fewer entries on the modem.
Standard for new installations beginning 2021
1st digit |
APU # |
LAN Port |
Access type |
Example APU 2 Telnet |
8 |
1 |
21 |
FTP |
|
8 |
1 |
22 |
SSH |
|
8 |
1 |
23 |
Telnet |
166.143.207.77:8223 |
8 |
1 |
24 |
Detector |
|
9 |
1 |
23 |
Telnet |
166.143.207.77:9123 (first DCHP issue on modem-192.168.1.111) |
Railert II-no change
1st digit |
CloudGate |
LAN Port |
Access type |
Example CG Telnet |
8 |
0 |
80 |
Browser |
|
8 |
0 |
22 |
SSH/SCP |
|
8 |
0 |
23 |
Telnet |
63.43.143.249:8023 |
Previous Standard (pre 2021), Telnet only (not removing from existing modems)
Digit 1-3 |
APU # |
Access type |
Example APU 2 Telnet |
800 |
1 |
Telnet |
63.43.143.249:8002 |
COM1000 version Railert-no change
Port |
Access type |
Example COM1000 Telnet |
6123 |
Telnet to COM1000 |
63.43.140.208:6123 |
12345 |
SmartPass Serial Port |
|
6789 |
SmartPass 485 Port |