by didine93 » Tue Jun 23, 2020 8:23 am
I followed the instructions but I don't know how to add IP addresses for the whitelist
White List and Dynamic List control
1. If not already, please login as the ‘root’ user to get to the root prompt.
2. Type ‘crontab -e’ to edit the crontab entry; Please be careful making modifications in this
screen as it may result in undesired system behavior
3. Using the up and down arrow keys put a # at the beginning of any line containing ‘VBfirewall.pl’ in it; You can modify these lines instead but for simplicity we are commenting them
out, making them not run at all
4. Using the down arrow key, scroll to the very end of the screen until the cursor no longer moves
down
5. Type in the following and then press ENTER when done: * * * * * /usr/local/bin/VB-firewall.pl
--white --dynamic --quiet
6. Type in the following and then press ENTER when done: @reboot /usr/local/bin/VB-firewall.pl
--white --dynamic --quiet
7. Press CTRL-X to exit this screen
8. When asked to Save, press the Y key
9. Press the ENTER key to accept the default filename presented; Changing the filename will
result in an error and no changes will be made
10. At the root prompt, type ‘yast firewall’ and press the ENTER key
11. Using the up and down arrow keys, move the highlight bar until ‘public’ is highlighted, then
press the ENTER key; You can use the TAB key to move the highlight bar to the proper window
that public is in if it’s not there by default
12. Press the TAB key until the highlight bar moves to the window that has “Allowed” above it;
These are the rules that are allowed access to the system
13. Using the up and down arrow keys, move the highlight bar to the following items and then press
the SPACE bar once: Asterisk; If you also want to control web access through the white and
dynamic list, repeat this step for the ‘apache2’ and ‘apache2-ssl’ items
14. Press ALT-E to remove these items from the allowed list; DO NOT remove RTP from the
allowed list
15. Press ALT-A to accept and apply these changes; You should end up back at a root prompt
afterwards
Due to the way connection tracking works in the underlying OS, a reboot might be required for the
changes to fully come into effect. This will result in only the IPs in the white list and the dynamic
authentication from being allowed to connect to ViciDial services.