Quote from: dmcgough on <strong>Today</strong> at 06:40:45 PM[...]I don't want to suddenly start routing all of my actual traffic to 8.8.8.8 via WAN2[...]
Quote from: lmoore on November 17, 2026, 06:59:58 AMIf you have more than one public IP address on your service, you could use One-to-One NAT (BINAT) between your ITSP and your internal PBX and see if that changes the behaviour.
Quote from: lmoore on November 17, 2026, 06:59:58 AMI've read various postings about port-forwarding to the internal PBX. I have not encountered a situation where this has been a requirement. Firewall configurations I've used rely upon the connection for the outgoing registration as the channel with which incoming calls will arrive from the ITSP.
In your environment, and prior to 26.7.8_1, what problem does forwarding inbound connections for port range 5060-5063 resolve for you?
Quote from: lmoore on November 17, 2026, 06:59:58 AM...I may look into this quirk one day and see if changing the Firewall rule setting under advanced mode of the Destination NAT entry from Manual to Register rule.
Perhaps you are seeing something similar with your VoIP traffic.
Quote from: nero355 on <strong>Today</strong> at 05:14:46 PMI forgot to ask : Can the 'NULL Route configuration' mentioned some time ago prevent that ?
Quote from: bimbar on <strong>Today</strong> at 04:33:41 PMI hope it will get better when the bugs are mostly found.
Quote from: Carcharoth on <strong>Today</strong> at 05:54:38 PMYes, of course! Thank you for the idea!AWESOME!!! :)
https://github.com/Tellyke892/opnsense-netgate-1100
Quote from: nero355 on <strong>Today</strong> at 04:44:38 PMQuote from: Carcharoth on November 19, 2026, 04:36:54 PMThanks to the awesome work Maurice has done I was able to install Opnsense into a Netgate 1100, and it's working. If anyone is curious I'll link a full guide.May I suggest converting this guide to GitHUB/GitLAB/whatever you like the most... for easier access and readability ? :)
https://drive.google.com/file/d/1jy6wmW2TumZvh1PlwcIhep5jogcSxo15/view?usp=sharing
Quote from: Maurice on November 19, 2026, 05:58:50 PMThanks for the success story and the tutorial. Interesting to hear that bootefi works on this hardware and with this U-Boot build. That's not always the case...Thank you for the corrections, I addressed them in the github repo!
If you use a ufs-serial-vm-aarch64 image (which defaults to a serial console), you'll have console access from the start. I create these specifically for devices without a video console.
If you erase the eMMC before you write the OPNsense image to it, you don't have to manually repair the backup GPT header.
You don't have to change anything in System / Firmware / Settings. In my aarch64 VM images, the "(default)" mirror already points to my repo.
Cheers
Maurice