#Tag
WG Tunnel
An WireGuard & AmneziaWG Android client with auto-tunneling, lockdown & proxying.
With auto-tunneling, tunnels automatically turn on, off, or change based on your network.
Available on its own F-droid repo, IzzyOnDroid, and Google Play.
What's the common wisdom regarding #Ubuntu #Linux and systemd-resolved, dnsmasq, and NetworkManager?
Had a weird thing happen where a #Wireguard tunnel didn't go up but DNS was still trying to connect to the DNS server over the WireGuard tunnel and was failing.
Is there any way to stop the DNS madness? It looks like they're both clobbering each other.
WG Tunnel
An WireGuard & AmneziaWG Android client with auto-tunneling, lockdown & proxying.
With auto-tunneling, tunnels automatically turn on, off, or change based on your network.
Available on its own F-droid repo, IzzyOnDroid, and Google Play.
What's the common wisdom regarding #Ubuntu #Linux and systemd-resolved, dnsmasq, and NetworkManager?
Had a weird thing happen where a #Wireguard tunnel didn't go up but DNS was still trying to connect to the DNS server over the WireGuard tunnel and was failing.
Is there any way to stop the DNS madness? It looks like they're both clobbering each other.
I did some more digging on how to get my Tailscale traffic to bypass a Wireguard VPN which otherwise routes all internet traffic on OpenWrt without using the 'pbr' package, and found a rather strange document:
tl;dr it's definitely possible, but I'm going to have to bite the bullet and not use the simple "route all traffic over Wireguard and enable a 'killswitch' to prevent leaks" two-checkbox setup I've been using thus far.
I did some more digging on how to get my Tailscale traffic to bypass a Wireguard VPN which otherwise routes all internet traffic on OpenWrt without using the 'pbr' package, and found a rather strange document:
tl;dr it's definitely possible, but I'm going to have to bite the bullet and not use the simple "route all traffic over Wireguard and enable a 'killswitch' to prevent leaks" two-checkbox setup I've been using thus far.
@Luminex my own, using #wireguard
Has anyone run into an issue in #WireGuard in which the Endpoint is a fully qualified domain name (e.g. vpn.example.org:51820) and the tunnel won't work, but it will work if you put in the IP address (which is IPv4)? I wonder if it has to do with having both IPv4 and IPv6 stacks running and active at the same time on the client and it can't, for some reason our another, establish the tunnel correctly?
Has anyone run into an issue in #WireGuard in which the Endpoint is a fully qualified domain name (e.g. vpn.example.org:51820) and the tunnel won't work, but it will work if you put in the IP address (which is IPv4)? I wonder if it has to do with having both IPv4 and IPv6 stacks running and active at the same time on the client and it can't, for some reason our another, establish the tunnel correctly?
wireguard-fpga: Full-throttle, wire-speed hardware implementation of Wireguard VPN, using low-cost Artix7 FPGA with opensource toolchain
wireguard-fpga: Full-throttle, wire-speed hardware implementation of Wireguard VPN, using low-cost Artix7 FPGA with opensource toolchain
Wireguard benchmark megathread for devices running OpenWrt
https://forum.openwrt.org/t/a-wireguard-comparison-db/187586
Wireguard benchmark megathread for devices running OpenWrt
https://forum.openwrt.org/t/a-wireguard-comparison-db/187586
My daughter left home because University is located towns-away from here. This means she now has to connect her iPad to $HOME in order to watch the movies that are hosted in our local VOD system.
Yet another #OpenBSD and #Wireguard user that don’t even know about it. She only knows that she uses a #VPN and that it’s not NordVPN.
Imagine I have a couple VPNs+NAT and a few socks proxies (ssh tunnel, shadowsocks, vless, etc). Can you suggest a good way to monitor the "connection quality" of each of them? (on my local machine)
I want to easily see, which are degraded (usually due to ISP/gov doing DPI and blocking related traffic) and which are nice and healthy.
Cc: @dlakelan
#proxy #i2p #tor #freedom #network #networking #socks #dpi #wireguard #vless #shadowsocks #AskFedi #AskLemmy
OMG #WireGuard can be a pain to debug but OMG it works well once all is sorted.
The work on #EU_OS continues. In the last days, the Proof-of-Concept pages at https://eu-os.eu/poc/ have received a few updates on provisioning, branding and thoughts on user data backups. Open questions and issues are listed at https://gitlab.com/eu-os/eu-os.gitlab.io/-/issues
Please lend us your helping hand, reshare ♻️ and spread the word 🗣️!
1/3
2/3 Topics #EU_OS needs help with:
1) What is the best way to backup user data for Linux EU OS users? https://gitlab.com/eu-os/eu-os.gitlab.io/-/issues/46 #borgbackup #btrfsbk #btrfs#nextcloud
2) How can unattended deployment with #foreman look like during pilot stage (thus without reconfiguring the network/DHCP yet)? https://gitlab.com/eu-os/eu-os.gitlab.io/-/issues/39 #foreman
3) How can a modern VPN provide extra security for people in home offices or on business trips? https://gitlab.com/eu-os/eu-os.gitlab.io/-/issues/47 #tailscale #headscale #rosenpass #wireguard #openvpn
How are you integrating #WireGuard with an identity provider like OpenID, MS, or Goog for MFA?
welp, my latest Fedora KDE update borked my Wireguard installation. No discernable errors. It just... won't connect to its peer.
Maybe it's time to do something other than Fedora...
A space for Bonfire maintainers and contributors to communicate
