Ranger802004 / asusmerlin

ASUS Merlin
GNU General Public License v3.0
34 stars 3 forks source link

Load Balance mode frequent timeouts #2

Closed iBenMoore closed 1 year ago

iBenMoore commented 1 year ago

Leaving this here as the SNBForums post is locked to new posts due to being older than 6 months.

I've been testing out the latest script in load-balanced mode on a 2900, and it seems to be running OK and logging shows where it's seen a bit of packet loss here or there, but it's rare. But I still feel there's something screwy/missing with routing or DNS in load balancing mode as I frequently get connection timeouts with web browsing where a page refresh usually results in an immediate load of the page that was timing out. This is not new since I've introduced your script, it's generally how load balance mode has worked without it Any ideas or possible solutions for load balancing mode that your script might not be correcting yet?

Ranger802004 commented 1 year ago

I would recommend to send me debug logs after running the script at startup.  That is usually due to missing FWMark rules and I need to verify your router is adding them properly.Sent from my iPhoneOn Dec 13, 2022, at 7:10 PM, iBenMoore @.***> wrote: Leaving this here as the SNBForums post is locked to new posts due to being older than 6 months. I've been testing out the latest script in load-balanced mode on a 2900, and it seems to be running OK and logging shows where it's seen a bit of packet loss here or there, but it's rare. But I still feel there's something screwy/missing with routing or DNS in load balancing mode as I frequently get connection timeouts with web browsing where a page refresh usually results in an immediate load of the page that was timing out. This is not new since I've introduced your script, it's generally how load balance mode has worked without it Any ideas or possible solutions for load balancing mode that your script might not be correcting yet?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

iBenMoore commented 1 year ago

No problem, does this work?

Dec 14 08:39:31 ntpd: Initial clock set Dec 14 08:39:31 kernel: Tuxera FAT 12/16/32 driver version 3016.7.20 [Flags: R/W MODULE]. Dec 14 08:39:31 kernel: Built against headers 4.1.27 #4 SMP PREEMPT Wed Jun 5 11:59:06 CST 2019 arm64 Dec 14 08:39:31 kernel: Running on kernel 4.1.27 #2 SMP PREEMPT Sun Jul 24 18:28:27 EDT 2022 aarch64 Dec 14 08:39:31 rc_service: ntpd_synced 2963:notify_rc restart_diskmon Dec 14 08:39:31 kernel: Tuxera NTFS driver 3018.6.22d [Flags: R/W MODULE]. Dec 14 08:39:31 kernel: Built against headers 4.1.27 #4 SMP PREEMPT Wed Jun 5 11:59:06 CST 2019 arm64 Dec 14 08:39:31 kernel: Running on kernel 4.1.27 #2 SMP PREEMPT Sun Jul 24 18:28:27 EDT 2022 aarch64 Dec 14 08:39:31 start_ddns: update WWW.DNSOMATIC.COM default@dnsomatic.com, wan_unit 0 Dec 14 08:39:31 kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead. Dec 14 08:39:31 kernel: Tuxera HFS+ driver 3017.6.20 Dec 14 08:39:31 kernel: Built against headers 4.1.27 #4 SMP PREEMPT Wed Jun 5 11:59:06 CST 2019 arm64 Dec 14 08:39:31 kernel: Running on kernel 4.1.27 #2 SMP PREEMPT Sun Jul 24 18:28:27 EDT 2022 aarch64 Dec 14 08:39:31 kernel: usbcore: registered new interface driver usblp Dec 14 08:39:31 start_ddns: Clear ddns cache. Dec 14 08:39:31 start_ddns: Start Inadyn(10). Dec 14 08:39:31 kernel: init (1): drop_caches: 1 Dec 14 08:39:31 init: fwver: 386.7_2 (sn: /ha:F0:2F:74:C6:9C:A8 ) Dec 14 08:39:31 inadyn[2981]: In-a-dyn version 2.9.1 -- Dynamic DNS update client. Dec 14 08:39:31 inadyn[2981]: Failed resolving hostname ip: Name or service not known Dec 14 08:39:31 disk_monitor: Finish Dec 14 08:39:31 disk_monitor: be idle Dec 14 08:39:32 inadyn[2981]: Update forced for alias ip, new IP# 75.204.4.65 Dec 14 08:39:32 inadyn[2981]: Updating cache for ip Dec 14 08:39:33 WAN(0)_Connection: WAN was restored. Dec 14 08:39:33 WAN(1)_Connection: WAN was restored. Dec 14 08:39:36 BONDING: option disabled Dec 14 08:39:36 roamast: ROAMING Start... Dec 14 08:39:37 wlceventd: wlceventd_proc_event(527): eth5: Auth 30:85:A9:2F:EE:D1, status: Successful (0), rssi:0 Dec 14 08:39:37 wlceventd: wlceventd_proc_event(556): eth5: Assoc 30:85:A9:2F:EE:D1, status: Successful (0), rssi:0 Dec 14 08:39:38 dnsmasq-dhcp[2049]: DHCPREQUEST(br0) 192.168.1.82 30:85:a9:2f:ee:d1 Dec 14 08:39:38 dnsmasq-dhcp[2049]: DHCPACK(br0) 192.168.1.82 30:85:a9:2f:ee:d1 android-f647c1786db5d6db Dec 14 08:39:42 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind AC:74:B1:C4:A8:C4, status: 0, reason: Unspecified reason (1), rssi:0 Dec 14 08:39:42 wlceventd: wlceventd_proc_event(508): eth6: Disassoc AC:74:B1:C4:A8:C4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0 Dec 14 08:39:43 wlceventd: wlceventd_proc_event(527): eth6: Auth 74:E2:0C:93:8F:B9, status: Successful (0), rssi:0 Dec 14 08:39:43 wlceventd: wlceventd_proc_event(556): eth6: Assoc 74:E2:0C:93:8F:B9, status: Successful (0), rssi:0 Dec 14 08:39:43 wlceventd: wlceventd_proc_event(527): eth6: Auth AC:74:B1:C4:A8:C4, status: Successful (0), rssi:0 Dec 14 08:39:43 wlceventd: wlceventd_proc_event(537): eth6: ReAssoc AC:74:B1:C4:A8:C4, status: Successful (0), rssi:0 Dec 14 08:39:43 kernel: br0: received packet on eth6 with own address as source address Dec 14 08:39:55 wlceventd: wlceventd_proc_event(527): eth6: Auth BE:32:3D:73:BC:1A, status: Successful (0), rssi:0 Dec 14 08:39:55 wlceventd: wlceventd_proc_event(556): eth6: Assoc BE:32:3D:73:BC:1A, status: Successful (0), rssi:0 Dec 14 08:39:56 dnsmasq-dhcp[2049]: DHCPREQUEST(br0) 192.168.1.91 be:32:3d:73:bc:1a Dec 14 08:39:56 dnsmasq-dhcp[2049]: DHCPACK(br0) 192.168.1.91 be:32:3d:73:bc:1a Dragon-S20FE Dec 14 08:40:05 wlceventd: wlceventd_proc_event(527): eth5: Auth 64:1C:AE:EA:85:22, status: Successful (0), rssi:0 Dec 14 08:40:05 wlceventd: wlceventd_proc_event(556): eth5: Assoc 64:1C:AE:EA:85:22, status: Successful (0), rssi:0 Dec 14 08:40:15 crond[2057]: time disparity of 2425595 minutes detected Dec 14 08:41:00 wan-failover.sh: Debug - Locked File: /var/lock/wan-failover.lock Dec 14 08:41:00 wan-failover.sh: Debug - Trap set to remove /var/lock/wan-failover.lock on exit Dec 14 08:41:00 wan-failover.sh: Debug - Script Mode: run Dec 14 08:41:00 wan-failover.sh: Debug - Function: systemcheck Dec 14 08:41:00 wan-failover.sh: Debug - Log Level: 7 Dec 14 08:41:00 wan-failover.sh: System Check - Process ID: 3281 Dec 14 08:41:00 wan-failover.sh: Debug - Function: nvramcheck Dec 14 08:41:00 wan-failover.sh: Debug - NVRAM Check Passed Dec 14 08:41:00 wan-failover.sh: System Check - Version: v1.6.0-beta2 Dec 14 08:41:00 wan-failover.sh: Debug - Firmware: 386.7 Dec 14 08:41:00 wan-failover.sh: System Check - IPRoute Version: 5.11.0 Dec 14 08:41:00 wan-failover.sh: Debug - JFFS custom scripts and configs: 1 Dec 14 08:41:00 wan-failover.sh: Debug - Checking Alias in /jffs/configs/profile.add Dec 14 08:41:01 wan-failover.sh: Debug - Checking for Configuration File: /jffs/configs/wan-failover.conf Dec 14 08:41:01 wan-failover.sh: Debug - Function: setvariables Dec 14 08:41:01 wan-failover.sh: Debug - Reading /jffs/configs/wan-failover.conf Dec 14 08:41:01 wan-failover.sh: Debug - Checking for missing configuration options Dec 14 08:41:01 wan-failover.sh: Debug - Reading /jffs/configs/wan-failover.conf Dec 14 08:41:01 wan-failover.sh: Debug - Function: debuglog Dec 14 08:41:01 wan-failover.sh: Debug - Function: nvramcheck Dec 14 08:41:01 wan-failover.sh: Debug - NVRAM Check Passed Dec 14 08:41:01 wan-failover.sh: Debug - Model: GT-AC2900 Dec 14 08:41:01 wan-failover.sh: Debug - Product ID: GT-AC2900 Dec 14 08:41:01 wan-failover.sh: Debug - Build Name: GT-AC2900 Dec 14 08:41:01 wan-failover.sh: Debug - Firmware: 386.7 Dec 14 08:41:01 wan-failover.sh: Debug - IPRoute Version: 5.11.0 Dec 14 08:41:01 wan-failover.sh: Debug - WAN Capability: wan usb lan Dec 14 08:41:01 wan-failover.sh: Debug - Dual WAN Mode: lb Dec 14 08:41:01 wan-failover.sh: Debug - Load Balance Ratio: 3:1 Dec 14 08:41:01 wan-failover.sh: Debug - Dual WAN Interfaces: lan wan Dec 14 08:41:01 wan-failover.sh: Debug - ASUS Factory Watchdog: 0 Dec 14 08:41:01 wan-failover.sh: Debug - JFFS custom scripts and configs: 1 Dec 14 08:41:01 wan-failover.sh: Debug - HTTP Web Access: 0 Dec 14 08:41:01 wan-failover.sh: Debug - Firewall Enabled: 1 Dec 14 08:41:01 wan-failover.sh: Debug - IPv6 Firewall Enabled: 1 Dec 14 08:41:01 wan-failover.sh: Debug - LEDs Disabled: 0 Dec 14 08:41:01 wan-failover.sh: Debug - QoS Enabled: 0 Dec 14 08:41:01 wan-failover.sh: Debug - DDNS Enabled: 1 Dec 14 08:41:01 wan-failover.sh: Debug - DDNS Hostname: ip Dec 14 08:41:01 wan-failover.sh: Debug - LAN Hostname: GT-AC2900-9CA8 Dec 14 08:41:01 wan-failover.sh: Debug - WAN IPv6 Service: disabled Dec 14 08:41:01 wan-failover.sh: Debug - WAN IPv6 Address: Dec 14 08:41:01 wan-failover.sh: Debug - Default Route: default nexthop via 192.168.0.1 dev eth4 weight 3 nexthop via 192.168.2.2 dev eth0 weight 1 Dec 14 08:41:01 wan-failover.sh: Debug - OpenVPN Server Instances Enabled: Dec 14 08:41:01 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:01 wan-failover.sh: Debug - Setting parameters for wan0 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Enabled: 1 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Routing Table Default Route: default via 192.168.0.1 dev eth4 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Ping Path: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Target IP Rule: Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Target IP Route: Dec 14 08:41:01 wan-failover.sh: Debug - wan0 IP Address: 192.168.0.6 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Real IP Address: Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Real IP Address State: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Gateway IP: 192.168.0.1 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Gateway Interface: eth4 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Interface: eth4 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Automatic ISP DNS Enabled: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Automatic ISP DNS Servers: 1.1.1.1 1.0.0.1 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Manual DNS Server 1: 1.1.1.1 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Manual DNS Server 2: 1.0.0.1 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 State: 2 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Aux State: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Sb State: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Primary Status: 1 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 USB Modem Status: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 UPnP Enabled: 1 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 NAT Enabled: 1 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Target IP Address: 8.8.8.8 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Routing Table: 100 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 IP Rule Priority: 100 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Mark: 0x80000000 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 Mask: 0xf0000000 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 From WAN Priority: 200 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 To WAN Priority: 400 Dec 14 08:41:01 wan-failover.sh: Debug - wan0 OVPN WAN Priority: 100 Dec 14 08:41:01 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:01 wan-failover.sh: Debug - Setting parameters for wan1 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Enabled: 1 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Routing Table Default Route: default via 192.168.2.2 dev eth0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Ping Path: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Target IP Rule: Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Target IP Route: Dec 14 08:41:01 wan-failover.sh: Debug - wan1 IP Address: 192.168.2.5 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Real IP Address: Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Real IP Address State: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Gateway IP: 192.168.2.2 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Gateway Interface: eth0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Interface: eth0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Automatic ISP DNS Enabled: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Automatic ISP DNS Servers: 1.1.1.1 1.0.0.1 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Manual DNS Server 1: 1.1.1.1 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Manual DNS Server 2: 1.0.0.1 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 State: 2 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Aux State: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Sb State: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Primary Status: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 USB Modem Status: 0 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 UPnP Enabled: 1 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 NAT Enabled: 1 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Target IP Address: 8.8.4.4 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Routing Table: 200 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 IP Rule Priority: 100 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Mark: 0x90000000 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 Mask: 0xf0000000 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 From WAN Priority: 200 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 To WAN Priority: 400 Dec 14 08:41:01 wan-failover.sh: Debug - wan1 OVPN WAN Priority: 200 Dec 14 08:41:01 wan-failover.sh: Debug - Function: wanstatus Dec 14 08:41:01 wan-failover.sh: Debug - Function: nvramcheck Dec 14 08:41:01 wan-failover.sh: Debug - NVRAM Check Passed Dec 14 08:41:01 wan-failover.sh: Debug - System Uptime: 117 Seconds Dec 14 08:41:01 wan-failover.sh: Debug - Boot Delay Timer: 0 Seconds Dec 14 08:41:01 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:01 wan-failover.sh: Debug - Setting parameters for wan0 Dec 14 08:41:01 wan-failover.sh: WAN Status - wan0 enabled Dec 14 08:41:01 wan-failover.sh: Debug - Checking wan0 State Dec 14 08:41:01 wan-failover.sh: Debug - Checking wan0 for null IP or Gateway Dec 14 08:41:01 wan-failover.sh: Debug - Checking wan0 for Default Route in 100 Dec 14 08:41:01 wan-failover.sh: Debug - Recursive Ping Check: 1 Dec 14 08:41:01 wan-failover.sh: Debug - Checking wan0 for IP Rule to 8.8.8.8 Dec 14 08:41:01 wan-failover.sh: WAN Status - Adding IP Rule for 8.8.8.8 to monitor wan0 Dec 14 08:41:01 wan-failover.sh: WAN Status - Added IP Rule for 8.8.8.8 to monitor wan0 Dec 14 08:41:01 wan-failover.sh: Debug - Checking wan0 for packet loss via 8.8.8.8 - Attempt: 1 Dec 14 08:41:15 wan-failover.sh: Debug - wan0 Packet Loss: 0% Dec 14 08:41:15 wan-failover.sh: Debug - Checking wan0 for Default Route in 100 Dec 14 08:41:15 wan-failover.sh: Debug - wan0 Ping Path: 1 Dec 14 08:41:15 wan-failover.sh: WAN Status - wan0 has 0% packet loss Dec 14 08:41:15 wan-failover.sh: Debug - wan0 Status: CONNECTED Dec 14 08:41:15 wan-failover.sh: Debug - Function: setwanstatus Dec 14 08:41:15 wan-failover.sh: Debug - WAN Status Mode: 1 Dec 14 08:41:15 wan-failover.sh: Debug - WAN0 Status: CONNECTED Dec 14 08:41:15 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:15 wan-failover.sh: Debug - Setting parameters for wan1 Dec 14 08:41:15 wan-failover.sh: WAN Status - wan1 enabled Dec 14 08:41:15 wan-failover.sh: Debug - Checking wan1 State Dec 14 08:41:15 wan-failover.sh: Debug - Checking wan1 for null IP or Gateway Dec 14 08:41:15 wan-failover.sh: Debug - Checking wan1 for Default Route in 200 Dec 14 08:41:15 wan-failover.sh: Debug - Recursive Ping Check: 1 Dec 14 08:41:15 wan-failover.sh: Debug - Checking wan1 for IP Rule to 8.8.4.4 Dec 14 08:41:15 wan-failover.sh: WAN Status - Adding IP Rule for 8.8.4.4 to monitor wan1 Dec 14 08:41:15 wan-failover.sh: WAN Status - Added IP Rule for 8.8.4.4 to monitor wan1 Dec 14 08:41:15 wan-failover.sh: Debug - Checking wan1 for packet loss via 8.8.4.4 - Attempt: 1 Dec 14 08:41:18 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:E7:C2:EE:20:5F, status: Successful (0), rssi:0 Dec 14 08:41:18 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:E7:C2:EE:20:5F, status: Successful (0), rssi:0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Packet Loss: 0% Dec 14 08:41:30 wan-failover.sh: Debug - Checking wan1 for Default Route in 200 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Ping Path: 1 Dec 14 08:41:30 wan-failover.sh: WAN Status - wan1 has 0% packet loss Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Status: CONNECTED Dec 14 08:41:30 wan-failover.sh: Debug - Function: setwanstatus Dec 14 08:41:30 wan-failover.sh: Debug - WAN Status Mode: 1 Dec 14 08:41:30 wan-failover.sh: Debug - WAN1 Status: CONNECTED Dec 14 08:41:30 wan-failover.sh: Debug - Function: debuglog Dec 14 08:41:30 wan-failover.sh: Debug - Function: nvramcheck Dec 14 08:41:30 wan-failover.sh: Debug - NVRAM Check Passed Dec 14 08:41:30 wan-failover.sh: Debug - Model: GT-AC2900 Dec 14 08:41:30 wan-failover.sh: Debug - Product ID: GT-AC2900 Dec 14 08:41:30 wan-failover.sh: Debug - Build Name: GT-AC2900 Dec 14 08:41:30 wan-failover.sh: Debug - Firmware: 386.7 Dec 14 08:41:30 wan-failover.sh: Debug - IPRoute Version: 5.11.0 Dec 14 08:41:30 wan-failover.sh: Debug - WAN Capability: wan usb lan Dec 14 08:41:30 wan-failover.sh: Debug - Dual WAN Mode: lb Dec 14 08:41:30 wan-failover.sh: Debug - Load Balance Ratio: 3:1 Dec 14 08:41:30 wan-failover.sh: Debug - Dual WAN Interfaces: lan wan Dec 14 08:41:30 wan-failover.sh: Debug - ASUS Factory Watchdog: 0 Dec 14 08:41:30 wan-failover.sh: Debug - JFFS custom scripts and configs: 1 Dec 14 08:41:30 wan-failover.sh: Debug - HTTP Web Access: 0 Dec 14 08:41:30 wan-failover.sh: Debug - Firewall Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - IPv6 Firewall Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - LEDs Disabled: 0 Dec 14 08:41:30 wan-failover.sh: Debug - QoS Enabled: 0 Dec 14 08:41:30 wan-failover.sh: Debug - DDNS Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - DDNS Hostname: ip Dec 14 08:41:30 wan-failover.sh: Debug - LAN Hostname: GT-AC2900-9CA8 Dec 14 08:41:30 wan-failover.sh: Debug - WAN IPv6 Service: disabled Dec 14 08:41:30 wan-failover.sh: Debug - WAN IPv6 Address: Dec 14 08:41:30 wan-failover.sh: Debug - Default Route: default nexthop via 192.168.0.1 dev eth4 weight 3 nexthop via 192.168.2.2 dev eth0 weight 1 Dec 14 08:41:30 wan-failover.sh: Debug - OpenVPN Server Instances Enabled: Dec 14 08:41:30 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:30 wan-failover.sh: Debug - Setting parameters for wan0 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Routing Table Default Route: default via 192.168.0.1 dev eth4 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Ping Path: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Target IP Rule: 100: from all to 8.8.8.8 iif lo oif eth4 lookup wan0 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Target IP Route: Dec 14 08:41:30 wan-failover.sh: Debug - wan0 IP Address: 192.168.0.6 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Real IP Address: Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Real IP Address State: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Gateway IP: 192.168.0.1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Gateway Interface: eth4 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Interface: eth4 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Automatic ISP DNS Enabled: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Automatic ISP DNS Servers: 1.1.1.1 1.0.0.1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Manual DNS Server 1: 1.1.1.1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Manual DNS Server 2: 1.0.0.1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 State: 2 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Aux State: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Sb State: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Primary Status: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 USB Modem Status: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 UPnP Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 NAT Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Target IP Address: 8.8.8.8 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Routing Table: 100 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 IP Rule Priority: 100 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Mark: 0x80000000 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 Mask: 0xf0000000 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 From WAN Priority: 200 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 To WAN Priority: 400 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 OVPN WAN Priority: 100 Dec 14 08:41:30 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:30 wan-failover.sh: Debug - Setting parameters for wan1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Routing Table Default Route: default via 192.168.2.2 dev eth0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Ping Path: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Target IP Rule: 100: from all to 8.8.4.4 iif lo oif eth0 lookup wan1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Target IP Route: Dec 14 08:41:30 wan-failover.sh: Debug - wan1 IP Address: 192.168.2.5 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Real IP Address: Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Real IP Address State: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Gateway IP: 192.168.2.2 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Gateway Interface: eth0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Interface: eth0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Automatic ISP DNS Enabled: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Automatic ISP DNS Servers: 1.1.1.1 1.0.0.1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Manual DNS Server 1: 1.1.1.1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Manual DNS Server 2: 1.0.0.1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 State: 2 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Aux State: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Sb State: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Primary Status: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 USB Modem Status: 0 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 UPnP Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 NAT Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Target IP Address: 8.8.4.4 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Routing Table: 200 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 IP Rule Priority: 100 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Mark: 0x90000000 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 Mask: 0xf0000000 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 From WAN Priority: 200 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 To WAN Priority: 400 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 OVPN WAN Priority: 200 Dec 14 08:41:30 wan-failover.sh: Debug - Function: switchdns Dec 14 08:41:30 wan-failover.sh: Debug - Function: nvramcheck Dec 14 08:41:30 wan-failover.sh: Debug - NVRAM Check Passed Dec 14 08:41:30 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:30 wan-failover.sh: Debug - Setting parameters for wan0 Dec 14 08:41:30 wan-failover.sh: Debug - Manual DNS Settings for wan0 Dec 14 08:41:30 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:30 wan-failover.sh: Debug - Setting parameters for wan1 Dec 14 08:41:30 wan-failover.sh: Debug - Manual DNS Settings for wan1 Dec 14 08:41:30 wan-failover.sh: Debug - Function: checkiprules Dec 14 08:41:30 wan-failover.sh: Debug - Function: nvramcheck Dec 14 08:41:30 wan-failover.sh: Debug - NVRAM Check Passed Dec 14 08:41:30 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:30 wan-failover.sh: Debug - Setting parameters for wan0 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 UPNP Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan0 NAT Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - Checking IPTables Mangle Rules Dec 14 08:41:30 wan-failover.sh: Debug - Checking Guest Networks IPTables Mangle Rules Dec 14 08:41:30 wan-failover.sh: Debug - Checking fwmark IP Rules Dec 14 08:41:30 wan-failover.sh: Debug - OVPNSPLITTUNNEL Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - Function: getwanparameters Dec 14 08:41:30 wan-failover.sh: Debug - Setting parameters for wan1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 UPNP Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - wan1 NAT Enabled: 1 Dec 14 08:41:30 wan-failover.sh: Debug - Checking IPTables Mangle Rules Dec 14 08:41:30 wan-failover.sh: Check IP Rules - Adding IPTables - PREROUTING MANGLE match rule for br0 marked with 0x90000000 Dec 14 08:41:30 wan-failover.sh: Check IP Rules - Added IPTables - PREROUTING MANGLE match rule for br0 marked with 0x90000000 Dec 14 08:41:30 wan-failover.sh: Check IP Rules - Adding IPTables - OUTPUT MANGLE match rule for eth0 marked with 0x90000000 Dec 14 08:41:31 wan-failover.sh: Check IP Rules - Added IPTables - OUTPUT MANGLE match rule for eth0 marked with 0x90000000 Dec 14 08:41:31 wan-failover.sh: Check IP Rules - Deleting IPTables - OUTPUT MANGLE match rule for eth0 marked with 0x80000000 Dec 14 08:41:31 wan-failover.sh: Check IP Rules - Deleted IPTables - OUTPUT MANGLE match rule for eth0 marked with 0x80000000 Dec 14 08:41:31 wan-failover.sh: Debug - Checking Guest Networks IPTables Mangle Rules Dec 14 08:41:31 wan-failover.sh: Debug - Checking fwmark IP Rules Dec 14 08:41:31 wan-failover.sh: Debug - OVPNSPLITTUNNEL Enabled: 1 Dec 14 08:41:31 wan-failover.sh: Debug - WAN0STATUS: CONNECTED Dec 14 08:41:31 wan-failover.sh: Debug - WAN1STATUS: CONNECTED Dec 14 08:41:31 wan-failover.sh: Debug - Function: lbmonitor Dec 14 08:41:31 wan-failover.sh: Debug - Function: nvramcheck Dec 14 08:41:31 wan-failover.sh: Debug - NVRAM Check Passed Dec 14 08:41:31 wan-failover.sh: Load Balance Monitor - Monitoring wan0 via 8.8.8.8 for Packet Loss Dec 14 08:41:31 wan-failover.sh: Load Balance Monitor - Monitoring wan1 via 8.8.4.4 for Packet Loss Dec 14 08:41:35 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:E7:C2:EE:20:65, status: Successful (0), rssi:0 Dec 14 08:41:35 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:E7:C2:EE:20:65, status: Successful (0), rssi:0 Dec 14 08:41:41 wlceventd: wlceventd_proc_event(527): eth6: Auth 76:05:08:E8:E4:34, status: Successful (0), rssi:0 Dec 14 08:41:41 wlceventd: wlceventd_proc_event(556): eth6: Assoc 76:05:08:E8:E4:34, status: Successful (0), rssi:0 Dec 14 08:41:41 wlceventd: wlceventd_proc_event(527): eth6: Auth 9A:5B:02:DF:FF:6A, status: Successful (0), rssi:0 Dec 14 08:41:41 wlceventd: wlceventd_proc_event(556): eth6: Assoc 9A:5B:02:DF:FF:6A, status: Successful (0), rssi:0 Dec 14 08:41:46 wlceventd: wlceventd_proc_event(527): eth6: Auth 68:E7:C2:EE:21:C5, status: Successful (0), rssi:0 Dec 14 08:41:46 wlceventd: wlceventd_proc_event(556): eth6: Assoc 68:E7:C2:EE:21:C5, status: Successful (0), rssi:0

iBenMoore commented 1 year ago

Any additional info I could provide that might help Ranger?

Ranger802004 commented 1 year ago

Any additional info I could provide that might help Ranger?

Sorry I just recently got back in country and am catching up. I will send you a few commands to run to capture output. I don’t see it creating any FWMark Rules for eth4 in the log but that could be because they already exist as they should.

Ranger802004 commented 1 year ago

Any additional info I could provide that might help Ranger?

Run these commands and provide me the output you get back.

ip rule list iptables -t mangle -L PREROUTING -v -n iptables -t mangle -L OUTPUT -v -n

iBenMoore commented 1 year ago

Here you go:

ASUSWRT-Merlin GT-AC2900 386.7_2 Sun Jul 24 21:39:14 UTC 2022 admin@GT-AC2900-9CA8:/tmp/home/root# admin@GT-AC2900-9CA8:/tmp/home/root# ip rule list 0: from all lookup local 100: from 192.168.1.30 lookup wan1 100: from all to 8.8.8.8 iif lo oif eth4 lookup wan0 100: from all to 8.8.4.4 iif lo oif eth0 lookup wan1 150: from all fwmark 0x80000000/0xf0000000 lookup wan0 150: from all fwmark 0x90000000/0xf0000000 lookup wan1 200: from 192.168.0.6 lookup wan0 200: from 192.168.2.5 lookup wan1 200: from 1.1.1.1 lookup wan0 200: from 1.0.0.1 lookup wan0 200: from 1.1.1.1 lookup wan1 200: from 1.0.0.1 lookup wan1 400: from all to 192.168.0.1 lookup wan0 400: from all to 192.168.2.2 lookup wan1 400: from all to 1.1.1.1 lookup wan0 400: from all to 1.0.0.1 lookup wan0 400: from all to 1.1.1.1 lookup wan1 400: from all to 1.0.0.1 lookup wan1 32766: from all lookup main 32767: from all lookup default admin@GT-AC2900-9CA8:/tmp/home/root# admin@GT-AC2900-9CA8:/tmp/home/root# admin@GT-AC2900-9CA8:/tmp/home/root# iptables -t mangle -L PREROUTING -v -n Chain PREROUTING (policy ACCEPT 49M packets, 8317M bytes) pkts bytes target prot opt in out source destination 16M 1360M balance all -- br0 0.0.0.0/0 0.0.0.0/0 state NEW 4750K 480M CONNMARK all -- br0 0.0.0.0/0 0.0.0.0/0 connmark match 0x80000000/0x80000000 CONNMARK restore mask 0xf0000000 647K 211M CONNMARK all -- eth4 0.0.0.0/0 0.0.0.0/0 state NEW CONNMARK xset 0x80000000/0xf0000000 388K 68M CONNMARK all -- eth0 0.0.0.0/0 0.0.0.0/0 state NEW CONNMARK xset 0x90000000/0xf0000000 1157K 148M CONNMARK all -- br0 0.0.0.0/0 0.0.0.0/0 connmark match 0x90000000/0x90000000 CONNMARK restore mask 0xf0000000 admin@GT-AC2900-9CA8:/tmp/home/root# admin@GT-AC2900-9CA8:/tmp/home/root# admin@GT-AC2900-9CA8:/tmp/home/root# admin@GT-AC2900-9CA8:/tmp/home/root# iptables -t mangle -L OUTPUT -v -n Chain OUTPUT (policy ACCEPT 20M packets, 5340M bytes) pkts bytes target prot opt in out source destination 8510 1061K CONNMARK all -- eth4 0.0.0.0/0 0.0.0.0/0 connmark match 0x80000000/0x80000000 CONNMARK restore mask 0xf0000000 2808 347K CONNMARK all -- * eth0 0.0.0.0/0 0.0.0.0/0 connmark match 0x80000000/0x80000000 CONNMARK restore mask 0xf0000000

iBenMoore commented 1 year ago

I was doing some ping testing the other day looking at what MTU's my provider devices are using, and sometimes saw connection problems where when the problem was occurring the dns that was returned for any of the sites I was ping testing was 10.0.0.1, which of course made them unreachable. Thought that might offer a clue as to what might be going on...

Ranger802004 commented 1 year ago

This is wrong, your 2nd WAN should be marked with 0x90000000 by default. Can you send me your config file content as well?

8510 1061K CONNMARK all -- eth4 0.0.0.0/0 0.0.0.0/0 connmark match 0x80000000/0x80000000 CONNMARK restore mask 0xf0000000 2808 347K CONNMARK all -- eth0 0.0.0.0/0 0.0.0.0/0 connmark match 0x80000000/0x80000000 CONNMARK restore mask 0xf0000000

Ranger802004 commented 1 year ago

Also, I see in the previous logs it does create properly but your output you last send me shows it incorrect with 0x8 still.

Dec 14 08:41:30 wan-failover.sh: Check IP Rules - Adding IPTables - OUTPUT MANGLE match rule for eth0 marked with 0x90000000 Dec 14 08:41:31 wan-failover.sh: Check IP Rules - Added IPTables - OUTPUT MANGLE match rule for eth0 marked with 0x90000000 Dec 14 08:41:31 wan-failover.sh: Check IP Rules - Deleting IPTables - OUTPUT MANGLE match rule for eth0 marked with 0x80000000 Dec 14 08:41:31 wan-failover.sh: Check IP Rules - Deleted IPTables - OUTPUT MANGLE match rule for eth0 marked with 0x80000000

Ranger802004 commented 1 year ago

Try the latest beta (v1.6.1-beta3) and see if it helps improve your experience. I built in a function to check the rules during the Load Balance Monitoring loop at the most of every 15 minutes and if this is successful I will likely make this a configuration option.

iBenMoore commented 1 year ago

Thanks. I've been running on failover mode lately so I can test out FlexQOS (since AFAIK QOS doesn't work under load-balance mode), but I'll make time to flip back over to load balanced mode to test out this latest beta.

Ranger802004 commented 1 year ago

Thanks. I've been running on failover mode lately so I can test out FlexQOS (since AFAIK QOS doesn't work under load-balance mode), but I'll make time to flip back over to load balanced mode to test out this latest beta.

Have you been able to test?

Ranger802004 commented 1 year ago

A resolution for the identified problem was introduced in v2.0.0