Redundant Scheduler does not work

[SpencerXZX]

Expected Behavior

Redundant scheduler should send duplicated packets on all interfaces and use the fastest response.

Current Behavior

Internet is not accessible when using redundant scheduler, however I can ping IPs and resolve DNS, so I am not sure where the problem lies. The CPU usage of my router goes all the way to max, showing a load of 20 despite being a quad core router.

Possible Solution

Not sure. But all of the other schedulers seem to work, so it seems to be just this one.

Steps to Reproduce the Problem

1. Turn on mptcp redundancy scheduler
2. Try to browse the internet.

Context (Environment)

Trying to minimize latency for online gaming using two WANs.

Redundant scheduler causes high cpu usage and no internet access.

Specifications

• OpenMPTCProuter version: openmptcprouter v0.62-snapshot-6.6 r0+28308-c06d4df974
• OpenMPTCProuter VPS version: 0.1032-test 6.6.36-x64v3-xanmod1
• OpenMPTCProuter VPS provider: Local provider
• OpenMPTCProuter platform: R5S
• Country: USA

[Ysurac]

I don't have issues with Shadowsocks-Rust and XRay, but OpenVPN doesn't work with red scheduler.
I will check that.

[SpencerXZX]

I am using XRay VLess with Glorytun TCP and it does not work. I've tried a bunch of different proxies but never swapped from Glorytun, maybe that's it?

[Ysurac]

You can disable VPN to test. Glorytun TCP doesn't always work well with 6.6 (In fact not working at all in MPTCP mode... I just modified source code)

[SpencerXZX]

Ok I will test when I get home, could this have been causing my issue?

[SpencerXZX]

I updated my router to the latest snapshot after the glorytun tcp update, however I am still seeing the same results. This time, I tried disabling the VPN entirely. Now the status screen sometimes shows direct output, and for a few seconds will show connected to the VPS, in fact, I was able to get a webpage to half load by refreshing a bunch, but it wouldn't fully load. I tested shadowsocks rust 2022 and xray vless, both with vpn disabled and couldn't get it to work. Please let me know if I can provide any other info to help:

I've tested this both on R5S as well as X86 and I get the same result.

[Ysurac]

The new snapshot is not yet build, and It's not directly related I think.
I'm making tests on kernel 6.12, I will test on 6.6.

[SpencerXZX]

Thanks, I tried compiling 6.12 but it doesn't appear to be compatible with R5S yet, or I did something wrong. I'm not very familiar with compiling from source so it's likely I made a mistake.

[Ysurac]

It's only tested on x86_64 for now.

[SpencerXZX]

Have you had a chance to test this on 6.6 yet? Or can anyone else test on 6.6? Trying to figure out if it's an issue on my side or not. I don't have access to my x86 test device anymore so I can't test 6.12 on x86_64.