By default, WAF 2.0 will only create port redirections for public IPs. However, it can be set to observe on the private interface. It can happen, that your server does not have a public interface, in this case, there are more possibilities
Private IP addresses
192.168.0.0 – 192.168.255.255
172.16.0.0 – 172.31.255.255
10.0.0.0 – 10.255.255.255
192.168.0.0 – 192.168.255.255
172.16.0.0 – 172.31.255.255
10.0.0.0 – 10.255.255.255
The server is used in an internal network only
If the server is used only in an internal network then please note that the WAF 2.0module was not made for that. So the WAF module might not be triggered.
If the server is used only in an internal network then please note that the WAF 2.0module was not made for that. So the WAF module might not be triggered.
If there is a gateway in front of the server, which is accepting the requests from outside and it forwards the requests to the appropriate destination
- Open
/etc/bitninja/WAFManager/config.ini
with your preferred text editor.
e.g.: nano/etc/bitninja/WAFManager/config.ini
- Find the [redirect_options] flag in the file
e.g.: innano use ctrl+w then type [redirect

- Delete one of the semicolons from the beginning of the interface[]= lines
- Add the name of the interface that is connected to the gateway like this:
interface[]='eth1'
if the interface’s name is eth1 - Save changes and exit the text editor
- e.g.: in nano
ctrl+x
and then pressy
and then press enter
- e.g.: in nano
- Restart BitNinja with
service bitninja restart