Quote from: danman on Today at 01:36:22 PMI finally made the first part! Which means I got my brain working with PVID and UNTAGGED etc.w00t w00t !!! NICE! :D
AP is fully working now. One switch works... yeah, this part is done.
Thank you @nero355 & viragomann for all the hints/help! That was really helpful =)
On Sunday will be the swap with the openwrt main router and then I've to check the other switches, proxmox and whatnot.
QuoteI'll be back ;)OK Arnold :P
Quote from: gpb on Today at 03:30:33 PMI didn't read all the above, but one note about that switch.I have read about some weird issues with the TP-Link 105/108 E and PE models in the past, but a lot of those issues were fixed via either new Revisions or simply Firmware Updates so it would be nice to know which combination you have at the moment for future reference :)
Do not use DHCP for the IP address assignment of the switch itself, just put in a static address. Reason...sometimes the switch will get an IP address from one of the other VLANs. I spent some time on this and it appears it sends a DHCP request on all VLANs and which ever answers first wins.
So it may seem to work, but sometimes when it renews its address it might change. Just an FYI. I have a few of these and they are set and forget, otherwise.
Quote from: tessus on Today at 12:26:23 PMI am slightly confused right now.I think a lot of people would be less confused if they would just keep an eye on the Release Notes carefully each time there is an update/upgrade and in this case perhaps also at least only read the Migration Assistant part that's related to the Firewall Rules migration :)
Quote from: OPNenthu on August 04, 2026, 10:20:24 PMI may need to break down and install a standalone DNS there to get this load off of OPNsense.You could ofcourse give it a small dedicated DNS Server running on a Raspberry Pi 2B/3B or perhaps even a Pi Zero and keep everything else as is :)