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

Network Observatory

  • 3 Devlogs
  • 41 Total hours

So basically I am making a software that lets you browse you through different modes and lets you see what connections are made to your network and you can go deeper and see domains and addresses of the devices usage

Open comments for this post

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.

1
0
98
Open comments for this post

11h 6m 44s logged

Devlog 1 - Js started

I started making my mesh in python , I first needed to understand how the mesh actually worked so for first few hours i was trying random things on my pc with python that might add onto my mesh later on , i first start with making my protocol file which basically define the messages that my MESH nodes will understand, wasnt really that tough , then later on I went to make my first Node, i first defined ports and hosts and then went on to defining how they will communicate and how it will be done, and for the cli i for now gave it one command only

For now i really js made my terminals communicate , later i will add more features

0
0
48

Delete project?

Are you sure you want to permanently delete this project? This action cannot be undone.

All devlogs, followers, and associated data will be removed.

Followers

Loading…