Smash

joined 2 years ago
[–] Smash@lemmy.self-hosted.site 33 points 5 days ago

Verständlich, ein Webserver mit 301 Weiterleitungen verbraucht ja auch unvorstellbar viele Ressourcen, nicht etwa wie KI

[–] Smash@lemmy.self-hosted.site 7 points 6 days ago (1 children)

Danke ohne den grünen Pfeil auf den roten Kreis hät ichs einfach übersehen

Ein E-Auto? Niemals

[–] Smash@lemmy.self-hosted.site 1 points 2 weeks ago

Not the whole anime, but it happens to me at every story arc in gintama

[–] Smash@lemmy.self-hosted.site 4 points 3 weeks ago (1 children)

Und Wasser ist nass

[–] Smash@lemmy.self-hosted.site 2 points 3 weeks ago (1 children)

GJ-bu maybe? Yoshiraku and Yuyushiki sound similar too

[–] Smash@lemmy.self-hosted.site 2 points 3 weeks ago

Das ist warum wir keine schönen Dinge haben können

[–] Smash@lemmy.self-hosted.site 7 points 1 month ago

It's continuing? Fuck yeah! Hopefully we'll see Hanekawa again too

[–] Smash@lemmy.self-hosted.site 1 points 1 month ago

I really hoped for a release this year 🥲

[–] Smash@lemmy.self-hosted.site 1 points 1 month ago

A lot of shows for MD PTWL, but still no 'The angel next door spoils me rotten season 2'...

[–] Smash@lemmy.self-hosted.site 3 points 1 month ago

The entirety of Kill La Kill in one go on new years eve, wouldn't recommend (24 EPs are too much)

And Vivy which I watched with my mom, was like a long movie

[–] Smash@lemmy.self-hosted.site 4 points 1 month ago (1 children)

Sadly, AFAIK it's still necessary to build a grass cache before generating grass LODs, unpractical for my ever changing and huge modlist

 
 

Wie hosted ihr eure Instanzen?

43
[solved] WireGuard VPN IP Issue (lemmy.self-hosted.site)
submitted 2 years ago* (last edited 2 years ago) by Smash@lemmy.self-hosted.site to c/selfhosted@lemmy.world
 

I tried debugging this issue for hours now but I'm out of ideas. I'm running WireGuard on my OPNsense firewall. It worked flawlessly for about a year but now I've gotten a really strange issue.

Here is the Client config: Client

As you can see, the Client got assigned the IP 10.10.10.11/32

I can ping this IP and the Client can access all Server in the network when connected with the VPN.

BUT when it connects to hosts in the LAN, it doesn't use it's assigned 10.10.10.11 IP but the public IP of the OPNsense firewall instead.

This also doesn't happen every time, but most of the time. I assume that it's perhaps a ARP issue, but I don't know why the OPNsense firewall sends its public IP (WireGuard Endpoint IP) instead of the Clients assigned IP at all.

The IP the Client should use in the LAN (virtual VPN IP): virtual IP

The IP which the Client actually uses (Endpoint IP): Endpint IP

Every help would be greatly appreciated!


EDIT: I removed and re-added the peers in OPNsense and it works again, at least for now. Maybe something broke during an update(?). I will report back if this already fixed the issue (the problem can sometimes be hard to replicate)

EDIT 2: The issue reappeared. But I noticed, that I now have the problem only with Gecko based browsers, chromium works fine (tested on Android).

EDIT 3: The issue only appeared with Gecko based browsers because mine are configured to use some public DOH DNS, which resolved my internal host FQDNs to public IPs, not private ones from the LAN

 
view more: next ›