Ave people
A little update on this bug.
The machine which suffers from this bug runs testing, and recently
upgraded from dhcp3-client to isc-dhcp-client. Other packages were
also upgraded to recent versions.
Software now installed:
kernel : linux-image-2.6.32-5-amd64 (2.6.32-18)
samba : 2:3.4.8~dfsg-2
netbase : 4.42
ifupdown : 0.6.10
isc-dhcp-client : 4.1.1-P1-9
Still, the bug remains. As before, mostly samba only binds to
ipv6, sometimes it just works and binds to both ipv4/ipv6. A "service
restart samba" always returns with samba bound to both ipv4 and ipv6.
However, the next change in /etc/network/interfaces reliably fixes this
bug. Every boot samba now binds to both ipv4 and ipv6. (without the need
to restart samba after booting)
--- interfaces--orig 2010-08-12 22:36:34.000000000 +0200
+++ interfaces 2010-08-12 22:36:59.000000000 +0200
@@ -6,6 +6,6 @@ auto lo
iface lo inet loopback
-allow-hotplug eth0
+auto eth0
iface eth0 inet dhcp
Also, with this change in "/etc/network/interfaces" I see a change in
/var/log/boot. The diff between "allow-hotplug eth0" and "auto eth0"
(both when samba works straight out of a boot without restarting samba)
gives:
- Configuring network interfaces...done.
+ Configuring network interfaces...Internet Systems Consortium DHCP Client
4.1.1-P1
+ Copyright 2004-2010 Internet Systems Consortium.
+ All rights reserved.
+ For info, please visit https://www.isc.org/software/dhcp/
+
+ Listening on LPF/eth0/00:22:15:68:50:f0
+ Sending on LPF/eth0/00:22:15:68:50:f0
+ Sending on Socket/fallback
So it seems the root cause of this bug is that eth0 is not reliably
started. Reliably as in: both ipv4/ipv6 are full up and running.
Question:
Should this bug be reassigned to the "ifupdown" or "netbase" package?
Greetz
Martijn
-----------------------------------------
Ceterum censeo Carthaginem esse delendam
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
