Re: [leaf-devel] commands in /etc/networking/interfaces?

[davidMbrooke <le...@da...>]

On Tue, 2012-05-08 at 18:35 +0200, KP Kirchdoerfer wrote:
> Hi;
> 
> I see a problem with hostapd and ipv6 addresses.
> (To summarize: hostapd started from /etc/init.d/ destroys ipv6 addresses
> from managed interfaces - the bug has been reported in 2010 to hostapd,
> and is (also) described also here
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536630)
> 
> While this a known bug/problem, my main concern is that the workaround
> for a Debian-based system as found in Debian bug report above - "to not
> start hostapd from /etc/init.d and instead from interfaces after wlan0
> is up" does not work on LEAF Bering-uClibc (tested with 5-prealpha)
> 
> "auto wlan0
> iface wlan0 inet static
>     address xxx.xxx.xxx.xxx
>     netmask xxx.xxx.xxx.xxx
>     hostapd /etc/hostapd/hostapd.conf"
> 
> Note the last line! This does not work, even with using the full path to
> hostapd... It does work (avoid starting hostapd form init.d) when I
> start hostapd form the CLI.
> 
> It looks like the command in interfaces doesn't even run...?
> 
> Anyone who can confirm that running from /etc/networking/interfaces
> works at all?
> 
> kp

Hi kp,
Is that syntax for the workaround correct??? I haven't tested this on
5.x yet but on 4.x I use commands in /etc/network/interfaces all the
time - but they need to be prefixed with a keyword, typically "up".

For example, I use:
    auto eth1.16
    iface eth1.16 inet static
        vlan_raw_device eth1
        address 192.168.16.1
        netmask 255.255.255.0
        broadcast 192.168.16.255
        up ip addr add 192.168.16.11/24 brd 192.168.16.255 dev eth1.16
label eth1.16:0

Works fine! The text after the "up" can be any shell command, IIRC.

See http://wiki.debian.org/NetworkConfiguration for more details.

david