How many kmsg_tailer processes is enough ? (21 ?) Raspberry Pi 3 B+ on 8.0.0-rc41
( Only went looking because poor old RingLogger got duplicate after duplicate of the dmesg message set 
)
Oh, and also, why is udhcpc running on my wired interface ??
< DāOh, of course, it needs to renew leases and all that jazz . . sorry >
Lol. Getting connected to NervesHub often requires restarting :nerves_runtime which apparently doesnāt cleanup after itself. Really I only use that for development so maybe Iāll just disable it in production releases.
As for the udhcpc on eth0, I assume you are using static? That could cause problems if there is a DHCP server running. Iāll make a ticket for that one
Hey, thanks @connor, pls. donāt bother with that udhcpc on eth0 mention !
I corrected my misteak with an edit which you may have missed.
DHCP wired works well, and, I havenāt bothered trying "static" "wired" _ because I didnāt know that VintageNet supports it yet (?)
Iām fairly certain it does but I havenāt tested it personally
Hmmm . . I tried just now . . all good except thereās no /etc/resolv.conf created so no DNS lookups.
@connor, that NTP servers issue is not entirely repeatable . . previous Factory Reset (5 minutes ago) Configurator correctly did its magic and plugged in my desired names.
Next Factory Reset just now, I got the out-of-the-box default names (4 of them) instead.
Iāll dig deeper . . as Iām still looking at why the Configurator AP is so slooooooooow.
( currently using v8.0.0-rc46 as .IMG downloaded )
P.S. What do I need to do to build :iw on Ubuntu 18.04.2 ? Hereās my failure
apt-get install pkg-config libnl-genl-3-dev -y
This is very strange. maybe iāll change the check from where it is now to where credentials get checked. Will have another update coming up
I just had a realization on why it probably isnāt working for you.
Farmbot only resets NTP after the device connects to the internet currently. Obviously if the device canāt reach the first NTP servers, it wonāt be able to connect to the internet due to SSL cert errors etc. Iāve moved the check to when a network interface
becomes lower_up which for ethernet means the cable is plugged in, and for wifi means the ap has been associated with. I hope this will fix it. https://github.com/FarmBot/farmbot_os/pull/867
Thanks for all your help testing!
Thanks for all your recent amazing coding !
Hey, { You code, I test } == win<ā>win 
Re: that DNS resolver issue with static wired config . . should I send it to VintageNet or do you think itās a User-problem ( i.e. FarmBotOS coding ) ?
< I know this NTP server user-specified issue is not a big one, but itās functionality that pre-existsed and itās also desirable for School, College, Uni. networks that are usually hyper-managed. >
I think the NTP issue should be fixed now. The DNS issue is currently open on VintageNet if I remember correctly
The āNTP issueā does seem to be fixed now, thanks.
Thanks, too, for that hint to get :iw built . . with the aid of asdf Iām building firmware again ! Yay 
AND, unexpectedly, the Configurator AP is back to being responsive (!!) . . I wonder why ?
Now running -rc46 commit 2ba6c31f . .
There was an update to the DNS settings on the configutor AP. This may have fixed it. hopefully Frank Hunleth is working on a proper fix to not require IW
Thanks @connor . . Iāll test all that soon as itās ready.
Meantime, spoke too soon about that Configurator AP performance . . after 1st Factory Reset, itās back to its bad old unresponsive ways. Now that I can build again, I can debug 
A new one. WiFi Regulatory Domain is not passed into persisted network config. Itās stuck at "US"
< added with edit >
Also, VintageNet.Technology.WiFi starts the AP with country: US, not country: 00 as the code suggests it should do.
here is the DNS issue i was talking about
Yeah in the Config of the Farmbot application i have it set to US. Maybe i should default it to 00 world at boot and default configuration to US but allow users to supply it.
Iāve opened a pr here to allow changing regulatory domain
RC47 should now have better support for regulatory domain. Interested to see if it helps with your āslowā configurator issues
Now testing on -rc50 at commit 6315b224 and have a couple of observations.
The Configurator AP is now completely unusable for me (here in AU). Iām trying to investigate and will try to compare host_mode in VintageNet with the prior NervesNetwork behaviour.
If thereās a user in a Country outside US thatās willing to test Configurator, thatād be excellent.
Seems that the WiFi layer is Ok and stable (auth, associate) but the ARP and IP layers are ācactusā (very unreliable).
Canāt get the Farmduino v1.4 firmware on-line . . but do get some nice cyan debug logs
debouncey Pin Binding log during 1st synch. ( minor issue ? )Now testing on v8.0.0-rc52 at commit 89835f06 built from src
debug log dumps during upload of fbos_config JSONdebouncey
Now testing on v8.0.0-rc53 from the CI .IMG file from GitHub
boot, firmware ( farmduino_k14 ) connects and runs fine.shutdown and restart, connection to Farmduino firmware can never be re-established ! . . despite n x flash firmware attempts from the Firmware pop-up on the Device page ( picture follows) . . . time to burn a new SDHC 
< new news re: firmware >
Use WebApp Device -> FIRMWARE dropdown to set firmware None
then set firmware Farmduino (Genesis v1.4) revives the connection 
< new news re: Configurator AP >
@connor and @Gabriel thereās good news on the Configuratorās WiFi AP . . today I used a different RPi3B+ board and the AP is working very nicely (i.e. as expected).
Puzzling failure on that particular RPi3B+ I was using . . it always worked fine as a WiFi Client . . just not much good as an Access Point
Further testing on v8.0.0-rc53 configuring a wireless network connection reveals that the WiFi Regulatory Domain ( country ) is ( still ) not persisted from the Configurator Advanced form.
Remains as default 'US'.
