• 3 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: May 13th, 2025

help-circle




  • If you’re not going the VPS route it’s even easier. Pangolin handles the wireguard tunnel for you with a docket container running newt. Very straightforward.

    My goals have been:

    1. Avoid opening ports on my home network.
    2. Don’t require people using my services to join my Tailnet (or some other VPN).
    3. Require 2FA/passkeys (via Authentik for the moment) on anything that’s publicly accessible.

    There’s plenty of YT stuff out there for Pangolin, but I haven’t seen a lot for their cloud service. Personally, I prefer it to self-hosting it. Similar to tailscale, the free tier meets my needs, and their security team is (hopefully) more competent and better staffed than… me.

    Of course, you get what you pay for, but I see this as a similar position as Tailscale & Cloudflare. With my free account, I’m piggy-backing off the security infrastructure of their enterprise offerings. Obviously I don’t get all the fine-grained controls of those tiers, but like the other two companies, they have a reputation to uphold, and from that perspective a breech is a breech. Even if it only affects free tier users, it makes them look bad.


  • Pangolin handles proxying (it runs traefik under the hood) and cloudflare-like protection (crowdsec). I did self-host it, but the free tier does what I need.

    It does set up a wireguard tunnel between itself and the Newt resources you set up. That’s hard for proxy traffic. I have Tailscale set up for any other traffic between my resources.

    I asked a similar question as you a few months ago (I think in this community), and one of the responses kind of put the fear in me. I went forward anyway, and never really did anything with my VPS. I’m still setting this new arrangement up, but so far really happy with it.


  • I used swag, dockerproxy, and cloudflare in the past. That allowed me to run things without exposing ports on my home router.

    I recently moved to Pangolin cloud. Still not exposing any ports on my home server. Also repositioned my VPS to use pangolin as well. Haven’t hashed out the details, but the idea will be to allow port 443 on public IP, and anything else over tailnet.

    Moral of the story: look very hard for ways to do what you want to do without having to expose ports on your router. Unless you want your hobby to become your second job. I enjoy self hosting. I don’t enjoy being paranoid about some script kiddie pummeling my setup with some AI-generated attacks while I’m asleep.




  • ClownStatue@piefed.socialtolinuxmemes@lemmy.worldNoice
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    3 months ago

    Maybe someone who only used csh? I can’t remember if ^a is a default in that shell. I thought it started with ksh or bash.

    ETA: just looked it up and I’m dumb. Comes from emacs (of course) and looks like it was introduced in bash. I guess I could claim ignorance, being a VI man, but I actually knew at some point that it came from emacs. I think I can count on 1 hand the number of times I’ve used emacs






  • ClownStatue@piefed.socialtomemes@lemmy.worldTitle
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 months ago

    You’re not wrong, but I think the point is highlighting 1 extremely privileged little girl’s accomplishment without bothering to mention that entire populations within their own country accomplish the same thing with significantly less help.

    Nothing against her at all. I’m all for people being smart and accomplished, regardless of class or circumstance. But given the general sentiment against immigrants in most parts of the world, this article is the fluffiest of fluff pieces when you think for a second about what it could have done to illustrate the similar accomplishments of far far less fortunate children.



  • I was looking for that. Your note jogged my memory and I was able to find it. Strangely, the device was saying that it was being interviewed. I’ve rebooted home assistant again. When I tried to reinterview, it fails immediately. I see the following in the log:

    2026-04-07 20:58:16.157 CNTRLR   [Node 009] Beginning interview - last completed stage: None
    2026-04-07 20:58:16.158 CNTRLR   [Node 009] new node, doing a full interview...
    2026-04-07 20:58:16.159 CNTRLR » [Node 009] querying protocol info...
    2026-04-07 20:58:16.159 DRIVER   one or more queues busy
    2026-04-07 20:58:16.160 DRIVER » [REQ] [GetNodeProtocolInfo]
    2026-04-07 20:58:16.160 SERIAL » 0x010500410009b2                                                     (7 bytes)
    2026-04-07 20:58:16.163 SERIAL « [ACK]                                                                   (0x06)
    2026-04-07 20:58:16.165 SERIAL « 0x010a0141d39c0104100100ee                                          (12 bytes)
    2026-04-07 20:58:16.166 SERIAL » [ACK]                                                                   (0x06)
    2026-04-07 20:58:16.167 DRIVER « [RES] [GetNodeProtocolInfo]
    2026-04-07 20:58:16.167 CNTRLR « [Node 009] received response for protocol info:
                                     basic device class:    Routing End Node
                                     generic device class:  Binary Switch
                                     specific device class: Binary Power Switch
                                     node type:             End Node
                                     is always listening:   true
                                     is frequent listening: false
                                     can route messages:    true
                                     supports security:     false
                                     supports beaming:      true
                                     maximum data rate:     100000 kbps
                                     protocol version:      3
    2026-04-07 20:58:16.168 CNTRLR   [Node 009] Interview stage completed: ProtocolInfo
    2026-04-07 20:58:16.169 CNTRLR » [Node 009] pinging the node...
    2026-04-07 20:58:16.170 DRIVER » [Node 009] [REQ] [SendDataBridge]
                                      source node id:   1
                                      transmit options: 0x01
                                      callback id:      83
                                     └─[NoOperationCC]
    2026-04-07 20:58:16.170 SERIAL » 0x010f00a900010009010001000000005302                                (17 bytes)
    2026-04-07 20:58:16.175 SERIAL « [ACK]                                                                   (0x06)
    2026-04-07 20:58:16.178 SERIAL « 0x010401a90152                                                       (6 bytes)
    2026-04-07 20:58:16.179 SERIAL » [ACK]                                                                   (0x06)
    2026-04-07 20:58:16.180 DRIVER « [RES] [SendDataBridge]
                                       was sent: true
    2026-04-07 20:58:16.234 SERIAL « 0x011d00a953010005007f7f7f7f7f00010100000000020300007f7f7f7f7f1d    (31 bytes)
    2026-04-07 20:58:16.235 SERIAL » [ACK]                                                                   (0x06)
    2026-04-07 20:58:16.236 DRIVER « [REQ] [SendDataBridge]
                                       callback id:            83
                                       transmit status:        NoAck, took 50 ms
                                       routing attempts:       3
                                       protocol & route speed: Z-Wave, 40 kbit/s
                                       routing scheme:         Direct
                                       TX channel no.:         1
    2026-04-07 20:58:16.237 CNTRLR   [Node 009] The node did not respond after 1 attempts, it is presumed dead
    2026-04-07 20:58:16.238 CNTRLR   [Node 009] The node is dead.
    2026-04-07 20:58:16.240 CNTRLR   [Node 009] ping failed: The node did not acknowledge the command (ZW0204)
    2026-04-07 20:58:16.241 CNTRLR   [Node 009] Interview attempt (1/5) failed, node is dead.
    

    Tried rebuilding routes to the node and saw similar node is not responding messages in the log. Strange that the physical switch still works though.