"Recent posts
#21
Tutorials and FAQs / Re: ndp-proxy-go: Proxy ISP pr...
Last post by Courier1027 - Today at 09:10:16 AMQuoteIf you receive a DNS server from your ISP, but want the router to be the sole DNS server, use a Port Forward to force traffic destined to port 53 to the local running Unbound server instead.I am very new to IPv6 and this is my hobby project so please be gentle. I have already implemented this in IPv4 with port forward to 127.0.0.1. How do I identify the IPv6 address of the local running Unbound server and implement for IPv6? My IPv6 stack is working well with this plugin with LAN configured as link-local so thanks for this.
#22
25.7, 25.10 Series / Re: (Solved?) Freeradius - can...
Last post by franco - Today at 09:01:36 AM #23
25.7, 25.10 Series / Re: Help Needed: Branding & UI...
Last post by franco - Today at 09:00:19 AMWe do offer branding as a service. :)
Cheers,
Franco
Cheers,
Franco
#24
25.7, 25.10 Series / Re: Help Needed: Branding & UI...
Last post by meyergru - Today at 08:38:56 AMWow. Just wow.
Sounds a little like "I am too dense to actually modify the code by myself to start a business on your hard work - could you please do that for me or at least help me do it?"
Good luck with that.
Sounds a little like "I am too dense to actually modify the code by myself to start a business on your hard work - could you please do that for me or at least help me do it?"
Good luck with that.
#25
General Discussion / Re: new setup cannot reach lin...
Last post by meyergru - Today at 08:31:22 AMThere are some virtualisation settings in most BIOSes, often called SVM or AMD-V (IOMMU comes to mind, but your quote about the board sucking makes me think the latter is not available). Also, I always use "host" CPU emulation type in Proxmox, where the CPU is not emulated, but passed thru to the VM.
#26
25.7, 25.10 Series / Help Needed: Branding & UI/UX ...
Last post by chaitya22 - Today at 06:15:02 AMHello everyone,
I'm working on a custom OPNsense 25.7 build based on FreeBSD 14.3, and I need guidance on how to properly replace all references to "OPNsense" with "cwdelta" throughout the system (product name, UI labels, metadata, etc.).
I have already done the following:
Cloned and built OPNsense using the official tools
Modified build.conf values such as:
PRODUCT_NAME=cwdelta
PRODUCT_CORE=cwdelta
CORE_PRODUCT=cwdelta
Set a custom core branch (COREBRANCH=delta)
Rebuilt the system (make base, make kernel, make packages, make core)
However, I still see OPNsense text in various areas, especially during package generation and UI components.
It looks like some branding is still coming from defaults in tools, core, or other template files.
Before I continue rebuilding everything again, I want to confirm:
My Questions
Which files control product naming/branding in OPNsense 25.7?
Are there additional places beyond build.conf and defaults.mk that I need to modify?
Is there a recommended/official way to fully rebrand OPNsense
so that the product name, package names, UI labels, and version information show "cwdelta" everywhere?
Are the branding strings pulled from:
core/src/opnsense?
MVC templates?
Hardcoded PHP constants?
Package plist metadata?
Does OPNsense 25.7 use any cached branding from previous builds that needs to be cleared manually?
My goal is to create a cleanly rebranded version without modifying core logic — only text, names, and UI elements.
Any guidance from developers or users who have done full rebranding would be greatly appreciated.
Thank you in advance!
— Chaitya
I'm working on a custom OPNsense 25.7 build based on FreeBSD 14.3, and I need guidance on how to properly replace all references to "OPNsense" with "cwdelta" throughout the system (product name, UI labels, metadata, etc.).
I have already done the following:
Cloned and built OPNsense using the official tools
Modified build.conf values such as:
PRODUCT_NAME=cwdelta
PRODUCT_CORE=cwdelta
CORE_PRODUCT=cwdelta
Set a custom core branch (COREBRANCH=delta)
Rebuilt the system (make base, make kernel, make packages, make core)
However, I still see OPNsense text in various areas, especially during package generation and UI components.
It looks like some branding is still coming from defaults in tools, core, or other template files.
Before I continue rebuilding everything again, I want to confirm:
My Questions
Which files control product naming/branding in OPNsense 25.7?
Are there additional places beyond build.conf and defaults.mk that I need to modify?
Is there a recommended/official way to fully rebrand OPNsense
so that the product name, package names, UI labels, and version information show "cwdelta" everywhere?
Are the branding strings pulled from:
core/src/opnsense?
MVC templates?
Hardcoded PHP constants?
Package plist metadata?
Does OPNsense 25.7 use any cached branding from previous builds that needs to be cleared manually?
My goal is to create a cleanly rebranded version without modifying core logic — only text, names, and UI elements.
Any guidance from developers or users who have done full rebranding would be greatly appreciated.
Thank you in advance!
— Chaitya
#27
25.1, 25.4 Series / Re: tailscale issue
Last post by jmcgee - Today at 05:29:04 AMroot@OPNsense:~ # cd /var/run/tailscale
root@OPNsense:/var/run/tailscale #
root@OPNsense:/var/run/tailscale #
#28
25.7, 25.10 Series / Re: Please Help, Experimenting...
Last post by House Of Cards - Today at 04:24:53 AMYou cannot view this attachment.
Should all my redirect rules point to that port, (HTTP, HTTPS)? I feel like I might have tried that.
EDIT: I changed the DNS rule to 9053, and the HTTP/S rules to 9040. Same behavior. I have another port forward rule for DNS lower in the rules list for those devices that try to bypass my hardwired DNS, but that shouldn't be blocking anything from the TOR rules, as they are on top in the Port Forward rules.
Should all my redirect rules point to that port, (HTTP, HTTPS)? I feel like I might have tried that.
EDIT: I changed the DNS rule to 9053, and the HTTP/S rules to 9040. Same behavior. I have another port forward rule for DNS lower in the rules list for those devices that try to bypass my hardwired DNS, but that shouldn't be blocking anything from the TOR rules, as they are on top in the Port Forward rules.
#29
Zenarmor (Sensei) / Something broke
Last post by ldanna1945 - Today at 03:44:27 AMJust after latest opnsense update to
OPNsense 25.7.8-amd64
FreeBSD 14.3-RELEASE-p5
OpenSSL 3.0.18
The firewall would continuously reboot. Left it till next morning and the opnsense was back up. looking at Zenarmor I saw the engine was stopped . I restarted and it immediately shutdown. Looking at the console monitor of the unit see iflib_netmap_config txr 2 rxr 2 txd 1024 rxd 1024 rbufsz. This comes up every time I restart Zemarmor engine. I disabled the IPS service and now engine starts and stays started but the above message persists every time engine starts.
Any Ideas of what is causing this? Note: I did not have this condition before the latest update.
Thanks to the group
Larry
OPNsense 25.7.8-amd64
FreeBSD 14.3-RELEASE-p5
OpenSSL 3.0.18
The firewall would continuously reboot. Left it till next morning and the opnsense was back up. looking at Zenarmor I saw the engine was stopped . I restarted and it immediately shutdown. Looking at the console monitor of the unit see iflib_netmap_config txr 2 rxr 2 txd 1024 rxd 1024 rbufsz. This comes up every time I restart Zemarmor engine. I disabled the IPS service and now engine starts and stays started but the above message persists every time engine starts.
Any Ideas of what is causing this? Note: I did not have this condition before the latest update.
Thanks to the group
Larry
#30
25.7, 25.10 Series / PPPoE link only comes up after...
Last post by ToasterPC - Today at 03:39:56 AMHi there!
I'm using an SFP module to connect my ISP's fiber link directly to the machine I'm running OPNsense with (Minisforum MS-01), applying the requisite VLAN tag directly to the bridge interface in Proxmox and connecting it as a VirtIO network adapter to take advantage of multiqueueing.
However, after starting the configuration of the firewall VM from scratch this time, it seems I might have changed a setting that prevents the PPPoE link from coming up immediately when the VM is started or rebooted, and as such I need to manually bring the interface down and up after a blackout thanks to the UPS shutting the computer off before running out of juice.
Considering that this might happen overnight or when I'm out of reach, it can make remote troubleshooting a little bit more difficult than what's ideal, but I'm not sure where to begin looking.
So far, I can tell that the behavior is consistent whether I'm using the SFP module or the ISP router in bridge mode, but not much more than that.
If y'all needed to look into this, where would you begin?
Thanks in advance!
I'm using an SFP module to connect my ISP's fiber link directly to the machine I'm running OPNsense with (Minisforum MS-01), applying the requisite VLAN tag directly to the bridge interface in Proxmox and connecting it as a VirtIO network adapter to take advantage of multiqueueing.
However, after starting the configuration of the firewall VM from scratch this time, it seems I might have changed a setting that prevents the PPPoE link from coming up immediately when the VM is started or rebooted, and as such I need to manually bring the interface down and up after a blackout thanks to the UPS shutting the computer off before running out of juice.
Considering that this might happen overnight or when I'm out of reach, it can make remote troubleshooting a little bit more difficult than what's ideal, but I'm not sure where to begin looking.
So far, I can tell that the behavior is consistent whether I'm using the SFP module or the ISP router in bridge mode, but not much more than that.
If y'all needed to look into this, where would you begin?
Thanks in advance!
