You are browsing as a guest. Sign up (or log in) to start making projects!

11h 10m 5s logged

Devlog - 2 - made it work with VMs (kind of)

Last time I worked my node could already listen to TCP port 8765, recieve JSON msges , respond to hello, return basic system info. WAS not really a big mesh it was just a basic mesh, then I thought of actually start making an actual network. First I tried connecting across VMs and environments but that ended not good as I used a nest VM and its pretty restricted so I just thought why not first experiment on Codespace and thankfully that worked , It ran on 2 different nodes, laptop and codespace with same port, I faced some problems with port forwarding on codespace initially it was due to the wrong gh port being used , and same being used at the same times, now i also added it so it could talk with “python test_client.py 127.0.0.1 9000” like now it was not js working locally rather on a specified tcp address.
Now here comes the biggest part I added a peer system , it basically means a MESH node can remember other nodes on the network, a peer represents another node and currently stores - id, endpoint, last seen and status.
Added a peer registry which is basically the local database of these peers
Added register, allowing one node to tell another “I exist, and here’s how you can reach me…”
Current MESH state: nodes can communicate remotely, identify themselves, register peers, and maintain basic peer state.

0
98

Comments 1

@arpitaanuna

Wow! Nice progresss :)