[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [PATCH] ifup: ifdown for network interface with mapped configuration
From:       Richard Genoud <richard.genoud () gmail ! com>
Date:       2013-04-25 10:38:44
Message-ID: CACQ1gAiqsyrS7ugqVXJXxU6q5OXzHQu_qzCTGJD6L86YOGQb4Q () mail ! gmail ! com
[Download RAW message or body]

2012/11/25 Matthias Loy <matthias.loy@hbm.com>:
> Hello,
>
> we are using ifup from busy box in our embedded devices. In order to
> reconfigure network interfaces we call ifdown, change the configuration
> files and call ifup again. We found that ifdown does not work on mapped
> configurations like eth1-dhcp or dhcp-manual. ifup is working fine.
>
> Attached you find a small patch solving our problem. Is this ok for you?
>
> regards,
> Matthias Loy

I agree with you.

IMHO,
ifdown -a
should bring down the interfaces that
ifup -a
has brought up.

With mappings, that's not the case.

Without your patch, we must do something like :
for i in `cat /var/run/ifstate` ; do ifdown $i ; done

Could this patch be included ?

Richard.
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]