On Mon, Jun 1, 2020 at 9:39 PM Reuben Dowle wrote:
> When changing an interface MTU direct through ip command, netifd will get
> be out of sync. The netifd internally tracked MTU (discoverable through
> ubus call network.device status '{"name":"xxx"}' call will always show 1500
> (or whatever the
;
Https://www.4rf.com<https://www.4rf.com>
[cid:Family_53c410b1-7227-4a5f-9acb-f09bd7617a39.png]
<http://www.4rf.com/news/events>
From: openwrt-devel On Behalf Of
Michael Jones
Sent: Tuesday, 26 May 2020 5:21 am
To: Aleksander Morgado
Cc: openwrt-devel
On Mon, May 25, 2020 at 8:00 AM Aleksander Morgado
wrote:
> Other protocol handlers, like uqmi, are also able to setup the MTU,
> and instead of doing it via proto_send_update, they just do it like
> this:
>
> [ -n "$mtu" ] && {
> echo "Setting MTU to $mtu"
>
Hey,
> >> There's an ongoing discussion in the ModemManager package in github
> >> related to how the MTU may be configured in the network interface
> >> based on what the MM bearer object reports:
> >> https://github.com/openwrt/packages/issues/11383
> >>
> >> E.g.:
> >>
> >> $ ip route show
> >>
Hey,
>>
>> There's an ongoing discussion in the ModemManager package in github
>> related to how the MTU may be configured in the network interface
>> based on what the MM bearer object reports:
>> https://github.com/openwrt/packages/issues/11383
>>
>> E.g.:
>>
>> $ ip route show
>> default via 25
On Thu, May 21, 2020, 07:44 Aleksander Morgado
wrote:
> Hey!
>
> There's an ongoing discussion in the ModemManager package in github
> related to how the MTU may be configured in the network interface
> based on what the MM bearer object reports:
> https://github.com/openwrt/packages/issues/11383
Hey!
There's an ongoing discussion in the ModemManager package in github
related to how the MTU may be configured in the network interface
based on what the MM bearer object reports:
https://github.com/openwrt/packages/issues/11383
E.g.:
$ ip route show
default via 25.225.105.222 dev wwan0 proto
> -Original Message-
> From: Alin Năstac [mailto:alin.nas...@gmail.com]
> Sent: Mittwoch, 5. Februar 2020 14:43
> To: Adrian Schmutzler
> Cc: openwrt-devel
> Subject: Re: [OpenWrt-Devel] [netifd][PATCH] interface-ip: transfer prefix
> route
> ownership to
Original Message-
> > From: Alin Năstac [mailto:alin.nas...@gmail.com]
> > Sent: Mittwoch, 5. Februar 2020 14:38
> > To: Adrian Schmutzler
> > Cc: Hans Dedecker ; openwrt-devel > de...@lists.openwrt.org>
> > Subject: Re: [OpenWrt-Devel] [netifd][PATCH] interface-i
Hi,
please use a "v2" next time.
Best
Adrian
> -Original Message-
> From: Alin Năstac [mailto:alin.nas...@gmail.com]
> Sent: Mittwoch, 5. Februar 2020 14:38
> To: Adrian Schmutzler
> Cc: Hans Dedecker ; openwrt-devel de...@lists.openwrt.org>
> Subje
route.addr = addr.addr;
> > > > }
> > > >
> > > > + addr.flags |= DEVADDR_OFFLINK;
> > > > if (system_add_address(l3_downlink, &addr))
> > > > return;
> > >
From: Alin Nastac
When netifd manages the prefix route directly, it will remove it
the moment prefix gets deprecated. This will make it impossible
for the target to send ICMPv6 errors back to LAN devices still
using the deprecated prefix, thus breaking the L-14 requirement
of RFC 7084.
Signed-of
Behalf Of Alin Nastac
> Sent: Mittwoch, 5. Februar 2020 09:34
> To: Hans Dedecker
> Cc: openwrt-devel
> Subject: Re: [OpenWrt-Devel] [netifd][PATCH] interface-ip: transfer prefix
route
> ownership to kernel when IPv6 address becomes deprecated
>
> Hi Hans,
>
> On Tue, Feb
p;addr))
> > return;
> >
> > --
> > 2.7.4
> >
I've downloaded the patch from
https://patchwork.ozlabs.org/patch/1232885/ and applied it
successfully with a git am command line:
nastaca@cplx1037:/usr/localdisk/openwrt/netifd$ git am
~/Down
Hi Alin,
On Mon, Feb 3, 2020 at 4:27 PM Alin Nastac wrote:
>
> From: Alin Nastac
>
> When netifd manages the prefix route directly, it will remove it
> the moment prefix gets deprecated. This will make it impossible
> for the target to send ICMPv6 errors back to LAN devices still
> using the depr
From: Alin Nastac
When netifd manages the prefix route directly, it will remove it
the moment prefix gets deprecated. This will make it impossible
for the target to send ICMPv6 errors back to LAN devices still
using the deprecated prefix, thus breaking the L-14 requirement
of RFC 7084.
Signed-of
On Fri, Feb 22, 2019 at 9:17 AM Martin Tippmann wrote:
>
> Hi,
>
> I'm calling some iptables rules from a scripts in /etc/hotplug.d/iface
> and these failed because there seems to be no $DEVICE variable for
> ACTION=ifdown events.
>
> It's not really obvious that the device is not populated for if
Hi,
I'm calling some iptables rules from a scripts in /etc/hotplug.d/iface
and these failed because there seems to be no $DEVICE variable for
ACTION=ifdown events.
It's not really obvious that the device is not populated for ifdown
events, is there a reason for this? I guess the data about the de
Hello,
Docs are clear that when a route does not have the gateway field, it
will use the one from interface. However, it does not work like that.
When a route does not have a gateway, it is added as an onlink route.
I added a flag to differ between '0.0.0.0' and when gateway is absent.
The proble
Hi everyone,
I have a weird situation where proto_add_host_dependency() does not like IPv6
addresses. The WAN/WAN6 interface don't have global unicast addresses assigned,
but my protocol script calls
proto_add_host_dependency "${config}" "${ip}"
with $ip containing a global unicast address.
Hi Felix,
I noticed an inconsistency with following description on the Wiki page
for network config, section type 'route' (IPv4 Routes), option 'gateway' :
"Network gateway. If omitted, the gateway from the parent interface is
taken; if set to 0.0.0.0 no gateway will be specified for the route"
Felix,
I am trying to add wlan0 interface to bond interface but unable to add.
While digging further, I realized that below commit is not allowing me to
add.
http://git.openwrt.org/?p=project/netifd.git;a=commitdiff;h=8cb06c3efe734a52
1507cba7b5f0ba206e2476e0
I also noticed initial code was added
Felix,
I am trying to add wlan0 interface to bond interface but unable to add.
While digging further, I realized that below commit is not allowing me to
add.
http://git.openwrt.org/?p=project/netifd.git;a=commitdiff;h=8cb06c3efe734a52
1507cba7b5f0ba206e2476e0
I also noticed initial code wa
On Sun, 2016-05-15 at 20:50 +0800, Yousong Zhou wrote:
> > > I remember `proto_add_host_dependency` can be used to instruct
> > > netifd
> > > to setup such a route. But it looks like the relevant code for
> > > openconnect.sh is now commented out.
> > It was causing an infinite loop, and I could
On 15 May 2016 at 19:14, Nikos Mavrogiannopoulos
wrote:
> On Sat, 2016-05-14 at 18:29 +0800, Yousong Zhou wrote:
>> On 14 May 2016 at 16:18, Nikos Mavrogiannopoulos
>> wrote:
>> >
>> > Hi,
>> > A user of openconnect VPN is trying to use openconnect as a
>> > default
>> > route on his router [0].
On Sat, 2016-05-14 at 18:29 +0800, Yousong Zhou wrote:
> On 14 May 2016 at 16:18, Nikos Mavrogiannopoulos
> wrote:
> >
> > Hi,
> > A user of openconnect VPN is trying to use openconnect as a
> > default
> > route on his router [0]. Currently this works by setting
> > defaultroute=1
> > on his /e
On 14 May 2016 at 16:18, Nikos Mavrogiannopoulos
wrote:
> Hi,
> A user of openconnect VPN is trying to use openconnect as a default
> route on his router [0]. Currently this works by setting defaultroute=1
> on his /etc/config/network, however, once the default route is setup
> the VPN connection
Hi,
A user of openconnect VPN is trying to use openconnect as a default
route on his router [0]. Currently this works by setting defaultroute=1
on his /etc/config/network, however, once the default route is setup
the VPN connection drops because there is no direct route to the VPN
gateway.
Obviou
Hello,
I have a system where I want to reload a service when a monitor
interface appears. The monitor interface is configured in
/etc/config/wireless as:
config wifi-iface 'monitor'
option device 'radio0'
option ifname 'moni0'
option mode 'monitor'
Unfortunately netifd ev
* Daniel Dickinson [22.01.2016 07:55]:
> For a netifd protocol is there way to tell netifd to *not*
> automatically try to restart the connection?
we have samething similar for PPPoE.
option 'authfail' '1' # since r33291
check package/network/services/ppp/files/ppp.sh
bye, bastian
_
Hi Felix (or anyone else who knows netifd)
For a netifd protocol is there way to tell netifd to *not*
automatically try to restart the connection?
I'm asking for the case of VPN where if the password it wrong (e.g. due
to an stoken that expires before the connection completes), too many
rep
Hi,
upgrading to latest openwrt trunk broke PPPoE connectivity with fsl-gianfar
Ethernet driver for me.
Reason is the fsl-gianfar driver changed its behavior regarding link state
notifications:
linux 3.10:
[ 1471.142926] libphy: mdio@ffe24000:09 - Link is Up - 1000/Full
ip monitor:
15:43:53.02
Netifd (or the protocol defintions) add a prefix like "br-", "6in4-",
"pppoe-" etc. to names of interfaces with selected protocols and bridge
interfaces. Example: 6in4-tunnel interface "sixxs" gets created in the system
as "6in4-sixxs".
https://dev.openwrt.org/browser/trunk/package/network/ipv6
This patch can fix the issue that luci web shows '?' sign when WAN port work on
DHCP-client mode without
setting hostname. After adding the hostname check, the udhcpc can work with
'-H' parameter correctly and
send hostname to dhcp server.
Signed-off-by: tymon.huang
---
package/network/config/
Signed-off-by: tymon.huang
---
package/network/config/netifd/files/lib/netifd/proto/dhcp.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh
b/package/network/config/netifd/files/lib/netifd/proto/dhcp.sh
index 0e88af9..bf91c29 10075
This is mainly for protocols with no_proto_task set. L2TP with xl2tpd
is such a case and the issue this commit tries to address is that xl2tpd
could fail redialing the connection (segfault or abort) without the
notice of netifd causing the concerned interface being left down.
This patch solves it
Signed-off-by: Yousong Zhou
---
device.h|3 +++
interface.c |4 ++--
interface.h |1 +
ubus.c |2 +-
4 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/device.h b/device.h
index ce135ba..798e19e 100644
--- a/device.h
+++ b/device.h
@@ -160,8 +160,11 @@ struct
Hello,
I'd like to ask if I am right to conclude that the netifd does not
support multiple network {} entries in the wpa_supplicant conf file.
Using multiple network entries in the wpa_supplicant conf file would
be useful to configure the OpenWrt to auto associate to any visible
'network' on the
Hi Lars,
I struggled with this issue as well and after a brief chat with nbd the
conclusion was to force the tap device to be "external", this will cause
netifd to leave its routes and address config alone, even when ifup is
called on the network.
In short you need to prepare the vpn interface
Hi,
currently I am struggling with the management of dynamically created network
interfaces.
Specifically I want to create an openvpn connection to a server and add the
automatically generated network interface (tapX; managed by openvpn) to a
specific zone.
I planned to use the following commands
Hello All,
As I roughly outlined before in another thread ("synchronous network
reload/restart"), I am trying to re-configure several dependent network
interfaces thru ubus/netifd on BB.
I have one physical wireless device and 3 virtual interfaces:
- moni (moni0)
- mesh (mesh0)
- ap (ap0)
On
On Fri, Jan 9, 2015 at 12:25 PM, Steven Barth wrote:
> Our dnsmasq init script registers /tmp/dnsmasq.d as an additional
> configuration dir, so you can place files there and restart it. However I'm
> not sure as to how much we want netifd to do dnsmasq-specific stuff or how
> we would do it.
Wel
Our dnsmasq init script registers /tmp/dnsmasq.d as an additional
configuration dir, so you can place files there and restart it. However
I'm not sure as to how much we want netifd to do dnsmasq-specific stuff
or how we would do it.
Of course the bad thing here again is that dnsmasq doesn't su
On Fri, Jan 9, 2015 at 9:48 AM, Hans Dedecker wrote:
> On Thu, Jan 8, 2015 at 5:43 PM, Nikos Mavrogiannopoulos
> wrote:
>> Currently a protocol can register a dns server with netifd using the
>> proto_add_dns_server function. That however, does not allow
>> registering a DNS server for a specific
On Thu, Jan 8, 2015 at 5:43 PM, Nikos Mavrogiannopoulos
wrote:
> Currently a protocol can register a dns server with netifd using the
> proto_add_dns_server function. That however, does not allow
> registering a DNS server for a specific domain. I checked the netifd
> code and there is no provisio
Currently a protocol can register a dns server with netifd using the
proto_add_dns_server function. That however, does not allow
registering a DNS server for a specific domain. I checked the netifd
code and there is no provision for that. Would it make sense to add
such functionality to netifd, or
I got wrong country set and couldn't use channels 12/13. So I set:
wireless.radio1.country=pl
however calling
/etc/init.d/network reload
didn't do anything. It seems netifd doesn't notice country change.
--
Rafał
___
openwrt-devel mailing list
openwrt-d
On Thu, Jul 17, 2014 at 06:28:09PM +0200, Hans Dedecker wrote:
> Hi Baptiste,
>
> I have added GRE support (gre/gretap/grev6/grev6tap) in netifd which I'm
> currenlty testing. The implementation looks the same as for 6rd/dslite tunnel
> interfaces (thus allowing to set mtu/ttl/remote end point);
Hi Baptiste,
I have added GRE support (gre/gretap/grev6/grev6tap) in netifd which I'm
currenlty testing. The implementation looks the same as for 6rd/dslite tunnel
interfaces (thus allowing to set mtu/ttl/remote end point); additonally it
allows to set gre specific parameters (ikey/okey/iseq/os
Hi,
I am currently adding GRE support for OpenWRT, based on 6in4 support [1]
(since I couldn't find any documentation).
What is the proper way to support address configuration for tunnel
interfaces? It seems redundant to handle static address configuration for
each tunnel type, especially with t
Greeting,
I found /sbin/ifup does not take new network config, through it does reload
before bringing interface up.
ifup orders netifd reload config via ubus call. But netifd uses an async event
loop to do reloading work:
void netifd_reload(void)
{
main_timer.cb = netifd_do_reload;
On 2014-03-27 20:57, James Wood wrote:
> Hi Felix
>
>
>
> We’re recently come up against a problem whereby when you switch
> protocol to 3G/PPPoE, and then switch back to DHCP on the WAN interface,
> netifd is failing to bring up the WAN interface.
Should be fixed in r40384, thanks for reportin
Hi Felix
We're recently come up against a problem whereby when you switch protocol to
3G/PPPoE, and then switch back to DHCP on the WAN interface, netifd is
failing to bring up the WAN interface.
I've tracked it down to a line inside /lib/netifd/dhcp.script:
proto_init_update "*" 1
Hello,
I have spent some days debugging an issue I am frequently seeing with
netifd and ppp modems. When connecting the modem after having
connected and disconnected it once, i.e., the second time netifd
"sees" the modem, netifd frequently thows a sigsev.
After going through the code, adding prin
Hello,
I am trying to get Tayga working with netifd. I have used OpenWRT for a
while now, but this is my first development effort.
I, personally, think that is have come quiet far. I discovered the proto
scripts and created one myself. I even got Tayga running with the script
and its settings, but
On 2013-10-29 13:31, Gui Iribarren wrote:
> I'm trying to get a macvlan interface brought up by netifd
> on last week openwrt trunk
> BARRIER BREAKER (Bleeding Edge, r38505)
> with netifd - 2013-10-19-566af724dad393fa127e07469dcc9ade62bd3a75
>
> and i'm probably missing something very silly, but i
On 10/29/2013 01:31 PM, Gui Iribarren wrote:
I'm trying to get a macvlan interface brought up by netifd
on last week openwrt trunk
BARRIER BREAKER (Bleeding Edge, r38505)
with netifd - 2013-10-19-566af724dad393fa127e07469dcc9ade62bd3a75
and i'm probably missing something very silly, but i'm not
I'm trying to get a macvlan interface brought up by netifd
on last week openwrt trunk
BARRIER BREAKER (Bleeding Edge, r38505)
with netifd - 2013-10-19-566af724dad393fa127e07469dcc9ade62bd3a75
and i'm probably missing something very silly, but i'm not getting any
reaction or error whatsoever. The
On 2013-09-15 10:23 PM, Bastian Bittorf wrote:
> * Felix Fietkau [15.09.2013 21:59]:
>> > maybe i misunderstand uci - IMHO the question is:
>> > how can i name an anonymous section?
>> From the command line help:
>> rename .[.]=
>
> 8-) ok, i could believe it - so one can NOT name a sect
* Felix Fietkau [15.09.2013 21:59]:
> > maybe i misunderstand uci - IMHO the question is:
> > how can i name an anonymous section?
> From the command line help:
> rename .[.]=
8-) ok, i could believe it - so one can NOT name a section,
but must generate an unamed/anonymous section and a
On 2013-09-15 7:55 PM, Bastian Bittorf wrote:
> * Felix Fietkau [15.09.2013 19:50]:
>> > which commands should i use for naming the alias section? i tried e.g.
>> >
>> > uci set network.@alias[-1].name=test
>> >
>> > can you please write down the commands in the right order?
>> If you run uci w
* Felix Fietkau [15.09.2013 19:50]:
> > which commands should i use for naming the alias section? i tried e.g.
> >
> > uci set network.@alias[-1].name=test
> >
> > can you please write down the commands in the right order?
> If you run uci without arguments, it'll print a command line help :)
On 2013-09-15 2:35 PM, Bastian Bittorf wrote:
> * Felix Fietkau [15.09.2013 13:54]:
>> > uci add network alias
>> > uci set network.@alias[-1].interface="lan"
>> > uci set network.@alias[-1].bla=...
>> >
>> > uci add network route
>> > uci set network.@route[-1].interface=cfg164d8f
>> > uci set n
* Felix Fietkau [15.09.2013 13:54]:
> > uci add network alias
> > uci set network.@alias[-1].interface="lan"
> > uci set network.@alias[-1].bla=...
> >
> > uci add network route
> > uci set network.@route[-1].interface=cfg164d8f
> > uci set network.@route[-1].bla=...
> Bad idea. The cfg164d8f na
On 2013-09-15 1:25 PM, Bastian Bittorf wrote:
> * Felix Fietkau [15.09.2013 12:52]:
>> I probably should have written instead of alias. The alias
>> section needs a name (it's considered an interface by netifd), and the
>> route 'interface' option needs to point at that alias section name.
>
> t
* Felix Fietkau [15.09.2013 12:52]:
> I probably should have written instead of alias. The alias
> section needs a name (it's considered an interface by netifd), and the
> route 'interface' option needs to point at that alias section name.
thank you. it works like this:
uci add network alias
uc
On 2013-09-15 12:16 PM, Bastian Bittorf wrote:
> * Felix Fietkau [15.09.2013 11:58]:
>> Try network.myroute.interface=alias
>
> uci changes looks now like this:
>
> network.cfg114d8f=alias
> network.cfg114d8f.interface=lan
> network.cfg114d8f.proto=static
> network.cfg114d8f.ipaddr=192.168.10.2
* Felix Fietkau [15.09.2013 11:58]:
> Try network.myroute.interface=alias
uci changes looks now like this:
network.cfg114d8f=alias
network.cfg114d8f.interface=lan
network.cfg114d8f.proto=static
network.cfg114d8f.ipaddr=192.168.10.2
network.cfg114d8f.netmask=255.255.255.0
network.cfg12c8b4=route
On 2013-09-15 10:20 AM, Bastian Bittorf wrote:
> when setting an alias network via
>
> network.@alias[0]=alias
> network.@alias[0].interface=lan
> network.@alias[0].proto=static
> network.@alias[0].ipaddr=192.168.10.2
> network.@alias[0].netmask=255.255.255.0
>
> and adding a route 'myroute' on t
when setting an alias network via
network.@alias[0]=alias
network.@alias[0].interface=lan
network.@alias[0].proto=static
network.@alias[0].ipaddr=192.168.10.2
network.@alias[0].netmask=255.255.255.0
and adding a route 'myroute' on top of this,
the route will not be established on bootup
network.
On 2013-05-22 3:57 AM, Ken Bantoft (SI) wrote:
>
> * Note: Posted on the forum, but no replies after a few days so asking
> here *
>
>
> I'm in the process of adding support for ISDN data (via capi), and have a
> question about netifd.
>
> Since it's ppp over CAPI, all the lower level stuff wor
Thanks Jow... That seemed to do the trick! Now just need to sort out why
pppd works fine from CLI (pppd call ... &) but complains "/usr/sbin/pppd:
no device specified and stdin is not a tty" but won't take /dev/null as a
parameter either.
Ken
On 13-05-22 7:54 AM, "Jo-Philipp Wich" wrote:
>
Hi,
did you set "available=1" and "no_device=1" in the
proto_pppoi_init_config() procedure?
Take a look how pptp is instantiated, that one is a device-less protocol
as well.
~ Jow
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://l
* Note: Posted on the forum, but no replies after a few days so asking
here *
I'm in the process of adding support for ISDN data (via capi), and have a
question about netifd.
Since it's ppp over CAPI, all the lower level stuff works fine (I can call
pppd from CLI and it connects nicely) however
Hi Kristian,
at first: thanks for your feedback. I really like the general idea of
this patch, however:
1) Instead of using the interface index to decide on interface metric, a
table-option is added to interfaces. This way, users are sure which tables will
be used for policy routing and can
On 07/08/12 08:50, Tathagata Das wrote:
> Hi,
> First of all thanks all who designed netifd and ubus.
>
> I would like to use netifd in my OpenWRT based router. So I am looking into
> the source code of netifd and ubus. But I didn't find much information about
> ubus. Is there any documents on
Hi,
First of all thanks all who designed netifd and ubus.
I would like to use netifd in my OpenWRT based router. So I am looking into the
source code of netifd and ubus. But I didn't find much information about ubus.
Is there any documents on how they interact ?
I heard that Luci uses netifd fo
On 2012-06-24 3:07 PM, Daniel Golle wrote:
> Hi Felix,
>
> On 24/06/12 15:47, Felix Fietkau wrote:
>> Support for that is already part of netifd in a proto-independent way.
>
>> There is already the 'defaultroute' option (defaults to 1). Set that to
>> 0 and netifd will not apply udhcpc's default
Hi Felix,
On 24/06/12 15:47, Felix Fietkau wrote:
> Support for that is already part of netifd in a proto-independent way.
> There is already the 'defaultroute' option (defaults to 1). Set that to
> 0 and netifd will not apply udhcpc's default route.
I'm aware us this option and tried using it, s
On 2012-06-24 3:18 AM, Daniel Golle wrote:
> Hi!
>
> From what I can see, the udhcpc script currently doesn't support any way to
> not
> set or override the default-gateway.
Support for that is already part of netifd in a proto-independent way.
> In some cases (here: I connect to an non-routed i
Hi!
>From what I can see, the udhcpc script currently doesn't support any way to not
set or override the default-gateway.
In some cases (here: I connect to an non-routed infrastructure using DHCP, then
use PPP-over-L2TP on top of it to get to the Internet) this would be feasible.
The scenario loo
On 2011-11-01 10:49 PM, Jonathan Bennett wrote:
Just for kicks, I decided to compile bleeding edge trunk and try out
the new netifd system. I attempted to connect to my cable modem via
dhcp, and this error showed up in the log:
Sep 8 15:44:59 OpenWrt daemon.notice netifd: wan (1223): ./dhcp.sh:
Just for kicks, I decided to compile bleeding edge trunk and try out
the new netifd system. I attempted to connect to my cable modem via
dhcp, and this error showed up in the log:
Sep 8 15:44:59 OpenWrt daemon.notice netifd: wan (1223): ./dhcp.sh:
eval: line 1: proto_dhcp_setup: not found
After a
On 2011-10-22 1:30 AM, Hanno Schupp wrote:
Thank you for the fast response.
For sake of clarification: When you mention 'network configuration scripts'
are you talking about scripts like the old brcm-2.4 init.d netconfig script
and things like target profile specific network configuration defaul
ubject: Re: [OpenWrt-Devel] Netifd and ubus in trunk - Please provide some
details
On 2011-10-22 12:59 AM, Hanno Schupp wrote:
> Hi Felix,
>
> What is this netifd and ubus business appearing in trunk? What is it
> implementing or replacing? Will it affect all platforms and be
> in
On 2011-10-22 12:59 AM, Hanno Schupp wrote:
Hi Felix,
What is this netifd and ubus business appearing in trunk? What is it
implementing or replacing? Will it affect all platforms and be included
firmware images by default or does it have to be specifically compiled
into an image? How can we help
Hi Felix,
What is this netifd and ubus business appearing in trunk? What is it
implementing or replacing? Will it affect all platforms and be included
firmware images by default or does it have to be specifically compiled into an
image? How can we help you testing this new package, what should
87 matches
Mail list logo
