Commit 9ac5f230 authored by Vitaly Lipatov's avatar Vitaly Lipatov

gateway: support list of WAN interfaces via i_interfaces config option

Replace hardcoded i_interface/i_interface2 slots with a loop over wan_ifaces list. New i_interfaces option accepts comma/space-separated list of interfaces. Old i_interface/i_interface2 config still works as fallback for backwards compatibility.
parent 1a8c46d0
...@@ -11,6 +11,10 @@ ...@@ -11,6 +11,10 @@
# Second input interface # Second input interface
#i_interface2 = brlocal2 #i_interface2 = brlocal2
# List of WAN interfaces (preferred over i_interface/i_interface2)
# Comma and/or space separated, e.g.: ether1, ether3, enp8s0f0
#i_interfaces = ether1, ether3
# Internal interface (for blocking outgoing connections to banned IPs) # Internal interface (for blocking outgoing connections to banned IPs)
# When internal users access banned IPs on ports 80/443, # When internal users access banned IPs on ports 80/443,
# traffic is redirected to ban_server (DNAT by destination, not source) # traffic is redirected to ban_server (DNAT by destination, not source)
...@@ -21,6 +25,12 @@ ...@@ -21,6 +25,12 @@
# Maximum number of entries in ipset (default: 2000000) # Maximum number of entries in ipset (default: 2000000)
#maxelem = 2000000 #maxelem = 2000000
# Whitelist file: one IPv4/IPv6 address or CIDR network per line, '#' for comments.
# Loaded into ipset eterban_white (and eterban_white_ipv6) on service start.
# Whitelisted IPs are never added to the ban ipset and bypass DNAT to ban_server.
# Default: /etc/eterban/whitelist.txt
#whitelist_file = /etc/eterban/whitelist.txt
[API] [API]
# API server for checking if IP is banned # API server for checking if IP is banned
#listen_host = 127.0.0.1 #listen_host = 127.0.0.1
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment