[OpenWrt-Devel] [PATCH] gre: Generic Routing Encapsulation package support

Hans Dedecker dedeckeh at gmail.com
Sun Aug 3 15:33:00 EDT 2014


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 grev6tap interfaces support this option.
The network option has no link to the assignment of a static IP
address on a gre interface; I would expect it to work as described
below independent from the network option.
If the network option is not the most optimal/elegant solution for the
use case described above I'm all ears for other suggestions/solutions.

Bye,
Hans


>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 peeraddr '192.0.2.42'
>         option network 'tunnel'
>
>config interface mygre_static
>option proto static
>option ifname @mygre
>option ipaddr 10.0.0.217
>option netmask 255.255.255.0
>
>
>Same should hopefully work with gre and gretap as source.
>If this does the trick I'm for removing the option network stuff.
>
>
>
>Cheers,
>
>Steven
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel



More information about the openwrt-devel mailing list