Not only UDP #1

Closed
opened 2016-03-16 15:34:53 -04:00 by nejtr0n · 4 comments
nejtr0n commented 2016-03-16 15:34:53 -04:00 (Migrated from github.com)

It would be grate to use not only UDP, but TCP/ip protocol.

It would be grate to use not only UDP, but TCP/ip protocol.
kanocz commented 2016-03-16 17:42:36 -04:00 (Migrated from github.com)

It's possible to implement communication also by TCP, but in case if you have more servers connected, each server will connected to all of other servers + any lost packet will affect whole delivery within this connection. If you need it for some special situation (for example some of endpoints are behind NAT) I can implement this

It's possible to implement communication also by TCP, but in case if you have more servers connected, each server will connected to all of other servers + any lost packet will affect whole delivery within this connection. If you need it for some special situation (for example some of endpoints are behind NAT) I can implement this
nejtr0n commented 2016-03-17 03:06:15 -04:00 (Migrated from github.com)

Unfortunately, I don't know golang, and could not understand, how your program works =(
I'll try to explain my case.
I'm trying to make cluster of docker-swarm nodes. (https://docs.docker.com/swarm/). Main component of system - decentralized key/value storage (https://www.consul.io/intro/) This technology
has internal failover system. (Like replication and election of master, when some node is down)
I think lcvpn is the best solution for my case. (If some node is down - neighbours elcting new master and life is go on)
But you have wrote, that lcvpn "Communicates via UDP directly to selected host (no central server)" in readme.
It means no tcp connections between nodes. Am I right?

Unfortunately, I don't know golang, and could not understand, how your program works =( I'll try to explain my case. I'm trying to make cluster of docker-swarm nodes. (https://docs.docker.com/swarm/). Main component of system - decentralized key/value storage (https://www.consul.io/intro/) This technology has internal failover system. (Like replication and election of master, when some node is down) I think lcvpn is the best solution for my case. (If some node is down - neighbours elcting new master and life is go on) But you have wrote, that lcvpn "Communicates via UDP directly to selected host (no central server)" in readme. It means no tcp connections between nodes. Am I right?
kanocz commented 2016-03-17 04:57:33 -04:00 (Migrated from github.com)

Yes, you're right, no tcp connection, but there is "udp connection", but it's only about connection between lcvpn instances. Using lcvpn you can create encrypted network between more servers and within this network applications can use both udp and tcp connections without any limitation, so you can use docker-swarm on it

Yes, you're right, no tcp connection, but there is "udp connection", but it's only about connection between lcvpn instances. Using lcvpn you can create encrypted network between more servers and within this network applications can use both udp and tcp connections without any limitation, so you can use docker-swarm on it
nejtr0n commented 2016-03-17 07:51:56 -04:00 (Migrated from github.com)

Oh, it's great!! Thank you for this tool!

Oh, it's great!! Thank you for this tool!
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kanocz/lcvpn#1
No description provided.