According to what he wrote he doesn't:He need the ONT my friend.
ok, thanks, the connection I want is something like this:
ftth-->ont-->wifi router (the supposed to be Mikrotik hap ac2)
the first two are already in my home, I need the third one.
https://mikrotik.com/product/SFPONU...
Mikrotik don't do/make directly GPON/MODEM. ...
https://mikrotik.com/product/SFPONU...
Mikrotik don't do/make directly GPON/MODEM. ...
the isp says 1000/300
and, granted, 300/200
I'm not yet at home so I can not tell more ...
I live most of the time alone, so I use one device at time (well, I can watch a football match while I'm using Facebook, but it's not relevant I suppose)
I do not have a NAS.
chromecast streams for ex. a youtube video at max 1080, the paytv streams directly from their server in full hd (it can reach up to 4k indeed, but my television is not 4k capable, so i watch in 1080p)
and also my imac is not 4k capable.
I'm not from Mikrotik but I've done a measurement specifically targeted to performance when PPPoE is used, together with firewall in different level of optimization. I've provided the link to the results in my post #7 above. So yes, hAP ac² does handle 1 Gbit/s bidirectionally over PPPoE with fasttrack, spending about 30% of total CPU capacity on it; without fastrack, it is at slightly above 1/2 of that throughput, and the CPU load is at about 1/2 of the totally available capacity.Ummm a LOT.... maybe this router is "small" for that.
But I prefer an answer from somebody from mikrotik.
Just a word of caution: according to MT support, switch chip embedded in IPQ4xxx (the SoC used in hAP ac2) features a bug in scenario which includes pppoe-client run on top of vlan interface, PPPoE discovery packets and untagging them on egress (the last part being the problematic one). I guess this won't affect you as PPPoE will leave your RB tagged. Workaround is to use bridge vlan-filtering (it works just fine), but does put some stress on router's CPU - not neglectable with a few 100Mbps.the mikrotik has to be configured with a V-Lan (835) on the Wan port and with a ppoe connection
The former.@mkx, is that issue related to egress untagging of a VLAN tag or of the proprietary tag bearing the Ethernet interface address which the CPU uses to tell the switch which egress port to use?
Here I am again to you.
In the end I activated a less performing connection because actually that gigabit connection was too expensive and it was not worth it for my use.
I have instead activated a connection, always in ffth, at 200mbps, and the ISP has installed me a hap mini but in fact I have some troubles.
My mac disconnects randomly. the wifi icon is active and seems to be connected, but keeping a ping open on the router's ip (via mac os terminal) I see that it does not reach it.
this can happen 1 time a day or 10 times a day, for no apparent reason.
When this happens the router is not reachable for a few minutes (from 2-3 minutes up, on average, to 10-15) then it reconnects itself.
To speed up the reconnection I can disable and reactivate the wifi of the mac from the wifi icon.
With the other devices I did not notice disconnections.
The channel is currently set to Automatic, previously it was a fixed channel but I had the same problem. When I changed to another fixed channel I had big problems of connection, it almost never connected and when it was successful it remained connected a few seconds / minute, and then it fell.
There are no other routers on those channels and all the devices are at 4-8 meters distant, with no walls.
Unfortunately the router is blocked by the ISP so I can not do any change. But I think there is a problem more in terms of software than in channel (if I take another router and connect it to the mikrotik and put it on the same channel, it works perfectly ...)
Also I have unstable pings: from 1.300ms to 100.000ms (ping on the router) while when it was on the channel that did not work the pings were also 6.000.000ms.
The ISP says there are no problems on their side...so I dunno what to do...
I would still like to buy the ac2 so I can configure it as I want (and so for getting the full speed without the 100mbps cap of the mini hap due to his 100mbps lan port) but I don't want to have the same problem...
Do you think it's a routeros problem? or maybe it's an hardware incompatibility with mini hap?
my mac wifi card works properly with other routers/network, and anyway I just tried to erase all the network preferences without solve the problem...
I'm sorry, those are the values during the issue with the fixed channel with incompatibility problems (few minutes connected then the connection dropped):
64 bytes from 192.168.10.1: icmp_seq=20593 ttl=64 time=1.106 ms
64 bytes from 192.168.10.1: icmp_seq=20594 ttl=64 time=9.117 ms
64 bytes from 192.168.10.1: icmp_seq=20595 ttl=64 time=1.444 ms
64 bytes from 192.168.10.1: icmp_seq=20596 ttl=64 time=1001.384 ms
64 bytes from 192.168.10.1: icmp_seq=20597 ttl=64 time=1033.101 ms
64 bytes from 192.168.10.1: icmp_seq=20598 ttl=64 time=67.216 ms
64 bytes from 192.168.10.1: icmp_seq=20599 ttl=64 time=356.064 ms
64 bytes from 192.168.10.1: icmp_seq=20600 ttl=64 time=11.985 ms
64 bytes from 192.168.10.1: icmp_seq=20601 ttl=64 time=1689.592 ms
64 bytes from 192.168.10.1: icmp_seq=20602 ttl=64 time=739.624 ms
64 bytes from 192.168.10.1: icmp_seq=20603 ttl=64 time=284.389 ms
64 bytes from 192.168.10.1: icmp_seq=20604 ttl=64 time=355.536 ms
64 bytes from 192.168.10.1: icmp_seq=20605 ttl=64 time=7.931 ms
64 bytes from 192.168.10.1: icmp_seq=20606 ttl=64 time=2.030 ms
64 bytes from 192.168.10.1: icmp_seq=20607 ttl=64 time=1.638 ms
64 bytes from 192.168.10.1: icmp_seq=20608 ttl=64 time=1.916 ms
64 bytes from 192.168.10.1: icmp_seq=20609 ttl=64 time=69.548 ms
64 bytes from 192.168.10.1: icmp_seq=20610 ttl=64 time=24.315 ms
64 bytes from 192.168.10.1: icmp_seq=20611 ttl=64 time=5.847 ms
64 bytes from 192.168.10.1: icmp_seq=20612 ttl=64 time=2.511 ms
64 bytes from 192.168.10.1: icmp_seq=20613 ttl=64 time=1.460 ms
64 bytes from 192.168.10.1: icmp_seq=20614 ttl=64 time=36.485 ms
64 bytes from 192.168.10.1: icmp_seq=20615 ttl=64 time=2.434 ms
Request timeout for icmp_seq 20617
64 bytes from 192.168.10.1: icmp_seq=20616 ttl=64 time=2111.054 ms
64 bytes from 192.168.10.1: icmp_seq=20617 ttl=64 time=1110.350 ms
64 bytes from 192.168.10.1: icmp_seq=20618 ttl=64 time=1496.038 ms
64 bytes from 192.168.10.1: icmp_seq=20620 ttl=64 time=748.860 ms
64 bytes from 192.168.10.1: icmp_seq=20621 ttl=64 time=83.973 ms
Request timeout for icmp_seq 20623
Request timeout for icmp_seq 20624
Request timeout for icmp_seq 20625
64 bytes from 192.168.10.1: icmp_seq=20623 ttl=64 time=3678.486 ms
64 bytes from 192.168.10.1: icmp_seq=20624 ttl=64 time=2677.941 ms
Request timeout for icmp_seq 20628
Request timeout for icmp_seq 20629
Request timeout for icmp_seq 20630
64 bytes from 192.168.10.1: icmp_seq=20625 ttl=64 time=6737.358 ms
64 bytes from 192.168.10.1: icmp_seq=20626 ttl=64 time=5736.842 ms
64 bytes from 192.168.10.1: icmp_seq=20627 ttl=64 time=4736.788 ms
64 bytes from 192.168.10.1: icmp_seq=20628 ttl=64 time=3736.273 ms
64 bytes from 192.168.10.1: icmp_seq=20629 ttl=64 time=2734.735 ms
64 bytes from 192.168.10.1: icmp_seq=20630 ttl=64 time=1734.476 ms
64 bytes from 192.168.10.1: icmp_seq=20631 ttl=64 time=729.978 ms
64 bytes from 192.168.10.1: icmp_seq=20632 ttl=64 time=1883.099 ms
64 bytes from 192.168.10.1: icmp_seq=20633 ttl=64 time=880.844 ms
64 bytes from 192.168.10.1: icmp_seq=20634 ttl=64 time=254.967 ms
64 bytes from 192.168.10.1: icmp_seq=20635 ttl=64 time=116.320 ms
64 bytes from 192.168.10.1: icmp_seq=20636 ttl=64 time=1268.493 ms
64 bytes from 192.168.10.1: icmp_seq=20637 ttl=64 time=290.232 ms
64 bytes from 192.168.10.1: icmp_seq=20638 ttl=64 time=2325.129 ms
64 bytes from 192.168.10.1: icmp_seq=20639 ttl=64 time=1321.953 ms
64 bytes from 192.168.10.1: icmp_seq=20640 ttl=64 time=319.970 ms
64 bytes from 192.168.10.1: icmp_seq=20641 ttl=64 time=129.697 ms
64 bytes from 192.168.10.1: icmp_seq=20642 ttl=64 time=1213.285 ms
64 bytes from 192.168.10.1: icmp_seq=20643 ttl=64 time=210.389 ms
64 bytes from 192.168.10.1: icmp_seq=20644 ttl=64 time=2694.722 ms
64 bytes from 192.168.10.1: icmp_seq=20645 ttl=64 time=1694.713 ms
64 bytes from 192.168.10.1: icmp_seq=20646 ttl=64 time=694.535 ms
64 bytes from 192.168.10.1: icmp_seq=20647 ttl=64 time=305.937 ms
64 bytes from 192.168.10.1: icmp_seq=20648 ttl=64 time=2012.982 ms
64 bytes from 192.168.10.1: icmp_seq=20649 ttl=64 time=1128.094 ms
64 bytes from 192.168.10.1: icmp_seq=20650 ttl=64 time=125.739 ms
64 bytes from 192.168.10.1: icmp_seq=20651 ttl=64 time=1799.265 ms
64 bytes from 192.168.10.1: icmp_seq=20652 ttl=64 time=824.765 ms
64 bytes from 192.168.10.1: icmp_seq=20653 ttl=64 time=6875.559 ms
64 bytes from 192.168.10.1: icmp_seq=20654 ttl=64 time=5873.657 ms
and this is the actual situation (set to auto):
64 bytes from 192.168.10.1: icmp_seq=56740 ttl=64 time=1.585 ms
64 bytes from 192.168.10.1: icmp_seq=56741 ttl=64 time=1.927 ms
64 bytes from 192.168.10.1: icmp_seq=56742 ttl=64 time=1.636 ms
64 bytes from 192.168.10.1: icmp_seq=56743 ttl=64 time=2.383 ms
64 bytes from 192.168.10.1: icmp_seq=56744 ttl=64 time=1.382 ms
64 bytes from 192.168.10.1: icmp_seq=56745 ttl=64 time=1.799 ms
64 bytes from 192.168.10.1: icmp_seq=56746 ttl=64 time=1.507 ms
64 bytes from 192.168.10.1: icmp_seq=56747 ttl=64 time=1.949 ms
64 bytes from 192.168.10.1: icmp_seq=56748 ttl=64 time=2.711 ms
64 bytes from 192.168.10.1: icmp_seq=56749 ttl=64 time=1.111 ms
64 bytes from 192.168.10.1: icmp_seq=56750 ttl=64 time=1.810 ms
64 bytes from 192.168.10.1: icmp_seq=56751 ttl=64 time=1.884 ms
64 bytes from 192.168.10.1: icmp_seq=56752 ttl=64 time=1.083 ms
64 bytes from 192.168.10.1: icmp_seq=56753 ttl=64 time=1.472 ms
64 bytes from 192.168.10.1: icmp_seq=56754 ttl=64 time=1.672 ms
64 bytes from 192.168.10.1: icmp_seq=56755 ttl=64 time=2.357 ms
64 bytes from 192.168.10.1: icmp_seq=56756 ttl=64 time=2.081 ms
Request timeout for icmp_seq 56757
64 bytes from 192.168.10.1: icmp_seq=56758 ttl=64 time=70.810 ms
64 bytes from 192.168.10.1: icmp_seq=56759 ttl=64 time=1.525 ms
64 bytes from 192.168.10.1: icmp_seq=56760 ttl=64 time=5.153 ms
64 bytes from 192.168.10.1: icmp_seq=56761 ttl=64 time=3.443 ms
64 bytes from 192.168.10.1: icmp_seq=56762 ttl=64 time=1.185 ms
64 bytes from 192.168.10.1: icmp_seq=56763 ttl=64 time=1.885 ms
64 bytes from 192.168.10.1: icmp_seq=56764 ttl=64 time=1.689 ms
64 bytes from 192.168.10.1: icmp_seq=56765 ttl=64 time=27.647 ms
64 bytes from 192.168.10.1: icmp_seq=56766 ttl=64 time=3.096 ms
64 bytes from 192.168.10.1: icmp_seq=56767 ttl=64 time=35.419 ms
64 bytes from 192.168.10.1: icmp_seq=56768 ttl=64 time=1.324 ms
64 bytes from 192.168.10.1: icmp_seq=56769 ttl=64 time=1.115 ms
64 bytes from 192.168.10.1: icmp_seq=56770 ttl=64 time=104.078 ms
64 bytes from 192.168.10.1: icmp_seq=56771 ttl=64 time=1.307 ms
64 bytes from 192.168.10.1: icmp_seq=56772 ttl=64 time=1.274 ms
It's a Mac book problem i seeOhhh you have a DOT (decimals)... 1.106 ms means 1 seg and 106 ms jajajajaja
NOT 1106 ms....
sure, I know, I understand very well and I know it's not your fault!
Unfortunately, with a blocked router, we can not do anything, I can only buy an ac2 and set it up with your advice.
two more things:
channel 9 is the one that gave me problems of impossibility to connect from every device in my house.
currently is configured on auto by the ISP, it only hooks channels 3-6-8.
The 3 is stable but slow, the 6 does not reach 1mbps, the 8 is the most performing (15-40mbps), but it changes a lot over time.
my airport is an old model, it has the 5ghz network but not simultaneously with the 2.4ghz (or one or the other), and since here some devices are only 2.4ghz (printer, webcam) is set on 2.4ghz.
For this reason I say that at the same time, frequency and position it suffers less the noise, as far I can see here.
tried now on windows virtualized on the mac but the airport card is virtualized ad a shared ethernet controller, so Inssider don't see a valid wireless card...This progrma also show you interferences, not just WIFI... it show anything in 2.4 Ghz. Of course, you won't know what is.. but it will show "noise".
Dont you have a "normal" pc? jajaja
no no...wait!A rough idea... you've said you've purchased a hAP ac², right? As there is a copper Ethernet cable between the ONT and the ISP's Mikrotik, you can connect your hAP ac² in bridge mode with hardware acceleration switched off and use /tool sniffer to capture the WAN traffic of the ISP's Mikrotik as it would be forwarded through the bridge. If your ISP uses PPPoE, there is a fair chance that the password goes in plaintext so you might be able to see the username and password and use them to set up the PPPoE client of your hAP ac² the same way; if they use DHCP, it is even easier.
So you could replace their Mikrotik by our own one and have full acccess to configuration.