Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - OtterTech

#1
Thanks so much for your response! That makes sense I think.. So if my network is 192.168.100.0/32 (still learning subnets.. would it be /24?) I'd just add that to the "allowed IPs"? Again.. thanks for bearing with a newbie here. Also, when I ssh to the pi (or use filezilla) would I use the tunnel address the pi is given (10.0.0.6)?

Thanks again!
#2
I'm sure this is a low-interest low-priority question compared to the more involved post floating around, but I would SO appreciate a little guidance here. I'm considering running another wireguard instance and pointing it to the 10.0.0.0/32 network.. would that work?

Anybody willing to even point me in the right direction with a tutorial online? I've learned a ton from this community, and this is the first wall I've hit that I can't seem to figure out on my own.
#3
I have been using OPNsense for a couple years, though I am still very much a beginner, so please bear with me. Searched up and down for an answer to this but, can't quite figure it out.

Wireguard is configured on OPNsense and running beautifully with several peers (multiple phones, laptop, etc) connecting back to our home network. I just added a raspberry pi as a peer that is connected at my inlaws house (it's running a digital picture frame). I had thought that I could access it from home to toss on new photos via filezilla, but I can't access it (using it's address: 10.0.0.6). I'm sure this is an easy firewall rule, or some small "allowed IPs" situation, but I just can't figure it out on my own. Any tips? Easy fix?