Package: ifupdown
Version: 0.7.49
Followup-For: Bug #709378
This bug is still present in ifupdown 0.7.49.
Note that this makes it impossible to use the pre-up command in the interfaces
file.
This can have puzzling and annoying consequences for anyone who planned to use
that to set up the firewa
Hello,
On 24 May 2013 14:07, Matthew Foulkes wrote:
>> root@bee:~# ifup -v lo
>> ip link set up dev lo 2>/dev/null
>> Configuring interface lo=lo (inet)
>> run-parts --verbose /etc/network/if-pre-up.d
>> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
>> run-parts --verbose /etc/netwo
Hi Andrew,
On Wed, May 22, 2013 at 11:21:51PM +0200, Andrew Shadura wrote:
> Hello,
>
> On Wed, 22 May 2013 22:13:21 +0100
> Matthew Foulkes wrote:
>
> > Since ifupdown 0.7.43 entered testing, I have noticed "ifup -v lo" and
> > "ifdown -v lo" attempting to bring the loopback interface up/down
Hello,
On Wed, 22 May 2013 22:13:21 +0100
Matthew Foulkes wrote:
> Since ifupdown 0.7.43 entered testing, I have noticed "ifup -v lo" and
> "ifdown -v lo" attempting to bring the loopback interface up/down
> twice.
Please elaborate that. I have specifically changed the internal
definition of th
Package: ifupdown
Version: 0.7.43
Severity: normal
Dear Maintainer,
Since ifupdown 0.7.43 entered testing, I have noticed "ifup -v lo" and
"ifdown -v lo" attempting to bring the loopback interface up/down twice.
I guess this is because ifup/ifdown now predefine lo internally as an
auto interface
5 matches
Mail list logo
