Associate
Yeah AX3 is where it's @ I guess, if you can get your hands on one that is.
None the less it is still a great capable device and I'm not sure the 864cpu would handle pi-hole as well.
**Official MikroTik Hardware **
- Thread starter jonneymendoza
- Start date
Yeah AX3 is where it's @ I guess, if you can get your hands on one that is.
None the less it is still a great capable device and I'm not sure the 864cpu would handle pi-hole as well.
Associate
you did well to get an AX2, I haven't seen them on sale or in stock anywhere. It could replace my hAP lite but it is my favourite router.
Last edited:
Associate
Last edited:
Associate
I also noticed some of the WiFi tools are not available with the wave2 router I have.
Code:
country: United Kingdom
2.4ghz: 2412 MHz 20/40mhz 20 dBm
2417 MHz 20/40mhz 20 dBm
2422 MHz 20/40mhz 20 dBm
2427 MHz 20/40mhz 20 dBm
2432 MHz 20/40mhz 20 dBm
2437 MHz 20/40mhz 20 dBm
2442 MHz 20/40mhz 20 dBm
2447 MHz 20/40mhz 20 dBm
2452 MHz 20/40mhz 20 dBm
2457 MHz 20/40mhz 20 dBm
2462 MHz 20/40mhz 20 dBm
2467 MHz 20/40mhz 20 dBm
2472 MHz 20/40mhz 20 dBm
5ghz: 5180 MHz 20/40/80mhz 23 dBm indoor
5200 MHz 20/40/80mhz 23 dBm indoor
5220 MHz 20/40/80mhz 23 dBm indoor
5240 MHz 20/40/80mhz 23 dBm indoor
5260 MHz 20/40/80mhz 23 dBm DFS (CAC 1 min) indoor
5280 MHz 20/40/80mhz 23 dBm DFS (CAC 1 min) indoor
5300 MHz 20/40/80mhz 23 dBm DFS (CAC 1 min) indoor
5320 MHz 20/40/80mhz 23 dBm DFS (CAC 1 min) indoor
5500 MHz 20/40/80/160mhz 30 dBm DFS (CAC 1 min)
5520 MHz 20/40/80/160mhz 30 dBm DFS (CAC 1 min)
5540 MHz 20/40/80/160mhz 30 dBm DFS (CAC 1 min)
5560 MHz 20/40/80/160mhz 30 dBm DFS (CAC 1 min)
5580 MHz 20/40/80/160mhz 30 dBm DFS (CAC 1 min)
5600 MHz 20/40/80/160mhz 30 dBm DFS (CAC 10 min)
5620 MHz 20/40/80/160mhz 30 dBm DFS (CAC 10 min)
5640 MHz 20/40/80/160mhz 30 dBm DFS (CAC 10 min)
5660 MHz 20/40mhz 30 dBm DFS (CAC 1 min)
5680 MHz 20/40mhz 30 dBm DFS (CAC 1 min)
5700 MHz 20mhz 30 dBm DFS (CAC 1 min)
Last edited:
Associate
Back to Basics!
Made me chuckle
Made me chuckle
Associate
Teardown..
Associate
Anybody using FQ_Codel on Mikrotik, I know it's less important the faster you go and that I should just apply it to the upstream but I guess it makes life easier when it comes to sharing the bandwidth. I am finding PCQ slightly slower but more even on the downloads, IE not getting heavy spikes. maybe it just needs fine-tuning not sure what to put in for 250M/25M example as follows via TBB tests. The FQ_Codel seems to Burst vs PCQ more smooth.
Also PCQ uses 20% cpu vs 30% FQ_Codel for the same tests.
Modem
Down 287500061 bps
Up 27500061 bps
QOS disabled 274.4Mbps Down 26.1Mbps Up
QOS Enabled below... QOS set Down 250M Up 25M
PCQ
FQ_Codel
Shout Out to @Steveocee for pointing out that WAN ether1, up is down and down is up....
Edit: I must stress that all these tests are over WiFi with repeatable results
Also PCQ uses 20% cpu vs 30% FQ_Codel for the same tests.
Modem
Down 287500061 bps
Up 27500061 bps
QOS disabled 274.4Mbps Down 26.1Mbps Up
QOS Enabled below... QOS set Down 250M Up 25M
PCQ
FQ_Codel
Shout Out to @Steveocee for pointing out that WAN ether1, up is down and down is up....
Edit: I must stress that all these tests are over WiFi with repeatable results
Last edited:
Look what just arrived
Soldato
Bought a mikrotik wireless wire the other day and have it up and running currently.
I have a concern, which is that the way its set up and where we sit in our external office, my wife's working position at her desk is in view of the master transmitter.
Is this any sort of health hazard? Moving desks around isn't really feasible, I may be able to rearrange the transmitter so she's not in view, but I just want to check whether I'm being mad worrying that a 60GHz signal may or may not be at all dangerous. The max power consumption of each unit is 5W.
Either way it is inevitable at some point while moving between house and home office we'll be in view of the transmitters, but I suppose being in view all day in sat working position is potentially an awful lot worse.
Just looking for someone to hopefully set my mind at ease.
I have a concern, which is that the way its set up and where we sit in our external office, my wife's working position at her desk is in view of the master transmitter.
Is this any sort of health hazard? Moving desks around isn't really feasible, I may be able to rearrange the transmitter so she's not in view, but I just want to check whether I'm being mad worrying that a 60GHz signal may or may not be at all dangerous. The max power consumption of each unit is 5W.
Either way it is inevitable at some point while moving between house and home office we'll be in view of the transmitters, but I suppose being in view all day in sat working position is potentially an awful lot worse.
Just looking for someone to hopefully set my mind at ease.
Soldato
Correct - it won’t pass through skin. If you put your hand in front of the antenna you will lose the connection.
Associate
If I need to power My Hap ax2 over PoE, what do I need to buy to supply power to it so I can mount it to the ceiling with just two cables. One from the Internet and another to my switch I don't have any PoE gear at all apart from the Hap ax2. Or is this not how it works, am I correct in thinking the PoE bit just relates to port 1.
Block Diagram https://i.mt.lv/cdn/product_files/C52iG-5HaxD2HaxD-TC_220807.png
Current Setup VM Hub----> cat5e----> Ether1 Ether2------> Switch none PoE
Powering
Number of DC inputs 2 (PoE-in, DC jack)
PoE-in input Voltage 18-28 V
DC jack input Voltage 12-28 V
PoE-out Passive PoE Ether1, max out per port output (input < 30 V): 600mA
Max total out 0.6 A
Total output power 16.8 W
Power adapter nominal voltage 24 V
Power adapter nominal current 1.2 A
Max power consumption (without attachments) 12 W
Max power consumption 27 W
Block Diagram https://i.mt.lv/cdn/product_files/C52iG-5HaxD2HaxD-TC_220807.png
Current Setup VM Hub----> cat5e----> Ether1 Ether2------> Switch none PoE
Powering
Number of DC inputs 2 (PoE-in, DC jack)
PoE-in input Voltage 18-28 V
DC jack input Voltage 12-28 V
PoE-out Passive PoE Ether1, max out per port output (input < 30 V): 600mA
Max total out 0.6 A
Total output power 16.8 W
Power adapter nominal voltage 24 V
Power adapter nominal current 1.2 A
Max power consumption (without attachments) 12 W
Max power consumption 27 W
Don
I believe all you should need is: RBGPOE PoE injector, for Gigabit LAN products
Last edited:
Associate
Brilliant, I'll get one of those.I believe all you should need is: RBGPOE PoE injector, for Gigabit LAN products
Thanks
Associate
Anybody trying 7.7 Stable.
I'm testing now.
*) wifiwave2 - added "datapath" settings to configure data forwarding for an interface (CLI only);
*) wifiwave2 - added "ft-preserve-vlanid" parameter to control whether to change VLAN ID after FT;
*) wifiwave2 - added "provisioning" menu to automatically assign interface configurations to radios (CLI only);
*) wifiwave2 - added disable/enable commands to configuration profile sub-menus (CLI only);
*) wifiwave2 - added information of per-station throughput in the registration table;
*) wifiwave2 - added initial CAPsMAN support (only compatible with wifiwave2 interfaces) (CLI only);
*) wifiwave2 - added interworking/Hotspot 2.0 support (CLI only);
*) wifiwave2 - added more informative log messages on configuration profile changes;
*) wifiwave2 - added option to set per-client vlan-id in access list (only supported on 802.11ax interfaces) (CLI only);
*) wifiwave2 - do not permit a client device to be connected to more than one interface at a time;
*) wifiwave2 - fixed "radio-mac" provisioning matcher;
*) wifiwave2 - fixed 4-way handshake with TKIP;
*) wifiwave2 - improved compliance with regulatory domain information;
*) wifiwave2 - improved general system stability;
*) wifiwave2 - improved system stability when multiple virtual AP are configured;
*) wifiwave2 - properly report interface on which traffic is received when multiple station interfaces are used concurrently;
*) wifiwave2 - released packages for MMIPS, PPC, TILE and x86;
*) wifiwave2 - removed maximum limit for group key update interval and changed the default to 1 day;
I'm testing now.
*) wifiwave2 - added "datapath" settings to configure data forwarding for an interface (CLI only);
*) wifiwave2 - added "ft-preserve-vlanid" parameter to control whether to change VLAN ID after FT;
*) wifiwave2 - added "provisioning" menu to automatically assign interface configurations to radios (CLI only);
*) wifiwave2 - added disable/enable commands to configuration profile sub-menus (CLI only);
*) wifiwave2 - added information of per-station throughput in the registration table;
*) wifiwave2 - added initial CAPsMAN support (only compatible with wifiwave2 interfaces) (CLI only);
*) wifiwave2 - added interworking/Hotspot 2.0 support (CLI only);
*) wifiwave2 - added more informative log messages on configuration profile changes;
*) wifiwave2 - added option to set per-client vlan-id in access list (only supported on 802.11ax interfaces) (CLI only);
*) wifiwave2 - do not permit a client device to be connected to more than one interface at a time;
*) wifiwave2 - fixed "radio-mac" provisioning matcher;
*) wifiwave2 - fixed 4-way handshake with TKIP;
*) wifiwave2 - improved compliance with regulatory domain information;
*) wifiwave2 - improved general system stability;
*) wifiwave2 - improved system stability when multiple virtual AP are configured;
*) wifiwave2 - properly report interface on which traffic is received when multiple station interfaces are used concurrently;
*) wifiwave2 - released packages for MMIPS, PPC, TILE and x86;
*) wifiwave2 - removed maximum limit for group key update interval and changed the default to 1 day;
Looks cool.
Soldato
We’ve had two of the bigger brother of this on test For about 3 months now and apart from being SwitchPr0n they’re utterly pointless for anything currently in the real world. These were built for the likes of Meta.