Log file quite a bit bigger

Comments

• jks

  February 2020

  The "update exiting..." message shouldn't be getting logged. I'll fix that in the next release. It was inadvertently changed in a recent rewrite of the code.
  
  You should consider adding 47.74.181.109/32 to your ip blacklist. IP geolocation puts it in (supposedly) Hangzhou.
  
  Yes, running any linux command that takes cpu cycles away from the Kiwi server (or does filesystem I/O) can cause audio hiccups because it disrupts the realtime requirements of the Kiwi server (i.e. it doesn't run often enough for long enough).
• VR2BG

  February 2020

  The "update exiting" I think has been going on for a while now.
  
  Didn't quite make it yesterday, but expect today's log dump to be triple the usual size.
  
  Since all this started, I have now had on three occasions local users denied as all receivers reported to be in use. Each time, the local user was already a local user & simply retuned by selecting another bookmark. And as admin, the local user could see that not all eight receivers were in use when they were said to be. One time, kicking the only non-local user so another receiver was not in use still resulted in the local user being told all receivers were in use.
  
  ?????? - is the blacklist sufficiently dimensioned to block all of Bravoland? I've got enough Bravoland mucking up my life as it is!
  
  73, VR2BG.
• jks

  February 2020

  Your public Kiwi seems to still be running v1.380. I fixed the log issue in v1.382 (current release) on Feb 20/21.
  
  The blacklist is just a front-end for iptables which should accept a very large number of entries and no restrictions on subnet specifications.
• VR2BG

  February 2020

  Updates are done with some hesitation here since the FF audio issue as if something like that happens again, there's no way to go back. Went to v1.382 yesterday.
  
  Good to know if I eventually need to block all of the People's Paradise, it might fit. Have already got a good start on it, /24 at a time. |^)
  
  Am still enjoying existing local users being told my Kiwi is full on a retune from time to time, the most recent this morning when I got home from work & my Kiwi had three receivers free. I don't recall this happening before & it's happening a lot, so there must be a reason...
  
  73, VR2BG.
• VR2BG

  February 2020

  FF instance in lower right hand corner previously had RX0, but on selecting another bookmark got fobbed off as my Kiwi apparently only has 5 receivers now.
  
  Now 30 minutes later, it still insists it's chock-a-block.
  
  
• VR2BG

  March 2020

  Oops, make that blacklisting the People's Paradise at /16 each go...
  
  After about an hour, my Kiwi apparently decided it had more than five receivers again & let the local user back on without having done anything other than wait. This was the third time this happened; it hasn't happened again since.
  
  Log file now >20 MB (10x usual size). All the IPs I've blocked are constantly at it. I have been having problems using remote access on my phone to control my local user computers - sometimes the ones on WiFi were very slow to respond... then later they were fine & the machines on Ethernet seemed to be constipated. At first I suspected my WiFi/router was trying to tell me it is about to die due to old age, but with what must be a dozen log lines/minute at times, I now wonder if it's simply choking on all the dodgy Bravo activity.
  
  73, VR2BG.
• Powernumpty

  March 2020

  One thing that confuses me about your screen shot, have you edited the remote addresses?
  To me 192.168.3.x are all local addresses so not sure of your setup?
  I only ask as I'm trying to work out how the Kiwi will filter if the remote stations all look local.
  
  73, Stu
• cathalferris

  March 2020

  Looks as though all the 192.168.x.x addresses are the local network listeners; but that the Kiwi is reporting all in use though 3 are definitely being shown in the admin interface as being free.
  
  Very interesting that the geolocation for VR2BG's LAN addresses is (correctly) showing HK region.
• VR2BG

  March 2020

  Yes, 192.168.3.* are local users & yes, despite there being several free receivers, the local user has been fobbed off because apparently all the receivers were in use. This has happened several times ever since all the dodgy Bravo activity started.
  
  I believe the Kiwi knows I'm in Hong Wrong based on the external IP of the GPON service from our dominate telco... which is why I'm apparently all over Hong Wrong.
  
  73, VR2BG.
• Powernumpty

  March 2020 edited March 2020

  OK that makes sense, same location randomisation happens here but I was thrown by the location (doh).
  I did try installing/running "iptraf" on a Kiwi here to see what connections are passing data, might be interesting on one that is getting locked up but it will negatively impact CPU so don't leave it running for long*
  73, M0AQY
  
  *If you are daft enough to install something I have mentioned at all.
• Powernumpty

  March 2020

  Another possible option is a software router? Pfsense etc?
  It might even be possible to get alternative firmware (E.G. DD-Wrt/Tomato) for some hardware you already have.
  
  Your other comments reminded me to give thanks for my fairly unrestricted living conditions.
  Good luck.
  
  73, Stu
• WA2ZKD

  March 2020

  Pi-hole might do it https://pi-hole.net/