jks
About
- Username
- jks
- Joined
- Visits
- 35,583
- Last Active
- Roles
- Member, Administrator, Moderator
- Points
- 600
Reactions
Comments
-
v1.817 rolls back to Mongoose 5.6 fixing the problem. I see what the problem is, but I could not find where exactly the problem was. So I'll look for it offline. We'll continue to have the "connections from 127.0.0.1" problem as a result. …
-
What do you mean "while switching modes"? Error 502 is "Bad gateway". Do you have an unusual network setup? Private proxy? Wireless link, etc?
-
This 10 second delay is unfortunate. But it's essential that the algorithm has no false positives.
-
These Kiwi most likely have the setting "Number of simultaneous channels available for connection by non-Kiwi apps" set to "None" (admin "connect" tab). The algorithm for determining if a connection is a "bot"…
-
Almost certainly because I've been updating the IP address blacklist and you have automatic blacklist downloads turned on. On the admin status tab is a list of all possible reasons for a nightly restart. The last item in that list "Network tab:…
-
@bwilson That's valuable intel -- thank you. I've taken them out of the global blacklist. If anyone wants to add them back just put 133.9.0.0/16 into your local blacklist.
-
So there is some indication now the tariff would be collected as VAT is now in the UK/Europe. That is, DHL contacts you when the parcel lands and asks for the tariff to be paid via credit card PLUS their "processing" fee (amount TBD). Then…
-
Don't know. NZ tariff just got bumped from 10 to 15%. But the unknown is the overhead. What does DHL charge us in fees? How much of my time gets spent dealing with this instead of working on stuff you guys actually want? The list goes on and on..
-
Yep, bug in the Mongoose web server we use. Fixed by switching to an updated version. I had been planning this switch for a long time (it's needed for wide band mode), but delayed because it's a major change. Now there is a good reason to finally ma…
-
I think this problem may have been found.
-
Okay, blacklist pushed with 7 new IP ranges.
-
Well, it seems they do have an assigned /16. You have to go to the .jp nic to find it. No wonder we're out of IPv4 addresses. There's no way a university needs 64k public IPs in this day and age..
-
Do you have a more specific IP address? There is no way Waseda has a /16 allocation (64k hosts) and I'm not going to blacklist 133.9.0.0/16 since the whois for that large range is not allocated to Waseda.
-
So the problem here was a Kiwi purchased from a distributor that was old enough it didn't have the two boards (Kiwi, Beagle) held together via the two nylon standoffs. Vibration in transit was enough to separate the two header connectors such that t…
-
Private messaging has been disabled because it can't be moderated.
-
Updates have been made to the forum rules (first post). They are shown in bold text.
-
Interesting. The Feb 20/21 date/time is when the particular log message was recorded. Note in part 4 that I was logging in as a user. I wonder if we were chasing some problem back then. I couldn't find anything in my notes or email about that. Maybe…
-
So the problem with those screen captures is that they're log messages from 5 months ago -- Feb 20 & 21. Look at the times on the left of each message. When running the msl command you'll get thousands of messages dumped. What I really want to s…
-
Well, this entire thing quickly becomes yet another SNR-related rabbit hole. One that I can ill afford at the moment given all the other important stuff I'm working on. I'm only doing it because of a person who is very unhappy the top NZ SNR score i…
-
I don't know what that bash error is. Probably not of great significance. But perhaps an indication of an unclean shutdown (pulling power in the middle of a disk [eMMC] write). What's more concerning is further down where the Kiwi server only ran 6 …
-
Hi Paul. I sent you an email a few hours ago. What's the serial number of your Kiwi? Reply via email to support@kiwisdr.com instead of here if you like.
-
Okay, I wasn't sure how much you knew. Once someone knows how to ssh it's a pretty good bet they know all the rest. When logged in using account "debian" do a sudo su and give the root account password which should be the same as the Kiwi …
-
Pre-sunrise. Freezing cold. I hate NZ winters.. Have you tried restarting or power-cycling since the restart after flashing? Sometimes things just get stuck for unknown reasons. Since you're ssh'd in do a safer restart via the restart command (as ro…
-
Hi John. Not sure what might have happened. The TDoA station list is generated dynamically by the same process that generates the rx.kiwisdr.com list, which in turn causes map,kiwisdr.com to be updated. But the reference station list is static, and …
-
Yes, because it makes no sense to try and register a Kiwi as being public when there will be no channels anyone can connect to! If you want all your channels to have a password then presumably everyone who knows the password also knows how to get to…
-
The wording of that menu item is perhaps not 100% clear. But I couldn't think of a better way of saying it.
-
So I think the summary here is that there are routers that behave badly and the Kiwi code needs to be changed to accommodate that. Starlink after a power outage is another case. Apparently it takes forever for the terminal to acquire sats and assign…
-
On the admin page, "security" tab, change the menu called "Number of channels not requiring a password even if password set". You might have it set to "1" currently while also having a user password specified. Either re…
-
That ZL4MD one is what I used to develop the scheme. Thanks, I'll try the others. I'm curious to see how well it does in more marginal cases. I'm sure some adjustment will be needed.
-
I don't understand why in both those cases there is a 3 minute delay after carrier-up until an DHCPv4 is assigned. The Kiwi code only waits for a little while before it gives up and takes whatever it has. In the first case the IPv6LL. This is becaus…