Smash

joined 1 year ago
[–] [email protected] 12 points 11 hours ago (8 children)
[–] [email protected] 1 points 2 days ago (1 children)

I tried it but it's pretty complex compared to tubesync and uses weird af filenames, unusable for media servers

[–] [email protected] 2 points 2 days ago (3 children)

I use tubesync, works great

[–] [email protected] 2 points 4 days ago

Lemon got pretty annoying this episode

[–] [email protected] 1 points 1 week ago

Same. Giri Harem and Alya-san are also pretty good

[–] [email protected] 3 points 1 week ago

Der Föderalismus ist so ein unfassbar beschissenes System, das könnte sich jede halbwegs intelligente Kreatur niemals ausdenken

[–] [email protected] 12 points 1 week ago

Pest vs Cholera

[–] [email protected] 8 points 2 weeks ago

Das passiert weil Google seine Monopolstellung ausnutzt und webfunktionen nicht standard konform implementieren

[–] [email protected] 2 points 2 weeks ago

Manche Ordner in Echtzeit mit GoodSync auf meine NAS welche alle 15min snapshots erstellt und nächtlich auf eine von zwei aus dem Safe kommenden HDDs sichert. Meinen Haupt PC monatlich mit DISK2VHD auf die NAS und mein Smartphone mit NeoBackup und Syncthing.

[–] [email protected] 18 points 2 weeks ago (1 children)

Who comes up with this?

[–] [email protected] 4 points 3 weeks ago

Not only the visuals, the VAs are also very good

 
 

Wie hosted ihr eure Instanzen?

46
[solved] WireGuard VPN IP Issue (lemmy.self-hosted.site)
submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]
 

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

89
Minah (i.ibb.co)
 
view more: next ›