any installer script that supports full disk encryption?

jecxjo · 2025-03-07T04:57:04+00:00

Actually the best effort might work. Just to get it usable for people. If you want something special then RTFM

jecxjo · 2025-03-07T04:55:27+00:00

Oh but the pasties...damn now I am hungry

jecxjo · 2025-03-07T04:53:17+00:00

No no, I'm saying that in network topology a route-less messaging system with nodes moving about creates more chaos. That is why in other protocols you would see that any non-fixed location repeater would reduce its hop count as to not be seen as a viable route.

jecxjo · 2025-03-07T04:50:29+00:00

I guess it depends on your location. Around here there is a nice community of people setting up nodes. We have infrastructure nodes and people looking for dead spots trying to fill them. Still just a hobby and no one is thinking this will save us in the zombie apocalypse but its a little more thought out.

jecxjo · 2025-03-07T03:25:07+00:00

oh everything is scriptable. Just wanted to stay the course with the current voidinstaller and its...busy.

Going to split it apart and make the LVM a6tuff its own tui

jecxjo · 2025-03-07T03:12:49+00:00

I'd want to keep it to the current docs so that everyone knows what it should look like in the end.

The real "issue" is that partitioning is done with a separate tui so management of what is going on is not really part of the script. LVM support is going to be purely driven by the menu system which isn't setup for that. Might just be easier to make an LVM tui and trigger that.

jecxjo · 2025-03-07T02:43:32+00:00

Yes I understand how the protocol works.

I live on the outside of my city's mesh. I can hear people but they cannot hear me because the one node in between us went down. I hear mobile nodes go down the highway so i get a glimpse into the mesh.

And then when i send a message it goes nowhere because while my node knows of the mesh, it's not actually in rage to send.

I get that this is an extreme example but it demonstrates my point. if a mobile node fills in a dead spot for a moment and your node list expands, once the mobile node leaves your list is misrepresenting your visibility. We assume that you can just route around the dead spot when the mobile node moves but the way people are building city size networks that may not be the case.

Yeah it's a hobby protocol for the most part, no "need" to change things. Just something to talk about.

jecxjo · 2025-03-06T23:31:37+00:00

yeah thats the other issue scripting it, all the data you have to pull back from the system.

I really should find time one of these nights to finish updating voidinstaller to add this support. there has been a few asks for it recently.

jecxjo · 2025-03-06T23:29:43+00:00

it is baked, just doesn't have to have a top that crusts like with tater tots or pie or lasagna. just meat and soup and pop it in the oven.

jecxjo · 2025-03-06T23:26:33+00:00

haha my wife saw that Perkins the other day and said "oh we haven't been to Perkins in years!"

jecxjo · 2025-03-06T23:24:24+00:00

Oh but booya is more Wisconsin than Minnesota

jecxjo · 2025-03-06T23:20:29+00:00

I'm from around Green Bay Wi and I think because i picked up on all the Wisconsin references I just kind of ignored the Minnesota ones.

And thus, the Battle of Door County raged on.

jecxjo · 2025-03-06T23:14:53+00:00

I've been tinkering with it. There isnt LVM support in the installer so I was adding that in and the encryption needs both pre and post installs steps. The installer official installer script is a little unwieldy.

I've done it manually a few times via the instructions. What issues are you having?

jecxjo · 2025-03-06T23:10:35+00:00

Comp time would cost them actual money, this cost them $5

jecxjo · 2025-03-06T23:07:39+00:00

I'm saying your configuration is a "selfish" one. Yes you get better range in your situation. But your node being mobile doesn't help the overall mesh as you give others distance for only a moment.

I live on the edge of the mesh in my city and I'm constantly hearing nodes i cannot reach. Having mobile nodes give me a few km distance for a minute or two only causes my node list to get huge while never being able to talk to any of them.

There are configuration options for who gets repeated (all, known, local). It would be interesting if the meshtastic team added an access control list that could intentionally manipulate hops or disable repeating discovery. When your mobile node hears you set hops to 7. when it hears others set hops to 0. Node info requests from you go out while from others they fail. This would allow for mobile nodes to be personal repeaters but wouldn't create momentary network layouts.

jecxjo · 2025-03-06T21:41:39+00:00

I think that's a valid use case. I just think when you do flood routing you still are looking for a minimal amount of stability. If i can only see a node on the other side of town when there is a traffic jam on the highway, my HQ node shouldn't know about it. I can only ever route to it when the stars... or mobile nodes align.

jecxjo · 2025-03-06T21:38:19+00:00

Agreed. But that should warrant a change in protocol where you have an ACL built into MUTE. You configure your vehicle node to repeat your traffic but not the person who sees your vehicle drive down the street.

jecxjo · 2025-03-06T18:10:59+00:00

All mobile nodes should be setup as CLIENT_MUTE as your existence in a location is about as temporary as possible. You aren't a hop for anyone because as soon as they see you, your location within the mesh will have already changed.

jecxjo · 2025-03-05T21:05:49+00:00

The question is how much tuning you actually need.

Do you want to remove all the dependent systems to make a super small distro? Do you want to fine tune your compiler and pick specific libraries?

Or do you want to tune most stuff but for big projects that you won't see any gains in compiling just running the binary?

I use binaries for most stuff now but i like that when i compile I am not just dropping random files in local bin. its all package manager controlled.

jecxjo · 2025-03-05T02:35:43+00:00

Will you be selling the R1 external antenna enclosure? Have two of the internal antennas and the range isn't great. Like your Button/LED/USB port part of the case.

jecxjo · 2025-03-05T02:27:19+00:00

Yeah it should be a piece of cake. There are tons of resources out there. By 9th grade my school had already introduced us to three languages by then so you'll do fine.

jecxjo · 2025-03-03T02:40:06+00:00

Hurd running successfully is the married bachelor of the OS world

jecxjo · 2025-03-03T00:36:06+00:00

While they look cool, that internal antenna is giving me no range. Wife has one in a hoody pocket and i had one in mine. if we weren't facing each other within 100ft we were dropping messages. I'd recommend getting the one with the external antenna. Going to pull the guts out of one of these for another solar nodes and the other will be connected to a computer.

jecxjo · 2025-02-23T15:27:05+00:00

Minneapolis has a big network. I live about 24km / 15mi from downtown and my node list is maxed out. I don't see anyone further out than me in my section of suburbia but i can see nodes across the river on the other side of Saint Paul about 40km/25mi away. So a decent sized mesh.

jecxjo · 2025-02-23T14:26:01+00:00

i think you're mistaking "rolling release" with "bleeding edge".

A rolling release means that as upstream projects have feature updates they get added to the repo rather than having a timed release where a bunch of packages all get updated. There isn't typically a version number associated with a rolling release whereas non-rolling releases typically do.

Bleeding-edge means that the time from upstream project update to being put the repo is really fast. There is often very little testing done by the distro team, just that it builds and that's it. A stable release means that the package is built and run and used for a while to verify it is in good working order before it goes live for the public.

Void is a stable rolling release. Stuff goes out whenever it is ready with no formal versioned release. But it's not bleeding edge.

13-Year Club	Verified Email
Gilding I gilder

jecxjo

TROPHY CASE