That’s for logging into the web GUI IIRC, not for authorizing a connection from wg client to wg server.

Source? I remember a follow up to a post about that saying it was a misinterpretation of their T&Cs

I have a reverse proxy, but that won’t do ALL traffic, right? Just http or https?

Like if I want to ssh into the different servers, it won’t handle that, will it?

I have a reverse proxy, but that won’t do ALL traffic, right? Just http or https?

Like if I want to ssh into the different servers, it won’t handle that, will it?

Final Update: it’s the hardware, I think it was overheating in general, but also the SSD seems to have been dying and the ram wasn’t particularly reliable, possibly due to the heat.

Good lesson not to buy the cheapest thing from AliExpress! My new box is working great.

UPDATE: It crashed again today, and I was able to pull some logs and check the temperature at the time of the crash. (91 degrees which dropped to 71 degrees right before crashing?

From system log

<13>1 2024-03-13T18:30:44-04:00 OPNsense.my.home opnsense 44846 - [meta sequenceId="1192"] /usr/local/etc/rc.newwanipv6: No IP change detected (current: IPV6ADDRESSREDACTED, interface: wan)
<13>1 2024-03-13T18:30:53-04:00 OPNsense.my.home opnsense 60522 - [meta sequenceId="1193"] /usr/local/etc/rc.newwanipv6: No IP change detected (current: IPV6ADDRESSREDACTED, interface: wan)
<45>1 2024-03-13T22:12:44-04:00 OPNsense.my.home syslog-ng 10182 - [meta sequenceId="1"] syslog-ng starting up; version='4.6.0'
<13>1 2024-03-13T22:12:45-04:00 OPNsense.my.home kernel - - [meta sequenceId="2"] ---<<BOOT>>---
<13>1 2024-03-13T22:12:45-04:00 OPNsense.my.home kernel - - [meta sequenceId="138"] WARNING: / was not properly dismounted

From dmesg

arp: 192.168.1.61 moved from someMAC to anotherMAC on igc1
arp: 192.168.1.61 moved from anotherMAC to someMAC on igc1
WARNING: / was not properly dismounted
WARNING: /: mount pending error: blocks 40 files 4

I mean, I’m not saying that errors on the drive are the CAUSE of the problem, more likely a symptom, but it does look like it just straight up crashed, right?

Dmesg doesn’t go back very far, does it? I only see the current boot and the one before that, which was a normal shutdown.

I believe I was able to see the last logs before the system turned off last time, and the last messages were syncing discs and all buffers synced, which I would have expected to be part of a normal shutdown.

If it happens again I’ll be sure to get the logs before the crash or shut down and save it to a file.

Cool, that’s exactly what my plan is currently. I will eventually run all the cables but I want to drop in this firewall and start learning it in the meantime.

I may even go the route of some managed switches and WANs that do support multiple SSIDs on different VLANs, but first I want to get comfortable with my new single network.

That is what I have been planning per my other comments.

Modem to WAN port of firewall, LAN port of firewall to wireless router in AP mode, other lan ports to other devices?

Could you please explain in more detail? The goal is to plug my firewall directly in, as I understand it.

Worst case I’ll just use the 4 LAN ports on the TPLink and leave the WAN on the TPLink unused

That would be great, and if the WAN port becomes a LAN port, even better. I don’t see anything about that in the manual, but I’ll cross my fingers

Sopuli seems to be down, so responding from a different account.

Yeah, it’s actually that there isn’t power for the Celeron box where all the other Ethernet currently is.

Just so I’m understanding, why would all traffic need to go to my router (do you mean the opnsense one or the tplink one) twice? Wouldn’t it go Device -> Switch -> opnsense -> modem > internet? Or for my intranet communications, Device1 -> switch -> opnsense -> switch -> device2