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
omv-firstaid - configure network interface not working with RPI 4 #417
Comments
Can you please try to find out which parameter is incorrect. I'm not able to reproduce this, so i can only change values by guessing. Potential code might be: Another option might be to get some infos from your tty: |
I think this has something to do with the network port on the PI itself. Everything else works properly within omv-firstaid. Just the configure network thing does not. I tried several other values in the files you mentioned. But it does not work at all after clicking the option 1. Stty size is 32 76 |
Can confirm same issue on my Ras Pi 4 as well, I agree it's probably not a terminal sizing issue as I've tested it on a 2160p monitor over DP, a 1080p TV over HDMI and also via SSH on my Monitor, Tablet and Phone, exact same result every time. I struggle to believe all those devices share a terminal size. Unlike OP I'm running OMV 4. |
- Fix some pylint warnings Signed-off-by: Volker Theile <votdev@gmx.de>
It seems no network interfaces are detected. The commit 66b6569 will display an error in this case. |
While that does fix the error, why is not finding the network interface? It is eth0 and configured properly in the omv web interface for dhcp on my system. |
…faces are detected. Signed-off-by: Volker Theile <votdev@gmx.de>
I can not tell you why. UDEV is used to identify the network interfaces, see https://github.com/openmediavault/openmediavault/blob/master/deb/openmediavault/usr/share/openmediavault/firstaid/modules.d/10configure_network.py#L57. |
It is finding it but it is returning a device_type of 'none'. Not sure how to fix that.
|
Could you execute
and the same for wlan0, docker0 and vethb514523. |
device = pyudev.Device.from_name(context, "net", "eth0") device = pyudev.Device.from_name(context, "net", "wlan0") device = pyudev.Device.from_name(context, "net", "docker0") device = pyudev.Device.from_name(context, "net", "vethb514523") |
Thx, but this will not produce the expected result, sorry. Please execute the following code:
|
====== eth0 ====== |
Any suggestion what we can use instead of the currently expected properties Example:
|
Maybe the |
It exists for the devices that should be used though. So, I would think that would work. |
…ation information. Signed-off-by: Volker Theile <votdev@gmx.de>
…ation information. Signed-off-by: Volker Theile <votdev@gmx.de> (cherry picked from commit 7a9c5b3)
Description of issue/question
omv-firstaid - configure network interface not working with RPI 4
Steps to reproduce issue
Versions report
newest OMV5.x
Error Message
ERROR: dialog-like terminated due to an error: the dialog-like program exited with status 3 (which was passed to it as the DIALOG_ERROR environment variable). Sometimes, the reason is simply that dialog was given a height or width parameter that is too big for the terminal in use. Its output, with leading and trailing whitespace stripped, was:
Error: Expected at least 5 tokens for --menu, have 4.
If you need more output, just tell me.
The text was updated successfully, but these errors were encountered: