KumiSystems/openwrtv4
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
openwrtv4/package/network/services/igmpproxy/files/igmpproxy.config

15 lines
288 B
Text
Raw Normal View History

igmpproxy: move to trunk, add myself as maintainer SVN-Revision: 40730
2014-05-08 13:14:34 +00:00
config igmpproxy
option quickleave 1
igmpproxy: add a silent logging option [0-3](none, minimal[default], more, maximum) It is not 100% backward compatible, because now 0 disables logging Signed-off-by: Dmitry Tunin <hanipouspilot@gmail.com>
2018-07-28 14:06:28 +00:00
# option verbose [0-3](none, minimal[default], more, maximum)
igmpproxy: move to trunk, add myself as maintainer SVN-Revision: 40730
2014-05-08 13:14:34 +00:00
igmpproxy: fix creation of firewall rules The init sccript for igmpproxy uses the option 'network' both as an interface name for fetching the l3_device name and for creating the firewall rules. This only works if the name of the network and firewall zone are identical. This commit introduces a new option 'zone' for configuring the upstream and downstream firewall zones in order for the init script to create the required firewall rules automatically. When no such options are given, the init script falls back to not creating the firewall rules and the user can opt to create these manually. Signed-off-by: Jaap Buurman <jaapbuurman@gmail.com>
2018-05-01 09:53:53 +00:00
config phyint
igmpproxy: move to trunk, add myself as maintainer SVN-Revision: 40730
2014-05-08 13:14:34 +00:00
option network wan
igmpproxy: fix creation of firewall rules The init sccript for igmpproxy uses the option 'network' both as an interface name for fetching the l3_device name and for creating the firewall rules. This only works if the name of the network and firewall zone are identical. This commit introduces a new option 'zone' for configuring the upstream and downstream firewall zones in order for the init script to create the required firewall rules automatically. When no such options are given, the init script falls back to not creating the firewall rules and the user can opt to create these manually. Signed-off-by: Jaap Buurman <jaapbuurman@gmail.com>
2018-05-01 09:53:53 +00:00
option zone wan
igmpproxy: move to trunk, add myself as maintainer SVN-Revision: 40730
2014-05-08 13:14:34 +00:00
option direction upstream
list altnet 192.168.1.0/24
igmpproxy: fix creation of firewall rules The init sccript for igmpproxy uses the option 'network' both as an interface name for fetching the l3_device name and for creating the firewall rules. This only works if the name of the network and firewall zone are identical. This commit introduces a new option 'zone' for configuring the upstream and downstream firewall zones in order for the init script to create the required firewall rules automatically. When no such options are given, the init script falls back to not creating the firewall rules and the user can opt to create these manually. Signed-off-by: Jaap Buurman <jaapbuurman@gmail.com>
2018-05-01 09:53:53 +00:00
config phyint
igmpproxy: move to trunk, add myself as maintainer SVN-Revision: 40730
2014-05-08 13:14:34 +00:00
option network lan
igmpproxy: fix creation of firewall rules The init sccript for igmpproxy uses the option 'network' both as an interface name for fetching the l3_device name and for creating the firewall rules. This only works if the name of the network and firewall zone are identical. This commit introduces a new option 'zone' for configuring the upstream and downstream firewall zones in order for the init script to create the required firewall rules automatically. When no such options are given, the init script falls back to not creating the firewall rules and the user can opt to create these manually. Signed-off-by: Jaap Buurman <jaapbuurman@gmail.com>
2018-05-01 09:53:53 +00:00
option zone lan
igmpproxy: move to trunk, add myself as maintainer SVN-Revision: 40730
2014-05-08 13:14:34 +00:00
option direction downstream
Reference in a new issue Copy permalink