Messages

would have sworn that it I had seen under HA

It's always been under 'Virtual IPs' and the naming was never logical to me. But it is how it is and keeps your brain active :)

Run the script manually from shell and see what the output of it is.
I copied the script from your referenced thread to a test system here and it works fine.

And run some zfs pool command by hand, e.g 'zpool status' and see what that shows.

All settings are left at default with the exception of the 802.1Q VLAN Configuration and the 802.1Q VLAN PVID Setting.

According to the screenshot you are getting WAN on VLAN10 on port 1 and port 5 is your trunk port. _But_ ythe ports 1-5 are set as untagged for VLAN1 and you also set port 1-4 as untagged for VLAN10/20/30/40.

That will not work, one port can only ever have one PVID set (that looks correct in the other image) which results in that each port can only ever be set as untagged for one VLAN.

In '8012.1Q Configuration': VLAN10 - 40 are set correct but for VLAN1 you have to set untagged for port 5 (becaue port 5 has PVID 1) and I wouldn't set any port to tagged for VLAN1. Because you don't want VLAN1 on any of the other ports. You have port 1-4 configured as Access Ports (Cisco lingo, 'Native VLAN' in UniFi lingo) and there is no reason to carry VLAN1 as tagged traffic on these ports.

With that you can receive WAN traffic on VLAN10 in OPNsense. So I assume you configured your WAN as a VLAN10 interface in OPNsense?

Anyone have any clue what I should be doing here? I

You can also search for DEC740/DEC750 and serial port configuration, they seem to use the same hardware (serial mmio at address 0xfedc9000).

What settings did you try so far? And do you get any output at all when booting Linux? Are you booting using grub and 'console=ttyS0,115200' was added to the 'linux' line in grub?

This blog post [Proxmox on DEC740](https://loganmarchione.com/2025/10/proxmox-backup-server-on-the-opnsense-dec740/) doesn't mention any special steps.

LLM suggests:

"Before you can get a Debian installer's serial output to appear, you must enable legacy UART in the BIOS,

At the UEFI/BIOS prompt, navigate to:

Setup Utility → AMD CBS → FCH Common Options → Uart Configuration Options
and enable the legacy UART features."


_But_ the OPNsense documentation recommends the opposite for OPNsense:

https://docs.opnsense.org/hardware/serial_connectivity.html#legacy-uart-vs-uefi-serial

"... support for EFI serial has changed, which requires EFI based systems to disable legacy support to prevent confusing the operating system"

It's probably worth changing this setting and give it a go.

Addition: I remember using clonezilla to make a complete backup of my DEC740. And adding 'console=ttyS0,115200n81' to the grub commandline (and some clonezilla specific stuff) was enough to make it work. But I'm not sure about the BIOS UART setting, I lent the DEC740 to someone and haven't got it right now.

I realized i didn't unpack the files. helps if i read the instructions

Better late then never :) Have an excellent Sunday.

Please post the exact commands you run (up to the one that failed), one by one. And include what operation system you used.

Yes. I'd just like to disable the local port as well

Port 323 is the control port, which is used to make changes by non-root users while chrony runs. E.g. with 'chronyc' from the command line. It can't be disabled.

But as mentioned since it is only accessable from the machine itself, it's no issue.

OK, but is it this for example

I have no idea, I assume it's that but not sure.

The driver is maintained by AMD AFAIK but OPNsense made changes too since their boxes use it.

If it's Aquantia or RealTek and even Broadcom or Mellanox

That type of NIC is in the Desico appliances, like the DEC7xx or DEC8xx. It's from AMD and usually baked into the SoC.

Excellent to hear, I'm in no hurry. Let's see what happens :)

Hello,

As the title implies: are the plans to introduce a desktop model of a DEC39xx?

Coming back to this. Does anyone know how to do policies?

Can you provide a screenshot? That wording doesn't ring a bell at all. What phone and browser on the phone are you using?

If 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.

At what network size and data throughput does this become relevant?

VPP is a very fast and efficient packet processor and would allow to reach 10Gbit throughput on small, fanless devices.
E.g. the DEC740 can't do 10Gbit with OPNsense (it does 5-6 Gbit) and if the NICs were supported (which they are not) I could saturate my line.

Having said that: VPP seems best suited for routing, since it only supports ACLs (but they seem to be able to do firewall-ish rules).

Two articles about VPP on FreeBSD from Pim van Pelt (who used to run the SIxXS tunnel service with Jeroen Massar) for the interested:

https://ipng.ch/s/articles/2024/02/10/vpp-on-freebsd-part-1/
https://ipng.ch/s/articles/2024/02/10/vpp-on-freebsd-part-2/

He does work and develop for/with VPP (on Debian) and has got a lot of interesting articles about it, in a routing context.

Searching the internet for "Sonicwall TZ300 cpu specs" returns https://www.reddit.com/r/sonicwall/comments/m6aemk/ram_and_cpu_specs_of_tz_models/.

It lists a few Sonicwall models, the TZ300 is one of them but there seem to be multiple generation.

TZ 300 1GB Ram 1.6GHz (2x 800MHz Mips64 Octeon Processor)

If correct, Mips64 would be a show stopper in any case.

Addition: In an TZ300 unboxing video (https://www.youtube.com/watch?v=ath1kafIRVM) at 9:25 it shows in the GUI 2x 800Hz Mips64 Octeon Processor under Dashboard / Multi-Core Monitor. You can verify it yourself if the SonicOS is still on your device.