Aug 22 10:41:42 dnsmasq-script[1757]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
Aug 22 10:41:38 wlceventd: main(1239): wlceventd Start...
Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_conv_type.js.lock: 2 No such file or directory
Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_vendor_type.js.lock: 2 No such file or directory
Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_bwdpi_type.js.lock: 2 No such file or directory
Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor
Aug 22 10:41:38 kernel: br0: port 3(eth5) entered learning state
kernel: CFGP2P-ERROR) wl_cfgp2p_find_ndev : p2p inactive
kernel: wfd_unregisterdevice Successfully unregistered ifidx 4 wfd_idx 0
kernel: CFG80211-ERROR) wl_add_remove_eventmsg : Get event_msgs error (-19)
kernel: CFG80211-ERROR) wl_cfg80211_add_virtual_iface : Recvd application provided mac address:xx:xx:xx:xx:xx:xx
Those are all normal networkmap messages that have been present for years. Typically seen after you issue a reboot.Couple of logging anomalies but not sure what / if they are affecting anything:
but that file does exist in /jffs.Code:Aug 22 10:41:42 dnsmasq-script[1757]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory
And then:
The nmp*_type.js files are in /usr/networkmap but there are no corresponding .lock files in /var/lock.Code:Aug 22 10:41:38 wlceventd: main(1239): wlceventd Start... Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_conv_type.js.lock: 2 No such file or directory Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_vendor_type.js.lock: 2 No such file or directory Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor Aug 22 10:41:38 networkmap: Error locking /var/lock//usr/networkmap/nmp_bwdpi_type.js.lock: 2 No such file or directory Aug 22 10:41:38 networkmap: Error unlocking -1: 9 Bad file descriptor Aug 22 10:41:38 kernel: br0: port 3(eth5) entered learning state
Normal behaviour unless you have a 160MHz capable client currently connected.Lastly, 160mhz won't stick for more than about 30 secs after `dfs state: in state monitoring` starts and dropping back to `dfs state: idle` unless the channel is Auto. Log levels are debug/all and there is no hint as to why; no mention of radar detection for example. Also curious that I don't see any chanspec output detailing the step down from 160 to 80. When I tried Auto it chose 116 and was stable for the few minutes I tried before trying with fixed channel again.
Is it though; shouldn't the dfs state remain as in-service monitoring unless it is tripped by radar ? Looks like @octopus has had that for 10+ hrs. That has been my prior experience and this time around my laptop wouldn't connect at anything but 80mhz using channel 36 but did connect at 160mhz when using auto.Those are all normal networkmap messages that have been present for years. Typically seen after you issue a reboot.
Normal behaviour unless you have a 160MHz capable client currently connected.
I also work in IT, but unfortunately these are consumer devices and you simply can't just pull in your config from a text file like you can on your cisco routers. There was a cryptic note in the release notes for firmware 3.0.0.4.388.23110 that stated a factory reset is required. Also sometimes previous bug can cause inaccessible parameters to be corrupted. It's frustrating I agree.In 2023, having to perform a factory reset and reprogram is pure and utter BS. I'm not going in and reprogramming a thing. I've been a CCIE for 20 years and the day I have to go in and do a factory reset to upgrade a Cisco device is the day I quit I.T.
Sadly Asus choose to store some default config values such that we can't just write them easily from either UI or a CLI, and sometimes a factory reset is the only way to get them re-written.ASUS RT-AX88U Pro will qualify for the ‘Engineered for Intel® Evo™’ designation only when used with firmware version 3.0.0.4.388.23110 or greater. Please download that update to ensure the best experience in compatibility and performance. After Firmware upgrade, please do factory reset to apply the changes.
Does anyone know if this is just standard background noise, or does it represent a misconfiguration, etc.? Thanks.
Aug 21 22:43:04 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 21 22:43:07 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 21 22:43:20 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 21 22:43:22 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 21 23:28:48 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 21 23:28:51 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 100 mbps full duplex
Aug 22 07:51:05 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 07:51:09 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 22 11:58:04 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 11:58:06 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 100 mbps full duplex
Aug 22 12:30:18 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 12:30:22 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 22 15:32:17 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 15:32:19 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Aug 22 15:32:33 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link DOWN.
Aug 22 15:32:36 kernel: eth5 (Int switch port: 6) (Logical Port: 6) (phyId: 13) Link Up at 1000 mbps full duplex
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!