static IP is changed via DHCP :-O

English Network/Internet
1

I’ve updated a x86_64 system from 12.2 to 13.1 using DVD media.
The update has gone more or less okay (some issues like apache2 errors because of some changes in configuration files).
But the most annoying error is that I loose connection.
I’ve researching and I’ve found that my network card looses it’s IP.
The card is configured with static IP 192.168.2.2 and IPV6 is disabled, but when conectivity is lost I got this:


tutatis:~ # ifconfig -a
enp3s6    Link encap:Ethernet  HWaddr 00:A0:0C:C7:7E:C7  
          inet6 addr: fe80::2a0:cff:fec7:7ec7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2722 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2039 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3448174 (3.2 Mb)  TX bytes:231063 (225.6 Kb)
          Interrupt:20 Base address:0x6000 

enp3s6:av Link encap:Ethernet  HWaddr 00:A0:0C:C7:7E:C7  
          inet addr:169.254.9.233  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:20 Base address:0x6000 

eth0      Link encap:Ethernet  HWaddr 1C:6F:65:AA:FE:47  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:33232 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24178 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:43258789 (41.2 Mb)  TX bytes:6800857 (6.4 Mb)

the card is enp3s6, it’s a PCI ethernet 100 card.
I’ve other card: eth0 wich is the mobo 1gpbs card
I’ve tried to configure eth0 (even removing the pci card) with the same results

As you can see a second “card” appears: enp3s6:av with a IP I’ve not configured: 169.254.9.233

If I restart the network, this second card dissapear and all begin to work fine:


tutatis:~ # /etc/init.d/network restart
redirecting to "systemctl  restart network.service"
tutatis:~ # ifconfig -a
enp3s6    Link encap:Ethernet  HWaddr 00:A0:0C:C7:7E:C7  
          inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::2a0:cff:fec7:7ec7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2854 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2142 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3585340 (3.4 Mb)  TX bytes:241625 (235.9 Kb)
          Interrupt:20 Base address:0x6000 

eth0      Link encap:Ethernet  HWaddr 1C:6F:65:AA:FE:47  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:33232 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24178 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:43258789 (41.2 Mb)  TX bytes:6800857 (6.4 Mb)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3401 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3401 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1604426 (1.5 Mb)  TX bytes:1604426 (1.5 Mb)

But it only last some minutes.

Any help?

regards

2

On 2014-09-04 20:16, fperal wrote:
>
> I’ve updated a x86_64 system from 12.2 to 13.1 using DVD media.
> The update has gone more or less okay (some issues like apache2 errors
> because of some changes in configuration files).
> But the most annoying error is that I loose connection.
> I’ve researching and I’ve found that my network card looses it’s IP.
> The card is configured with static IP 192.168.2.2 and IPV6 is
> disabled, but when conectivity is lost I got this:

I guess that you have to remove the configuration and then add it again,
from scratch. See the release notes.

Some extra notes re upgrade via dvd, from my notes:

Upgrading the DVD upgrade

The typical problem is that the DVD can not upgrade what is not included
in the DVD itself. The cure is to run, after the offline upgrade, a
modified online upgrade:


zypper dup
zypper up
zypper patch

Make sure you only have the 4 official repos active before running that
(an exception could be nvidia/ati repo, if it was used previously).
Then, verify:

Upgrading rpm query


rpm -q -a --queryformat "%{INSTALLTIME};%{INSTALLTIME:day}; \
%{BUILDTIME:day}; %{NAME};%{VERSION}-%-7{RELEASE};%{arch}; \
%{VENDOR};%{PACKAGER};%{DISTRIBUTION};%{DISTTAG}
" \
| sort | cut --fields="2-" --delimiter=\; \
| tee rpmlist.csv | less -S

or

rpm -q -a --queryformat "%{INSTALLTIME}	%{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME}	%15{VERSION}-%-7{RELEASE}	%{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" | tee rpmlist | less -S

or


rpm -q -a --queryformat "%{INSTALLTIME}	%{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME}	%15{VERSION}-%-7{RELEASE}	%{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" | tee rpmlist \
| egrep -v "openSUSE.13\.1" | less -S

(not containing 13.1)

With that query, you find listed at the top old packages that may have
to be upgraded manually, because they belong to the previous release, or
perhaps came from extra repositories and no equivalent was found in the
active repos. In that case you have to start at this phase to add the
needed extra repositories and update those packages.

Many of them show in red in YaST,

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

3

And also check that NetworkManager.service is disabled.

IIRC 12.2 had that service unconditonally enabled, and a config variable NETWORKMANAGER (or similar) decided whether it should actually start or not.
That variable got dropped in 12.3 and since then only one of the two network services should be enabled. But something may have gone wrong with that migration, and you maybe ended up with both being active (and NetworkManager starting the DHCP client).

So run:

systemctl status NetworkManager

and run this when it says enabled:

sudo systemctl disable NetworkManager

Or use YaST->System->Services Manager to check the status and possibly disable it.

If in doubt, please post the output.

And the status of network.service might be helpful as well:

systemctl status network.service

Switching at least once between ifup and NetworkManager in YaST->Network Devices->Network Settings should also fix it, if that is indeed the case.

4

Network manager was active and although I tell yast configuration to configure the card with ifup, network manager was changing it.
Once disabled network manager all works.

regards

5

On Thu, 04 Sep 2014 18:16:01 +0000, fperal wrote:

> As you can see a second “card” appears: enp3s6:av with a IP I’ve not
> configured: 169.254.9.233

That’s not a DHCP-issued address - it’s an address that’s issued
automatically when DHCP isn’t available. The address range is referred
to as the “link-local” address block.

It’s probably showing up because something’s configuring that virtual
interface and you don’t have a DHCP server.

OI would be inclined to figure out what’s causing the connection to be
lost - output from dmesg might help determine that.

Jim

Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

6

Glad to hear that the problem has problem seems to be resolved (disabling network manager).

Wrapping up a few loose ends…

  • Don’t avoid Carlos’ recommendation to do a “zypper dup” - There are probably plenty of internal consistencies in your upgrade that should be resolved before they appear as actual problems.
  • You should inspect your existing DHCP’s IP address range and then configure your static address outside that range. I would guess that “192.168.2.2” could be within your DHCP’s range so some machine will be allocated that address some time.

TSU

7

I did, but first I had to solve the IP problem because The IP was disappearing so quickly I could not do a zypper dup before.

  • You should inspect your existing DHCP’s IP address range and then configure your static address outside that range. I would guess that “192.168.2.2” could be within your DHCP’s range so some machine will be allocated that address some time.

TSU

No that’s okay I’ve my network configured with static IPs in the lower range.

regards

8

On 2014-09-07 20:46, fperal wrote:
>
> tsu2;2663157 Wrote:

>> Wrapping up a few loose ends…
>> - Don’t avoid Carlos’ recommendation to do a “zypper dup” - There are
>> probably plenty of internal consistencies in your upgrade that should be
>> resolved before they appear as actual problems.
>
> I did, but first I had to solve the IP problem because The IP was
> disappearing so quickly I could not do a zypper dup before.

I thought so…

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)