New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no ip address given in console #924
Comments
Turns our Fing is available for Android, iOS, Windows, and OS X. There is a fing package for linux but it is of dubious packaging quality as per my Ubuntu 15.04. |
On an ubuntu system one can:- |
I still have this happening on testing 3.8-8.05, upgraded from a clean install of 3.8-7 to 3.8-8 then testing selected and updates applied. system is core 2 duo but boot from msata in pci so pretty quickly. |
…#924 Previously /etc/issue was updated by initrock but sometimes this took a few goes. Recently only a single try has been attempted. Return to multiple tries as needed in many instances.
I am now working on a pull request to return prior behaviour as we have recently had a regression that caused only a single try when the interface was still in the throws of getting it's IP. This resulted in /etc/issues never getting updated with an IP, even after multiple presses use to be the case in #734 . Should be ready to merge later today. |
As we may still be waiting for a background update of the /etc/issue message that Enter will provide updated network status as this will cause a re-read of the possibly now updated /etc/issue containing the just configured ip.
Closing as pr #940 should address this. |
As of 3.8-8 the console displays "The system does not have an ip address"
Yet it does, login and ifconfig displays this.
Reproduced by fresh 3.8-7 install, applied 3.8-8 update and then rebooted.
All subsequent reboots display this same misleading message.
Rockstor machine can be found in list of all machines via "fing" app on android or "arp -a" in terminal on linux system or via router webUI dhcp / connected clients section.
The text was updated successfully, but these errors were encountered: