legoraft @ legoraft @lemmy.world

Posts

1

Comments

8

Joined

2 yr. ago

yeah tje 192.135.163.0 is changed, originally it was 192.168.0.1/24 iirc. Weird that there isn't anything wrong, because when.I use the internal IP of the cockpit machine with the port the cockpit instance is on, it doesn't show anything. Thanks for the help tho!

Here is my config file (I redacted the keys and changed up IP's just to be safe):

    
[Interface]
PrivateKey = [Redacted]
Address = 192.135.163.201/24
DNS = 192.135.163.1
DNS = fritz.box

[Peer]
PublicKey = [Redacted]
PresharedKey = [Redacted]
AllowedIPs = 192.135.163.0/24,0.0.0.0/0
Endpoint = 9xs.myfritz.net:51609
PersistentKeepalive = 25

  

I've tried this, but it didn't work. At home, I can access my cockpit server by typing the machines IP and port 8080. When I try this on the VPN though, it doesn't work. I can access my routers settings, but not the server.

The best thing would be if I can just type the local IP of my server in the browser and just get routed to my server when I have the VPN enabled

Thank you for the info! I'll take a look at tailscale and try to wrap my head around the wireguard thing. Thanks for the help!

Hi! I've done a bit more thorough googling, because of you I knew what to look for a bit better. I have a wireguard vpn on my fritz box router enabled, which allows me to connect to the vpn from my laptop.

I've read up on how to acces local devices and I found something about adding an IP to the "AllowedIPs" section, but I don't really get which IP I should add.

do you have the dotfiles to that bar somewhere?

that bar is amazing! What are you using?