"
Nope.
I didn't start yelling. Just asking.
I didn't start yelling. Just asking.
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.
Pages1
#2
25.7, 25.10 Series / Re: Unbound to forward .home domain
January 09, 2026, 07:05:40 AM
It was not my intention to start a fundamental discussion about the .home domain.
A customer has such a domain which wasn't a problem for the last 5 years as unbound forwarded the domain correctly to the customers dns-server (Win).
But since the last update it doesn't.
A customer has such a domain which wasn't a problem for the last 5 years as unbound forwarded the domain correctly to the customers dns-server (Win).
But since the last update it doesn't.
#3
25.7, 25.10 Series / Unbound to forward .home domain
January 06, 2026, 06:06:36 PM
Hey guys,
unbound doesn't forward *.home-domains since last update to 25.7.10.
It worked before for quite a couple years.
Anybody knows why?
unbound doesn't forward *.home-domains since last update to 25.7.10.
It worked before for quite a couple years.
Anybody knows why?
#4
Virtual private networks / Access IPSec-Tunnels "behind" the OPNsense from WireGuard-Peer
November 20, 2025, 05:01:29 PM
I have an OPNsense with a working WireGuard-setup for my mobile devices.
The peer-config routes all ipv4-traffic through the tunnel.
So far so good.
I want to reach subnets on site-2-site IPSec-tunnels (made by OPNsense) from the peer through the tunnel.
Do i have to include the wireguard-network on OPNsense in the IPSec-tunnel-config or is there another way?
Thanx.
The peer-config routes all ipv4-traffic through the tunnel.
So far so good.
I want to reach subnets on site-2-site IPSec-tunnels (made by OPNsense) from the peer through the tunnel.
Do i have to include the wireguard-network on OPNsense in the IPSec-tunnel-config or is there another way?
Thanx.
#5
General Discussion / Re: ACME Challenge HTTP-01 stopped working
February 19, 2024, 06:00:21 PMQuote from: bazbaz on February 19, 2024, 05:06:11 PM
try to manually assign the external IP address in challenge's options
this works for my setup.
Thanks
#6
24.1, 24.4 Legacy Series / Re: acme not working anymore (since 21 Dec 2023)
February 03, 2024, 07:29:11 PM
there is no dns-api support at STRATO. >:(
#7
24.1, 24.4 Legacy Series / Re: acme not working anymore (since 21 Dec 2023)
February 02, 2024, 01:12:49 PM
same here.
OPNsense running on port 8443/tcp. Some hosts behind with Port-Forwarding to 443/tcp.
In acme.sh log it shows one of the hosts behind - accessible with Port-forwarding to 443/tcp - that it uses the OPNsense https-Port 8443 to validate with the http-01-challenge.
"only ports 80 and 443 are supported, not 8443"
OPNsense running on port 8443/tcp. Some hosts behind with Port-Forwarding to 443/tcp.
In acme.sh log it shows one of the hosts behind - accessible with Port-forwarding to 443/tcp - that it uses the OPNsense https-Port 8443 to validate with the http-01-challenge.
"only ports 80 and 443 are supported, not 8443"
#8
22.7 Legacy Series / Re: Maltrail not working - checksum mismatch for mailtrail.conf
September 13, 2022, 08:53:45 AM
same here.
#9
22.7 Legacy Series / Re: very slow boot (Configuring firewall...)
August 11, 2022, 11:48:35 AM
FTS FUTRO S920
MB: FTS D3313-A1x
AMD GX-415GA SOC with Radeon(tm) HD Graphics (4 cores, 4 threads)
8GB RAM
32GB SSD
REALTEK onboard NIC for LAN
Draytek VigorNIC 132 PCIe as VDSL Modem for WAN
MB: FTS D3313-A1x
AMD GX-415GA SOC with Radeon(tm) HD Graphics (4 cores, 4 threads)
8GB RAM
32GB SSD
REALTEK onboard NIC for LAN
Draytek VigorNIC 132 PCIe as VDSL Modem for WAN
#10
22.7 Legacy Series / very slow boot (Configuring firewall...)
August 11, 2022, 09:56:14 AM
I'm having very long boot times (10min).
At the console screen it happens when opnsense is "Configuring firewall..." which appears multiple times during the system startup.
Any glue ?
At the console screen it happens when opnsense is "Configuring firewall..." which appears multiple times during the system startup.
Any glue ?
#11
22.1 Legacy Series / Re: Alias based firewall rules doesn't work after upgrade to 22.1.8
May 27, 2022, 12:09:50 PM
Thanx for the hotfix. It is working as before.
#12
22.1 Legacy Series / Alias based firewall rules doesn't work after upgrade to 22.1.8
May 25, 2022, 01:57:16 PM
I have a ccouple ipsec site2site tunnels running on my opnsense.
Each LAN on the remote sites has an alias. I use these aliases to define rules that pass every traffic/protocol to the remote site.
ssh, http, https will pass, every other traffic will be blocked since the update to 22.1.8 as i can see in the live log by the default block rule.
This was not expected.
Just to try i added an ANY-2-ANY rule and it works again - but this is just vor testing.
Each LAN on the remote sites has an alias. I use these aliases to define rules that pass every traffic/protocol to the remote site.
ssh, http, https will pass, every other traffic will be blocked since the update to 22.1.8 as i can see in the live log by the default block rule.
This was not expected.
Just to try i added an ANY-2-ANY rule and it works again - but this is just vor testing.
Pages1
