How to connect with the remote server

[Rohan-Kar]

I want to try to connect with remote server but getting some error please guide me how to connect with remote server . and i aso deployed the server_sidecar and follow the https://docs.ockam.io/guides/use-cases/add-end-to-end-encryption-to-any-client-and-server-application-with-no-code-change this doc .
here is the command ockam tcp-outlet create --at /node/server_sidecar --from /service/outlet --to remoteip:5000

here is the error is error: invalid value '192.168.1.100:5000' for '--to <ROUTE>': unregistered protocol prefix "192.168.1.100:5000"

Thanks

[mrinalwadhwa]

@Rohan-Kar could you share a full list of commands that you're trying to run.

[Rohan-Kar]

@mrinalwadhwa Thanks
here i am sharing my command Please check
server side terminal

1. ockam node create relay
2. in another terminal python3 -m http.server --bind 127.0.0.1 5000
3. ockam node create server_sidecar
4. ockam tcp-outlet create --at /node/server_sidecar --from /service/outlet --to clientip:5000
5. ockam forwarder create server_sidecar --at /node/relay --to /node/server_sidecar
   client side server terminal
   1.ockam node create client_sidecar
   2.ockam secure-channel create --from /node/client_sidecar --to serverip:5000 (here i am getting error )
   3.ockam tcp-inlet create --at /node/client_sidecar --from 127.0.0.1:7000 --to -/service/outlet

[Rohan-Kar]

@mrinalwadhwa Please check once

[mrinalwadhwa]

Hey @Rohan-Kar

ockam secure-channel create --from /node/client_sidecar --to serverip:5000

the --to argument here has to be an Ockam Route, it cannot be a simple ip:port.
We're writing a complete guide on how to build routes but in the meantime try the following in your example:

$ ockam node create client_sidecar
$ ockam secure-channel create --from /node/client_sidecar --to /ip4/SERVERIP/tcp/5000/service/hop/service/forward_to_server_sidecar/service/api \
  | ockam tcp-inlet create --at /node/client_sidecar --from 127.0.0.1:7000 --to -/service/outlet

Replace SERVERIP with an actual IP value, it cannot be a DNS name. If it is a DNS name the route would be written differently.

$ ockam node create client_sidecar
$ ockam secure-channel create --from /node/client_sidecar --to /dnsaddr/serverip/tcp/5000/service/hop/service/forward_to_server_sidecar/service/api \
  | ockam tcp-inlet create --at /node/client_sidecar --from 127.0.0.1:7000 --to -/service/outlet

Note the second command is one single command.

Let us know how it works.

If things aren't working correctly you can reset your entire system with ockam reset --yes

[Rohan-Kar]

@mrinalwadhwa i have put the relay node port number but still same error .

here is the relay node port number please check

if possible can we get in call and fix it .
Thanks for your Guidance .

[mrinalwadhwa]

Sure, happy to help. Please email me at [email protected]

[Rohan-Kar]

@mrinalwadhwa
Thanks for the guidance
Here i am deployed the relay node and also open the port 3000 but getting error Please have a look on that

[mrinalwadhwa]

That likely means relay_server_ip:3000 is not accessible to rohan-vm-1
From rohan-vm-1 if you run nc -zv relay_server_ip 5000... what is printed?

[Rohan-Kar]

my relay node running on port 3000 so when i type the above command
Connection to relayip 3000 port [tcp/*] succeeded! like this . but when i tried with port 5000 noting will coming the blank screen .

[9to1url]

I am trying to run this example, but I couldn't find anywhere has the : ockam forwarder create
Is this been replaced by ockam tcp-inlet create?

[9to1url]

I don't have a link on your website, but I tried to mimic @Rohan-Kar example in this thread, connect one client to a server remotely. the setup is client IP: 11.11.11.11, the server IP: 22.22.22.22.

On server side run a python http server on port 5000 , use it to verify if can connect from the other side of the tunnel.

On client side follow exactly same but change the IP and Ockam Route by following Mrinal's advise.

[SanjoDeundiak]

I think people's examples are something that will eventually be outdated (as we actively change things), and there is no way for us to update them. Please use one of the examples we have on our website. For example, this one https://www.ockam.io/blog/connect_private_influxdb (all the InfluxDB specifics can be ignored). I also suggested that in my reply to you on Discord yesterday

[9to1url]

Sure let me do the connect_private_influxdb instead. since I am not familiar both influxdb or telegraf, can I simplify the influxdb to a simple web server , also simplify the client to a curl?

[SanjoDeundiak]

Should work

[9to1url]

Great, I followed the steps and running very well :-)

Here is the iperf3 test, I found the speed not very stable and thruput not very great, any idea?

❯ iperf3 -c 127.0.0.1 -p 8087
Connecting to host 127.0.0.1, port 8087
[  5] local 127.0.0.1 port 50300 connected to 127.0.0.1 port 8087
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.01   sec  8.23 MBytes  68.7 Mbits/sec
[  5]   1.01-2.01   sec  1.21 MBytes  10.2 Mbits/sec
[  5]   2.01-3.01   sec   622 KBytes  5.10 Mbits/sec
[  5]   3.01-4.01   sec  1.21 MBytes  10.2 Mbits/sec
[  5]   4.01-5.01   sec  1.21 MBytes  10.2 Mbits/sec
[  5]   5.01-6.01   sec  1.84 MBytes  15.4 Mbits/sec
[  5]   6.01-7.01   sec  1.21 MBytes  10.2 Mbits/sec
[  5]   7.01-8.01   sec  1.82 MBytes  15.3 Mbits/sec
[  5]   8.01-9.00   sec  2.45 MBytes  20.5 Mbits/sec
[  5]   9.00-10.00  sec  1.82 MBytes  15.3 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.00  sec  21.6 MBytes  18.1 Mbits/sec                  sender
[  5]   0.00-10.00  sec  19.7 MBytes  16.5 Mbits/sec                  receiver

iperf Done.