starkzarn

joined 2 years ago
[–] starkzarn 1 points 4 days ago

The primary thing is rather than "dumb" flood routing, you can choose the path your message takes to its destination; as a repeater operator you can also choose the path it takes to repeat out. Its a slight compensation to people carelessly placing infrastructure nodes with poor configurations in poor places. Not perfect, but better. Adoption is much, much lower though, and the licensing is not copyleft.

[–] starkzarn 2 points 4 days ago

My pleasure. It was a good question, I think I'll even include a note on that in the post when I get home this evening and can edit.

Cheers!

[–] starkzarn 2 points 5 days ago (2 children)

That's a great question!

No, blocking a node -- router or other -- will only block packets originating from that node. All traffic that is forwarded by that node, but originating from others will still be received.

Ultimately, the only place that blocking nodes strategically makes sense is on high utilization routers. If you're just blocking nodes on a client, it's not changing channel or airtime utilization for the rest of the mesh. That said though, if someone is harassing you then a block on a client is still fully worth it. 🙂

[–] starkzarn 2 points 5 days ago (3 children)

Meshcore does address some of the biggest shortfalls of Meshtastic, but I absolutely HATE that they're positioned to either rugpull, or setup a perpetual "freemium" model. It's also not interoperable, so if Meshcore is to work, it needs the numbers like Meshtastic has.

[–] starkzarn 3 points 5 days ago (5 children)

Yeah, so far the most prevalent thing around my area has been "it's a hobby for the sake of being a hobby." No one does anything terribly useful or important with it. I can tell you that I would certainly never rely on it as a form of emergency communication.

 

cross-posted from: https://infosec.pub/post/32151664

This is a generic metrics post to leverage a spare ESP32 meshtastic node to ingest metrics into Grafana! We've had some congestion issues due to poor config in my area, and this has helped me pinpoint which nodes are causing the biggest problems, and block them at my repeater.

 

This is a generic metrics post to leverage a spare ESP32 meshtastic node to ingest metrics into Grafana! We've had some congestion issues due to poor config in my area, and this has helped me pinpoint which nodes are causing the biggest problems, and block them at my repeater.

[–] starkzarn 2 points 1 week ago

La Marzocco

[–] starkzarn 7 points 3 weeks ago (1 children)

It's not about user-led synergy. The personal data market is slurped up by those that already have and are building correlations. Just because a user didn't report anything to their insurer doesn't mean an insurer sure as shit isn't going to want the data if they can link it to the user whatsoever, so long as it will make them more money.

This is hypothetical, of course, but it's the way the market of data brokers works.

[–] starkzarn 15 points 3 weeks ago (3 children)

You joke, but I guarantee there's a market. Consider health insurance companies that see an opportunity to charge everyone more unless they can prove their good brushing habits via app data.

[–] starkzarn 1 points 3 weeks ago

Options are great, this is what drives the Linux community to come up with great solutions!

That said... Kate is an easy winner for me.

[–] starkzarn 6 points 1 month ago (2 children)

A fatalist take like this doesn't help anyone. Do you lock your doors at night even though you're not be continuously robbed? It's always worth it to try and protect yourself.

[–] starkzarn 12 points 1 month ago

What's yours then?! Sounds like something a fed would say...

Also your mother's maiden name and the name of your elementary school.

[–] starkzarn 2 points 1 month ago

Love me some graylog

 
 

This one is less focused on self-hosting a homelab service, but I thought might be interesting for the homelabbers here. I got into this hobby through my career in cybersecurity, and decided to write up a little post about a tool I frequently use, mitmproxy!

 

cross-posted from: https://infosec.pub/post/28466166

If you've followed any of my self-hosted headscale with Podman series, I wrote up another "bonus" post talking about OIDC configuration with Authelia. Took some trial and error, so I figured I'd document it in the public notebook.

 

If you've followed any of my self-hosted headscale with Podman series, I wrote up another "bonus" post talking about OIDC configuration with Authelia. Took some trial and error, so I figured I'd document it in the public notebook.

 

cross-posted from: https://infosec.pub/post/28196930

Another post in the records for the tech blog, this time all about opensource network monitoring with LibreNMS!

 

Another post in the records for the tech blog, this time all about opensource network monitoring with LibreNMS!

 

For those that were interested in my PART 1 post of the Grafana Loki OPNSense firewall log monitoring, I present you: PART 2! This one is the good one (albeit less technical) where we get the eye candy after getting the log ingestion pipeline already setup in part 1.

 

cross-posted from: https://infosec.pub/post/27200076

My first blog series on headscale with traefik through podman quadlets was pretty well received on here. I'm just getting started with this blog, and thought the second topic I recently worked on might be popular in this crowd too: a lower resource method of centralizing logs for OPNSense with Grafana Loki (and Alloy) including geoIP!

view more: next ›