Skip to main content

Palo Alto NDP Monitoring

Palo Alto NDP Monitoring
PAN-OS version 8.0 Palo Alto Networks introduced another IPv6 feature, namely “NDP Monitoring for Fast Device Location“. It basically adds a few information to the existing neighbor cache such as the User-ID (if present) and a “last reported” timestamp. That is: the admin has a new reporting window within the Palo Alto GUI that shows the reported IPv6 addresses along with its MAC addresses. This is really helpful for two reasons: 1) a single IPv6 node can have multiple IPv6 addresses which makes it much more difficult to track them back to the MAC address and 2) if SLAAC is used you now have a central point where you can look up the MAC-IPv6 bindings (comparable to the DHCP server lease for legacy IPv4).

For IPv4 you already have the DHCPv4 “View Allocation” window on the Palo Alto GUI. But for IPv6 addresses that are generated by the nodes themselves via SLAAC, everyone lacks a reporting instance for the MAC-IPv6 bindings. I wrote a few posts about monitoring MAC-IPv6 address bindings a couple of years ago. This feature now makes the traceability of IPv6 nodes available, at least for the local link (layer 2) from the firewall. (Reminder: NDP is link-local only, hence does not traverse any layer 3 routing instance.)
For this test I used a PA-200 with PAN-OS 8.0.3.

Activation & Tracing

You must only activate the “Enable NDP Monitoring” checkmark within the IPv6 tab for each interface you would like to enable it. You’re done. ;)

Every new Neighbor Advertisement is now stored along with its MAC address. Palo Alto will also add the User-ID if it’s known for that particular IPv6 address. Note the new clickable symbol in the “Features” column which opens the list. You can also filter the output, e.g., for a MAC address. This is quite useful since a single MAC address can have multiple IPv6 addresses, either because of privacy extensions or because of couple of configured addresses, such as virtual hosts on an F5 load-balancer as in my case:

Neighbor Cache vs. NDP Monitoring

The NDP Monitoring is not that different from the already available neighbor cache, though it uses some other sources. While the “neighbor cache” is an IPv6 standard functionality, this “NDP monitoring” captures neighbor advertisements and duplicate address detection (DAD) messages. Comparing both outputs on the CLI the NDP Monitoring has two more columns: “user id” and “last reported” (while it has a bad column size since the first two columns have no spacing when using subinterfaces). The following listing shows the normal neighbor cache (beginning at line 1), the new NDP monitoring output (line 52) and a filtered version of the NDP monitoring output based on a single MAC address (line 91).
I am not quite sure why I have more entries within the neighbor cache compared to the NDP monitoring. And only two link-local fe80:: addresses in the NDP mon section while 13 (!) in the interface. Hm. Maybe this is related to the fact that the NDP Monitor feature was not enabled since the start of the firewall. It is probably congruent with the “interface” output after the next reboot
Labels:

Comments

Post a Comment

Popular posts from this blog

Checkpoint firewall common commands part 2

Checkpoint firewall common commands part 2 For basic firewall informaton gathering: fgate stat -Status and statistics of Flood-Gate-1. fwaccel <stat|stats|conns>  – View status, statistics or connection table of SecureXL. fw getifs -Show list of configured interfaces with IP and netmask. cpstat <app_flag> [-f flavour] -View OS, HW and CP application status. Issue cpstat without any options to see all possible application flags <app_flag> and corresponding flavours. Examples: cpstat fw -f policy – verbose policy info cpstat os -f cpu – CPU utilization statistics cpinfo -y all   -List all installed patches and hotfixes. cpd_sched_config print -Show task scheduled with CPD scheduler. enabled_blades -View enabled software blades avsu_client [-app <app>]   , get_version <app>  -Get signature version and status of content security .Without the -app option “Anti Virus” is used. show co...
Post a Comment
Read more

Unable to Connect to Server Checkpoint R80

Unable to Connect to Server Checkpoint R80 Unable to Connect to Server A connection to the management server will fail if: A firewall between SmartConsole and the management server blocks Port 19009 -  port 19009 is used for a new R80 service. Allow traffic on this port for all clients and management servers. No GUI clients are assigned -  Open the Gaia Portal. If the First Time Configuration Wizard opens, complete it. If the First Time Configuration Wizard has already run, open  User Management > GUI Clients  and add a client. When using Multi-Domain Security Management, connect SmartConsole to the Multi-Domain Server and make sure the domains have GUI clients assigned to them. The required processes are not reachable -  Make sure the computer with SmartConsole installed can reach the IP address of the management server, and that these server processes are up and running: cpm fwm Operation time out  – Your connection ...
Post a Comment
Read more

Checkpoint firewall common commands part1

Checkpoint firewall common commands part1 For starting or stopping firewall services cpstop -Stop all Check Point services except cprid . You can also stop specific services by issuing an option with cpstop. For instance cpstop FW1 stops FW-1/VPN-1 or use cpstop WebAccess to stop WebAccess. cpstart -Start all Check Point services except cprid . cpstart works with the same options as cpstop . cprestart -Combined cpstop and cpstart . Complete restart. cpridstop, cpridstart, cpridrestart -Stop, start or restart cprid , the Check Point Remote Installation Daemon. fw kill [-t sig] proc -Kill a Firewall process. PID file in $FWDIR/tmp/ must be present. Per default sends signal 15 (SIGTERM).Example: fw kill -t 9 fwm fw unloadlocal – Uninstalls local security policy and disables IP forwarding. For getting basic firewall information : fw ver [-k] , fwm [mds] ver, vpn ver [-k], fgate ver -Show major and minor version as well as build numb...
Post a Comment
Read more