Selfhosted

39640 readers

298 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

ufw's rules is not working (lemmy.ml)

submitted 5 days ago by [email protected] to c/[email protected]

36 comments fedilink hide all child comments

I want to set up ufw on my server, but something wrong here. Even when I trying to block 22 port ssh still working and nothing changing. I have ufw enabled, but nothing works.

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

[–] [email protected] -1 points 5 days ago (2 children)

, no, I want to open, for example this port, but:

[–] [email protected] 7 points 5 days ago (1 children)

Do you have something listening on port 52038 that will respond to a port scan? If not it will report as closed.

[–] [email protected] 1 points 5 days ago* (last edited 5 days ago) (2 children)

It's my port for wireguard and here what I can't understand: when I blocking port for this wireguard service I still can use wireguard even if ufw deny it.

[–] [email protected] 5 points 5 days ago (1 children)

Wireguard appears as closed unless it receives the proper packet.

[–] [email protected] 1 points 5 days ago

that's what I looked for

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

Is wireguard incoming or outgoing from the machine you're trying to block it on?

[–] [email protected] 1 points 5 days ago (1 children)

outgoing, I guess. I mean, it's on my vps which I want to use for vpn

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

Make sure you're creating a block rule specifically on outgoing in that case.

[–] [email protected] 1 points 5 days ago (1 children)

when I just use ufw allow [port] command it'll not work?

[–] [email protected] 3 points 5 days ago

Outgoing should already allow everything, so no need to specifically allow it.

[–] [email protected] 4 points 5 days ago (1 children)

That's a website tool checking? It's almost certainly only going to check TCP, since most of them don't do anything with UDP because it's... more complicated.

You may need to find an alternate way to do that, something like iperf or netcat (nc -u ip port)

[–] [email protected] 2 points 4 days ago* (last edited 4 days ago)

nmap works great for this

traceroute might also be usable vith the -p switch I guess?