No subject

function. From "proto_send_update" function we are calling "_proto_notify"
which intern calls below ubus call.

ubus -S call network.interface notify_proto { "action": 6, "host":
"192.168.11.5", "ifname": "wan1", "interface": "gre1" }:
Jan  5 10:50:46 RV340 netif: SRI:ubus  call network.interface notify_proto
{ "action": 0, "ifname": "gre-gre1", "link_up": true, "tunnel": { "mode":
"greip", "mtu": 1280, "df": true, "ttl": 64, "local": "172.31.3.8",
"remote": "192.168.11.5", "link": "wan1", "info": "0,0,0,0,0,0" }, "data":
{ "zone": "tunnel" }, "keep": false, "interface": "gre1" }

But above command is returning with "Invalid argument error". This error is
being thrown from netifd from function "proto_shell_update_link". In this
function "if (!tb[NOTIFY_LINK_UP])" statement becomes true and
"UBUS_STATUS_INVALID_ARGUMENT" is being returned.

I tried to understand the "tb" structure, but could not understand the json
to "json_object" conversion. Could you please help how to debug this
further.

I think, I am missing some thing in config (as u suggest in previous mail)
and debugging from the code to find it out. I tried multiple examples
available over net, but nothing worked out for me. Can you please review my
config once again.

Thanks for your help.

Regards,
Sridhar

On Thu, Nov 19, 2015 at 7:06 PM, Steven Barth <cyrus at openwrt.org> wrote:

> You are most likely missing a route to the remote tunnel endpoint
> (192.168.11.5).
> The system doesn't know which interface and next hop to send the tunneled
> packets to, thats why its blocking the tunnel bringup.
>
>
> Cheers,
>
> Steven
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>

--001a11c1295ea307320524f39711
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi Steven,<br><br></div><div>Thank you so much f=
or your valuable info. I have missed this route and struggled more than a w=
eek. Very grateful for your suggestion.<br></div><div>With the added route =
I am able to proceed further. But still stuck in below point.<br><br></div>=
<div>From gre.sh, we are calling "proto_send_update" in the inter=
face setup function. From "proto_send_update" function we are cal=
ling "_proto_notify" which intern calls below ubus call.<br><br>u=
bus -S call network.interface notify_proto { "action": 6, "h=
ost": "192.168.11.5", "ifname": "wan1", =
"interface": "gre1" }:<br>Jan=C2=A0 5 10:50:46 RV340 ne=
tif: SRI:ubus=C2=A0 call network.interface notify_proto { "action&quot=
;: 0, "ifname": "gre-gre1", "link_up": true, =
"tunnel": { "mode": "greip", "mtu":=
 1280, "df": true, "ttl": 64, "local": "=
172.31.3.8", "remote": "192.168.11.5", "link&=
quot;: "wan1", "info": "0,0,0,0,0,0" }, &quot=
;data": { "zone": "tunnel" }, "keep": fa=
lse, "interface": "gre1" }<br><br></div><div>But above =
command is returning with "Invalid argument error". This error is=
 being thrown from netifd from function "proto_shell_update_link"=
. In this function "if (!tb[NOTIFY_LINK_UP])" statement becomes t=
rue and "UBUS_STATUS_INVALID_ARGUMENT" is being returned.<br><br>=
</div><div>I tried to understand the "tb" structure, but could no=
t understand the json to "json_object" conversion. Could you plea=
se help how to debug this further.<br><br></div><div></div><div>I think, I =
am missing some thing in config (as u suggest in previous mail) and debuggi=
ng from the code to find it out. I tried multiple examples available over n=
et, but nothing worked out for me. Can you please review my config once aga=
in.<br><br>Thanks for your help.<br></div><div><br></div>Regards,<br></div>=
Sridhar<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Thu, Nov 19, 2015 at 7:06 PM, Steven Barth <span dir=3D"ltr"><<a href=
=3D"mailto:cyrus at openwrt.org" target=3D"_blank">cyrus at openwrt.org</a>></=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">You are most likely missing =
a route to the remote tunnel endpoint (192.168.11.5).<br>
The system doesn't know which interface and next hop to send the tunnel=
ed packets to, thats why its blocking the tunnel bringup.<br>
<br>
<br>
Cheers,<br>
<br>
Steven<br>
_______________________________________________<br>
openwrt-devel mailing list<br>
<a href=3D"mailto:openwrt-devel at lists.openwrt.org" target=3D"_blank">openwr=
t-devel at lists.openwrt.org</a><br>
<a href=3D"https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel=
" rel=3D"noreferrer" target=3D"_blank">https://lists.openwrt.org/cgi-bin/ma=
ilman/listinfo/openwrt-devel</a><br>
</blockquote></div><br></div>

--001a11c1295ea307320524f39711--

--===============3641716729878523015==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

--===============3641716729878523015==--