I can't see anything weird...
... but randomly appears
Code: Select alldhcp-client on ether8-WAN lost IP address 89.XXX.XX.18 - lease stopped locally
Let's assume they are working on it.
... if for whatever reasons you applied an excessive voltage to ether1 I would expect It to fry, not the other ports.
I don't understand why mikrotik doesn't have some kind of roadmap...
AFAIK not even protocol (http), only host name, e.g. youtube.com ...It should match http://youtube.com but not a lot more.
No idea. Can you give us a hint?Guess who will be buying a tplink the first sale I see on their wifi7 products.......
What can I do?
I thought RSTP was the most common one?... MSTP is the most universally compatible one.
Stickers already exist:
I just said anything but some kind of metallic sticker Now who knows what will arrive from Temu...
Not really ... wifi-qcom-ac is only available for routers with ARM architecture ... AC devices of other architectures are "doomed" to run legacy wireless driver ... which doesn't support any new functionality (like PPSK) and I believe it never will.yes, it should.
But does this really work for you? Only one VLAN can have bidirectional traffic (single PVID per port).... and I still wanted several VLANs untagged on the same port (because my WiFi APs are not VLAN aware).
There's such a feature already: port extender. Not many devices are compatible ... and it comes with some serious gotchas. But it's here.Don't know if this has been discussed already ...
That was my point exactlyErrmm ... that's an article from 2014 ?!
advertising: 1G-baseX
link-partner-advertising:
In the meantime your devices probably have restarted ...
Apparently, I speak truth.
When did MT make changelogs easily understandable?Well, why not just mention that in changelog?
/interface bridge vlan
add bridge=SW1 tagged=SW1,ether8 vlan-ids=40
/ip dhcp-client
add interface=Management
I'd say it means DFS.What does "D" mean in Current Channel?
Find them ... as per advice by @tdw. Yes, it's manual work, but if you want to catch plaintiff, you need to do some detective work before you send out the guns.However not knowing where they come from is troubling us, we only see the LAN ip and mac address of the source.
You haven't mentioned what the log is currently mentioning.Code: Select all/system logging action ...
It's actually shooting under / between the branches.
could this solve it?
https://github.com/ncravino/mikrotik_en ... our-router
In such a case it _might_ also be worthwhile to export config, netinstall device and then re-apply config again.
I think the problem is DOH, if I do a torch I see requests towards 8.8.8.8:443. so AdGuard is skipped. How do I manage these requests to process everything from AdGuard?
:put [ /interface/ethernet/get sfp-sfpplus1 sfp-ignore-rx-los ]
What to do to resolve the issue?
But I didn't like the fact that with usage of datapath I got a tagged wireless traffic
You can. But TPlink has to perform NAT also for "alien" subnets on LAN side ... and I've no idea if that's possible or not.You cannot have the rb5009 providing separate subnets without double NAT ...
... if L3 hashing policy is used by them
Is there a guide I could follow that helps me to setup WiFi?