Did you assign veth1 interface to that container ?
PS export of config is a lot more clear for everyone then all those screenshots ...
AFAIK it is advised not to do that since some clients may completely avoid an AP playing such tricks.Ofcourse you can play with tx power, as well you can add access lists to block clients when a thresshold is reached.
Worst case (if cable is no option): powerline.Be aware that you will have a 2.4GHz radio as backhaul, don't expect to much of it. If possible, run cables.
I took care of that for youHow can I mark this as solved?
" old" Hex runs The Dude since a long time.Now that hEX Refresh has an ARM CPU, does that mean it can run Dude?
Self-knowledge is the beginning of all wisdom ...My skills are actually limited but my ability to pester those far more knowledgeable are second to none!
viewtopic.php?t=211863Even for the useful RB750Gr3 there is now an announced replacement with 128MB flash!
Was there an announcement I missed? Where do you see this?
Done.We might have to rename this threadCode: Select all*) wifi - re-word the "SA Query timeout" log message to "not responding";
This one ?I am facing this same proble with RB 3011 UiAS-RM
I have install wifi - qcom package and still master interface unknown.
Please how can i get this down.
Doubtful ... most likely a config issue.The configuration is correct as I have made dozens, Ethernet port is on the Bridge.
Just used one of your little gems as a response to someone having trouble searching for host-names (which can be case "anything")Case INsensitive search (on example on comment field)
viewtopic.php?t=191504#p971246
Where did you get that from ?...but ROS can be hard to master.
Could be but unlikely.Is it possible they told me a router already compromised?
Probably this one:PS, i had a link to a great Mikrotik forum article/guide on implementing VLANs, but seems the article has been deleted - does anyone have a link to a suitable article please?
It depends.Actually, there's nothing complicated about it; you just need to manually add the wireless package
I never said it was related to device mode.If your containers stopped working after upgrade to 7.17, it might not be related to device mode at all.
1) You do not use VLAN1
2) You DO NOT use VLAN1
3) You do not use Quickset
4) You do not use detect internet
5)...
... and didn't pay attention that those test results are not what they were expected to be ?As if they, somehow, only tested the 1Gbps MGMT port?Those results do look very bad
Updated device FW as well to 7.16 ?PoE from a 4011.powered by power supply or Poe?
Max out per port output (input 18-30 V) 1000 mA
Max out per port output (input 30-57 V) 570 mA
In that case apply simple port forward towards the server which will accept these wireguard users.But that's not what I asked about. I do not want to terminate these Wireguard users on the RB5009 (see earlier post).