arping VS Pion WebRTC

Install Linux and arping

I want to compile the arping utility for an embedded device running Linux that has MIPS architecture. I used the instructions in the GitHub repo and I was able to compile it for my PC by running ./bootstrap.sh, ./configure, make, and sudo make install but that was compiled for my machine which is an x86_64 computer and probably won't work on the MIPS device. Can anyone walk me through the process of compiling this for MIPS architecture? I've never really compiled anything from source before so I don't know what I am doing. I searched online and couldn't find anything that helped me, I don't really know what to search for honestly.

A curious question. Aside from my day job, this seems like a thing I do all day. :-)

I'm not sure what the motivation for your question is. Do you feel like everything's been invented and built already, and it's just a matter of (at most) plugging the things together?

I find myself constantly thinking "this should exist". I don't have time to make them all exist.

https://github.com/ThomasHabets/arping

Nothing like it existed at the time, and I wanted to send ARP requests as easily as sending ICMP ping.

https://github.com/ThomasHabets/simple-tpm-pk11

I wanted to use a TPM chip for SSH client keys, and couldn't find anything like it.

https://github.com/ThomasHabets/tlssh

I wanted to explore what it would be like to have SSH, but with identities not based on providing username, but an x509 cert. (and TPM chip protecting the key)

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....

When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!

Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)

-----

I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!

* https://github.com/shinyoshiaki/werift-webrtc (Typescript)

* https://github.com/pion/webrtc (Golang)

* https://github.com/webrtc-rs/webrtc (Rust)

* https://github.com/algesten/str0m (Rust)

* hhttps://github.com/sepfy/libpeer (C/Embedded)

* https://webrtc.googlesource.com/src/ (C++)

* https://github.com/sipsorcery-org/sipsorcery (C#)

* https://github.com/paullouisageneau/libdatachannel (C++)

* https://github.com/elixir-webrtc (Elixir)

* https://github.com/aiortc/aiortc (Python)

* GStreamer’s webrtcbin (C)

See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

I have worked four jobs related to https://github.com/pion/webrtc and one for https://webrtcforthecurious.com

Two companies used Pion. The other two were just using the protocol (WebRTC)

In my experience Go has been relatively approachable for people that are good at PHP. It has a great standard library and a pretty solid ecosystem, though frameworks aren’t as popular in Go. There are some well regarded libraries for things like WebRTC via https://github.com/pion/webrtc WebSicket via https://github.com/nhooyr/websocket

Don't try to make RTC yourself, it looks easy, but in fact, it's a really hard problem to solve. Use https://pion.ly/ it's a pretty solid package they also have a discord/slack channel with a lot of helpful people there.

Maybe you can reuse some of this code: https://github.com/pion/webrtc/blob/master/examples/data-channels/main.go