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 - Famousjaxx

#1
I fixed it by doing something so totally unrelated to OPNSense that I'm actually more confused than before.

In the docker compose file for PiHole, I had to map not only port 53 on the host to port 53 internally, but also the hosts IP address. In this case of course the host is my Raspberry Pi.

So the config line went from this:
"53:53/TCP"
"53:53/UDP"


To this:
"192.168.117.200:53:53/UDP"
"192.168.117.200:53:53/TCP"


I found this suggestion on an extremely obscure forum after working out that my containers DNS resolution wasn't working when the DNS server was set to the PiHole host IP but would work if I set it to something externally like 8.8.8.8.

The real head scratcher is why did this work without issue when the TP Link router was installed?

After hours of troubleshooting this is one question I'm happy to walk away from unanswered.

Thanks all!
#2
Would appreciate any wisdom with this.

Basically as per the title, I run the Prowlarr docker app on a raspberry pi device locally on my LAN. After replacing my $100 basic TP-Link router with OPNSense, Prowlarr is unable to connect to any of the 8 configured indexing sites. Example indexing sites are 1337x.to and apibay.org

The OPNSense router is basically a fresh install and as far as I know anything LAN interface side has full access to the internet. I've added a couple of port forwards from the WAN interface for VPN but nothing that should interfere with this.

The kicker is that if I put the TPLink router back in, everything works fine.

I'm getting the following errors through Prowlarr:

"Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. Resource temporarily unavailable (apibay.org:443)"

"Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. Resource temporarily unavailable (1337x.to:443)


Some points to consider
- DNS on my LAN points to the same raspberry PI device as it's running PiHole
- My WAN interface is configured with IPv4 DHCP and IPv6 none
- LAN interface is configured as IPv4 static 192.168.1.254/24 and IPv6 none
- IPv6 is disabled on the raspberry PI

If I remove the OPNSense router and replace back with the cheap $100 TPLink router Prowlarr is immediately able to connect to all indexers again which suggests to me that the config on the raspberry PI side and Prowlarr side is fine.

I did try adding temporarily a WAN interface firewall rule to pass all source all destination just to see if that would help incase something was being blocked but it made no difference.

Thanks in advance for any advice.


#3
Confirming MikeH was on the money. Thanks so much mate, really appreciate it. Working like a charm now.
How embarrassing...  ;D
#4
Holy crap... you're definitely onto something. I kept seeing the word Pfsense coming up everywhere but assumed since Opnsense was a fork of sorts that Pfsense was still referenced in some installation locations/code.

I will report back shortly - you might have just resolved an embarrassing amount of troubleshooting hours on my part.

#5
Hi all,

Need some help installing Opnsense on a Topton PC purchased form Aliexpress.

Hardware: https://www.aliexpress.com/item/1005007199191153.html?spm=a2g0o.order_detail.order_detail_item.4.65d0f19cRYrUL6

I've downloaded the vga USB installer from this site and verified the checksum. Output below:

C:\Users\jayso\Downloads>certutil -hashfile OPNsense-24.7-vga-amd64.img.bz2 SHA256
SHA256 hash of OPNsense-24.7-vga-amd64.img.bz2:
11031aecabce97f6d5502f943d347704b5a888ec213d7f9229200877d72f297c
CertUtil: -hashfile command completed successfully.


I burned the ISO to USB using Rufus v4.6 with the default settings successfully (screenshot attached)

I'm able to boot off the USB without changing any settings in the BIOS.

My issue is that while it boots off the USB, I'm never prompted to log in with a username and password. After carefully reading the installtion guide and watching a few Youtube videos, everyone at this point gets prompted to login as either 'root' to continue to the live environment, or 'installer' to trigger unpacking and installing the OS onto the internal harddrive.

I get given the 16 options (screenshot attached) but can't trigger the opnsense-installer.

If I press '0' it just refreshes and takes me to the same 16 option menu.

If I press '8' and go to shell a "whoami" command clearly shows I'm logged in as root and I'm unable to 'su installer' (username not found).

I'm unable to execute 'opnsense-installer' in Shell either as root (Command not found). Furthermore I have SSH'd into it from my laptop but get the same results (no user 'installer')

Am tearing my hair out here - can anyone point me in the right direction? Why would the USB boot not give the option to go into installer mode and just go directly to live boot?

Thanks so much in advance