MONITOR 1.4.7 does not seem to like my WiFi mesh setup for auto-uploads
The Problem: Repetier-Server Monitor v1.4.7 fails when auto-uploading from a device connected to an auxiliary node on a WiFi Mesh setup.
I am using a TP-Link Onemesh/Easymesh setup for coverage over my land. My workshop is pretty remote, using a TP-link AX21 that may or may not bridge between 3 TP-Link RE700xs depending on dynamic routing. The main router is a TP-link AXE5400.
All of my RepServer Pi3s are hardwired via Ethernet on the AX21 router in the workshop, which is in MESH mode
So, to conceptualize: AX21 (workshop router in MESH mode, All pis are on this, and I am monitoring from this node)<->RE700x (Repeater node)<->AXE5400 (Main router).
When running RepServer Monitor from my workshop PC, any upload from the monitored folders usually fail-- seems to just stall and then after a while, give me an UPLOAD FAILED message through notifications. Sometimes it will work, but I've had it duplicate the files multiple times, only send a 0 byte file, but usually just fail completely.
The connection is STABLE - I've tested it extensively, and ping is OK, PL is OK, and it's not hopping nodes very often. The other test is uploading it from a device connected to the main AXE5400 router, and it seems to work fine.
I suspect it's some kind of bizarre network traversal that's confusing MONITOR. Of course, running a tracert only shows the direct path to the device i'm trying to upload to.
Is there a way to look at what Monitor is doing behind the scenes to see why it's failing so consistently?
I am using a TP-Link Onemesh/Easymesh setup for coverage over my land. My workshop is pretty remote, using a TP-link AX21 that may or may not bridge between 3 TP-Link RE700xs depending on dynamic routing. The main router is a TP-link AXE5400.
All of my RepServer Pi3s are hardwired via Ethernet on the AX21 router in the workshop, which is in MESH mode
So, to conceptualize: AX21 (workshop router in MESH mode, All pis are on this, and I am monitoring from this node)<->RE700x (Repeater node)<->AXE5400 (Main router).
When running RepServer Monitor from my workshop PC, any upload from the monitored folders usually fail-- seems to just stall and then after a while, give me an UPLOAD FAILED message through notifications. Sometimes it will work, but I've had it duplicate the files multiple times, only send a 0 byte file, but usually just fail completely.
The connection is STABLE - I've tested it extensively, and ping is OK, PL is OK, and it's not hopping nodes very often. The other test is uploading it from a device connected to the main AXE5400 router, and it seems to work fine.
I suspect it's some kind of bizarre network traversal that's confusing MONITOR. Of course, running a tracert only shows the direct path to the device i'm trying to upload to.
Is there a way to look at what Monitor is doing behind the scenes to see why it's failing so consistently?
Comments