-
-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OMR-Bypass doesn't work for subdomains (or only works for top-level domains) #3693
Comments
Are you sure you are using only OpenMPTCProuter IP address as DNS ? |
Yes, the IP address of the OpenMPTCProuter is the only configured DNS server:
|
What is the result of |
Sure, thanks for taking a closer look!
|
Can you try latest snapshots ? I fixed some issues. |
Thanks for the update @Ysurac. I've tried the latest snapshot and it fixes the initial problem, but when adding the
Note The output for
The configured services are:
Click here to see output of "nft list ruleset"
|
There is some issues on whatapps and aws ranges... |
Should be better in latest snapshot |
Thanks for the update @Ysurac. Today I got around to testing the OMR bypass configuration with a freshly installed VPS and the latest RPI5 snapshot, but it seems that the bypass mechanism isn't working at all at the moment. I also don't see (via
Click here to see output of "nft list ruleset"
|
I'm seeing this as well on the 6.6 snapshot, I think the "Section omr_bypass is disabled, ignoring section" is relevant. None of OMR Bypass is working. |
I would need the result of |
Router version: 0.62-snapshot-6.6 uci show omr-bypass:
uci show firewall:
I've verified that OMR is the DNS server assigned to my PC. Domains added to OMR-Bypass still go through the proxy. |
As it's a domain bypass, I would also need the |
uci show dhcp:
|
also keep getting these errors idk if they are related to it
|
OMR-ByPass doesn't seems to be running in both case. Maybe it crash... I will check after christmas. |
Should be better in latest snapshot. It's still compiling... |
Hi Ysurac, /etc/init.d/omr-bypass restart after making changes in omr-bypass in order to get it to work. It then works until I make another change, such as adding a domain. Then I have to restart again. I manually applied the omr bypass patch, didn't see an updated snapshot for x86. |
The changes seems to work, it was due to an "exit 0" in stop part of init script. Now after a |
uci get firewall.omr_bypass.enabled does return 1 for me. However, after I hit "Save and Apply" I run a traceroute on one of the domains, and it goes through my VPS. I then execute: /etc/init.d/omr-bypass restart And traceroute again, and it properly goes straight to my WAN ISP and not through VPS. |
i noticed that more often bypass stopped working, i have to restart command "/etc/init.d/omr-bypass restart" make it work again, i would said they crashed more often |
Check latest snapshot, reload and restart is now the same. This can be slow to start on some services bypass (for example amazon) |
I'm using the latest snapshot: [openmptcprouter-v0.62-snapshot-6.6-r0+28194-cc69be0c13-rockchip-armv8-friendlyarm_nanopi-r5s], which is causing the omrbypass to crash frequently. Notice a sample log below: but when it auto-reload, the omr-bypass said running but omr-bypass is not working (confirmed by ifconfig.me). Here is the full log of 3 cycles crashed, even though it restarted bypass itself, but it didn’t work until we had to execute the
|
It appears there is an ongoing issue. The omrvpn and the system frequently crash or restart. It seems that whenever a restart occurs, the bypass is expected to run, but it doesn't. As a result, each time the system restarts, we need to manually run |
I removed OMR-ByPass restart in latest snapshot, but I will test asap. |
So far, the version [openmptcprouter-v0.62-snapshot-6.6-r0+28194-cc69be0c13-rockchip-armv8-friendlyarm_nanopi-r5s-ext4..>] has resolved the restart issue, and it has been running without any crashes omr-bypass or problems for over half a day. I will continue to report if any crashes occur for the rest of the day. but the subdomain remain not working still. |
Tested again today with the latest snapshot (
Thanks @Ysurac. Closing this for now. If anyone is still experiencing problems, feel free to comment or start a new issue. Thanks to all who contributed! |
Expected Behavior
When using OMR-Bypass with
netflix
enabled in "Protocols and services" ornflxvideo.net
configured as a domain in "Domains", the bypass should work not only for the top-level domain, but also for any subdomain (e.g.random.sub.domain.name.nflxvideo.net
).Note
Netflix is just an example, it's the same for any other subdomain.
It also doesn't work, if only one bypass option is used.
Current Behavior
When running
traceroute nflxvideo.net
on a device where the MPTCP router is configured as the DNS server, the request is correctly routed through the configured master interface:When running
traceroute ipv4-c088-ord001-dev-ix.1.oca.nflxvideo.net
on the same device, the request will not be routed through the configured master interface, but will use the VPS:Steps to Reproduce the Problem
Note
Tested at time of issue creation
1. Add server IP & key
2. Add 2 WAN interfaces
3. Setup OMR-Bypass as described above
4. Use
traceroute
on any connected clientSpecifications
openmptcprouter-v0.62-snapshot-6.6-r0+28016-48028cd102-bcm27xx-bcm2712-rpi-5-squashfs-factory
0.1032-test 6.6.36-x64v2-xanmod1
The text was updated successfully, but these errors were encountered: