06-13-2026, 08:18 PM
Thanks for the fast response.
Well, I spent several hours working with it today and used multiple routers. What I have found is that no matter what I do, the SSID is not being saved or recalled or something when *NS is being used. Over the several hours, I could not get ANY SSID to save with *NS; spaces or not and regardless of which router is being used. I am in the middle of farm land so there isn't like a bunch of SSIDs being detected.
The only way I can get a router to be saved is if I use *SSID and that requires no spaces. So, I have created a virtual network on our main router so I can have an SSID with no spaces for the modem. It's a temporary work-around.
So, do I have a bad modem or has a bug perhaps creeped in with *NS?
tl;dr - The modem I have is not recalling ANY SSID, regardless of spaces or not, when I use the *NS command. It is only being recalled when I set it with the *SSID, which requires that the SSID has no spaces.
Well, I spent several hours working with it today and used multiple routers. What I have found is that no matter what I do, the SSID is not being saved or recalled or something when *NS is being used. Over the several hours, I could not get ANY SSID to save with *NS; spaces or not and regardless of which router is being used. I am in the middle of farm land so there isn't like a bunch of SSIDs being detected.
The only way I can get a router to be saved is if I use *SSID and that requires no spaces. So, I have created a virtual network on our main router so I can have an SSID with no spaces for the modem. It's a temporary work-around.
So, do I have a bad modem or has a bug perhaps creeped in with *NS?
tl;dr - The modem I have is not recalling ANY SSID, regardless of spaces or not, when I use the *NS command. It is only being recalled when I set it with the *SSID, which requires that the SSID has no spaces.