Difference between revisions of "local firewall objects database"
From cpwiki.net
| Line 2: | Line 2: | ||
| − | Object information such as IPs can be gathered locally on the firewall. This is useful for situations where you might cat $FWDIR/conf/masters to check the manager and logger configurations. | + | Object information such as IPs can be gathered locally on the firewall. This is useful for situations where you might cat $FWDIR/conf/masters to check the manager and logger configurations. The problem is all that file presents is object names and you might what the associated IP address... but not want to take the time to look it up on the GUI. |
The local firewall object information can be found in | The local firewall object information can be found in | ||
Revision as of 17:06, 27 March 2014
Firewall Versions: R65 to R75 (tested)
Object information such as IPs can be gathered locally on the firewall. This is useful for situations where you might cat $FWDIR/conf/masters to check the manager and logger configurations. The problem is all that file presents is object names and you might what the associated IP address... but not want to take the time to look it up on the GUI.
The local firewall object information can be found in
$FWDIR/database/objects.C
commands to run locally on the firewall
# grep -A 200 -r ": (mysmartcenter" * $FWDIR/database/objects.C | grep -i ipaddr objects.C- :ipaddr (192.168.1.100)
where mysmartcenter should be replaced with the object name of interest
a little cleaner command for bash on SPLAT or Gaia
# NAME="object_name_goes_here"; grep -A 200 -r ": ($NAME" * $FWDIR/database/objects.C | grep -i ipaddr
ipso
# set NAME="object_name_goes_here"; grep -A 200 -r ": ($NAME" * $FWDIR/database/objects.C | grep -i ipaddr
