Bug#682608: /etc/network/interfaces permissions
chuck adams <chuck.adams.k7qo@gmail.com> writes:
> Here is a working system, i.e. WiFi interface working,
> and /etc/network/interfaces permissions
>
> adams@debian:~$ ls -l /etc/network/interfaces
> -rw-r--r-- 1 root root 293 Jun 13 22:26 /etc/network/interfaces
>
> and contents of file are:
>
> --------------------------------------------------cut here
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth0
> #NetworkManager#iface eth0 inet dhcp
> --------------------------------------------------cut here
>
> The issue is with the contents of the file as shown in previous
> email with the ssid and password in the file. I believe the
> 644 or even the 600 is just fine. It is that the current
> d-i or netinst is placing the wrong info into the interfaces
> file.
>
I don't think the information in /etc/network/interface is wrong. I'm
only guessing that you come to this conclusion because the
network-manager applet does not show the connection. What actually
happens is this:
- netcfg currently only knows about /e/n/i and nothing about
network-manager. It just writes the configuration to /e/n/i.
- when finishing up the installation (right before the reboot) a script
is run which disables all interfaces that have the form "iface ifX
inet dhcp" without any additional configuration iff network-manager is
installed. All other interface definitions are untouched. That's why
your wireless interface is not disabled and shows up as "unmanaged" in
network-manager. Network-manager sees that this is confgured by
ifupdown and does not touch the interface.
- the wireless interface actually works as expected as long as you stay
in range of your wireless network.
- evolution and other programs using network-manager for network
detection wrongly think that there is no network connection.
There is nothing inherently wrong with this. It's probably just not the
configuration most (novice) users would expect. That's why we are
currently reworking this part to make it more user friendly.
> By any chance, is the netinst program written in C? I can
> help if it is. I just need pointers to the code and let
> me work on it, if you need the help. I have taught every
> course there is in CS when I was a tenured prof at the
> University of North Texas and I was lead instructor and
> course developer at sgi at one time.
Yes it's one of the few d-i components written in C. The git repository
for debian-installer can be found on git.debian.org. But beware it's not
the most beautiful piece of C code ever ;-) Also the functionality in
question should go to a finish-install script which is in shell.
The (unfinished) version fixing this can be found in
git://git.debian.org/git/d-i/netcfg, branch write_config.
Help also with other parts of netcfg would be appreciated. See the list
of open bugs at http://bugs.debian.org/netcfg :-) Two of the more
interesting open issues are IPv6 support and tagged VLAN support.
Gaudenz
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~
Reply to: