Package: ifupdown
Version: 0.7.53.1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Missing expected behavior in an external RasPi deployment.
* What exactly did you do (or not do) that was effective (or
ineffective)?
In order to understand the misbehavior of the deployed RasPi, I tried
to simulate the circumstances locally with an identical system. This
revealed a rather grave glitch, either in configuration, or the ifupdown
package itself.
consider this setup:
$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 10.10.10.222
netmask 255.255.255.0
gateway 10.10.10.1
I would expect, that eth0 would keep this static configuration.
When I start the RasPi with an plugged ethernet cable, the interface
is brought up correctly: it has set up the given static configuration.
When I unplug the cable, wait a bit, and replug it again, it takes a
couple of _minutes_ (~200sec), before eth0 gets an ip address again.
But this address is configured by dhcp now! Something similar happens,
when starting the RasPi unplugged, and plugging the cable later on.
It is ignoring the static configuration:
eth0 Link encap:Ethernet HWaddr b8:27:eb:f6:c2:ea
inet addr:172.16.26.138 Bcast:172.16.26.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:ebff:fef6:c2ea/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:86158 errors:0 dropped:0 overruns:0 frame:0
TX packets:17646 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:42621928 (40.6 MiB) TX bytes:1892035 (1.8 MiB)
Yes, this is the expected outcome from having:
iface eth0 inet dhcp
instead of:
iface eth0 inet static
...
in /etc/network/interfaces, which I'm using alternatively for local network
access. Question is, what causes this system to not use the given static
configuration?
The RasPi was formerly a rather plain Debian Wheezy system, that I upgraded
to Jessie because of a few missing packages, running in console mode (or
rather headless except for diagnostics).
No extra repos, no twiddling in the basic setup. All configuration changes
in the upgrade were taken from maintainer defaults.
As long as this static config is in place, I would expect it to use it
(given, an ethernet cable is plugged).
Any idea, what's going wrong here?
If this is not a PBKAC issue, and it doesn't appear as one to me, I would
rate it rather grave, but bugreport asked some strange questions, so it's
your call.
Oh, bugreport crashed for me in an attempt to send it - luckily I copied the
text in the clipboard before quitting vim. Oh well.
Thanks in advance,
Pete
-- System Information:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
Architecture: armv6l
Kernel: Linux 4.1.13+ (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ifupdown depends on:
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-59
ii iproute 1:3.16.0-2
ii iproute2 3.16.0-2
ii libc6 2.19-18+deb8u1
ii lsb-base 4.1+Debian13+rpi1+nmu1
Versions of packages ifupdown recommends:
ii isc-dhcp-client [dhcp-client] 4.3.1-6
Versions of packages ifupdown suggests:
ii net-tools 1.60-26
pn ppp <none>
pn rdnssd <none>
-- no debconf information
