Devlog 4: (Now with logging)

What change

• Rewrote a lot of the logic making it safer
• Added a timeout for pinging
• Added a Code struct which has TryFrom<&str> and std::fmt::Display implemented so it’s really easy to convert a code string to the code structure and back
• added logging with tracing
• Combined both sending sockets to one Arc<UdpSocket> so broadcaster and direct connection check share one socket reducing overhead
• Changed how I handle Errors, no longer ignoring them

Next up:

• Cli
• Maybe a tui

Devlog 3:

Got everything working in Rust.
Now the direct connection check works in both directions.

Next up:

• Optimizing
• TUI
• CLI

Devlog 2:

I started reimplementing everything in rust. Already have the discovery broadcast and listener working.
So the only things missing are the direct connection check from the program site and a better looking interface like a tui.

Devlog 1:

So I reverse engineered the protocol hak5 uses for SharkLink using one SharkJack Display and my PC with Wireshark for package inspection.

I first needed to implement the device discovery which is a broadcast UDP package which in plan text says <PIN> <Sender_Ip>\n so for example 1-3-3-7 192.168.178.1\n

Then I reverse engineered the ping messages which are a direct connection with first PING <Sender_IP>\n and then the response which is ACK <Sender_IP>\n.

Nextup:

Reimplement the program in rust and after that create a tui.