4G-AC68U router drops connections a lot

[In-cognito]

Hi. I got an asus 4g-ac68u modem/router that i only use with 4g lte. Im currently running firmware 4G-AC68U_3.0.0.4_384_81974 which is the next to newest one to se if it is a firmware issue, so far that is a no.
In the Wan setting window dual wan is not enabled, to only allow lte to connect. I have used both 'only lte' and 'wan and lte' and it still drop connections.
Current signals: rssi-75dbm, sinr 5db, rsrp -105dbm, rsrq -11dbm.

Symptoms are:

• Dropped connection (takes a few minutes to reconnect)
• Always gets a new public ip address
• Sometimes it won't reconnect at all, if that happens it will say "Nov 29 19:45:15 chat[2350]: Can't get terminal parameters: Inappropriate ioctl for device" in the System log window every few second
• Sometimes it reboot is my guess as it is unreachable via router.asus.com. As this have only happened 3 or so times i can say it are in a reboot state or crash stat

Observations:

• Two times have the connection dropped right after closing a game window. Confirmed with trying to open chrome right after game.
• It drops connection at least then 10 times a day, sometimes minutes apart other hours.

Efforts for a solution:

• Firmware downgrade in-conjuction with hard reset
• Tried both 'lte only' and 'wan + lte' connection with fail over and 'allow failback' box ticket under wan>dualwan>dualwan mode
• Repositioned router to a window

Spoiler: When in need of a manual reboot

Spoiler: When it auto re-connects

Spoiler: System log

May 5 07:05:00 kernel: <4>module: nf_conntrack_ftp bf6fd0b80c 00000000 cdee4b48 bf4ddc90
May 5 07:05:00 kernel: <0>1d60: cb471000 00000000 ccd54dc0 00000000 cdee4b48 c017f1b0 cb760000 00000000
May 5 07:05:00 kernel: <0>1d80: 000000module: tntfs bf64b000 493645
May 5 07:05:00 kernel: <4>module: tfat bf613000 186782
May 5 07:05:00 kernel: <4>module: ext2 bf5ff000 52776
May 5 07:05:00 kernel: <4>module: ext4 bf5be000 221674
May 5 07:05:00 kernel: <4>module: crc16 bf5b8000 1007
May 5 07:05:00 kernel: <4>module: jbd2 bf5a5000 48993
May 5 07:05:00 kernel: <4>module: ext3 bf583000 106409
May 5 07:05:00 kernel: <4>module: jbd bf572000 42367
May 5 07:05:00 kernel: <4>module: mbcache bf56b000 4599
May 5 07:05:00 kernel: <4>module: usb_storage bf55c000 34110
May 5 07:05:00 kernel: <4>module: sg bf551000 19855
May 5 07:05:00 kernel: <41b280
May 5 07:05:00 kernel: <0>1e20: 00000000 000000003
May 5 07:05:00 kernel: <4>module: scsi_wait_scan bf53f000 416
May 5 07:05:00 kernel: <4>module: scsi_mod bf51a000 108738
May 5 07:05:00 kernel: <4>module: ip6table_filter bf50d000 750
May 5 07:05:00 kernel: <4>module: jffs2 bf4ef000 91274
May 5 07:05:00 kernel: <4>module: zlib_deflate bf4e5000 19489
May 5 07:05:00 kernel: <4>module: cdc_acm bf4dc000 12614
May 5 07:05:00 kernel: <4>module: gobi bf4cf000 23478
May 5 07:05:00 kernel: <4>module: us 00000000
May 5 07:05:00 kernel: <0>1ea0: 00020441 cb76 mii bf4c0000 3367
May 5 07:05:00 kernel: <4>module: ehci_hcd bf4b2000 32382
May 5 07:05:00 kernel: <4>module: xhci_hcd bf49f000 5036df966b4 cdf966b8 00020442 000001 102552
May 5 07:05:00 kernel: <4>module: wl bf03c000 4200945
May 5 07:05:00 kernel: <4>module: dpsta bf033000 12782
May 5 07:05:00 kernel: <4>module: et bf01c000 65170
May 5 07:05:00 kernel: <4>module: igs bf014000 11992
May 5 07:05:00 kernel: <4>module: emf bf00b000 15449
May 5 07:05:00 kernel: <4>module: ctf bf000000 21199
May 5 07:05:01 kernel: <4>Modules linked in: tdts_udbfw tdts_udb(P) tdts(P) nf_nat_sip nf_conntrack_sip nf_nat_h323 nf_conntrack_h323 nf_nat_rtsp

#Did cut away 2000 lines so it can fitt on the forum for here

May 5 07:05:00 kernel: ctf: module license 'Proprietary' taints kernel.
May 5 07:05:00 kernel: Disabling lock debugging due to kernel taint
May 5 07:05:00 kernel: et_module_init: passivemode set to 0x0
May 5 07:05:00 kernel: et_module_init: txworkq set to 0x1
May 5 07:05:00 kernel: et_module_init: et_txq_thresh set to 0xce4
May 5 07:05:00 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.126 (r561982)
May 5 07:05:00 kernel: et_probe: mvlan vid[0]: 0
May 5 07:05:00 kernel: et_probe: mvlan vid[1]: 0
May 5 07:05:00 kernel: et_probe: mvlan en 0
May 5 07:05:00 kernel: dpsta_init: Jun 12 2019 23:31:45 msglevel 0x1
May 5 07:05:00 kernel: wl_module_init: passivemode set to 0x0
May 5 07:05:00 kernel: wl_module_init: igs set to 0x0
May 5 07:05:00 kernel: wl_module_init: txworkq set to 0x1
May 5 07:05:00 kernel: PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
May 5 07:05:00 kernel: wl0: wlc_ap_attach dynamic_ed_thresh_enable = 0
May 5 07:05:00 kernel: eth1: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
May 5 07:05:00 kernel: PCI: Enabling device 0002:02:00.0 (0140 -> 0142)
May 5 07:05:00 kernel: wl1: wlc_ap_attach dynamic_ed_thresh_enable = 0
May 5 07:05:00 kernel: eth2: Broadcom BCM4360 802.11 Wireless Controller 6.37.14.126 (r561982)
May 5 07:05:00 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
May 5 07:05:00 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
May 5 07:05:00 kernel: usb usb1: No SuperSpeed endpoint companion for config 1 interface 0 altsetting 0 ep 129: using minimum values
May 5 07:05:00 kernel: et0: et_mvlan_netdev_event: event 16 for vlan1 mvlan_en 0
May 5 07:05:00 kernel: et0: et_mvlan_netdev_event: event 5 for vlan1 mvlan_en 0
May 5 07:05:01 kernel: et0: et_mvlan_netdev_event: event 13 for vlan1 mvlan_en 0
May 5 07:05:01 kernel: et0: et_mvlan_netdev_event: event 1 for vlan1 mvlan_en 0
May 5 07:05:06 kernel: cdc_acm 2-2:1.2: This device cannot do calls on its own. It is not a modem.
May 5 07:05:06 kernel: cdc_acm 2-2:1.4: This device cannot do calls on its own. It is not a modem.
May 5 07:05:06 hotplug: add net usb0.
May 5 07:05:06 hotplug: Got net usb0, vid 0x5c6, pid 0x9026.
May 5 07:05:06 hotplug: set net usb0.
May 5 07:05:07 acsd: selected channel spec: 0xe06a (100/80)
May 5 07:05:07 acsd: Adjusted channel spec: 0xe06a (100/80)
May 5 07:05:07 acsd: selected DFS-exit channel spec: 0xe06a (100/80)
May 5 07:05:07 acsd: selected channel spec: 0xe06a (100/80)
May 5 07:05:07 acsd: Adjusted channel spec: 0xe06a (100/80)
May 5 07:05:07 acsd: selected channel spec: 0xe06a (100/80)
May 5 07:05:07 acsd: acs_set_chspec: 0xe06a (100/80) for reason APCS_INIT
May 5 07:05:07 4G-AC68U: start httpd:80
May 5 07:05:08 avahi-daemon[845]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 5 07:05:08 disk monitor: be idle
May 5 07:05:08 hour monitor: daemon is starting
May 5 07:05:08 httpd: Save SSL certificate...80
May 5 07:05:08 httpd: Succeed to init SSL certificate...80
May 5 07:05:09 jffs2: valid logs(1)
May 5 07:05:09 avahi-daemon[845]: Alias name "4G-AC68U" successfully established.
May 5 07:05:09 miniupnpd[891]: version 1.9 started
May 5 07:05:09 miniupnpd[891]: HTTP listening on port 44066
May 5 07:05:09 miniupnpd[891]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 07:05:10 lldpd[933]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
May 5 07:05:10 lldpd[933]: cannot get ethtool link information with GSET (requires 2.6.19+): Operation not permitted
May 5 07:05:12 kernel: SCSI subsystem initialized
May 5 07:05:12 Mastiff: init
May 5 07:05:20 WAN Connection: Ethernet link up.
May 5 07:05:24 WAN Connection: Ethernet link up.
May 5 07:05:24 rc_service: wanduck 174:notify_rc restart_wan_if 0
May 5 07:05:37 WATCHDOG: [FAUPGRADE][auto_firmware_check6451)]ntp_ready false
May 5 07:05:43 WAN Connection: ISP's DHCP did not function properly.
May 5 07:06:07 WATCHDOG: [FAUPGRADE][auto_firmware_check6451)]ntp_ready false
May 5 07:06:13 nat: apply nat rules (/tmp/nat_rules_usb0_usb0)
May 5 07:06:14 kernel: nf_conntrack_rtsp v0.6.21 loading
May 5 07:06:14 kernel: nf_nat_rtsp v0.6.21 loading
May 5 07:06:14 wan: finish adding multi routes
May 5 07:06:18 miniupnpd[891]: shutting down MiniUPnPd
May 5 07:06:19 miniupnpd[4062]: version 1.9 started
May 5 07:06:19 miniupnpd[4062]: HTTP listening on port 45614
May 5 07:06:19 miniupnpd[4062]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 07:06:24 ntp: start NTP update
Dec 16 21:17:47 rc_service: ntp 4060:notify_rc restart_diskmon
Dec 16 21:17:47 disk_monitor: Finish
Dec 16 21:17:49 WAN Connection: WAN was restored.
Dec 16 21:17:49 disk monitor: be idle
Dec 16 21:18:17 kernel: SHN Release Version: 2.0.1 7812743e
Dec 16 21:18:17 kernel: UDB Core Version: 0.2.18
Dec 16 21:18:18 kernel: sizeof forward pkt param = 192
Dec 16 21:18:19 BWDPI: fun bitmap = 3
Dec 16 21:18:22 crond[805]: time disparity of 1903152 minutes detected
Dec 16 21:18:24 BWDPI: start_bwdpi_db_10 for traffic analyzer
Dec 16 21:18:24 nat: apply nat rules (/tmp/nat_rules_usb0_usb0)
Dec 16 21:18:25 dhcp client: bound 10.151.157.69/255.255.255.255 via 10.151.157.69 for 7200 seconds.
Dec 16 21:18:30 hour monitor: ntp sync fail, will retry after 120 sec
Dec 16 21:18:30 syslog: WLCEVENTD wlceventd_proc_event(500): eth2: Auth 24:92:0E:78:F2:88, status: Successful (0)
Dec 16 21:18:30 syslog: WLCEVENTD wlceventd_proc_event(529): eth2: Assoc 24:92:0E:78:F2:88, status: Successful (0)
Dec 16 21:18:34 hour monitor: dpi engine doesn't exist

 

[In-cognito]

Additional info:
At times it seems to lose track of time.

Spoiler: System log

May 5 07:06:23 WAN Connection: WAN was restored.
May 5 07:06:23 ntp: start NTP update
Dec 18 09:01:15 rc_service: ntp 3727:notify_rc restart_diskmon
Dec 18 09:01:15 disk_monitor: Finish
Dec 18 09:01:16 disk monitor: be idle
Dec 18 09:01:51 crond[207]: time disparity of 1905295 minutes detected

 

[Baalsgate]

This is actually one of many issues in the Firmware that date back to 2018 , if you do a search you will find that people have been having this problem for years and there are mentions in forums going back to 2018 , Asus is just terrible at releasing new firmware to resolve the problem they have said this is fixed several times and clearly its not, the latest firmware is over a year old and is certainly not without many additional problems and some new ones that were not in earlier firmware releases , but perhaps because the volume of sales on this device 4G-AC68U router they dont have the budget to support it I dont know for sure why Asus fail to support the product but it is bad support from Asus all the same.

I bought one second hand and have been digging into its issues for a few months, the specifications are great but the firmware is still very buggy , if you can return it for a refund that would be my suggestion.

The actual problem is caused by the Qualicom Device which is connected internally in the unit via a usb port , the device randomly drops the device driver from the kernel but why it happens is still a mystery to me, then it just gets stuck requiring a physical reboot which is really annoying when it can happen several times a day, and with out a firmware patch this is going to keep happening.

The problem is outlined on another page i came across on my search for a solution , explaining the module crash :

https://advantech-ncg.zendesk.com/hc/en-us/articles/360025531711-How-to-trouble-shooting-Can-t-get-terminal-parameters-Inappropriate-ioctl-for-device-for-LTE-status-setting

All you can do is complain to Asus and open a support ticket but like its been happening for 3 years , they know about the problem but have just failed to do anything about it, which is unfortunate for a reasonably high end router it falls short of being reliable.

 

[Baalsgate]

Additional info:
At times it seems to lose track of time.

Spoiler: System log

May 5 07:06:23 WAN Connection: WAN was restored.
May 5 07:06:23 ntp: start NTP update
Dec 18 09:01:15 rc_service: ntp 3727:notify_rc restart_diskmon
Dec 18 09:01:15 disk_monitor: Finish
Dec 18 09:01:16 disk monitor: be idle
Dec 18 09:01:51 crond[207]: time disparity of 1905295 minutes detected

Yes it is another one of my grievances about this router as it fudges up the syslogs, it has no RTC so every reboot it goes back in time to May 5 , they could have added a script to look at the date stamp the syslog file and update the time from that or left a date in the nvram so it could update the system date much earlier in the boot process which would at least not make the syslogs look so ridiculous , as the NTP server is one of the last services to actually be started , would be nice if they did something about that too.

 

[In-cognito]

Thanks for answers. Guess my route is to try and return it or flash the router with openwrt.
Just in-case somone are trying to fix this issue; i do have a bunch more logs for when it auto re-connects and need a hard reset.

 

[Baalsgate]

Thanks for answers. Guess my route is to try and return it or flash the router with openwrt.
Just in-case somone are trying to fix this issue; i do have a bunch more logs for when it auto re-connects and need a hard reset.

pretty sure openwrt isnt compatible with this router , i looked at that too but its not on the list.