Quote from: Wrigleys on September 25, 2026, 02:06:51 PMI assume you can use "pass" instead of "match" like documented under Rule normalization:
Quote from: Monviech (Cedrik) on September 25, 2026, 02:10:07 PMNo, 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
Quote from: Greelan on September 25, 2026, 11:33:16 PMQuote from: Akruidenberg on September 25, 2026, 06:40:37 PMI cant update to the latest release.
Have you resolved this now?
If not:pkg clean -ay && pkg update -f
Quote from: nero355 on September 25, 2026, 10:19:07 PMI 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.Quote from: prutz0r on September 25, 2026, 09:32:34 PMBecause my whole network goes down or I need to run a cable directly between the MR and MSI 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!
QuoteNow to answer your question about VLANs partially :That would be the situation without VLANs that I have right now I think?
- When your OPNsense Interface is just the Default LAN for example you need to transport it as UNTAGGED to a Switch or Accesspoint.
Quote- 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?
Quote- VLANs between Switches usually go TAGGED too unless you are doing something special for whatever reason.I have only one switch.
Quote- VLANs from Switches to Accesspoints go TAGGED too unless you are doing something special for whatever reason.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?
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 :)
QuoteHeel veel succes alvast! ;)Bedankt, interessante puzzel, alleen wil ik niet voor iedereen in het huis dagen lang het netwerk uit de lucht hebben ;)
Quote from: nero355 on September 25, 2026, 09:53:36 PMThere was another topic where the DEC850 seemed to be the better choice indeed :)
Quote from: N0b0dy1985 on September 25, 2026, 07:31:37 PMAnyone have any clue what I should be doing here? IYou can also search for DEC740/DEC750 and serial port configuration, they seem to use the same hardware (serial mmio at address 0xfedc9000).