Recent content by Untried3868

Is there an SSID character limit in WR? I ask because it's cutting off the last character (16 17) of my SSID. Edit: Correction, 17 characters. Math is hard apparently.

I'm not sure which of the recent updates may have changed this, but one of my devices now shows "Wireless" rather than the connection SSID on MAIN. Another device on NODE connected to the same SSID is displayed properly. It was previously working correctly. I just checked for updates and I'm...

I'm seeing the 6G band in WR with a channel bandwidth of 80MHz but it's set to 160MHz. EDIT: Nevermind. Apparently it's the connecting device. Another connected to the 6G band showing 160MHz. My bad.

Under LAN - DHCP Server: Hostname (Optional) column.

Will one need a mortgage to purchase a Wi-Fi 8 router?

With the help of @JB_1366 (thank you!) I was able to get things working. As usual a PEBKAC or ID10T situation. ;) A couple of observations: If you're not using port 22 for ssh then you must alter the the command to create a known host file and make persistent (post #16, step 5) as follows...

I just installed the script via AMTM, ran through the initial setup including providing nicknames for both router and node (which the script found immediately). But when I bring up the GUI (Librewolf), it's only detecting wireless connections on the router, shows the node as offline. Does the...

No noticeable issues so far.

Just a follow-up. My OCD would not allow me to let this issue rest. I'm happy to report I was able to get the script working on my node using a new SSK enclosure which I found on Amazon. I thank everyone involved for the script and support.

I find it odd that one drive works, but the other failed with two different (albeit same brand/model) enclosures. At this point I'm not sure the juice is worth the squeeze. Thank you for all your help.

I'm sad to report I'm still getting the remote I/O error on the node, even with the new enclosure (UGreen with Patriot P210 drive). I tried both USB ports as well. No luck.

I tried swapping cables first, and plugging the node SSD into the router. Same error. I then swapped enclosures and plugged the SSD into the router again and the script worked without the I/O error. Off to Amazon to order a replacement. Thank you for responding.

Wouldn't that mean reformatting and setting up AMTM and associated add-ons from scratch? Or can I simply safely remove the enclosure from the router and plug it into the node?

I'm getting an Remote I/O error on my node. I followed the steps in the @jksmurf post #64 with the exception of WinSCP. I simply used wget to grab the files directly from @kuchkovsky GitHub page. Everything worked flawlessly on the router, but I get the following error on the node: ssd_trim...

Dirty upgrade from 102.7 on both router and node. No noticeable issues after about 3 hours of uptime.