[OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
If that file exists, read it and pass the content of the OPTIONS variable to netifd daemon. For instance, this would be a valid content for this file: OPTIONS=-r /tmp/resolv.XXX Signed-off-by: Jonh Wendell jonh.wend...@oiwifi.com.br --- package/network/config/netifd/files/etc/init.d/network |

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Felix Fietkau
On 2013-02-20 6:32 PM, Jonh Wendell wrote: If that file exists, read it and pass the content of the OPTIONS variable to netifd daemon. For instance, this would be a valid content for this file: OPTIONS=-r /tmp/resolv.XXX Signed-off-by: Jonh Wendell jonh.wend...@oiwifi.com.br Why do you

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Bastian Bittorf
* Jonh Wendell jonh.wend...@gmail.com [20.02.2013 18:41]: +[ -f $DEFAULT ] . $DEFAULT +service_start /sbin/netifd $OPTION this is not pretty, nifty and simple. (but must be!) use: [ -f $DEFAULT ] read OPTIONS $DEFAULT why should the user need to know your variable name. this passes

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
Because in my environment I need to pass some args to netifd (like -r). Right now, I'm patching /etc/init.d/network. The patch proposes a less intrusive solution. It's based on what other modules, like net-snmp do. 2013/2/20 Felix Fietkau n...@openwrt.org On 2013-02-20 6:32 PM, Jonh Wendell

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Felix Fietkau
What I meant was: why do you need to rename the resolv.conf file? - Felix On 2013-02-20 6:45 PM, Jonh Wendell wrote: Because in my environment I need to pass some args to netifd (like -r). Right now, I'm patching /etc/init.d/network. The patch proposes a less intrusive solution. It's based

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
2013/2/20 Felix Fietkau n...@openwrt.org What I meant was: why do you need to rename the resolv.conf file? Ahh. Because I don't want to use the dns servers dhcp gives to me. - Felix On 2013-02-20 6:45 PM, Jonh Wendell wrote: Because in my environment I need to pass some args to netifd

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jo-Philipp Wich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ahh. Because I don't want to use the dns servers dhcp gives to me. What about simply setting option peerdns 0 on the dhcp interface then? ~ Jow -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Thunderbird -

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
2013/2/20 Jo-Philipp Wich x...@subsignal.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ahh. Because I don't want to use the dns servers dhcp gives to me. What about simply setting option peerdns 0 on the dhcp interface then? hmmm, I hadn't seen this option. So, netifd reads that

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Felix Fietkau
On 2013-02-20 6:57 PM, Jonh Wendell wrote: 2013/2/20 Felix Fietkau n...@openwrt.org mailto:n...@openwrt.org What I meant was: why do you need to rename the resolv.conf file? Ahh. Because I don't want to use the dns servers dhcp gives to me. You don't need to modify anything scripts

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Jonh Wendell
2013/2/20 Felix Fietkau n...@openwrt.org On 2013-02-20 6:57 PM, Jonh Wendell wrote: 2013/2/20 Felix Fietkau n...@openwrt.org mailto:n...@openwrt.org What I meant was: why do you need to rename the resolv.conf file? Ahh. Because I don't want to use the dns servers dhcp gives to

Re: [OpenWrt-Devel] [PATCH] netifd: allow the use of /etc/default/netifd file

2013-02-20 Thread Felix Fietkau
On 2013-02-20 7:22 PM, Jonh Wendell wrote: 2013/2/20 Felix Fietkau n...@openwrt.org mailto:n...@openwrt.org On 2013-02-20 6:57 PM, Jonh Wendell wrote: 2013/2/20 Felix Fietkau n...@openwrt.org mailto:n...@openwrt.org mailto:n...@openwrt.org mailto:n...@openwrt.org