On 06/02/2012 06:53 PM, Felix Fietkau wrote:
>> - available=1 ???
> available=1 means that the interface can be brought up immediately
> instead of having to wait for an external trigger (usually only used
> together with no_device; if the interface is bound to a device, device
> presence controls
On 2012-05-31 9:56 AM, Roberto Riggio wrote:
> On 05/30/2012 04:09 PM, Felix Fietkau wrote:
>> Do you have any call to proto_init_update/proto_send_update in there,
>> similar to what the dhcp script does when it has acquired a lease?
>
> Hi, thanks for the feedback. I'm making some progresses now
On 05/30/2012 04:09 PM, Felix Fietkau wrote:
Do you have any call to proto_init_update/proto_send_update in there,
similar to what the dhcp script does when it has acquired a lease?
Hi, thanks for the feedback. I'm making some progresses now. This is the
current script:
#!/bin/sh
[ -n "$INC
On 2012-05-30 3:54 PM, Roberto Riggio wrote:
> On 05/30/2012 03:12 PM, Felix Fietkau wrote:
>> Please post the full script. What does 'ifstatus mesh' show?
>
> This is the skeleton of the script
>
> #!/bin/sh
>
> [ -n "$INCLUDE_ONLY" ] || {
> . /etc/functions.sh
> . ../netifd-p
On 05/30/2012 03:12 PM, Felix Fietkau wrote:
Please post the full script. What does 'ifstatus mesh' show?
This is the skeleton of the script
#!/bin/sh
[ -n "$INCLUDE_ONLY" ] || {
. /etc/functions.sh
. ../netifd-proto.sh
init_proto "$@"
}
proto_wing_init_config() {
On 2012-05-30 12:27 PM, Roberto Riggio wrote:
> Hi,
>
> I'm trying to adapt a package (wing, a routing protocol for WMN) to the
> new netifd infrastructure.
>
> I defined a new protocol by adding a new script in /lib/netfid/proto
> called wing.sh. The script (inspired by dhcp.sh) defines the fo
Hi,
I'm trying to adapt a package (wing, a routing protocol for WMN) to the
new netifd infrastructure.
I defined a new protocol by adding a new script in /lib/netfid/proto
called wing.sh. The script (inspired by dhcp.sh) defines the following
functions:
proto_wing_init_config()
proto_wing_
