Hello I’m looking for help with CAPsMAN wired behavior.
My network:
internet → Router(hAP ac3) → RB260GS → 2x cAP ac (CAPsMAN) ((( —5Ghz— ))) Windows 10 SMB client
RB260GS → OMV home server
hAP ac3 = Router, CAP manager
cAP ac = CAPsMAN APs, Bridged LANs and WLANs
RB260GS = switch
Server = openmediavault server
CAPsMAN basic configuration
add country="czech republic" datapath.client-to-client-forwarding=yes interface-list=LAN local-forwarding=yes distance=indoors installation=indoor mode=ap name=cfg1 security.authentication-types=wpa-psk,wpa2-psk encryption=aes-ccm ssid=MySSID
All wired and android wireless clients works well.
But without local forwarding CAPsMAN same error appears at all Windows 10 machines as wirelles clients, tested DELL, Acer, Lenovo notebooks.
Transfer to server always drops after average 60MB with error “0x8007003b An unexpected network error occurred.”
I changing only datapath local-forwarding and bridge to reach this error.
Firewall:
-“Building Advanced Firewall” like without bad TCP a ICMP chains
-raw firewall bypassed for testing
SMB client side wireshark:
Looks like CAPsMAN without local forwarding cause TCP drops under heavy load.
After enable local forwarding, copy data to server works well.
Is it Widows bug, or RouterOS CAPsMAN encapsulation bug, or I overlooked some setting?
I use CAPsMAN without local forwarding for practical reason better seeing and managing traffic from APs, I know it isnt deadly important. But I d like find where is problem.
router.rsc (15.1 KB)
