Selfhosted

40209 readers

732 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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

wireguard on freebsd (lemmy.sdf.org)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/selfhosted

6 comments fedilink hide all child comments

I am trying to setup a wireguard server on freebsd using this guide. the only thing i've done different is make the AllowedIPs 0.0.0.0/0

I seem to have messed something up because when I have wireguard running, i cannot ping or curl anything from the server. It doesn't take down the machine though, I am still able to ssh into the server.

I still have yet to get the client to actually connect, but i assume this networking issue is a potential cause. googling doesn't seem to help me find anyone with my same issue.

my wg0.conf is as follows

[Interface] Address = 10.96.100.1/32 # address the server will bind to

ListenPort = 51820 # listener port

PrivateKey = [redacted]

[Peer] #phone

AllowedIPs = 0.0.0.0/0

PreSharedKey = [redacted]

PublicKey = [redacted]

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

[–] [email protected] 2 points 1 year ago

Yeah I've always found that AllowedIPs name a little bit misleading. It is mentioned in the manpage:

A comma-separated list of IP (v4 or v6) addresses with CIDR masks from which incoming traffic for this peer is allowed and to which outgoing traffic for this peer is directed.

But I think it's a little funny how setting AllowedIPs also configures how packets are routed. I dunno.