Given the above, I agree with the below.for the last 2-3 years ap has been running from a poe switch and I have tried changing ports and using with the adapter and power supply from the kit and the behaviour persists.
Well, it seems it's time to switch to ax
The topic, please. This one is not the right place for discussing this, create a new one.What else should I change?
If the intention is to get the same behavior like a single VLAN-aware hardware switch, then yes.Is my statement (at high level) correct?
Set the level of all the policies you've added to unique. If that does not help, post the configuration exports from both devices.If I configured more that one subnet on the polices and the nat settings, but only one subnet has communication end to end.
Somehow there is an IPv6 DNS query that got responded in the sniff above... so I wonder what the mode setting is actually worthIn easy things to try... setting the mode to "IPv4" instead "auto" in the APN is worth a shot.
Here's why and how.how can i get the configurtaion ?
/interface/wireguard/peers/print detail shows items like current-endpoint-address, current-endpoint-port, rx, tx, last-handshake.how can i check if the wireguard connection was working ?
I have already expressed my opinion on that here. An additional tunnel can be useful but it is not a panacea.Do you think I can or should add another layer of access as a backup to the WG?
I've got that, I just used the VLAN numbes from the problematic site as a shortcut. I should have written "WAN VLAN" instead of "VLAN 10" and "LAN VLAN" instead of "VLAN 2" to avoid confusion.It's at the other site with a working /56 IPv6 prefix.
Diagnostic. Temporary. Where did I suggest it as a long term solution ?I'm not sure this method would be adequate on the longer term.
No way to find out unless you post the export of your actual configuration.What went wrong?
Nope, turns out it's me who has commited diagonal reading - the OP's issue is actually the same like @johnb175a's, except that the OP did not take as much effort to analyse it as @johnb175aGuilty.
The only solution I could ever find was to use bridge filter to drop packets escaping via WAN with any unexpected source address, but that is only possible for WANs using L2 interfaces ("IP over Ethernet" ones), not for PPP-based ones as those cannot be bridged.What are my options here?