"Recent posts
#51
Q-Feeds (Threat intelligence) / Re: Help fixing 'erroneous' Q-...
Last post by vk2him - August 10, 2026, 01:14:11 AMYou can create a pass rule so it will pass that port and stop processing. Put it above the qfeeds rule. Once qfeeds resolve the issue you can delete that port rule
#52
26.1, 26,4 Series / Re: SERVFAIL when domain has ...
Last post by NonGough - August 10, 2026, 12:36:56 AMSolved.
Thank you SanjivSharma for your suggestion regarding IPv6.
In System: Settings: General -- Networking (did not find anything in Ubound DNS settings),
the "Prefer to use IPv4 even if IPv6 is available" was unchecked. After a Console Reboot (i.e., 6) Reboot System), the execution of the software worked as expected. This package's dedicated domain has two IPv4 addresses in the DNS.
1) I needed to do a OPNsense reboot. The software package (accessed by a DNS domain) failed to execute until I rebooted.
2) I needed to change which browser I used to invoke the software package. Vivaldi failed while Firefox worked. Exploring whether network related settings and behaviors are different in these two specific browsers may yield interesting insights when OPNsense is the firewall.
3) The software package does not have IPv6 addresses, but {up.railway.app} does use them. {up.railway.app} with some browsers does something differently when a domain has no IPv6 addresses registered with OPNsense as the firewall. A reason to to have several current browsers on hand in case a complicated interaction of API's, browsers, IPv6 vs. Ipv4, and OPNsense!
4) There was no reason to have the "Prefer to use IPv4 even if IPv6 is available" checked. It was originally checked when OPNsense became my firewall in order to minimize learning complications for a firewall newbie to just about anything network/Internet. With IPv6 now in much wider use, there may no reason to ever have this checkbox checked for today's Internet (newbie or not).
5) A second software package from the same vendor (no IPv6 addresses and with only 1 IPv4 addess) still failed; even though the first software package now works without a workaround. Requires a workaround executing under Vivaldi with the built-in Proton VPN temporarily enabled. After the initialization phase, the Protoon VPN is disabled. Everything works as expected. This workaround using Vivaldi also works the the original software package I had problems with. I will launch one software package in Firefox, then use Vivaldi with Proton VPN temporarily enabled to startup the second software package (these two software packages do not like each others company when executing in the same browser it turns out).
6) Private (incognito) browser sessions may affect this problem, but I have been unable to determine anything specifically.
7) There may be other browser settings at play, such as caching, javascript (WebAssembly, JIT), browser vs. Unbound DNS blocklists, extensions, local storage, etc. may be at play .
Delighted to have both software packages now working as expected, albeit with a lot of unanswered questions as to exactly why and why they behave differently with different browsers.
Thank you SanjivSharma for your suggestion regarding IPv6.
In System: Settings: General -- Networking (did not find anything in Ubound DNS settings),
the "Prefer to use IPv4 even if IPv6 is available" was unchecked. After a Console Reboot (i.e., 6) Reboot System), the execution of the software worked as expected. This package's dedicated domain has two IPv4 addresses in the DNS.
1) I needed to do a OPNsense reboot. The software package (accessed by a DNS domain) failed to execute until I rebooted.
2) I needed to change which browser I used to invoke the software package. Vivaldi failed while Firefox worked. Exploring whether network related settings and behaviors are different in these two specific browsers may yield interesting insights when OPNsense is the firewall.
3) The software package does not have IPv6 addresses, but {up.railway.app} does use them. {up.railway.app} with some browsers does something differently when a domain has no IPv6 addresses registered with OPNsense as the firewall. A reason to to have several current browsers on hand in case a complicated interaction of API's, browsers, IPv6 vs. Ipv4, and OPNsense!
4) There was no reason to have the "Prefer to use IPv4 even if IPv6 is available" checked. It was originally checked when OPNsense became my firewall in order to minimize learning complications for a firewall newbie to just about anything network/Internet. With IPv6 now in much wider use, there may no reason to ever have this checkbox checked for today's Internet (newbie or not).
5) A second software package from the same vendor (no IPv6 addresses and with only 1 IPv4 addess) still failed; even though the first software package now works without a workaround. Requires a workaround executing under Vivaldi with the built-in Proton VPN temporarily enabled. After the initialization phase, the Protoon VPN is disabled. Everything works as expected. This workaround using Vivaldi also works the the original software package I had problems with. I will launch one software package in Firefox, then use Vivaldi with Proton VPN temporarily enabled to startup the second software package (these two software packages do not like each others company when executing in the same browser it turns out).
6) Private (incognito) browser sessions may affect this problem, but I have been unable to determine anything specifically.
7) There may be other browser settings at play, such as caching, javascript (WebAssembly, JIT), browser vs. Unbound DNS blocklists, extensions, local storage, etc. may be at play .
Delighted to have both software packages now working as expected, albeit with a lot of unanswered questions as to exactly why and why they behave differently with different browsers.
#53
Q-Feeds (Threat intelligence) / Re: Help fixing 'erroneous' Q-...
Last post by Taunt9930 - August 10, 2026, 12:27:16 AMQuote from: Patrick M. Hausen on August 09, 2026, 10:00:35 PMThey have a false positive reporting form in your TIP.
Yep, submitted. Just wondered if there was anything worth doing in the meantime. Hopefully it'll be reviewed swiftly.
#54
26.1, 26,4 Series / Re: SERVFAIL when domain has ...
Last post by SanjivSharma - August 09, 2026, 11:03:08 PMThat IPv6-specific error is the big clue here — Unbound trying to reach an IPv6 nameserver for up.railway.app and failing while the direct-to-AT&T-modem path works fine strongly points to broken IPv6 connectivity or DNS resolution specifically inside OPNsense's network, not a blocklist or plugin issue. Worth checking if Unbound has "Prefer IPv4 for outgoing queries" available under Unbound's advanced settings, since forcing it to skip that broken IPv6 path entirely would confirm the theory fast. CrowdSec and the DHCP services are almost certainly red herrings here given the error is happening at the DNS resolution layer itself, pointing straight at Unbound's IPv6 handling. The Best Online Betting App In India should work comfortably during busy cricket periods when many fixtures are live or upcoming. Clear tournament online betting apps in india grouping and a responsive bet slip can make a bigger difference than decorative features.
#55
German - Deutsch / Re: Neues setup - Fragen zur S...
Last post by Patrick M. Hausen - August 09, 2026, 10:27:18 PMDie Verantwortung für deine Konfiguration liegt bei dir. Du wirst hier keine "semi-offizielle" Abnahme bekommen. Nicht in einem Community-Forum und kostenlos. Ich mache sowas gerne gewerblich über meine Firma.
Just saying.
Just saying.
#56
German - Deutsch / Re: Neues setup - Fragen zur S...
Last post by name89214 - August 09, 2026, 10:15:48 PMSo, ich habe nochmal meine Einstellungen auf Werkseinstellungen zurückgesetzt und neu begonnen.
Zunächst mal bis hier hin meine Basiskonfiguration. Internet auf LAN funktioniert. Das sollte für Telekom VDSL so passen - ansonsten lasst es mich bitte wissen.
Ansonsten noch kleinere settings wie beep, theme, ...
Zu
In letzterer Anleitung "PPPoE ISP Setup" (https://docs.opnsense.org/manual/how-tos/pppoe_isp_setup.html) sollte man sowohl IPv4 als auch IPv6 config type als None setzen - entgegen der ersten Anleitung "IPv6 for generic DSL dialup" (https://docs.opnsense.org/manual/how-tos/ipv6_dsl.html).
Passt das so?
Die Tage mache ich mich ans Eingemachte wie Firewall, DNS, DHCP etc. und poste dann nochmal ein update. Besten Dank euch schon mal!
Zunächst mal bis hier hin meine Basiskonfiguration. Internet auf LAN funktioniert. Das sollte für Telekom VDSL so passen - ansonsten lasst es mich bitte wissen.
QuoteEinstellungen nach Anleitung "IPv6 for generic DSL dialup" https://docs.opnsense.org/manual/how-tos/ipv6_dsl.html
- System > General > System: Domain = home.arpa
- Interfaces > LAN > Static IPv4 address = 192.168.1.2/24
- Interfaces > WAN > Generic configuration: IPv6 Configuration Type = DHCPv6
- Interfaces > WAN > DHCPv6 client configuration: Request prefix only = check
- Interfaces > WAN > DHCPv6 client configuration: Send prefix hint = check
- Interfaces > WAN > DHCPv6 client configuration: Prefix delegation size = 56
- Interfaces > LAN > Generic configuration: IPv4 Configuration Type = Static IPv4
- Interfaces > LAN > Generic configuration: IPv6 Configuration Type = Track interface (legacy)
- Interfaces > LAN > DHCPv6 client configuration: Request prefix only = check
- Interfaces > LAN > Track IPv6 Interface: Parent interface = WAN
- Interfaces > LAN > Track IPv6 Interface: Assign prefix ID = 0
Einstellungen nach Anleitung "PPPoE ISP Setup" https://docs.opnsense.org/manual/how-tos/pppoe_isp_setup.html
Interfaces > WAN > Generic configuration: IPv4 Configuration Type = DHCP- Interfaces > WAN > Generic configuration: IPv4 Configuration Type = None
Interfaces > WAN > Generic configuration: IPv6 Configuration Type = DHCPv6- Interfaces > WAN > Generic configuration: IPv6 Configuration Type = None
- Interfaces > Devices > VLAN > add:
- Device = vlan0.1.7
- Parent = igb0 (ab:12:...) [WAN]
- VLAN tag = 7
- Description = vlan0.1.7
- Interfaces > Devices > Point-to-Point > add:
- Link Type = PPPoE
- Link interface(s) = vlan0.1.7
- Description = igb0_vlan_PPPoE
- Username = abc
- Password = 123
- Interfaces > Assignments: assign Device = pppoe0 (vlan0.1.7)-igb0...
- Interfaces > igb0_vlan7_PPPoE: Enable = check
- Interfaces > igb0_vlan7_PPPoE: IPv4 Configuration Type = PPPoE
Ansonsten noch kleinere settings wie beep, theme, ...
Zu
- Interfaces > WAN > Generic configuration: IPv4 Configuration Type =
DHCPNone - Interfaces > WAN > Generic configuration: IPv6 Configuration Type =
DHCPv6None
In letzterer Anleitung "PPPoE ISP Setup" (https://docs.opnsense.org/manual/how-tos/pppoe_isp_setup.html) sollte man sowohl IPv4 als auch IPv6 config type als None setzen - entgegen der ersten Anleitung "IPv6 for generic DSL dialup" (https://docs.opnsense.org/manual/how-tos/ipv6_dsl.html).
Passt das so?
Die Tage mache ich mich ans Eingemachte wie Firewall, DNS, DHCP etc. und poste dann nochmal ein update. Besten Dank euch schon mal!
#57
Q-Feeds (Threat intelligence) / Re: Help fixing 'erroneous' Q-...
Last post by Patrick M. Hausen - August 09, 2026, 10:00:35 PMThey have a false positive reporting form in your TIP.
#58
Hardware and Performance / Re: AX88179B USB NIC: 57 -> 97...
Last post by patient0 - August 09, 2026, 10:00:17 PMIf you want to get it fixed, you report it to upstream FreeBSD, https://bugs.freebsd.org. With a way to reproduce the issue, link to this forum thread, using less words if you can. Not sure how many people read a short story like that.
#59
General Discussion / Re: Help needed to update boot...
Last post by Patrick M. Hausen - August 09, 2026, 09:59:02 PM1. Update your LSI controller firmware? Update your SSD firmware? Place the vendor update tools on the EFI partition from your running FreeBSD OS, boot into EFI shell via IPMI, update $STUFF.
2. No obscure "dd" incantations to update the boot loader. FAT32, documented directory structure, done.
3. Manage boot order with "efibootmgr" from the running OS - no need to ever go to the BIOS for that.
First points that come to my mind.
2. No obscure "dd" incantations to update the boot loader. FAT32, documented directory structure, done.
3. Manage boot order with "efibootmgr" from the running OS - no need to ever go to the BIOS for that.
First points that come to my mind.
#60
Q-Feeds (Threat intelligence) / Re: Help fixing 'erroneous' Q-...
Last post by Taunt9930 - August 09, 2026, 09:41:04 PMAHH, brilliant - thanks both - I missed that. Didn't think to search for 43.131.0.0. (Yes, I'm on plus).
What's the best way to whitelist/bypass for that single address? I notice you can add domain whitelist in qfeeds, but not sure you can add an IP?
What's the best way to whitelist/bypass for that single address? I notice you can add domain whitelist in qfeeds, but not sure you can add an IP?
