Mastodawn

doctorzeromd Apr 11, 2024

Port forward to different IP based on destination address in opnsense

Port forward to different IP based on destination address in opnsense - Lemmy.World

cross-posted from: https://lemmy.world/post/14180956 [https://lemmy.world/post/14180956] > Hello all you lovely people! > > I’m trying to figure out if I can port forward to different servers based on the destination domain. > > I have a domain with a wildcard cert and I’d like to be able to route all traffic headed towards “1.domain.com [http://1.domain.com]” to a server I’m calling “1”. I’d still like traffic headed to domain.com [http://domain.com] to go to where it’s currently going, we can call this server “0”, and to be able to have a 2.domain.com [http://2.domain.com] or 3 or 4 in the future. > > I thought that having a port forward rule with: > interface: WAN > Protocol: any > source: any destination: a url alias including 1.domain.com [http://1.domain.com] > redirect target ip: local ip > > Would work, but it doesn’t seem to. Any tips?

Show thread

doctorzeromd Mar 16, 2024

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.

Show thread

doctorzeromd Mar 14, 2024

UPDATE: It crashed again today, and I was able to pull some logs and check the temperature at the time of the crash.

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?

doctorzeromd Mar 12, 2024

Determine shutdown cause in OPNSense

https://lemmy.world/post/13050803

Determine shutdown cause in OPNSense - Lemmy.World

Hi all, I’ve got a cheap Celeron box running OPNSense and it’s been pretty good so far, but I found twice that the device turned off at some point while I was at work, and I have been unable to figure out what’s causing it. The only change was that I enabled Monit to see if I could figure out what was causing crowdsec to stop sometimes but never ended up configuring anything. I’ve only been running it for a couple months though, so it’s possible that that is not related. I know that on a Mac (based on freebsd, right?) you can determine whether the shutdown reason was a hard shutdown, regular shutdown, or the power cable being unplugged. Is it possible to do that with OPNSense? I’d like to narrow it down to software or hardware ideally.