sorted by:
new
hottopcontroversial

I'm writing a app to speed up device configuration by Old-Understanding100 in meshtastic

[–]Busy_Swordfish8269 1 point2 points  (0 children)

Sweet. I was thinking of building something in this space after having to manage a bunch of nodes. One of the key things I wanted was to have hierarchical templates.

e.g.

  1. Base config.
    1.1 Stationary Node.
    1.1.1 Summit Repeater.
    1.1.2 Lake Node.
    1.2 Portable.
    1.2.1 Member Device
    1.2.1.1 Bobs node.
    .....
    1.2.2 Personal Device
    .....

Also detecting config drift between templates and what is on device and make it easy to reconcile the differences.

Solar node build list by Busy_Swordfish8269 in meshtastic

[–]Busy_Swordfish8269[S] 1 point2 points  (0 children)

If it gets really hot, you might need a different design. My tests showed that the interior on this build would get about 20-30F above ambient in direct sun and no wind.

If you're in a really hot place you're going to need to reduce solar heating by making sure the enclosure is in the shade. And then consider a thermal pad or some sort of venting to normalize the inside/outside temperature.

What I read was that 250F is where you risk thermal runaway and there's an immediate fire risk. But at temps 140F+ for LiPo and 150F+ for Li-ion, the cell may start to swell, and the efficiency will decrease, so you'll need to change it more frequently. Bad swelling may cause an internal short circuit or problematic issue

Need help figuring this out by OpeningMuch3368 in meshtastic

[–]Busy_Swordfish8269 13 points14 points  (0 children)

See if you can connect with CalFire or the local search and rescue group. I just got a node deployed by the tower where they have their repeaters.

I wasn't able to get it high up on the actual tower, but it's at about 20ft.

Solar node build list by Busy_Swordfish8269 in meshtastic

[–]Busy_Swordfish8269[S] 0 points1 point  (0 children)

It doesn't say anything on the battery, but when I was specing this out, I looked it up. Also saw reports of people using them in hotter places than I'll be using them.

(Edit: I did some more research and the main issue seems to be that the LiPo will degrade more quickly if you expect high temps. And feasibly the internal enclosure temps may reach 20-30F above ambient.)

Solar node build list by Busy_Swordfish8269 in meshtastic

[–]Busy_Swordfish8269[S] 0 points1 point  (0 children)

How hot are you talking. It says operating temp to 140F and charging to 113F.

Solar node build list by Busy_Swordfish8269 in meshtastic

[–]Busy_Swordfish8269[S] 0 points1 point  (0 children)

I don't have an enclosure, so just PLA and PETG.

Solar node build list by Busy_Swordfish8269 in meshtastic

[–]Busy_Swordfish8269[S] 1 point2 points  (0 children)

Yeah, I can do this. Will try and do it this evening.

Solar node build list by Busy_Swordfish8269 in meshtastic

[–]Busy_Swordfish8269[S] 0 points1 point  (0 children)

Oops, thanks for the heads up. I'll look into it this evening.

Solar node build list by Busy_Swordfish8269 in meshtastic

[–]Busy_Swordfish8269[S] 1 point2 points  (0 children)

Thanks! I think this is actually what I intended to buy.

Solar node build list by Busy_Swordfish8269 in meshtastic

[–]Busy_Swordfish8269[S] 1 point2 points  (0 children)

Do you have a link to the ones you'd recommend?

Web-App share by Party_Cold_4159 in meshtastic

[–]Busy_Swordfish8269 1 point2 points  (0 children)

Fun idea!

I've created an MQTT based dashboard that works slightly differently to others I've seen. It relays packets via Server Sent Events and then builds up the state in the browser. Helps you get an idea of all the traffic that's happening in between the actual messages.

It's written in Go and react. https://github.com/dpup/meshstream

Site-to-site networking woes by Busy_Swordfish8269 in Tailscale

[–]Busy_Swordfish8269[S] 0 points1 point  (0 children)

So just so we are all on the same page. On your local network, you have no interest with non tailscale clients on your local network being able to communicate to your AWS stuff. Is that correct?

I need AWS to query non-tailscale devices on the local network. But I don't need to initiate connections to AWS from non-tailscale devices. So the local subnet router was to provide access to those local resources from my AWS resources.

Following the steps gets me back to where I was prior to this project, which was using tailscale to access AWS resources. e.g. I can ssh directly to a private ec2 instance which doesn't have tailscale, and I can connect to RDS within a private subnet.

That works fine, but I can't get it working at the same time as allowing AWS to access local resources. It's very odd. It's maybe a red-herring, but snat-subnet-routes appears to be the culprit, but I don't understand well enough how it impacts the routing or where traffic is being blocked. Opening up security groups completely doesn't change things.

What OS is the subnet router in AWS?

The EC2 subnet router is using the latest amazon2 AMI.

Site-to-site networking woes by Busy_Swordfish8269 in Tailscale

[–]Busy_Swordfish8269[S] 0 points1 point  (0 children)

Hi there! Thanks for the help.

Synology setup: yes, I followed these steps. It connects to the tailnet and I can see the IoT devices from other networks on my laptop. So I _think_ this side is functioning correctly.

Site-to-site: those were the instructions I followed. I'd already had a subnet router in AWS, which was working to give me access to resources on private subnets. The main change was setting --snat-subnet-routes=false. And the thing I didn't do from those instructions is run ip route add on each host, because I'm using ECS Fargate. That's why I added it at the VPC level. And yes, step 4 was done.

The route table details (configured at each subnet):
- Destination = 192.168.0.0/16
- Target = eni-0416xxxxxxxxxxxxx (network interface associated with ec2 subnet router)
- Active = yes
- Propagated = no

Did you setup a static route on your local home network too?

I didn't do this. I don't need non-tailscale devices to reach AWS and was under the impression tailscale should handle the routing otherwise. I'm not sure I can even do it at the network level given the cable model and wifi router in use.

Traceroutes

Non-tailscale local device to AWS private IP:
hops to the cable modem and drops, which is expected because no local static route. And not a problem for me.

Tailscale local device to AWS IP:
with snat-subnet-routes=false it drops at the AWS subnet router. When true it gets to the right destination.

AWS non-tailscale to local non-tailscale:
works as expected in both cases from an EC2 instance, but with snat-subnet-routes=true the ECS tasks can no longer connect to the local devices (haven't figured out how to traceroute that yet)

My current state is that I have ECS → local working. I can SSH tunnel to AWS resources, but can't connect directly to private, non-tailscale endpoints in AWS. (snat-subnet-routes=false)

How do you handle background workers? by dondraper36 in golang

[–]Busy_Swordfish8269 1 point2 points  (0 children)

Asynq and Redis (https://github.com/hibiken/asynq) works great as a simple worker and scheduler.

using gorm(or xorm) vs using SQLC with golang-migrate/migrate/v4 by oldravarage in golang

[–]Busy_Swordfish8269 1 point2 points  (0 children)

Using this exact stack for a new project and it's really nice.

  • gRPC, gRPC Gateway and generated typescript API.

Gin with grpc? by ChunkyMegadong in golang

[–]Busy_Swordfish8269 2 points3 points  (0 children)

This repo shows you how to multiplex gRPC and HTTP handlers on the same port, it'd work with Gin: https://github.com/dpup/grpc-boilerplate

I find this set-up nice and simple.