search

Ysurac / openmptcprouter

OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt
https://www.openmptcprouter.com/
GNU General Public License v3.0
1.78k stars 255 forks source link

cascade NAT causes kernal crash #3264

Closed aladdinshammr closed 1 month ago

aladdinshammr commented 4 months ago

Expected Behavior

I expect OMR to work well whether I connected to it directly or I plug in a router that uses OMR as internet source

Current Behavior

OMR works fine when I connect to it directly, but when I connect a mikrotik router internet slows down then gradually stops.

I see in log something like this

Apr 8 23:28:06 OpenMPTCProuter daemon.err omr-tracker[25131]: sh: 66.6667: bad number Apr 8 23:35:23 OpenMPTCProuter daemon.err omr-tracker[25130]: sh: 66.6667: bad number

I don't have much knowledge in networking nor in linux, but I assume that is because of enabling net.ipv4.tcp_mtu_probing in OMR in a network that has multiple nat causes this problem as mentioned in this https://github.com/multipath-tcp/mptcp/issues/108

Specifications

Ysurac commented 4 months ago

Please update to v0.60 first What is the kernel used ? 5.4 or 6.1 ? net.ipv4.tcp_mtu_probing is disabled in OpenMPTCProuter.

aladdinshammr commented 4 months ago

@Ysurac

I tested it in kernal 5.4, and today I will test kernal 6.1. I use everything mentioned in this link https://github.com/Ysurac/openmptcprouter/issues/2961

but these notifications never go, and when I update the VPS using the advance setting tab in OMR router it changes the kernal to 5.4.

version2 v2

Ysurac commented 4 months ago

As I said, 0.60 is now available, you need to download it and update. Here you are using rc2.

aladdinshammr commented 4 months ago

@Ysurac

this https://download.openmptcprouter.com/release/v0.60/x86_64/targets/x86/64/?

Ysurac commented 4 months ago

Use https://www.openmptcprouter.com/download

aladdinshammr commented 4 months ago

That's weird. chrome until now shows me v0.59.1-5.4. it worked only when I changed the browser. maybe there is caching or something. strange

aladdinshammr commented 4 months ago

I upgraded now router version: 0.60-6.1 VPS version: 0.1030.6.1.0-18-cloud-amd64.

It seem stable until now , but I haven't tested it yet.

something different in this version: 1- when I check in http://amiusingmptcp.de/ , it complains that I don't use MPTCP. 2- I always get this errors in the log:

Apr 13 15:16:00 OpenMPTCProuter daemon.err omr-tracker[17486]: sh: 66.6667: bad number Apr 13 15:17:09 OpenMPTCProuter daemon.err dnsmasq[48]: nftset inet fw4 omr_dscp_cs2_4 netlink: Error: cache initialization failed: Invalid argument Apr 13 15:17:09 OpenMPTCProuter daemon.err dnsmasq[50]: nftset inet fw4 omr_dscp_cs2_4 netlink: Error: cache initialization failed: Resource busy Apr 13 15:19:24 OpenMPTCProuter daemon.err dnsmasq[105]: nftset inet fw4 omr_dscp_cs2_4 netlink: Error: cache initialization failed: Protocol error Apr 13 15:19:24 OpenMPTCProuter daemon.err dnsmasq[105]: nftset inet fw4 omr_dscp_cs2_4 netlink: Error: cache initialization failed: Protocol error Apr 13 15:27:16 OpenMPTCProuter daemon.err dnsmasq[580]: nftset inet fw4 omr_dscp_cs2_4 netlink: Error: cache initialization failed: Resource busy Apr 13 15:27:16 OpenMPTCProuter daemon.err dnsmasq[578]: nftset inet fw4 omr_dscp_cs2_4 netlink: Error: cache initialization failed: Invalid argument Apr 13 15:34:29 OpenMPTCProuter daemon.err omr-tracker[17486]: sh: 66.6667: bad number Apr 13 16:34:54 OpenMPTCProuter daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com Apr 13 16:36:06 OpenMPTCProuter daemon.warn dnsmasq[1]: possible DNS-rebind attack detected: dns.msftncsi.com Apr 13 16:36:06 OpenMPTCProuter daemon.warn dnsmasq[2]: possible DNS-rebind attack detected: dns.msftncsi.com Apr 13 16:43:24 OpenMPTCProuter daemon.err /usr/bin/ss-local[26213]: getpeername: Socket not connected

Ysurac commented 4 months ago

http://amiusingmptcp.de/ only test MPTCPv0, MPTCPv1 is used with kernel 6.1 For DSCP I will check.

aladdinshammr commented 4 months ago

This time the kernel didn't crash, but as usual, I lose the connection to the server.

system log:

Apr 14 16:24:40 OpenMPTCProuter user.notice OMR-VPS: Setting server config error, try again Apr 14 16:25:08 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later (can't ping server vps on 34.18.74.6, no server API answer on 34.18.74.6) Apr 14 16:25:28 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later Apr 14 16:25:38 OpenMPTCProuter user.notice OMR-VPS: Can't get vps token, try later

err

aladdinshammr commented 4 months ago

can I put a load balance of 4 connections as a master? maybe master connection needs to be with a high speed compared to the others

aladdinshammr commented 4 months ago

@Ysurac

is there anything useful in this ?

Apr 16 03:06:01 Aladdin user.notice post-tracking-001-post-tracking: wan3 (wan3) switched off because check error, interface have no IPv6, interface have no IPv6 gateway and ping from 192.168.4.52 error (1.0.0.1,114.114.115.115,1.2.4.8) Apr 16 03:06:01 Aladdin user.notice post-tracking-001-post-tracking: Delete default route to 157.175.187.120 dev wan3 Apr 16 03:06:03 Aladdin user.notice post-tracking-001-post-tracking: Change in routes, set ip route replace default scope global nexthop via 192.168.2.1 dev wan1 weight 1 nexthop via 192.168.3.1 dev wan2 weight 100 (omrvpn_intf: tun0) Apr 16 03:06:06 Aladdin user.notice OMR-VPS: Can't get vps token, try later (can't ping server vps on 157.175.187.120, no server API answer on 157.175.187.120) Apr 16 03:06:15 Aladdin user.notice post-tracking-001-post-tracking: wan3 (wan3) switched up Apr 16 03:06:15 Aladdin user.notice post-tracking-001-post-tracking: Interface route not yet set, set route ip r add default via 192.168.4.1 dev wan3 metric 9 Apr 16 03:06:23 Aladdin user.notice OMR-VPS: Can't get vps token, try later (can't ping server vps on 157.175.187.120, no server API answer on 157.175.187.120) Apr 16 03:06:27 Aladdin user.notice post-tracking-001-post-tracking: wan2 (wan2) switched off because check error, interface have no IPv6, interface have no IPv6 gateway and ping from 192.168.3.10 error (1.0.0.1,114.114.115.115,1.2.4.8) Apr 16 03:06:27 Aladdin user.notice post-tracking-001-post-tracking: Delete default route to 157.175.187.120 dev wan2 Apr 16 03:06:32 Aladdin user.notice post-tracking-020-status: Check API configuration... Apr 16 03:06:32 Aladdin user.notice post-tracking-020-status: Check API configuration... Done Apr 16 03:06:35 Aladdint user.notice post-tracking-001-post-tracking: wan2 (wan2) switched up Apr 16 03:06:35 Aladdin user.notice post-tracking-001-post-tracking: Change in routes, set ip route replace default scope global nexthop via 192.168.2.1 dev wan1 weight 1 nexthop via 192.168.4.1 dev wan3 weight 1 nexthop via 192.168.3.1 dev wan2 weight 100 (omrvpn_intf: Apr 16 03:06:35 Aladdin user.notice post-tracking-001-post-tracking: Interface route not yet set, set route ip r add default via 192.168.3.1 dev wan2 metric 8 Apr 16 03:06:48 Aladdin user.notice OMR-VPS: Can't get vps token, try later (can't ping server vps on 157.175.187.120, no server API answer on 157.175.187.120) Apr 16 03:06:57 Aladdin user.notice post-tracking-001-post-tracking: wan2 (wan2) switched off because check error, interface have no IPv6, interface have no IPv6 gateway and ping from 192.168.3.10 error (1.1.1.1,4.2.2.1,8.8.8.8) Apr 16 03:06:57 Aladdin user.notice post-tracking-001-post-tracking: Delete default route to 157.175.187.120 dev wan2 Apr 16 03:07:05 Aladdin user.notice post-tracking-001-post-tracking: wan2 (wan2) switched up Apr 16 03:07:05 Aladdin user.notice post-tracking-001-post-tracking: Change in routes, set ip route replace default scope global nexthop via 192.168.2.1 dev wan1 weight 1 nexthop via 192.168.4.1 dev wan3 weight 1 nexthop via 192.168.3.1 dev wan2 weight 100 (omrvpn_intf: Apr 16 03:07:05 Aladdin user.notice post-tracking-001-post-tracking: Interface route not yet set, set route ip r add default via 192.168.3.1 dev wan2 metric 8

github-actions[bot] commented 1 month ago

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days