Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Can't reach logo (fw1.84) via VPN

Created by: ghilu1963 at: 8/21/2024 1:24 PM (9 Replies)

Rating (0)

Thanks 1

10 Entries

8/21/2024 1:24 PM	Rate (0)
ghilu1963 Member Joined: 1/24/2022 Last visit: 9/18/2024 Posts: 5 Rating: (0)	Le Test !! Dear All , I found out the problem , Just Open the port 8080 and then When you want to download the Config from the Logo 8 just select the option "Dynamic DNS" and then add the Public IP:8080 or what ever port you forwarded this internet port "8080" to correspond on the internet... and then it asks you for the Web user password and after that you have complete control of the Logo 8 so to Recap , Go to your router, port forwarding , Internal port "8080" to External port (whatever port you like ) , at the IP of the LOGO and then get your public IP , for example 100.100.82.10 and then use the port you used for example 40 so in the Logo soft you should type .: 100.100.82.10:40 and then click TEST and you are done use the password and you are in Thank you in advance Le Test !! Salve, vorrei sapere se la procedura che è stata descritta è valida anche con le nuove versioni di LOGO con Fw 1.84? Purtroppo stiamo constatando che con questo nuovo fw non è più possibile raggiungere e configurare i nuovi dispositivi sotto port forwarding. Vi risulta anche a voi? C'è qualche soluzione al problema? Grazie ------------------------------------------------------------------------------------------ Split from Program a logo8 from a distance .
	Last edited by: Moderator_Lan at: 08/21/2024 13:56:25 Text formatting optimized Last edited by: Moderator_Lan at: 08/21/2024 14:03:40 New subject after splitting
Suggestion To thank Quote Answer

8/21/2024 1:38 PM	Rate (0)
ixo65 Grandmaster-Expert Joined: 12/18/2014 Last visit: 11/13/2024 Posts: 34212 Rating: (4261)	Please write your posts in English, English is the desired language in this forum. Thanks. Translate to English: ghilu1963 Hello, I would like to know if the procedure that has been described is also valid with the new versions of LOGO with Fw 1.84? Unfortunately we are finding that with this new fw it is no longer possible to reach and configure the new devices under port forwarding. Does this also happen to you? Is there a solution to the problem? Thanks Use VPN.

Suggestion To thank Quote Answer

8/21/2024 1:48 PM	Rate (0)
ghilu1963 Member Joined: 1/24/2022 Last visit: 9/18/2024 Posts: 5 Rating: (0)	I'm inside my organization's VPN and opening port 8080...102...502 can't reach the logo with fw1.84. Thank you

Suggestion To thank Quote Answer

8/21/2024 1:51 PM	Rate (0)
ixo65 Grandmaster-Expert Joined: 12/18/2014 Last visit: 11/13/2024 Posts: 34212 Rating: (4261)	Which LSC version use you? And Port 502 is reserved for Modbus TCP/IP.

Suggestion To thank Quote Answer

8/21/2024 2:00 PM	Rate (0)
ghilu1963 Member Joined: 1/24/2022 Last visit: 9/18/2024 Posts: 5 Rating: (0)	Using LSC 8.4, port 502/510 are used to communicate in modbus with SCADA. The problem is not the modbus but concerns the programming of the LOGO 1.84 from the LSC as per the screen Attachment LSC.jpg (220 Downloads)

Suggestion To thank Quote Answer

8/21/2024 2:05 PM	Rate (0)
Le Test !! Experienced Member Joined: 8/15/2015 Last visit: 8/21/2024 Posts: 133 Rating: (4)	Can you even PING the logo ? Lets start with the basics. What kind of VPN is it ? Split tunnel ? Full tunnel ? Do you have access to the subnet that the logo is on ? where is the logo located ? at your organizations location ? or ? Thanks Le_Test :D ghilu1963 I'm inside my organization's VPN and opening port 8080...102...502 can't reach the logo with fw1.84. Thank you

Suggestion To thank Quote Answer

8/21/2024 2:22 PM	Rate (0)
Le Test !! Experienced Member Joined: 8/15/2015 Last visit: 8/21/2024 Posts: 133 Rating: (4)	also. you public IP: 100.64.65.1is not a true public IP is a Carrier Grade NAT IP. That is why your port forwarding does not work. ghilu1963 Using LSC 8.4, port 502/510 are used to communicate in modbus with SCADA. The problem is not the modbus but concerns the programming of the LOGO 1.84 from the LSC as per the screen

Suggestion To thank Quote Answer

8/22/2024 8:13 AM	Rate (0)
ghilu1963 Member Joined: 1/24/2022 Last visit: 9/18/2024 Posts: 5 Rating: (0)	For simplicity, I attach a diagram of the problem that is highlighted (with the new LSC 8.4 for logos with FW 1.84) only in the condition in which the plc has a different IP from the OpenVPN class and where necessary to perform a PortFW on port 8080. In order to be able to remotely reach the plc using LSC it is necessary to enter in DNS dinamyc the address of the router followed by that of port 8080 where the PortFW was made ... (e.g. 100.64.10.x : 8080) I wanted to point out that all devices to date up to version LSC8.3 (about 300 LOGO! remote devices) are reachable and configurable regularly. Conversely, the problem arose with the LSC 8.4 relaise Is the door to be opened always the 8080 or has it changed?... something seems to have changed?!?! THANK YOU Attachment LSC.jpg (214 Downloads)

Suggestion To thank Quote Answer

8/22/2024 9:57 AM	Rate (0)
ixo65 Grandmaster-Expert Joined: 12/18/2014 Last visit: 11/13/2024 Posts: 34212 Rating: (4261)	See the attached excerpt from the 08-0BA2 manual. Attachment LOGO! 8 manual 0BA8 2023_06 xxxx8-0BA2.pdf (277 Downloads)

Suggestion To thank Quote Answer

8/22/2024 11:24 AM	Rate (0)
ghilu1963 Member Joined: 1/24/2022 Last visit: 9/18/2024 Posts: 5 Rating: (0)	Problem solved. The door (which opened heaven) is 8443 Very good.... Thank you for your availability and the information received.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users ixo65

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on