Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)CB
calm.like.a.bomb @ clmbmb @lemmy.dbzer0.com
Posts
8
Comments
376
Joined
2 yr. ago

  • It's the same with people asking me why I don't buy bluetooth headsets and insist on having wired headphones. I don't want to buy something extra when I already have a pair of VERY GOOD headphones and audio signal is always better on wire - even with lossless audio on bluetooth (which is not yet supported by (m)any devices).

  • That's how I started too. I used Aegis for almost two years. Then I found out about Authenticator Pro and decided to give it a try. The nice thing is that it can import an Aegis export file, so it's easy to get started. Give it a try and see if you like it.

  • If they're a fad, they've been a fad for over 35 years, so no longer a fad. Get it?

    I don't understand articles like this. Terminal multiplexers are tools that help people. And they're great tools especially when you work in environments where persistent sessions save your ass.

  • Coming back to this: it was a case of "did you turn it off and then back on?" I did some server upgrades a day before setting up wireguard and it's possible there were some changes that needed a reboot. I just rebooted today and everything works as expected.

  • Try changing your NAT rule to

    “iptables -t nat -A POSTROUTING -s 10.11.13.0/24 -o eth1 -j MASQUERADE”

    Also try changing your AllowedIPs to 10.11.13.0/24

    In fact I don't need to access anything on 10.11.12.13.0/24 - that's the peer to peer wireguard network. I want to be able to connect to any host on 10.11.12.0/24. Adding this network to AllowedIPs I'm now able to connect to .77 (which is my server) and to .1 (the router), but not on any other hosts in the house.

    The other issue may be the ability of the host/server to reach the IP address of the pihole macvlan interface. Have a look at this page, it’s helped me out before -> https://adventurenotvacation.com/2020/12/01/docker-macvlan-and-debian/

    This is done. I followed the instructions here: https://wiki.omv-extras.org/doku.php?id=omv6:omv6_plugins:docker_compose#how_to_create_a_vlan_with_ip_on_the_same_lan_as_the_host which are the same thing as the article you linked.

    ... I'm still looking into things.