Local admin log-in started to ask for password [delayed DHCP server startup]

Comments

• jks

  October 2018 edited October 2018

  Couple of questions:
  Is either of these Kiwis accessible from the Internet? If so, what's the URL?
  You say "started to ask for password" and then later "unable to connect" (browser saying that?). These are not the same thing. Which is it?
  
  If you can login as root to the Beagle then you can check for an admin password being set. But this almost certainly is not going to be the case. Type "cdk" to change to the configuration directory and then "more admin.json". Towards the start of the output you should see "admin_password":"" if no password has been set.
  
  Can you cut-and-paste the relevant messages from the log? They'll be like:

  Thu Oct  4 07:42:01 00:03:40.436 0...     [02]   PWD isLocal_if_ip: flg=0x18 fam=2 socktype=1 proto=6 addrlen=16 192.168.1.6
  Thu Oct  4 07:42:01 00:03:40.437 0...     [02] L PWD isLocal_if_ip: TRUE IPv4/4_6 remote_ip 192.168.1.6 ip_client 192.168.1.6/0xc0a80106 ip_server[IPv4] 192.168.1.103/0xc0a80167 nm /24 0xffffff00
  Thu Oct  4 07:42:01 00:03:40.437 0...     [02] L PWD admin config pwd set FALSE, auto-login TRUE
  Thu Oct  4 07:42:01 00:03:40.438 0...     [02] L PWD admin ALLOWED: no config pwd set, but is_local
  Thu Oct  4 07:42:01 00:03:40.438 0...     [02] L PWD admin ALLOWED: from 192.168.1.6
  
• G0EZY

  October 2018

  Sorry - admin password had been set.
  
  Following your instructions to look at the log through PuTTY - an admin password HAS been set and I have now used it successfully to get into the web admin interface and now I am able to look at the webAdmin security Tab and see the password, although the "Admin auto-login from local net even if password set?" is set to "Yes"
  
  I think I must be losing my marbles as I cannot remember setting a password and if I did it must have been in the last two days... I am sorry to have wasted your time. Although I would never have solved the problem without your instructions to check the log via PuTTY.
  
  Just to clarify the Local log-in "issue":
  
  If I use the full local IP address: http://192.168.1.103:8073/admin then password is (now) requested
  
  If I use: kiwisdr.local:8073/admin then I get "Unable to connect"
  
  However it is possible that "kiwisdr.local:8073/admin" has never worked as I have always used the full local IP address. My PCs are in a Windows Workgroup, the Kiwis are not.
  
  Map display
  
  Both Kiwis were visible on the map but just checked the map and now they are not. They are still accessible using
  
  http://g0ezy-kiwisdr.ddns.net:8073/ and
  http://g0ezy-kiwisdr.ddns.net:8079/
  
  I can see in the Log, many reports of "sdr.hu registration: DOWN" so now going to sort that out
  
  Thanks for your help
  
  Terry
• G0EZY

  October 2018

  Finally - realised what has happened. We have had mains supply problems. Kiwis rebooted before the router started so not supplied with IP and allocated their own address. When router started and addresses available the Kiwis kept their "Private IP address (inside your firewall/router)". After rebooting the Kiwis, the Router IP address replaced the default address and now all is back to normal and are showing on sdr.hu map.
• jks

  October 2018

  Okay, this makes more sense now. Looking at your log messages I see this when an admin connection was attempted 37 seconds after reboot:

  Thu Oct  4 09:49:34 00:00:37.025 ..23....     [04] PWD isLocal_if_ip: flg=0x18 fam=2 socktype=1 proto=6 addrlen=16 192.168.1.196
  Thu Oct  4 09:49:34 00:00:37.025 ..23....     [04] PWD isLocal_if_ip: IPv4 client, but no server IPv4/IPv4_6
  Thu Oct  4 09:49:34 00:00:37.028 ..23....     [04] PWD admin config pwd set TRUE, auto-login TRUE
  Thu Oct  4 09:49:34 00:00:37.030 ..23....     [04] PWD admin CAN'T DETERMINE: no local network interface information

  So yes, the Kiwi hadn't been able to determine its local address at that point. So local network auto-login would not be able to override and you were asked for the admin password. 02:44 after boot the Kiwi is finally able to get a response to its DHCP request (assigned the .103 address) and in turn start DDNS opening the port on your router:

  Thu Oct  4 09:51:41 00:02:44.259 ..23....          DDNS: public ip xx.xx.xx.xx
  Thu Oct  4 09:51:41 00:02:44.266 ..23....          DDNS: private IPv4 <192.168.1.103> 0xc0a80167 /24 0xffffff00
  Thu Oct  4 09:51:41 00:02:44.266 ..23....          DDNS: private IPv6  /64 ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:
  Thu Oct  4 09:51:41 00:02:44.266 ..23....          DDNS: private IPv6 LINK-LOCAL  /64 ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:
  

  And at 05:29 an admin connection without requiring the password succeeds:

  Thu Oct  4 09:54:26 00:05:29.653 ..23....     [04] PWD isLocal_if_ip: flg=0x18 fam=2 socktype=1 proto=6 addrlen=16 192.168.1.196
  Thu Oct  4 09:54:26 00:05:29.653 ..23....     [04] PWD isLocal_if_ip: TRUE IPv4/4_6 remote_ip 192.168.1.196 ip_client 192.168.1.196/0xc0a801c4 ip_server[IPv4] 192.168.1.103/0xc0a80167 nm /24 0xffffff00
  Thu Oct  4 09:54:26 00:05:29.657 ..23....     [04] PWD admin config pwd set TRUE, auto-login TRUE
  Thu Oct  4 09:54:26 00:05:29.659 ..23....     [04] PWD admin ALLOWED: config pwd set, but is_local and auto-login set
  Thu Oct  4 09:54:26 00:05:29.659 ..23....     [04] PWD admin ALLOWED: from 192.168.1.196