Smash

joined 2 years ago

Dafür gibts dann bald die Maut

Keine Sorge, du verpasst nichts, die neue UI ist ein riesen Haufen dampfende Scheiße

Why only a short anime... there are still close to none Yuri animes

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

Talented Cosplayer and pianist, huge respect

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

Fucking censorship for the China/US

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

But another instance also increases the required bandwidth and data usage for all other federated instances

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

This reads like a conversation by 12 year olds in a discord RP channel

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

Some are very easy to get, but you don't want those

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

Monogatari Series and Railgun

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

Her oldest videos don't ^^ I have nothing against suggest content on YT, but Google always tries to babysit and degrades everything to YT kids level

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

Except, it isn't, .NET Core is an open source framework by the .NET Foundation

 
 

Wie hosted ihr eure Instanzen?

43
[solved] WireGuard VPN IP Issue (lemmy.self-hosted.site)
submitted 1 year ago* (last edited 1 year 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 ›