SuperFreaky
Occasional Visitor
i retract my statement, had a few random reboots and a few dropouts.
reverting to 388.2_2 release.
reverting to 388.2_2 release.
Do the logs tell you anything? Merlin can't possibly fix anything - if it is in his control - without details. Alpha testing is meant to help a developer nail down issues. Can't do that without logs and details.i retract my statement, had a few random reboots and a few dropouts.
reverting to 388.2_2 release.
Every time router is rebooted or manually reboot SSD disk is unmounted have to unplug and plug in to have it to mount again.Updated my routers to beta2 with no problem.
0 days 22 hour(s) 1 minute(s) 54 seconds
Had to reboot master 2.4GHz as acting weird.
After that it's working just fine.
Thank you!
Every time router is rebooted or manually reboot SSD disk is unmounted have to unplug and plug in to have it to mount again.
Have you same behaving as me?
echo "- - -" > /sys/class/scsi_host/host<n>/scan
--> where <n>
is the host number.host0
, but sometimes it throws me a host1.WAN issues should now be resolved. It's a bug in the GPL archive for HND 5.04 models where the ethctl userspace tool is not properly added to the firmware, causing the switch to not being properly configured. The fix will be included in beta 3.
Yes.@RMerlin - I noticed you mentioned a fix to the WAN code a few posts above, is this the same thing?
No, I haven't had time to look into the DDNS issues yet.@RMerlin - I noticed you mentioned a fix to the WAN code a few posts above, is this the same thing?
No, I haven't had time to look into the DDNS issues yet.
I set the WAN IP and hostname verification to 30 minutes and it seems to be OK.OK, I have the syslog saved if it's of any use.
I set the WAN IP and hostname verification to 30 minutes and it seems to be OK.
You are better off running Asus firmware on the nodesHelp.. like my post previously.. 2 xt12’s one wired backhaul… when i update man xt12 unit to this beta all ok.. i then update the node , it updates but everything that links through it dies… i have to revert to 388.2.2 for the node and all works again.
Why is this happening with these beta’s i cannot even access the xt12 node to check operation mode.. do ‘t really want to disconnect.. factory reset and hard wire clise to main unit on a whim as its a ball ache.. any i sight welcome
Thx
Aug 10 16:25:56 kernel: CPU: 0 PID: 2691 Comm: cfg_server Tainted: P O 4.1.52 #2
Aug 10 16:25:56 kernel: Hardware name: Broadcom-v8A (DT)
Aug 10 16:25:56 kernel: task: ffffffc001f4b580 ti: ffffffc011b50000 task.ti: ffffffc011b50000
Aug 10 16:25:56 kernel: PC is at 0x2a7bc
Aug 10 16:25:56 kernel: LR is at 0x2a78c
Aug 10 16:25:56 kernel: pc : [<000000000002a7bc>] lr : [<000000000002a78c>] pstate: 80010010
Aug 10 16:25:56 kernel: sp : 00000000f6749bf8
Aug 10 16:25:56 kernel: x12: 00000000000be190
Aug 10 16:25:56 kernel: x11: 00000000f65194e0 x10: 00000000f651b270
Aug 10 16:25:56 kernel: x9 : 00000000f6749c84 x8 : 00000000ffdba032
Aug 10 16:25:56 kernel: x7 : 000000000000000c x6 : 00000000f6ff0ab8
Aug 10 16:25:56 kernel: x5 : 00000000f6517290 x4 : 00000000f65130c8
Aug 10 16:25:56 kernel: x3 : 00000000000a5180 x2 : 00000000f6500470
Aug 10 16:25:56 kernel: x1 : 000000000000001d x0 : 0000000000000000
Not a new setting but something you can turn on to insure the hostname is kept up to date.Is that a new setting that needs to be configured?
Mine is switched off, but the DDNS update has always worked in the past.
Pretty much instantly.
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!