Bug 1120637 - No controls for REMOTE_IPADDR= field in YaST2 VLAN settings
No controls for REMOTE_IPADDR= field in YaST2 VLAN settings
Status: CONFIRMED
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: YaST2
Leap 15.0
Other Other
: P5 - None : Enhancement (vote)
: ---
Assigned To: YaST Team
Jiri Srain
https://trello.com/c/ySe05gkj
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-01-03 13:15 UTC by Mikhail Kasimov
Modified: 2021-03-02 14:19 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Kasimov 2019-01-03 13:15:37 UTC
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.
Comment 1 Stefan Schubert 2019-01-04 09:11:57 UTC
Yes, sounds reasonable. Could you please add an entry in:
https://fate.suse.com/
in order to trigger the request ?
Thank you !
Comment 2 Mikhail Kasimov 2019-01-04 09:23:36 UTC
(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?
Comment 3 Michal Filka 2019-01-07 09:03:01 UTC
(In reply to Mikhail Kasimov from comment #0)
> 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.
Comment 4 Mikhail Kasimov 2019-01-09 07:49:44 UTC
Github: https://github.com/yast/yast-network/issues/716
Comment 5 Knut Alejandro Anderssen González 2020-02-04 09:49:59 UTC
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.
Comment 6 David Diaz 2020-02-07 07:52:57 UTC
(In reply to Knut Alejandro Anderssen González from comment #5)
> 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.