Messages

1

24.7 Production Series / Re: Problems accessing WebUI

« on: September 03, 2024, 11:44:03 am »

Never mind. I forgot to remove the USB-Stick when I tried to reload my old config. Now I installed OPNsense completely new on my internal SSD, removed the USB, rebooted while loading the old settings and there it is, the WebUI and all my settings

2

24.7 Production Series / Problems accessing WebUI

« on: September 03, 2024, 10:59:59 am »

Hi,

I accidentally changed the Web UI from HTTPS to HTTP and I lost access to the Web UI. I`ve installed OPNsense again and loaded my backup. Everything is working, I have internet access and my VLANs are working. I also have access via SSH. Unfortunately, I still have no access to the WebUI. Firefox is telling me this:

An error occurred during a connection to 192.168.1.1:8443. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG

Does anyone knows how to fix this?

Thanks

Chriss

3

24.1 Legacy Series / Re: Wireguard not able to connect

« on: April 23, 2024, 07:36:30 am »

I want to use wireguard in a roadwarrior setting. I want to use Wireguard for my phone to use Pihole. I have a interface assigned.
The WAN rule to allow external access to WG is set :    
IPv4 UDP    *    *    WireGuard (Group) net    51820    *    *       Allow acces from outside to WG

also I have a Floating Rule for any interface to access Pihole
IPv4 TCP/UDP    *    *    PiHole_DNS_Resolver     53 (DNS)    *    *    *    Allow Access to DNS

on WG i have a rule to allow access to everything (I know that this is bad, but it is now for testing:
IPv4 *    WireGuard (Group) net    *    *    *    *    *       Allow all WGs access to any

There is a forward rule to forward every other DNS request to Pihole
LAN WAN WG0 WireGuard (Group)    TCP/UDP    *    *    ! LAN net    53 (DNS)    PiHole_DNS_Resolver     53 (DNS)    Redirect DNS request to internal DNS resolver on all Interfaces

Outbound is set to automatic.
The WG interface is assigned an I configured the instance on Tunnel address 10.0.0.1/24

4

24.1 Legacy Series / Wireguard not able to connect

« on: April 22, 2024, 10:33:23 pm »

I'm sweating now for more than 8 hours in front of my PC. I tried multiple installations, different peers, different tunnel addresses, different everything. still cannot get Wireguard to work. It has worked yesterday but out of a sudden, without changing anything (just a reboot due to a short power outage) I'm unable to get WG back to live. The log shows every time /usr/local/opnsense/scripts/Wireguard/wg-service-control.php: ROUTING: entering configure using 'opt1'.
Another strange thing: If I let "Disable Routes" unchecked, sometimes it kills the whole internet connection. Something strange is happening. I'm really a newbie on OPNsense but it feels like it isn't my mistake.
Sometimes I can see a handshake but only a few KB up and download, on another try, nothing is happening. Is it just me or are there some bugs in this version?

the following settings have been made:

I want to use wireguard in a roadwarrior setting. I want to use Wireguard for my phone to use Pihole. I have a interface assigned.
The WAN rule to allow external access to WG is set :    
IPv4 UDP    *    *    WireGuard (Group) net    51820    *    *       Allow acces from outside to WG

also I have a Floating Rule for any interface to access Pihole
IPv4 TCP/UDP    *    *    PiHole_DNS_Resolver     53 (DNS)    *    *    *    Allow Access to DNS

on WG i have a rule to allow access to everything (I know that this is bad, but it is now for testing:
IPv4 *    WireGuard (Group) net    *    *    *    *    *       Allow all WGs access to any

There is a forward rule to forward every other DNS request to Pihole
LAN WAN WG0 WireGuard (Group)    TCP/UDP    *    *    ! LAN net    53 (DNS)    PiHole_DNS_Resolver     53 (DNS)    Redirect DNS request to internal DNS resolver on all Interfaces

Outbound is set to automatic.
The WG interface is assigned an I configured the instance on Tunnel address 10.0.0.1/24

5

German - Deutsch / Pi-Hole Nutzung im Wireguard VPN auf der OPNsense

« on: April 18, 2024, 04:39:28 pm »

Servus Schwarmintelligenz,

Kurz Vorweg: Ich bin IT begeistert, jedoch blutiger Anfänger in OPNsense und fuchs mich da gerade rein. Ich steh jetzt allerdings vor einem Problem.

Kurze Beschreibung:

Ich habe Pihole auf einem ThinkCentre mit Proxmox in einem LXC Container installiert. OPNSense läuft auf auf einem Barebone von Topton. Als DNS Resolver ist Unbound auf der OPNSense installiert. Soweit läuft alles, Unbound löst die DNS auf, Pihole fungiert als Sinkhole. Jetzt möchte ich Wireguard auf der OPNsense nutzen, damit vorallem mein Handy das PiHole nutzen kann. Dies scheitert jedoch und ich kann zwar die OPNsense bei aktiviertem Wireguard pingen, ich bekomme aber keine Verbindung ins Internet. Eine Firewallregel für den Zugriff auf das private Netzwerk habe ich erstellt und die funktioniert. Für Wireguard hab ich ein Interface angelegt. Warscheinlich ist es total einfach und ich sehe einfach den Wald vor lauter Bäumen nicht. Ich vermute mal, ich muss irgend eine Firewallregel hinzufügen, damit es funktioniert.

Vielen Dank für eure Hilfe