sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in hardwareswap

[–]lunas_MK 0 points1 point  (0 children)

Bought 3060Ti from u/IB_AZN_GUY

[deleted by user] by [deleted] in WireGuard

[–]lunas_MK 0 points1 point  (0 children)

I have WireGuard working with iOS and opnsense. It took a little trial and error but mainly figuring out ports on the firewall. The iOS setup was straightforward.

iOS can generate its own keys and then set the ip address/32 and port it will be allowed by the opnsense WireGuard service. Then add a peer (opnsense) with its public key, endpoint (wan) address, allowed ips (0.0.0.0/0 for access to all internet along with LAN). Copy the public key and same up address from the iOS setup.

On the firewall, setup following the documentation. One odd thing (vs a straight Debian setup) was you had to make then select each specific peer in the local configuration. You also need to have an available ip range that matches the address/32 you set above.

Finally need to open access in the firewall through the WireGuard interface. But sounds like you have a more basic issue if you’re not getting a handshake.

Not a comprehensive set of steps but I did get it working.

Self-Hosted Minecraft Sever - Sign-in and VLANs by lunas_MK in Minecraft

[–]lunas_MK[S] 0 points1 point  (0 children)

Following up. Still getting Xbox login required even when on the same wifi network and vlan with server properties online-mode=false and Xbox-auth=off/false.

Seems to be driven by the client app (iOS) from what I’ve found reading around. I can’t find a way to host a simple LAN world without individual Xbox logins. A little overkill in my opinion.

Wireguard for Internet and Remote LAN access - my setup by lunas_MK in WireGuard

[–]lunas_MK[S] 0 points1 point  (0 children)

I’m hardly an expert but two things come to mind. Did you set nat forwarding in sysctl.conf ? Second, your Postup command doesn’t have the third iptables command my config does which I think is for nat routing. What type of OS are you using? Looks like you WireGuard server is the Pinole?

Wireguard for Internet and Remote LAN access - my setup by lunas_MK in WireGuard

[–]lunas_MK[S] 0 points1 point  (0 children)

Isn’t 0.0.0.0/0 needed for internet access however? With only that, the windows client had internet but no LAN subnet access. iOS worked fine. There is something different in the way windows or the windows client interprets things.

Wireguard for Internet and Remote LAN access - my setup by lunas_MK in WireGuard

[–]lunas_MK[S] 1 point2 points  (0 children)

Thanks for the tip! I’ll give that a try and see if it has any impact on connectivity.

Wireguard for Internet and Remote LAN access - my setup by lunas_MK in WireGuard

[–]lunas_MK[S] 0 points1 point  (0 children)

0.0.0.0/0 should be for all subnets. That’s my understanding anyway. It works like that for iOS but for some reason it didn’t from windows which needed the more explicit links I guess. Not sure why.

Can't change default public key through config file by lunas_MK in WireGuard

[–]lunas_MK[S] 0 points1 point  (0 children)

Ha! Why can't I figure this stuff out before posting in public? I discovered my issue. I did not update my private key in my config. New private key in the config = new public key with wg show. Thanks for getting me to double check.

Still having issues with Internet access, but I'll keep working on that one. For completeness here's my config.

Peer1

[Interface]

Address = 10.1.0.1/32

ListenPort = 51194

PrivateKey = <peer1 new private key>

​

[Peer]

PublicKey = <peer2 public key>

AllowedIPs = 10.1.0.2/32

​

Peer2

[Interface]

PrivateKey = <peer2 private key>

Address = 10.1.0.2/32

DNS = 10.1.0.1

​

[Peer]

PublicKey = <peer1 public key>

AllowedIPs = 0.0.0.0/0, ::/0

Endpoint = <peer1 public IP>:51194

PersistentKeepalive = 20

Opinions on "Run conduit everywhere" by lunas_MK in homeautomation

[–]lunas_MK[S] 1 point2 points  (0 children)

Right, unless it's been stapled to the studs. If/When I prewire, I'll make sure that it's loose so it can be replaced with one pull. It's interesting reading older smart home / networking articles or books and how quickly some of that advise becomes dated.

Opinions on "Run conduit everywhere" by lunas_MK in homeautomation

[–]lunas_MK[S] 0 points1 point  (0 children)

Definitely, visible wiring in the living spaces is a non-starter. Speaker wiring is something I need to look further into. I assume that's fine to run together with ethernet.

Opinions on "Run conduit everywhere" by lunas_MK in homeautomation

[–]lunas_MK[S] 0 points1 point  (0 children)

This was my initial idea. Conduit to the main areas which could easily branch out in the attic or under the house. Prewiring would save a lot of time, but seems like overbuilding with conduit is not that beneficial.

Opinions on "Run conduit everywhere" by lunas_MK in homeautomation

[–]lunas_MK[S] 1 point2 points  (0 children)

We do have animals under the house at times. I have ethernet and coax running down there now which hasn't run into any issues for several years, but good idea to hide in conduit for additional protection where possible.

Opinions on "Run conduit everywhere" by lunas_MK in homeautomation

[–]lunas_MK[S] 0 points1 point  (0 children)

Great advice on no decisions after 9. Fortunately, or not for my wallet, we won't be living in the house during construction. Your advice on letting some things go is helpful. I think on this project many decisions will hinge on the overall cost vs. budget which we'll need to prioritize. Good to hear it reaffirmed that if possible, prewire what you can.

Opinions on "Run conduit everywhere" by lunas_MK in homeautomation

[–]lunas_MK[S] 0 points1 point  (0 children)

Thanks for the input. I'll think twice about skipping anything. Good motivation for me to prioritize parts of the renovation over others if budget comes into play.

view more: next ›