I have a HEX acting as router and a second HAPax2 as a access point. In between the line is a COAX cable that has Ethernet over Coax through MoCA. I am experiencing weird behavior where there is an unstable connection causing a +/- 50% ICMP packet loss. Client do get a DHCP lease and can connect to routeros but difficult. However, if i switch the HAPax2 with a regular dump switch, there is no packet loss and fast throughput (measured with iperf)!
The goal is to run the HAPax2 as access point.
Various setup and configurations i tried.
Preferred setup
Iperf server -> HEX -> MoCA adapter 1 ->COAX -> MoCA adapter 2 -> HAPax2 -> Client PC: Result: Iperf 20mbit/s and 50% ICMP packet loss
The HEX is acting as the main router with DHCP server. The HAPax2 is configured as a switch with DHCP disabled and a static IP on ether1. The client PC is running on ether2. Otherwise it is a basic configuration. The client PC receives the correct dhcp lease from the dhcp server and can connect to the webgui of routeros. There are no splitters on the COAX cable. Just a strait line from adapter 1 to adapter 2.
Hardware control setup:
Iperf server -> HEX -> MoCA adapter 1 ->COAX -> MoCA adapter 2 -> Client PC: Result: Iperf 350mbit/s and 0% ICMP packet loss
Removing the HAPax2 result in a direct dhcp lease from the dhcp server. The client pc is connected to cable with wifi disabled. Speed is fast and steady. This setup shows it is no faulty MoCA hardware.
Access point configuration control setup.
Iperf server -> HEX -> Powerline adapter 1 -> Powercable -> Powerline adapter 2 -> HAPax2 -> Client PC: result Iperf 70mbit/s and 0% icmp packet loss
Having a same configuration but with the setup with a Powerline will result in both the Client PC and the HAPax2 steady and happy. The performance of the Powerline is lacking behind that of the MoCA solution. This was my initial setup and worked, albeit slow connection. Again HEX is main router and HAPax2 configured as access point. This setup shows that the access point configuration works.
Hardware control setup 2
Resetting the HAPax2 to is default settings will give me a fast and steady connection albeit with NAT behind NAT.
Iperf server -> HEX -> MoCA adapter 1 ->COAX -> MoCA adapter 2 -> HAPax2 -> Client PC: Result: Ipef 350mbit/s and 0% ICMP packet loss
This setup is the default out of the box setup for RouterOS. So for the HAPax2 NAT is enabled, DHCP server is enabled on LAN with 192.168.88.0/24. On ether1 the HAPax2 get's a DHCP lease from the HEX. Everything works fine, but you get NAT behind NAT which is a situation i want to avoid. This setup shows that there is no hardware issues with the HAPax2.
The preliminary conclusion that i can draw is that i must be missing something in the configuration as a access point in combination with the MoCA adapters. I have read that COAX is half duplex. But how this translate into a configuration setting i do not know. I would assume that the interface / ethernet / Auto Negotiation enabled (default configuration) would handle this kind half duplex.
What might be causing the unstable connection to the HAPax2?
What might i be overlooking?
Thank you very much for you advice in advance.
Configuration of the HAPax2 with some information removed.
# 2024-01-04 17:17:20 by RouterOS 7.13
# software id = D2TY-4DYI
#
# model = C52iG-5HaxD2HaxD
/interface bridge
add admin-mac=48:A9:8A:D7:EB:C7 auto-mac=no comment=defconf name=bridge port-cost-mode=short
/interface wifi datapath
add bridge=bridge disabled=no name=capdp
/interface wifi
# managed by CAPsMAN
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=default-dhcp disabled=yes interface=bridge lease-time=10m name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether2 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=ether3 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=ether4 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=ether5 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=wifi1 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=wifi2 internal-path-cost=10 path-cost=10
add bridge=bridge interface=ether1 internal-path-cost=10 path-cost=10
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf disabled=yes interface=ether1 list=WAN
/interface wifi cap
set certificate=request discovery-interfaces=bridge enabled=yes slaves-datapath=capdp
/ip address
add address=192.168.1.4/24 comment=defconf interface=ether1 network=192.168.1.0
/ip dhcp-client
add comment=defconf disabled=yes interface=ether1
Ping results of the HEX -> MoCA -> HAP setup.
Pinging 192.168.1.15 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=5ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Ping statistics for 192.168.1.15:
Packets: Sent = 20, Received = 9, Lost = 11 (55% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 4ms
Iperf results of the HEX -> MoCA -> HAP setup.
Connecting to host 192.168.1.15, port 4444
[ 4] local 192.168.1.10 port 8213 connected to 192.168.1.15 port 4444
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.01 sec 512 KBytes 4.16 Mbits/sec
[ 4] 1.01-2.00 sec 7.25 MBytes 61.2 Mbits/sec
[ 4] 2.00-3.01 sec 0.00 Bytes 0.00 bits/sec
[ 4] 3.01-4.00 sec 384 KBytes 3.18 Mbits/sec
[ 4] 4.00-5.01 sec 14.9 MBytes 124 Mbits/sec
[ 4] 5.01-6.01 sec 0.00 Bytes 0.00 bits/sec
[ 4] 6.01-7.00 sec 256 KBytes 2.12 Mbits/sec
[ 4] 7.00-8.01 sec 10.8 MBytes 89.8 Mbits/sec
[ 4] 8.01-9.01 sec 0.00 Bytes 0.00 bits/sec
iperf3: error - control socket has closed unexpectedly
The goal is to run the HAPax2 as access point.
Various setup and configurations i tried.
Preferred setup
Iperf server -> HEX -> MoCA adapter 1 ->COAX -> MoCA adapter 2 -> HAPax2 -> Client PC: Result: Iperf 20mbit/s and 50% ICMP packet loss
The HEX is acting as the main router with DHCP server. The HAPax2 is configured as a switch with DHCP disabled and a static IP on ether1. The client PC is running on ether2. Otherwise it is a basic configuration. The client PC receives the correct dhcp lease from the dhcp server and can connect to the webgui of routeros. There are no splitters on the COAX cable. Just a strait line from adapter 1 to adapter 2.
Hardware control setup:
Iperf server -> HEX -> MoCA adapter 1 ->COAX -> MoCA adapter 2 -> Client PC: Result: Iperf 350mbit/s and 0% ICMP packet loss
Removing the HAPax2 result in a direct dhcp lease from the dhcp server. The client pc is connected to cable with wifi disabled. Speed is fast and steady. This setup shows it is no faulty MoCA hardware.
Access point configuration control setup.
Iperf server -> HEX -> Powerline adapter 1 -> Powercable -> Powerline adapter 2 -> HAPax2 -> Client PC: result Iperf 70mbit/s and 0% icmp packet loss
Having a same configuration but with the setup with a Powerline will result in both the Client PC and the HAPax2 steady and happy. The performance of the Powerline is lacking behind that of the MoCA solution. This was my initial setup and worked, albeit slow connection. Again HEX is main router and HAPax2 configured as access point. This setup shows that the access point configuration works.
Hardware control setup 2
Resetting the HAPax2 to is default settings will give me a fast and steady connection albeit with NAT behind NAT.
Iperf server -> HEX -> MoCA adapter 1 ->COAX -> MoCA adapter 2 -> HAPax2 -> Client PC: Result: Ipef 350mbit/s and 0% ICMP packet loss
This setup is the default out of the box setup for RouterOS. So for the HAPax2 NAT is enabled, DHCP server is enabled on LAN with 192.168.88.0/24. On ether1 the HAPax2 get's a DHCP lease from the HEX. Everything works fine, but you get NAT behind NAT which is a situation i want to avoid. This setup shows that there is no hardware issues with the HAPax2.
The preliminary conclusion that i can draw is that i must be missing something in the configuration as a access point in combination with the MoCA adapters. I have read that COAX is half duplex. But how this translate into a configuration setting i do not know. I would assume that the interface / ethernet / Auto Negotiation enabled (default configuration) would handle this kind half duplex.
What might be causing the unstable connection to the HAPax2?
What might i be overlooking?
Thank you very much for you advice in advance.
Configuration of the HAPax2 with some information removed.
# 2024-01-04 17:17:20 by RouterOS 7.13
# software id = D2TY-4DYI
#
# model = C52iG-5HaxD2HaxD
/interface bridge
add admin-mac=48:A9:8A:D7:EB:C7 auto-mac=no comment=defconf name=bridge port-cost-mode=short
/interface wifi datapath
add bridge=bridge disabled=no name=capdp
/interface wifi
# managed by CAPsMAN
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=default-dhcp disabled=yes interface=bridge lease-time=10m name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether2 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=ether3 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=ether4 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=ether5 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=wifi1 internal-path-cost=10 path-cost=10
add bridge=bridge comment=defconf interface=wifi2 internal-path-cost=10 path-cost=10
add bridge=bridge interface=ether1 internal-path-cost=10 path-cost=10
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf disabled=yes interface=ether1 list=WAN
/interface wifi cap
set certificate=request discovery-interfaces=bridge enabled=yes slaves-datapath=capdp
/ip address
add address=192.168.1.4/24 comment=defconf interface=ether1 network=192.168.1.0
/ip dhcp-client
add comment=defconf disabled=yes interface=ether1
Ping results of the HEX -> MoCA -> HAP setup.
Pinging 192.168.1.15 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=5ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Request timed out.
Reply from 192.168.1.15: bytes=32 time=4ms TTL=64
Ping statistics for 192.168.1.15:
Packets: Sent = 20, Received = 9, Lost = 11 (55% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 4ms
Iperf results of the HEX -> MoCA -> HAP setup.
Connecting to host 192.168.1.15, port 4444
[ 4] local 192.168.1.10 port 8213 connected to 192.168.1.15 port 4444
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.01 sec 512 KBytes 4.16 Mbits/sec
[ 4] 1.01-2.00 sec 7.25 MBytes 61.2 Mbits/sec
[ 4] 2.00-3.01 sec 0.00 Bytes 0.00 bits/sec
[ 4] 3.01-4.00 sec 384 KBytes 3.18 Mbits/sec
[ 4] 4.00-5.01 sec 14.9 MBytes 124 Mbits/sec
[ 4] 5.01-6.01 sec 0.00 Bytes 0.00 bits/sec
[ 4] 6.01-7.00 sec 256 KBytes 2.12 Mbits/sec
[ 4] 7.00-8.01 sec 10.8 MBytes 89.8 Mbits/sec
[ 4] 8.01-9.01 sec 0.00 Bytes 0.00 bits/sec
iperf3: error - control socket has closed unexpectedly
Statistics: Posted by Tikkie123 — Thu Jan 04, 2024 6:56 pm