[quote=Rebeka post_id=828304 time=1605233428 user_id=177766]
Good signal connection that cover 40 sqm.
…
I will use it for cafe.
[/quote]
Reading these two lines together makes me believe OP is writing about square metres … and any AP positioned centrally will cover square of 7x7 metres just fine.
Re: Yeah but Tom is a Yankee, its all square miles when you put in an “m” in there!
Here in the states , we use miles.
Yea … I’m a bone-head Yankee located in North Idaho
m - meter/meters - A meter is equal to 39.37 inches, or slightly more than three feet.
m² - square meter - A square meter is an area that measures one meter in length and width.
m ?
m could be any of the following ?
miles
meters
also
molecules ( really really close stuff )
milk ( yea the white liquid stuff )
If someone were to twist my arm and force me to buy MT wifi it would be the hapac3 due to its ability to use future wifi5 fixes.
The audience is also of that ilk but I think overkill for that small area??
Close - well OK , the United Stated and Canada are real close to each other ---- however … My WISP/ISP business is 2,500 miles ( 4 thousand km ) from your ISP/WISP. Your ISP business is actually closer to South America or Ireland than to where I am in North Idaho ----- lol
However … When it comes to switching using ROS ( using the ethernet switch chip -or the CPU for software switching ) , the Mikrotik ROS CLI & http & Winbox is just horrible !
For example - try doing this:
Let say you have 5 to 48 ethernet-and/or-sfp ports
Part 1 ( vlan access ports )
1-a - Some ports are untagged Vlan 5 ( mode access Vlan 5 )
1-b - Some ports are untagged Vlan 6 ( mode access Vlan 6 )
1-c - Some ports are untagged Vlan 7 ( mode access Vlan 7 )
Part 2 ( simple 802.1q Trunk ports )
2-a Four ports are trunk ( all Vlans allowed out and all Vlans allowed in )
Part 3 ( complex 802.1q Trunk ports )
3-a Two ports are trunk ( all vlans are allowed in&out except Vlan 1 and 9 and 10 )
3-b Two ports are trunk ( all vlans are allowed in&out except Vlans 3,15-30 )
3-c Two ports are trunk ( all vlans are allowed in&out except Vlans 50,52,60-70 )
3-d Two ports are trunk ( only Vlans 51,80,83-85 are allowd in&out )
3-e Two ports are trunk ( only Vlans 1,91,93-98 are allowd in&out )
I have worked with Cisco switches for over 20 years - easy.
There is tons of informatioin on the Internet showing how to do this on a Cisco.
When it comes to doing this on a Mikrotik ROS device, this is almost impossible.
You have to lookup what switch chip you have so that you know what the switch can do.
You are all over the place in many settings/screens.
Even if you are a god on Cisco switches, odds are you will fail the first dozen times trying to configure the above parts on a Mikrotik !
And , even if you decide to research and watch videos to switch on a Mikrotik, the information resources explaining how to do so are almost impossible to locate.
I wish Mikrotik would make some changes to their GUI ( web and winbox ) and create a new screen that has everything on one screen.
Am I the only person who has been trying for years to figure out how to do this on a Mikrotik and still can’t do this ?
frustrated - North Idaho Tom Jones
The reason there are so many switch chip discrepancies is because the Big Mik cuts costs by only giving you what you need, and that “need” changes depending on the device, unlike Cisco/other-vendor-here which gives you all the features as well as all the costs.
I almost agree.
Take Cisco switches for example.
There are many different types of switch chips in the many various types of Cisco switches.
What do all of them have in common ? – Identical configuration menus ( CLI or http ) across all of their IOS switches. If something is not supported , it’s easy/quick to figure it out.
On a Cisco , you can do a show run and see everything nice and neat and all in simple logical order.
On a Mikrotik, you can do an export and you are all over the place.
I am not saying a ROS re-write is necessary , but I do feel there needs to be a much better/easier way to configure vlan switching.
Even if it can’t be put in CLI or http or winbox ( for a simple single switch screen ) , then at least come up with a 3’rd tool to do this ( winbox-switch ??? ) or an app that runs on a windows computer that talks to the remote Mikrotik and makes all the switch changes easy because all you see is a simple one-screen switch layout on your desktop showing you what it can do or has done.
Mikrotik wireless is easily 6 years behind other WiFi vendors.
Mikrotik ACV2 never supported MU-MIMO. And it has only been placed in TESTING BRANCH in 2021.
I have been using wifi 6 from other vendors, coming up on a year now.
“Holy S–t, if that could control a good radio… That would be awesome!!!”
That is what everyone who has ever seen me grinding my teeth as I work in caps-man, has to say.
I wasted hundreds of hours on custom scripts and tweaking the hell out of caps-man. Only to be handicapped by it’s inherit radio flaws. It’s become apparent that Mikrotik wrote their own wifi drivers years ago. And they refuse to switch. So not only do their wifi access points perform like crap… They will not get better. Meanwhile, the rest of the world absolutely trounced them.
While it may cost more to use other vendors… The lack of client complaints, is absolutely worth it.
Well on bridge vlan filtering its time intensive… but easy.
Bridge ports are quick for trunk config, access ports a tad more work to add the pvid but if you have lots,
its a cut and paste and then just change PVID number and Etherport # on a line by line basis and done!
The real work is bridge vlan filter rules.
For each vlan ID that has a unique set of tagged and untagged ports a separate line is required.
When two or more VLAN IDs have identical sets of tagged and untagged ports one line can be used to capture them.