Am 12.07.19 um 22:12 schrieb Bernd Nachtigall:
>
>
> Am 12.07.19 um 19:08 schrieb Knurpht-openSUSE:
>> Op vrijdag 12 juli 2019 19:03:48 CEST schreef Bernd Nachtigall:
>>> Am 12.07.19 um 17:53 schrieb Knurpht-openSUSE:
>>>> Op vrijdag 12 juli 2019 16:35:33 CEST schreef Bernd Nachtigall:
>>>>> After I install
>>>>> openSUSE-Leap-15.1-ARM-XFCE-raspberrypi3.aarch64-2019.05.17-Snapshot1.18.
>>>>> raw .xz to a RasPi I get a IP via DHCP during the first boot.
>>>>>
>>>>> Then I configure a fix IP via YaST. But this fix IP is configured as
>>>>> secondary IP. Even if I remove the interface configuration and renew it
>>>>> with the fix IP - after the YaST config runs throught, there are a
>>>>> interface with a primary addess from DHCP and a additional secondary IP
>>>>> from the fixed config.
>>>>>
>>>>> Where i can change this tricky behavior?
>>>>>
>>>>> Bernd
>>>>
>>>> Please show some confirmation:
>>>> ip addr
>>>
>>> mon:/etc/sysconfig/network # ip a s
>>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
>>> group default qlen 1000
>>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>>> inet 127.0.0.1/8 scope host lo
>>> valid_lft forever preferred_lft forever
>>> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
>>> state UP group default qlen 1000
>>> link/ether b8:27:eb:8d:5b:c2 brd ff:ff:ff:ff:ff:ff
>>> inet 192.168.250.181/25 brd 192.168.250.255 scope global
>>> noprefixroute dynamic eth0
>>> valid_lft 2816sec preferred_lft 2816sec
>>> inet 192.168.250.185/25 brd 192.168.250.255 scope global secondary
>>> noprefixroute eth0
>>> valid_lft forever preferred_lft forever
>>> inet6 fe80::c369:b4f2:7cdc:133c/64 scope link noprefixroute
>>> valid_lft forever preferred_lft forever
>>> 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
>>> state DOWN group default qlen 1000
>>> link/ether d2:f6:86:b8:bd:70 brd ff:ff:ff:ff:ff:ff
>>>
>>>
>>> With this config it is not possible to connect to the I-Net. When I
>>> delete .181 the connection is possible but after a while dhcp is rising
>>> again.
>>>
>>> Bernd
>> How do you configure it? Looks like you added a connection instead of editing
>> the existing one.
>>
>
> No, I configure the existing interface.
> From my POV it looks like an added IP for an existing interface. But
> there is only one address configured for this interface. When look in YaST.
>
> If I do an:
> # ip addr del 192.168.250.181/25 dev eth0
> The main addr of eth0 is removed, even as the secondary IP and the
> address 192.168.250.185 is set as the main addr of eth0.
>
> After a while somewhat reconfigure the network to the old state where
> the DHCP addr is set :-\
>
> Bernd
>
It seems that I found the trick.
Ootb the NetworkManager is active. But if you enter the YaST lan part
you did not get an hint as in openSUSE for x86_64. So two configs fight
each other.
I remove the NetworkManager (zypper rm -u Networkmanager) and now it get
only my configured address without an additional IP from DHCP.
Bernd
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
