OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt
C-Rank Grade: B (Solid) - 45/100
External PR Merge Rate: 50%
Response Time: 14h
First Timer Success: -
Ysurac/openmptcprouter has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Ysurac/openmptcprouter respond to incoming external pull requests in approximately 14.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 45.0 places Ysurac/openmptcprouter in the B tier.
The external contributor pull request merge rate for Ysurac/openmptcprouter is 50.0%, based on public PR activity from non-core contributors.
Ysurac/openmptcprouter currently has 7 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt
Active maintainer team in Ysurac/openmptcprouter welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/Ysurac/openmptcprouter?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (62% approval). Large PRs (>500 lines) take ~69 hours (22% approval). Keep your diff compact for rapid review.
Expected Behavior Install OMR and put the IP address and API key, expected to be working Current Behavior Freshly install OMR and VPS, put the IP address and API Key, the OMR is not working. Keep getting direct output Specifications OpenMPTCProuter version: 0.64.2-6.18 OpenMPTCProuter VPS version: Not sure, but I did install the last one, run uname -a , getting kernel 6.18 OpenMPTCProuter VPS provider: local VPS at Indonesia OpenMPTCProuter platform: x86_64 Hyper-V
Expected Behavior After a fresh OpenMPTCProuter installation and a fresh OpenMPTCProuter VPS installation, entering the VPS IP address and server key in the setup wizard should establish the VPN tunnel. The dashboard should show "VPN tunnel UP" and the omrvpn interface should be available. The same setup, VPS provider, WAN connections and wizard configuration work correctly with an older OpenMPTCProuter version. Current Behavior With OpenMPTCProuter v0.64.1, the dashboard permanently shows "VPN tunnel DOWN" after a fresh installation. This was reproduced with: A fresh OpenMPTCProuter router installation A fresh VPS installation A new Hetzner Cloud VPS New VPS key / server key Both virtualized x86_64 hardware and physical x86_64 hardware Two WAN connections: DSL and 5G The VPS is reachable from both WAN connections: OMR admin/API communication to the VPS works. The router can retrieve VPS configuration. UDP traffic to the MQVPN server port 65443 reaches the VPS. The VPS sends replies
Expected Behavior Current Behavior trying to install AI on VPS: sudo RESET_DATA="true" bash ./install_omr-ai.sh ==> Installing base dependencies... ==> Verifying and importing InfluxData GPG key... [14:54:13] Key fingerprint verified: *********** ==> Adding InfluxData apt repository... ==> Installing influxdb3-core... Reading package lists... Done Building dependency tree... Done Reading state information... Done influxdb3-core is already the newest version (3.11.4-1). The following packages were automatically installed and are no longer required: exim4-base exim4-config libidn12 liblockfile-bin liblockfile1 libmbedcrypto16 libmbedtls21 libmbedx509-7 libnsl2 linux-image-6.12.100+deb13-arm64 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. ==> Writing /etc/influxdb3/influxdb3-core.conf... ==> Enabling and (re)starting influxdb3-core to apply config... ==> Waiting for InfluxDB 3 HTTP API... [14:54:18] InfluxDB 3 is up (HTTP 200
Hi , i'm facing issue with new Z8102AX and 5g Modems with modemmanger, i would really appreciate if anyone can put me in right direction if i change device type to USB it starts working but still no info in dashboard cellular Network. in dashboard Cellular Network packet service State is detached and signal quality is 0% in network interfaces shows error: Error: Unknown error (MM_3GPP_OPERATOR_REGISTRATION_FAILED) Or Error: Unable to set allowed mode list. after some time here is what i see in log ,one thing i noticed is saying modem is not handled by modemmanager root@OpenMPTCProuter:~# mmcli -m 0 -------------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: f1af8811f8e2e09606107221e6403e87a79339a6 -------------------------------- Hardware | manufacturer: Quectel | model: RM500U-EA | firmware revision: RM500UEAAAR03A13M2G_01.300.01.300 |
For my connection i utilize starlink as a second WAN, in order to reduce NAT port exhaustion i'd like to enable OMR bonding over IPv6. For starlink as it's assigned a global v6 dynamic subnet it would be ideal for OMR to establish using SLACC or DHCP. Currently when an interface is enabled for ipv4 DHCP, it does not seem to have the option available. I can confirm that other devices within the starlink VLAN do establish IPv6 connectivity natively via SLAAC. This differs to my primary wan where i have statically allocated v6 connectivity. I suspect my instance may be locked in IPv6 mode as initally it would obtain IPv6 for starlink when i first installed it (however at that time i did not have Ipv6 on my primary) Expected Behavior Both connections should obtain IPv6 and be able to OMR bond across IPv6 aswell as IPv4. Current Behavior Static allocated IPv6 has been established however SLAAC is not working for starlink connection. Specifications OpenMPTCProuter version: 0.63-6.12 Open
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to Ysurac/openmptcprouter, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of Ysurac/openmptcprouter acknowledge new external contributions in approximately 14 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
Ysurac/openmptcprouter has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~14 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 45.0 places Ysurac/openmptcprouter in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Ysurac/openmptcprouter currently has 7 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Ysurac/openmptcprouter are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.