Skip to main content


Showing posts from January, 2019

Configuring MAC Address filtering on Switch

For Cisco 4500 switch : Configuring Unicast MAC Address Filtering When unicast MAC address filtering is enabled, the switch drops packets with specific source or destination MAC addresses. This feature is disabled by default and only supports unicast static addresses. Example : Switch# configure terminal Switch(config)# mac address-table static c2f3.220a.12f4 vlan 4 drop Switch(config)# end Switch#

IP SLA tracking in Route MAP

Examples The following configuration sample shows a configuration used to track an object: ! Configure the objects to be tracked. ! Object 123 will be up if the router can ping ! Object 124 will be up if the router can ping ip sla monitor 1  type echo protocol ipicmpecho ip sla monitor schedule 1 start-time now life forever ! ip sla monitor 2  type echo protocol ipicmpecho ip sla monitor schedule 2 start-time now life forever ! track 123 rtr 1 reachability track 124 rtr 2 reachability ! ! Enable policy routing using route-map alpha on Ethernet 0. interface ethernet 0  ip address  ip policy route-map alpha ! ! is via this interface interface ethernet 1  ip address ! is via this interface interface ethernet 2  ip address ! ! Configure a route-map to set the next-hop to if object 123 is up. If object 123 ! is down,

NAT Cloud in EVE-NG

NAT Cloud in EVE-NG I want to share with you how to create a NAT cloud in the EVE-NG community edition. Essentially, this is a virtual network with a DHCP server, which will allow NAT connections over the management interface of the EVE-NG VM for Internet access. Interface, DHCP Server and NAT First of all, we need to create a network which can be used in the topology. I’ll be using the predefined pnet9 interface (Cloud 9 network) for this, but any other interface will do. 1 2 3 ip address add / 24 dev pnet9 echo 1 > / proc / sys / net / ipv4 / ip_forward iptables - t nat - A POSTROUTING - o pnet0 - s / 24 - j MASQUERADE This will assign an IP address to the device, enable IP forwarding in the kernel and establish an iptables rule to NAT the traffic to the pnet0 interface, which has the management IP address assigned. Technically, the pnet devices are bridges, but for the sake of this note this does no

SuperPuTTY for EVE-NG

To use SuperPuTTY as default client for telnet in Eve-NG for multi tab console When we click on Router or Switch in EVE-NG by default console open in CMD. Here I posting a method to use SuperPutty with EVE-NG so that you can use TAB function of SuperPutty. You need to edit registry  Enable handling of telnet://hostname:port/ URLs on the command line. With this feature, you can now set SuperPuTTY as the default handler for Telnet URLs  If you run the Registry Editor (Start->Run->regedit.exe) and set the value in: HKEY_CLASSES_ROOT\telnet\shell\open\command to be: "\path\to\SuperPutty.exe" (with the full pathname of your SuperPuTTY executable) In my case it like this : C:\Program Files (x86)\SuperPuTTY\SuperPutty.exe %1 Second most important thing : Select "Only allow single instance of SuperPutty to run" in SuperPutty options (Tools > Options) And in GUI options , select Tab Text : "Dynamic" And Fin