Linux

48176 readers

951 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

[Solved] Wireguard blocks ssh/smb :( (www.digitalocean.com)

submitted 1 year ago* (last edited 1 year ago) by Spider89@lemmy.world to c/linux@lemmy.ml

15 comments fedilink hide all child comments

This was manually solved, I didn't check any other comment till the issue was fixed.

Take a look at my comment.

Thank you all for helping!

Hello.

I have wireguard set but the second it runs, services like ssh (22) and smb (455/445?) stop working.

nmap thinks my system is down.

Here is my config, I followed debian's guide since my server is Deb12:

[Interface]
Address = 192.168.1.120/24
SaveConfig = true
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -t nat -A POSTROUTING -o wlp1s0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -t nat -D POSTROUTING -o wlp1s0 -j MASQUERADE
ListenPort = 51820
PrivateKey = XXX

[Peer]
PublicKey = xxx
AllowedIPs = 192.168.1.230/32
Endpoint = 192.168.1.230:50104

No extra config was made.

you are viewing a single comment's thread
view the rest of the comments

[–] Lem453@lemmy.ca 1 points 1 year ago (1 children)

Why is this needed? I have the minimal config for both server and client and smb and ssh bith work without issue.

[–] Spider89@lemmy.world 1 points 1 year ago (1 children)

Would you mind sharing the config (without keys)?

This is my first time using WG.

[–] Lem453@lemmy.ca 1 points 1 year ago* (last edited 1 year ago) (1 children)

There is nothing special about the config, it's the most basic config you can have as shown in the example at the bottom of this page.

https://docs.opnsense.org/manual/how-tos/wireguard-client.html

The part that was a bit complex is the 'server' setting. My server is on my router (opnsense) so you need to opnsense specific settings.

I suspect the reason you need the extra stuff is because of how the Debian server is setup so that stuff will vary if you ever try to run another 'server' node. (I put server in quotes because wireguard doesn't actually have server and client as a concept)

[–] Spider89@lemmy.world 1 points 1 year ago

I believe it's automated.

The server/client thing always confused me.