Open talitha77 opened 5 days ago
Aggregation is working or not ?
I'm not sure.. speed of starlink fluctuates .. is there a way to test? I'm getting quite a few OpenMPTCProuter daemon.err /usr/bin/ss-redir[18582]: remote recv: Socket not connected
Check in Network->MPTCP, bandwitdh tab, and check if more than one WAN is used during a speedtest.
seems so?
the problem with being on a ship is that each WAN is subject to outages. So i dont know which to assign as mptcp master. if WAN1 is master and then goes down, i lose connection for several seconds. I have assigned WAN2 as master as its less flaky.
its all gone horribly wrong
Can you test latest v0.61 rc2 ? https://github.com/Ysurac/openmptcprouter/issues/3528
v0.61rc2-6.6 r0+27346-c7ba5574f5! (https://github.com/user-attachments/assets/80ed68f5-a039-4c46-94ae-65b62c32af09) nothing works at all now.. no eth1 - eth4, so guess wan1 wan2.. however cannot save and apply changes at all
system seems to be unwriteable
i will have to put the old one back. i will try to work on the rpi5, perhaps using vlans instead of ethernet adapters.. does omr have the ability to configure vlans?
old one back in and running.. however it chokes when i put the network online.. i assumed a pi4 was too slow - also read only message again.. thats new
The filesystem readonly is due to corrupted FS or bad SD card.
ah ok.. i guess i will try again with the old image. at the moment it is working so i'll take a rest
tried again with different card, shut down properly, new install.. still says filesystem read only
What is the filesystem you choose ? ext4 or squashfs ?
ext4.. am trying again with 6.0.
I have tried everything i can think of.. now i'm not even getting aggregation. I have a suspicion three starlinks is not a good mix.. initially they all had 192.168.1.x subnets, and things were sort of ok. I changed each starlink routers subnet to 192.168.1.x , 192.168.2,x and 192.168.3.x just to keep them organised but things have got worse.. If its not something particular to starlink then i''m doing something wrong. But i'm just setting up with defaults
Expected Behavior
green flags all round on older OMR and VPS realease
Current Behavior
multipath seems to be blocked message on all three starlinks after new install both on local rpi5 and vps
Specifications
OpenMPTCProuter version: v0.60-6.1 r0+24843-acf40c022e
OpenMPTCProuter VPS version: 0.1030 6.1.0-22-amd64
OpenMPTCProuter VPS provider: VPSSERVER.com
OpenMPTCProuter platform:RPI5
using 5.9 with my older vps and all ok.. three starlinks green and happy. I have a new rpi5 with latest OMR and new vps with 6.1.0-22-amd64 # Debian 6.1.94-1 (2024-06-21) x86_64 GNU/Linux and now all three starlinks say that mptcp appears to be blocked. If i swap to the older vps that message goes away on one or two of the wans (of course i get a kernel mismatch).. note that mptctp testing is not there on latest release unless its moved. on the older OMR all starlinks report OK mptcp