>Thank you for this nice implementation. I've started some documentation
>on http://wiki.openwrt.org/doc/uci/network
Thx for documenting the gre options on the wiki
>
>A few comments after testing gre/gretap on BB-rc2 (with netifd 2014-07-30
>from trunk):
>
>1/ the firewall rules added by "zone" d
On Sun, Aug 03, 2014 at 11:37:51AM +0200, Steven Barth wrote:
> tbh. we should get rid of that option network stuff.
> I merged it anyway at first so we can get some experience with this
> gre-integration.
> Normally you should use something like this instead:
>
> config interface mygre
>
Main use case behind the network option is being able to add the
ethernet gre interface to a bridge interface as a hotplug interface
when the gre ethernet interface becomes active (as you cannot
configure the gre(v6)tap interface in the uci bridge ifname option);
therefore only the gretap and grev6
tbh. we should get rid of that option network stuff.
I merged it anyway at first so we can get some experience with this
gre-integration.
Normally you should use something like this instead:
config interface mygre
option proto 'gre'
option ipaddr '203.0.113.2'
option pee
On Sat, Aug 02, 2014 at 11:51:33PM +0900, Baptiste Jonglez wrote:
> 2/ "tunlink" does not seem to work for anything else than "wan". When
>trying to set it to "lan" (which is properly defined in the network
>config), the tunnel is not created. There is no error in readlog.
After some deb
Thank you for this nice implementation. I've started some documentation
on http://wiki.openwrt.org/doc/uci/network
A few comments after testing gre/gretap on BB-rc2 (with netifd 2014-07-30
from trunk):
1/ the firewall rules added by "zone" do no seem to be flushed when the
interface goes down
The package supports Generic Routing Encapsulation support by registering
following protocol kinds:
-gre
-gretap
-grev6
-grev6tap
Following options are valid for gre and gretap kinds:
-ipaddr
-peeraddr
-df
-mtu
-ttl
-tunlink
-zone
-ikey
-okey
