Now that we have our topology in place, the first thing is to enable "ipv6 unicast-routing". This will need to be enabled on all routers in the topology.Next, let's enable RIPngInterface and RIPng Configuration:In RIP version 1 and 2, to enable an interface to participate in the RIP network, we used the "network" command. In RIPng, RIP is enabled on the interface with "IPv6 rip" RIP Network "enable"Internet

ISP-1:

ISP-2:

LOCAL_SITE:

Let's verify the configuration from LOCAL_SITE perspective:

From the 2 diagrams above, we see that interfaces e1/0, e1/1 and Fa0/0 are participating in the RIP network. We also see in the additional RIP information.

From above, we see the list of routes learned via RIPng.

Let's see if our end system (kali) can reach the internet 2003::1/128

From the above, we see we can successfully trace from our Kali host internet 2003::1

From the above, we also see we can successfully ping from our Kali host to internet 2003::1. I will take the results of traceroute and ping to conclude that RIPng is working as expected.Lastly, let's peek into the RIP packet.

Above, we see a RIPng packet containing the networks being advertised to the Internet Router.

Below is a list of threat intelligence websites that you can use. Cymon.io is an excellent one as it searches around 200 different sources. If you’re looking for a more exhaustive list of threat intel sites, check out https://github.com/rshipp/awesome-malware-analysis