[Bug 1120637] New: No controls for REMOTE_IPADDR= field in YaST2 VLAN settings
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637 Bug ID: 1120637 Summary: No controls for REMOTE_IPADDR= field in YaST2 VLAN settings Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: mikhail.kasimov@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Hello! 've a test VLAN0, created via YaST2 standard wizard interface. Result config: ===== k_mikhail@linux-mk500:~> cat /etc/sysconfig/network/ifcfg-vlan0 BOOTPROTO='static' BROADCAST='' ETHERDEVICE='eth0' ETHTOOL_OPTIONS='' IPADDR='192.168.70.222/24' MTU='' NAME='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' VLAN_ID='0' ====== The question is about REMOTE_IPADDR='' field: it is present in final config, but cannot be defined in YaST2 GUI. Steps-to-reproduce: 1. Open YaST2 via X11 or terminal. 2. Add a VLAN interface via YaST2. 3. Check 'cat /etc/sysconfig/network/ifcfg-vlan0' output after 2. is finished. Possible solution: 1. Have specific filed in YaST2 GUI for that to have possibility to add such address. 2. Keep REMOTE_IPADDR='' as is in case of leaving this field empty in YaST2 settings. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637#c3
Michal Filka
Possible solution:
1. Have specific filed in YaST2 GUI for that to have possibility to add such address. 2. Keep REMOTE_IPADDR='' as is in case of leaving this field empty in YaST2 settings.
yast2-network should already do so. I mean keep options which are not under its control untouched (In reply to Mikhail Kasimov from comment #2)
(In reply to Stefan Schubert from comment #1)
Yes, sounds reasonable. Could you please add an entry in: https://fate.suse.com/ in order to trigger the request ? Thank you !
Unfortunately, my login works for features.opensuse.org only, but not for fate.suse.com resource.
Is it OK to file request on features.opensuse.org or even on yast2 github?
feel free to open it as a feature request for OpenSUSE. Yast code is shared anyway. Please link this bug in the fate request. Thanks. I'm going to close the bug as it turned into feature request. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637#c4
--- Comment #4 from Mikhail Kasimov
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637
Mikhail Kasimov
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637
Mikhail Kasimov
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637#c5
Knut Alejandro Anderssen González
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637
http://bugzilla.opensuse.org/show_bug.cgi?id=1120637#c6
David Diaz
I will reopen it as fate.opensuse.org is not available anymore. So marked the bug as an enhancement, although we still need to study use cases.
Please, don't forget to also add a comment in the Github issue with the final decision. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com