The KiwiSDR 2 online store is open for orders! Please visit kiwisdr.nz

"Still determining local interface address. Please try reloading page in a few moments." problem

rrobinetrrobinet
in Configuration and Operation
This isn't a big deal, since I can recover control by rebooting or power cycling the Kiwi.

This message greeted me on several Kiwis after SW upgrades.
/var/log/messages ends with:
...
Nov 4 23:47:11 kiwisdr kiwid: 00:00:48.802 0.234567 TIMEZONE: "PST", "America\/Los_Angeles"
Nov 4 23:47:47 kiwisdr kiwid: 00:01:24.468 0.234567 [07] PWD isLocal_if_ip: IPv4 client, but no server IPv4/IPv4_6
Nov 4 23:47:47 kiwisdr kiwid: 00:01:24.472 0.234567 [07] PWD admin config pwd set TRUE, auto-login TRUE
Nov 4 23:47:47 kiwisdr kiwid: 00:01:24.474 0.234567 [07] PWD admin CAN'T DETERMINE: no local network interface information

After a reboot admin access is OK.

Comments

  • jksjks
    Wired Ethernet or WiFi (wlan) connections?
  • rrobinetrrobinet
    This is a standard wired-LAN only connection.
  • ngmachangmacha
    I have been encountering this same problem several times too! I'm on wired LAN connection, yesterday everything was normal, today getting "Still determining local interface address. Please try reloading page in a few moments." connecting to admin page. Rebooted BBB several times, still the same. /var/log/messages ends with:
    Dec 12 11:20:26 kiwisdr kiwid: 00:16:31.608 01234... UPDATE: exiting because admin update check not enabled
    Dec 12 11:20:28 kiwisdr kiwid: 00:16:32.892 01234... [06] PWD isLocal_if_ip: IPv4 client, but no server IPv4/IPv4_6
    Dec 12 11:20:28 kiwisdr kiwid: 00:16:32.895 01234... [06] PWD admin config pwd set FALSE, auto-login FALSE
    Dec 12 11:20:28 kiwisdr kiwid: 00:16:32.897 01234... [06] PWD admin CAN'T DETERMINE: no local network interface information

    What could be a problem and how to fix this? Please help.
    Thanks a lot in advance.
  • PowernumptyPowernumpty
    BBB? BeagleBone Blue or Black?
    Any other network interfaces?
  • jksjks
    edited December 2019
    but no server IPv4/IPv4_6
    So the Kiwi doesn't think the Beagle has a network interface with a valid ip address. But how are you looking at the log then? Logging into the Beagle/Linux with an ssh connection as root? If so, please do a "ifconfig -a" and paste the results here.

    Your Kiwi is set to get an ip via DHCP I assume? And using wired Ethernet?
  • ngmachangmacha
    I'm logged in as root via ssh, and the normal user connection to KiwiSDR still works normally, all 8 of them! I'm running several WSPR sessions, as well as listening to stations - waterfall, audio, everything works. The problem is only with admin page access! After multiple restarts, it finally appears, but why this is happening?...

    Yes, I'm on wired Ethernet and DHCP. As requested here is ifconfig output:

    root@kiwisdr:~# ifconfig -a
    eth0 Link encap:Ethernet HWaddr c8:a0:30:ac:65:ad
    inet addr:192.168.0.28 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::caa0:30ff:feac:65ad/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:139188 errors:0 dropped:0 overruns:0 frame:0
    TX packets:136141 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:13687539 (13.0 MiB) TX bytes:117349637 (111.9 MiB)
    Interrupt:175

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:18 errors:0 dropped:0 overruns:0 frame:0
    TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1
    RX bytes:1112 (1.0 KiB) TX bytes:1112 (1.0 KiB)

    usb0 Link encap:Ethernet HWaddr c8:a0:30:ac:65:a0
    inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    BTW I don't know what that usb0 is, as nothing is plugged in the USB port. The beagle has only the power and LAN cable connected in, and two antenna cables (a magloop and GPS) connected to the Kiwi board...
  • jksjks
    Could do this again when you are sure the Kiwi is in a state where it isn't letting you in? And then try getting in as admin again after taking the ifconfig snapshot to be sure the Kiwi is still determining the local address? Everything here looks fine.

    This happens because if the Kiwi can't decide what its local ip address is then it darn sure can't let you into the admin page without supplying the admin password, assuming none has been set. Otherwise how could it distinguish attempted admin connections from the outside Internet?
  • HB9TMCHB9TMC
    @jks how about having the admin interface on a separate tcp port?
    Common practice in similar devices. But of course you can't keep users from sharing it with the entire internet.
  • ngmachangmacha
    Run it the whole day today for WSPR, and the whole day unable to login to the admin page. Then just connected via ssh, run cdp and ku, and the admin page appeared. How come?
  • jksjks
    Who knows.

    If I had the chance to connect to it while it was failing I probably could have seen what was going on (network issue, Kiwi bug, browser cache issue, ...) But too late for that now I suppose. Please let me know if it happens again. If it does it would really help if you can open port 8073 on your router. The Kiwi doesn't have to publicly listed, but I have to be able to connect on port 8073.
  • ngmachangmacha
    @jks not sure I can do that, our ISP doesn't allow access to the router... Let me see what can I do. What time zone are you in, how may I PM you?
  • jksjks
    edited December 2019
    You could just put your Kiwi on the proxy service. No router changes required. Follow the directions on the admin "connect" tab (bottom of page). Except don't bother getting an API key from sdr.hu. Just email me at support@kiwisdr.com and I'll send you an activated API key.

    I'm UTC+13, so somewhat inconvenient for Europe.
Sign In or Register to comment.