EWON Cosy 131 connected to KT LTE router on WAN to pass traffic to PLC on LAN

Ewon Support eWON Cosy
#1

Hello EWON support,

We have an eWON Cosy 131 in Korea. The local IT does not want us to directly connect to a SIM card. Instead they want to plug their LTE wireless router to the WAN port on the Cosy whenever we need to connect to the machine to support the PLC code. Currently I have their LTE router connected to the WAN port. I selected ethernet internet connection set it to DHCP but the internet connect wizard fails every time. Do I have to set up their LTE router as a Proxy with a static IP or what am I doing wrong?

Please let me know if more information is needed.

-Kody

#2

What errors in the event log are you seeing after the internet test? Are you able to access the internet with a PC connected in the same fashion? Can you run the talk2m connection checker on that PC? This could indicate the reason the ewon is not connecting.
Talk2M Connection Checker (ewon.biz)

#4

Thank you for the help Deryck!

I ran talk2m connect per your suggestion and the issue was on their side. It’s online now but the vpn is very slow. We have a 300+ ms ping time to any device on the LAN side while on the vpn. Just out of curiosity, how much of that delay would you estimate is because we are in South Korea going through the Japan Talk2M VPN servers?

#5

scratch that Deryck, just read the full log a little closer and saw

"2021-06-09 07:47:30.9327 TestThread TRACE Pinged 192.168.0.1 (192.168.0.1) in 1 ms
2021-06-09 07:47:30.9497 TestThread TRACE Pinged 192.168.0.1 (192.168.0.1) in 4 ms
2021-06-09 07:47:30.9497 TestThread TRACE Pinged 192.168.0.1 (192.168.0.1) in 1 ms
2021-06-09 07:47:30.9497 TestThread TRACE Pinged 192.168.0.1 (192.168.0.1) in 1 ms
2021-06-09 07:47:30.9497 TestThread TRACE Pinged 192.168.0.1 (192.168.0.1) in 0 ms
2021-06-09 07:47:30.9497 TestThread INFO The local gateway 192.168.0.1 can be reached
2021-06-09 07:47:30.9646 TestThread TRACE DNS test: device.api.talk2m.com = 92.52.111.213
2021-06-09 07:47:30.9646 TestThread INFO DNS OK. Talk2M hostname resolved.
2021-06-09 07:47:30.9646 TestThread TRACE Pinging wellknown public server 8.8.8.8
2021-06-09 07:47:31.0076 TestThread TRACE Pinged 8.8.8.8 (8.8.8.8) in 35 ms
2021-06-09 07:47:31.0434 TestThread TRACE Pinged 8.8.8.8 (8.8.8.8) in 34 ms
2021-06-09 07:47:31.0793 TestThread TRACE Pinged 8.8.8.8 (8.8.8.8) in 35 ms
2021-06-09 07:47:31.1149 TestThread TRACE Pinged 8.8.8.8 (8.8.8.8) in 34 ms
2021-06-09 07:47:31.1507 TestThread TRACE Pinged 8.8.8.8 (8.8.8.8) in 34 ms
2021-06-09 07:47:31.1507 TestThread INFO Can ping wellknown public server 8.8.8.8 "

So roughly 35 ms from server to my pc at least on their network…though that doesn’t make sense to me. that time should be roughly the same latency as me pinging devices on LAN side of the Ewon since the Ewon security is at a bare minimum…

Going to read other posts see if someone has already had this issue on latency (y) thanks again for the help!

#6

Hi @KodyD ,

A ping of 300ms is on the higher side but not necessarily abnormal depending on the device location. I typically see a ping of around 200ms for a device connecting to a server near me here is the US.