• 66 Posts
  • 1.84K Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle








  • Absolutely. If they’re small, you can handle them with thick leather gloves if you absolutely have to. Little brown bat’s don’t have teeth that are long or sharp enough to penetrate the leather. That won’t stop them from grabbing ahold of your finger to let you know that they are not happy.

    Of course, it’s best to avoid to touching them at all if possible. Especially if they allow you to get close enough to touch them. That’s pretty unusual and can be an indicator of rabies.

    This little guy (pictured) found his way into my basement, heard a spider moving in a glue trap, and managed to get stuck in said trap. He flew safely back to his buddies after we worked out our differences and he had a snack and some water.







  • I want to make sure I understand your goal correctly. Here’s what I’m getting.

    1. You have a wire guard connection that you want to use for outbound traffic from your local LAN.
    2. You have a Debian box that serves at the client in this situation.

    Here’s the part where I’m a little fuzzy

    1. You want to connect to your local LAN using another wire guard connection and have WAN requests routed from clients connecting to your LAN (via wire guard) out the wire guard connection mentioned in #1.

    Did I get any part of that wrong?

    Edit: NVM. I saw your response to another comment that sounds like this is exactly what you want.

    This should be achievable via routing. I actually do the same thing. The main difference is all the work is done on my router which handles both wire guard connections and routing.

    At the minimim you’re going to need:

    • A NAT rule on your local router to port forward incoming wire guard requests on the WAN to your Debian box. **Assuming the Debian box is also the wire guard server.
    • An iptables DSTNAT rule on your Debian box to route local traffic to the LAN gateway.
    • An iptables DSTNAT rule on your Debian box to route outbound WAN traffic that does NOT originate from your Debian box to the gateway at the other end of the outbound wire guard connection.

  • Sounds like an interesting read. The premise makes sense. Take the washing machine for example. Before the advent of the automatic washer, women spent most of their time cooking and doing laundry. Incredibly time consuming manual labor.

    Washing machines freed up a ton of time but also require complex infrastructure to operate. Same for any other “time saving” appliance.

    The comforts and conveniences enjoyed by much of modern society are unparalleled by any other point in history but just maintaining all those comforts and conveniences is a ton of work in itself.