@farcaller@fstab.sh

comments

• I actually don’t remember off the top of my head, huh. The output chain is not the one I use often. I’d think nft add rule tracing filter output ip protocol icmp icmp type echo-reply meta nftrace set 1 would do it. Just make sure the priority is low enough again.

  on nftables: Can't ping my own server in c/selfhosted@lemmy.world · 4d ago

• It is accepted just fine then. You might want to check the reverse, start in top of the output chain and trace the echo reply.

  on nftables: Can't ping my own server in c/selfhosted@lemmy.world · 17 Sep 2026

• nftables offers a very decent debugging interface. First, you add a rule to trace the packet (a new chain with high priority works best). Usually I’d suggest to add those rules by hand instead of relying on declarative configs:

  nft add table ip ping_trace
  nft 'add chain ip ping_trace prerouting { type filter hook prerouting priority -301; policy accept; }'
  

  Then you add the actual tracing rule there with the shape to match the incoming traffic:

  nft 'add rule ip ping_trace prerouting icmp type { echo-request, echo-reply } meta nftrace set 1'
  

  now you can run nft monitor trace and see the decisions made for the matching packets. Remember to delete the ping_trace table afterwards to clean up.

  on nftables: Can't ping my own server in c/selfhosted@lemmy.world · 16 Sep 2026

• First on how to get an ASN: you can buy it for reasonably cheap from a LIR. Some will even toss a free /48 with that. Happy to offer names in private so that there’s no advertising. Expect a budget quoted above.

  Once you have an ASN, you need to get an upstream - actually two as RIPE mandates at least two (otherwise why’d you need an ASN). Some LIRs would offer transit with ASN purchase. You can upstream via your ISP, if they allow you to (that’s very rare). Another option is a tunnel (there are free and paid ones) or a VM somewhere (some cloud providers offer to set up bgp with VMs they host). Generally, free ones are enough for basic stuff. Not much bandwidth and oftentimes IPv6 only, but you don’t pay anything either. Besides, you can ask around in various network related chats. Practically, I can offer ip transit with some marginally low burstable bandwidth, and that’s pretty common. You can look/ask around https://discord.gg/ipv6 for example.

  For getting ASN to your homelab you’re looking at a tunnel option, most probably. Great if you have static ipv4 - allows you to use more common tunnels, but is still doable with a floating IP (e.g. check bgptunnel).

  on How do people handle authoritative DNS redundancy for their self-hosted workloads? in c/selfhosted@lemmy.world · 5 Sep 2026

• BGP anycast person here. If you have any presence in the region RIPE operates in then the pricing is within the homelab reach. ASN and a block of /48 would be about 70 EUR/year.

  Alternatively, something like route64 would happily tunnel you IPs they announce for about 2 EUR/month.

  on How do people handle authoritative DNS redundancy for their self-hosted workloads? in c/selfhosted@lemmy.world · 4 Sep 2026

• I’ve used VM in my homelab for a while - it’s genuinely a smaller ram footprint, especially on the ingress path. You can even scale query separately if required.

  on Observability in c/selfhosted@lemmy.world · 20 Aug 2026

• I’d suggest VictoriaMetrics over pure Prometheus - better ram footprint is pretty useful nowadays.

  on Observability in c/selfhosted@lemmy.world · 20 Aug 2026