mastodon.zunda.ninja is one of the many independent Mastodon servers you can use to participate in the fediverse.
Zundon is a single user instance as home of @zundan as well as a test bed for changes of the code.

Administered by:

Server stats:

1
active users

#wireguard

0 posts0 participants0 posts today
Replied in thread

@lina we had a 1476 bytes MTU on the PPPoE interface. I would have expected a 1396 bytes MTU on the #WireGuard tunnel interface, but ping's with various sizes showed it had to be 1392 instead. Does that make sense, would the padding explain that?

alright #NixOS fediverse (or perhaps this is really a broader #Linux question) - I've got a NixOS #container (that's a systemd-nspawn container for you non-NixOS folks) running in a network namespace so that all of its traffic goes out over a #WireGuard interface. this works great and is awesome.

there's a problem, though. the container exposes some network services that I'd like to access from the host. normally they'd either magically be available (privateNetwork=false;) or they could be explicitly mapped. unfortunately, I don't think either of these work correctly in NixOS when netns is involved.

I can think of two options:

1. go through the effort to stand up another veth device for host/guest-only traffic

or 2. hack something together with netcat and shared filesystem space

in typing this out, I think I'm finding myself leaning towards the additional interface, though it's likely to be a pain.

is there a common pattern for these situations, or a solution that I'm not thinking of?

Hey @digitalcourage , ich habe vor einiger Zeit (anfangs nur für mich quasi als "Doku") zusammengeschrieben, wie ich meine #privatsphare versuche zu schützen, indem ich Werbung, Tracker usw. mit einem DNS-basierten Blocker für alle meine Geräte zentral abwehre.

Und weil ich das nicht nur zuhause für die ganze Familie haben wollte, habe ich das noch für unterwegs mit einem #Wireguard VPN auf meiner eigenen VM im europäischen Ausland garniert.

Und hier ist das Resultat meiner Gedanken und was ich warum und wie gemacht habe: thomasmerz.github.io/pihole-wi

Was haltet ihr und die anderen davon?

pihole-wireguard-knowhowpihole-wireguard-knowhowMy Setup for Pi-hole at home and in the cloud to be used with WireGuard for the whole family.

WireSep v0.10.0 is here. WireSep is a privilege separated implementation of WireGuard for OpenBSD.

This release contains a major effort to clarify all log messages so that looking at the logs no longer makes your eyes bleed. Furthermore it contains some cleanups found with GCC 8 and Clang Static Analyzer.

Thanks to everyone reporting back issues.

ChangeLog: github.com/timkuijsten/wiresep

github.comtimkuijsten/wiresepA privilege separated implementation of WireGuard for OpenBSD - timkuijsten/wiresep

#wireguard can create a point-to-point VPN network. Is that something that could be used to replace a #SSH connection?

Is there a concealable near future where we "wireguard" in to remote servers to administer them instead of SSHing in? If so, what would be the advantages/disadvantages of this versus current practice with SSH?

(I'm very open to the idea that I've misunderstood something fundamental and this question is really dumb/not-even-wrong)