Recent content by Akro

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. A

    Later than 3.0.0.4.374.39 - cell modem not working

    I did search the forums. Perhaps when you reply with such an answer, you could include either the search terms you used, or a link to the "well known issue". The only way I managed to find this was using keyword HUAWEI, which quite fortunately is correctly spelled...
  2. A

    Later than 3.0.0.4.374.39 - cell modem not working

    I would love to be able to upgrade to a newer version of Asuswrt-Merlin, but I find no version beyond 3.0.0.4.374.39 will work with my cell modem. Recent versions of stock ASUS firmware do not work either. It is a HUAWEI E153 USB modem (3G I believe). Log simply reports "Failed to...
  3. A

    HOW TO- Windows batch file to log into your router with PuTTY.

    A bit more elaborate... change the password on Guest Networks with this BAT file (WIFIchange.bat) from the command-line, using: WIFIchange.bat newpassword :: WIFIchange.bat @echo off cls :: :: Set Router Information :: you can use password login or keypair :: set...
  4. A

    Rogue variable in NVRAM

    [SOLVED] Rogue variable in NVRAM # nvram show | grep wl0.1_wpa_psk wl0.1_wpa_psk=goodfriends wl0.1_wpa_psk!={SETTING:WiFiPW}!! # badstring=$(nvram show | grep "wl0.1_wpa_psk" | grep "SETTING") # badchars=$(echo $badstring | sed 's/wl0.1_wpa_psk//g') # badpart=$(echo $badchars | awk...
  5. A

    Rogue variable in NVRAM

    Here is the issue - there are embedded non-printing/invisible characters inside. I went in through PuTTY and turned on it's logging, and found this: # nvram show | grep wl..1_wpa_psk size: 44778 bytes (20758 left) wl1.1_wpa_psk!={SETTING:WiFiPW}!! wl0.1_wpa_psk!={SETTING:WiFiPW}!! # I've...
  6. A

    Rogue variable in NVRAM

    Well, I've done it again... this time using sexec from Bitvise, running this from a .bat file: sexec.exe %rUSER%@%rHOST%:%rPORT% -pw=%rPASS% -tracelevel=1 -tracefile=%TRACEFILE% <test.sh >> %LOGFILE% 2>&1 Where 'test.sh' has this inside: guestnet24_1=wl0.1_wpa_psk guestnet50_1=wl1.1_wpa_psk...
  7. A

    Rogue variable in NVRAM

    Thanks for that RMerlin. I actually already tried that. I've since cleared the NVRAM and started over again (twice now since I managed to muck it up again). Here is some more background information that may help to track down the cause and possible solution. Keep in mind, I'm not much good...
  8. A

    Rogue variable in NVRAM

    [SOLVED] Rogue variable in NVRAM Can someone please help me to get rid of this rogue variable in NVRAM, short of clearing nvram? I am running Asuswrt-Merlin v3.0.0.4.374.39_0 on an ASUS RT-AC66U. admin@RT-AC66U:/tmp/home/root# nvram show | grep wl0.1_wpa_psk =anothertrysk size: 41956...
Top