Recent posts

#1

26.7 Series / Re: Pppoe Interfaces Linkage

Last post by meyergru - Today at 01:20:46 PM

...because the documentation knows better than you if your ISP needs a VLAN and if your modem supplies it in that case?

There are two cases:

1. your ISP does not need a VLAN - then your use the NIC device without one.
2. your ISP needs a VLAN - then you can do one of two things:
   a. if your modem supports it, you can set the VLAN in the modem and your NIC device without VLAN.
   b. if your modem does not support it or you do not want to lose modem access via the untagged VLAN, you can use the NIC device with VLAN.


I prefer 2b if needed for the reason given.

#2

26.7 Series / Re: Pppoe Interfaces Linkage

Last post by nicholaswkc - Today at 01:15:44 PM

Really, I thought there must a recommended approach from opsese doc.

#3

26.7 Series / Re: Action - Pass, Block, Reje...

Last post by devl_ish - Today at 12:08:01 PM

I assume you can use "pass" instead of "match" like documented under Rule normalization:

Thanks, used this approach and everything seems to be working.

No, the documentation is too new. It doesnt exist yet. But we fix that soon. So long you can look at the direct branch here:

https://github.com/opnsense/docs/blob/master/source/manual/how-tos/wireguard-client.rst

Thanks for that (and the work you do), road warrior was my next step to diversify my access away from TailScale (its great but I don't want to put all my eggs in one basket knowledge-wise).

#4

Development and Code Review / Re: Blocky DNS (Alternate to A...

Last post by Akruidenberg - Today at 11:19:38 AM

I cant update to the latest release.

Have you resolved this now?

If not:

Code Select Expand

pkg clean -ay && pkg update -f

yes its working with your command!

#5

General Discussion / Re: Going from no VLAN to VLAN...

Last post by prutz0r - Today at 11:01:03 AM

Because my whole network goes down or I need to run a cable directly between the MR and MS

I am guessing your Netgear Switch is blocking some kind of protocol that those things use to communicate...
Reason I am saying this is that I have read something similar once, but I can't remember anymore what the exact issue was :(

Can't you just DISABLE MESH functionality and configure all the units like a simple Accesspoint ?!

Another possible issue :
Not having a proper (R)STP setup on your Switches combined with the Mesh functionality of those things can indeed cause serious issues!

I read about loop prevention being able to cause all kinds of trouble so that's disabled. I really think the WAN and LAN interface are bridged in AP mode thus causing lot's of issues when connecting both to a switch on the same subnet. I think it's looping. That theory does fit my observations so far. Assuming mesh means using a wireless connection as backhaul and automatically finding the best path and considering roaming a seperate feature, mesh is disabled automatically when connecting the satellite, MS, wired to the MR. However the MR interfaces still seem bridged. To stop the loop I think I can solve the puzzle by isolating the connection between the MS and MR as networking is taken care of by the bridge. The MS have their own web interface but there is almost nothing you can configure. Rebooting, perhaps syncing for wireless mesh and that's about it. They really depend on the MR.

Now to answer your question about VLANs partially :
- When your OPNsense Interface is just the Default LAN for example you need to transport it as UNTAGGED to a Switch or Accesspoint.

That would be the situation without VLANs that I have right now I think?

- When your OPNsense Interface has VLANs assigned to it you need to transport them as TAGGED to a Switch or Accesspoint.

My default LAN will be VLAN 10 so that would mean connection from router to switch is tagged?

- VLANs between Switches usually go TAGGED too unless you are doing something special for whatever reason.

I have only one switch.

- VLANs from Switches to Accesspoints go TAGGED too unless you are doing something special for whatever reason.

Simple common example of "Something special" :
Some equipment needs to have it's Management Network transported as UNTAGGED instead of TAGGED.
Since your MESH units probably don't know what to do with VLANs on the "Switch side" you will need to do something like this, because both the regular traffic and management traffic will go via the same connection/network :)

This system is completely unaware of VLANs, it's not like Ubiquity where you apply a VLAN to an SSID so I would think the traffic is untagged anyway to the MR interface that connects the access points to the rest of the network and the internet? And then apply a fixed PVID to the relevant switch port?

Heel veel succes alvast! ;)

Bedankt, interessante puzzel, alleen wil ik niet voor iedereen in het huis dagen lang het netwerk uit de lucht hebben ;)

#6

Hardware and Performance / Re: 10G but reaching only 5-5....

Last post by ou1 - Today at 10:04:57 AM

There was another topic where the DEC850 seemed to be the better choice indeed :)

Yes, unfortunately at 1650 EUR (current price) and 45W typical power usage, this puts it out of reach for me as a home user. My M920q setup was under 400EUR including the X710 card and typically uses <20W. Not really comparable, an ancient mini PC with a hole cut into it and a fan over the hole, but it's silent and it gets the job done.

Maybe they didn't anticipate 10G internet to be so readily available when they designed the DEC750.

#7

26.7 Series / Re: Pppoe Interfaces Linkage

Last post by Patrick M. Hausen - Today at 08:19:03 AM

Depends on your ISP and your modem.

#8

26.7 Series / Pppoe Interfaces Linkage

Last post by nicholaswkc - Today at 05:50:32 AM

Dear all, what is the correct ppoe interface linkage at Interface.devices.ppp?

Using em0 or em0_vlanxxx?

#9

Hardware and Performance / Re: DEC-850v1 serial console o...

Last post by patient0 - Today at 05:27:25 AM

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.

#10

General Discussion / Re: Regular Summary Report via...

Last post by Greelan - Today at 02:13:27 AM

I am looking at adding a summary reporter to my notify plugin, as it sits well alongside the existing functionality.