hAP ac同士をPPPoEで接続する(計測)

hAP ac同士をPPPoEで接続し速度計測を行います

最初に

今回の記事はこの記事の続きです

hAP ac同士をPPPoEで接続する(設定) | fefcc.net
https://fefcc.net/archives/722

前記事でPPPoE構築した状態で速度計測を行いました
簡単に通信の流れを書くとこんな感じ
計測PC -> PPPoEクライアントhAP ac -> PPPoEサーバhAP ac -> 計測PC
PPPoEサーバ側はWANへ出ずhAP ac内のブリッジにて接続されています

DHCPでの2重ルータ状態で計測した下記記事のPPPoE接続版となります

hAP ac同士を接続しスループット計測 | fefcc.net
https://fefcc.net/archives/718

計測結果

前回の計測と同じくpingとiperf3(TCP/UDP)で計測しました
使用したiperf3のバージョンはこちら

[root@nettest02 ~]# iperf3 -v
iperf 3.1.7
Linux nettest02 3.10.0-862.6.3.el7.x86_64 #1 SMP Tue Jun 26 16:32:21 UTC 2018 x86_64
Optional features available: CPU affinity setting, IPv6 flow label, TCP congestion algorithm setting, sendfile / zerocopy, socket pacing

ping

[root@nettest02 ~]# ping -c 10 192.168.88.199
PING 192.168.88.199 (192.168.88.199) 56(84) bytes of data.
64 bytes from 192.168.88.199: icmp_seq=1 ttl=62 time=0.474 ms
64 bytes from 192.168.88.199: icmp_seq=2 ttl=62 time=0.468 ms
64 bytes from 192.168.88.199: icmp_seq=3 ttl=62 time=0.481 ms
64 bytes from 192.168.88.199: icmp_seq=4 ttl=62 time=0.481 ms
64 bytes from 192.168.88.199: icmp_seq=5 ttl=62 time=0.474 ms
64 bytes from 192.168.88.199: icmp_seq=6 ttl=62 time=0.458 ms
64 bytes from 192.168.88.199: icmp_seq=7 ttl=62 time=0.475 ms
64 bytes from 192.168.88.199: icmp_seq=8 ttl=62 time=0.427 ms
64 bytes from 192.168.88.199: icmp_seq=9 ttl=62 time=0.448 ms
64 bytes from 192.168.88.199: icmp_seq=10 ttl=62 time=0.492 ms

--- 192.168.88.199 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8999ms
rtt min/avg/max/mdev = 0.427/0.467/0.492/0.032 ms

iperf3 TCP

[root@nettest02 ~]# iperf3 -c 192.168.88.199 -i 1 -t 10
Connecting to host 192.168.88.199, port 5201
[  4] local 192.168.87.11 port 60208 connected to 192.168.88.199 port 5201
[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
[  4]   0.00-1.00   sec   110 MBytes   923 Mbits/sec   49    231 KBytes       
[  4]   1.00-2.00   sec   109 MBytes   913 Mbits/sec   40    190 KBytes       
[  4]   2.00-3.00   sec   109 MBytes   918 Mbits/sec   32    234 KBytes       
[  4]   3.00-4.00   sec   109 MBytes   918 Mbits/sec   35    252 KBytes       
[  4]   4.00-5.00   sec   110 MBytes   920 Mbits/sec   33    259 KBytes       
[  4]   5.00-6.00   sec   109 MBytes   915 Mbits/sec   31    234 KBytes       
[  4]   6.00-7.00   sec   110 MBytes   920 Mbits/sec   31    234 KBytes       
[  4]   7.00-8.00   sec   109 MBytes   917 Mbits/sec   38    251 KBytes       
[  4]   8.00-9.00   sec   109 MBytes   918 Mbits/sec   57    165 KBytes       
[  4]   9.00-10.00  sec   109 MBytes   916 Mbits/sec   34    236 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  1.07 GBytes   918 Mbits/sec  380             sender
[  4]   0.00-10.00  sec  1.07 GBytes   918 Mbits/sec                  receiver

iperf Done.
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.88.1, port 60206
[  5] local 192.168.88.199 port 5201 connected to 192.168.88.1 port 60208
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-1.00   sec   105 MBytes   885 Mbits/sec                  
[  5]   1.00-2.00   sec   109 MBytes   916 Mbits/sec                  
[  5]   2.00-3.00   sec   109 MBytes   917 Mbits/sec                  
[  5]   3.00-4.00   sec   109 MBytes   918 Mbits/sec                  
[  5]   4.00-5.00   sec   110 MBytes   920 Mbits/sec                  
[  5]   5.00-6.00   sec   109 MBytes   916 Mbits/sec                  
[  5]   6.00-7.00   sec   109 MBytes   918 Mbits/sec                  
[  5]   7.00-8.00   sec   110 MBytes   920 Mbits/sec                  
[  5]   8.00-9.00   sec   109 MBytes   918 Mbits/sec                  
[  5]   9.00-10.00  sec   109 MBytes   917 Mbits/sec                  
[  5]  10.00-10.04  sec  3.90 MBytes   850 Mbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-10.04  sec  0.00 Bytes  0.00 bits/sec                  sender
[  5]   0.00-10.04  sec  1.07 GBytes   914 Mbits/sec                  receiver

iperf3 UDP 10G

[root@nettest02 ~]# iperf3 -c 192.168.88.199 -u -i 1 -t 10 -b 10G
Connecting to host 192.168.88.199, port 5201
[  4] local 192.168.87.11 port 51191 connected to 192.168.88.199 port 5201
[ ID] Interval           Transfer     Bandwidth       Total Datagrams
[  4]   0.00-1.00   sec   114 MBytes   954 Mbits/sec  83543  
[  4]   1.00-2.00   sec   114 MBytes   954 Mbits/sec  83481  
[  4]   2.00-3.00   sec   114 MBytes   954 Mbits/sec  83483  
[  4]   3.00-4.00   sec   114 MBytes   954 Mbits/sec  83514  
[  4]   4.00-5.00   sec   114 MBytes   954 Mbits/sec  83482  
[  4]   5.00-6.00   sec   114 MBytes   954 Mbits/sec  83515  
[  4]   6.00-7.00   sec   114 MBytes   954 Mbits/sec  83516  
[  4]   7.00-8.00   sec   114 MBytes   954 Mbits/sec  83484  
[  4]   8.00-9.00   sec   114 MBytes   954 Mbits/sec  83468  
[  4]   9.00-10.00  sec   114 MBytes   954 Mbits/sec  83516  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  4]   0.00-10.00  sec  1.11 GBytes   954 Mbits/sec  0.015 ms  4602/834993 (0.55%)  
[  4] Sent 834993 datagrams

iperf Done.
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 192.168.88.1, port 60196
[  5] local 192.168.88.199 port 5201 connected to 192.168.88.1 port 51191
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  5]   0.00-1.00   sec   108 MBytes   910 Mbits/sec  0.020 ms  315/79963 (0.39%)  
[  5]   1.00-2.00   sec   113 MBytes   948 Mbits/sec  0.023 ms  507/83484 (0.61%)  
[  5]   2.00-3.00   sec   113 MBytes   947 Mbits/sec  0.013 ms  589/83489 (0.71%)  
[  5]   3.00-4.00   sec   113 MBytes   948 Mbits/sec  0.019 ms  536/83508 (0.64%)  
[  5]   4.00-5.00   sec   113 MBytes   948 Mbits/sec  0.021 ms  474/83484 (0.57%)  
[  5]   5.00-6.00   sec   113 MBytes   950 Mbits/sec  0.022 ms  421/83541 (0.5%)  
[  5]   6.00-7.00   sec   113 MBytes   949 Mbits/sec  0.019 ms  416/83499 (0.5%)  
[  5]   7.00-8.00   sec   113 MBytes   949 Mbits/sec  0.024 ms  402/83465 (0.48%)  
[  5]   8.00-9.00   sec   113 MBytes   948 Mbits/sec  0.019 ms  472/83467 (0.57%)  
[  5]   9.00-10.00  sec   113 MBytes   949 Mbits/sec  0.023 ms  451/83523 (0.54%)  
[  5]  10.00-10.04  sec  4.84 MBytes   955 Mbits/sec  0.015 ms  19/3570 (0.53%)  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Jitter    Lost/Total Datagrams
[  5]   0.00-10.04  sec  0.00 Bytes  0.00 bits/sec  0.015 ms  4602/834993 (0.55%)

hAP acのCPU負荷(iperf3実行時)

PPPoEクライアント側hAP ac

PPPoEサーバ側hAP ac

計測結果について

DHCPでの2重ルータ環境構築時と比較すると
pingが平均値で0.18ms増加
iperf3 TCPは若干の速度低下
iperf3 UDPはLostが出始めるものの速度は変わらず

CPU使用率を見ればわかる通り
2重ルータ状態ではほぼ負荷のなかった受信側(PPPoEサーバ側)が
95%まで上昇とほぼ頭打ちとなっているので
iperf3の結果に関してはその影響が若干出てると思われます

消費電力は無線LANを切った状態でPPPoE確立時のアイドルが4W
iperf3実行時の最大負荷(CPU 95%)でも5Wと+1Wで済んでました

Windows上でのファイル転送

おまけでPPPoEクライアント側のPCへ
PPPoEサーバ側WANポートを通してファイル転送をしてる様子です

最後に

今回紹介しているMikroTik hAP acの基本情報や入手元については
こちらの記事をご覧ください

MikroTik hAP acを開封 | fefcc.net
https://fefcc.net/archives/552