Protocol 255

Investigation and basic Understanding:

In every IPv4 packet, the byte at offset 9 identifies the protocol encapsulated in the packet. The most common protocols numbers are 1 (ICMP), 6 (TCP), and 17 (UDP). But here we will discussed protocol 255. 

In the document "Protocol Numbers" at http://www.iana.org/assignments/protocol-numbers, The Internet Assigned Numbers Authority lists assignments and technical references for protocol numbers 0 through 134. Protocols 135 through 254 are "unassigned" and 255, the highest possible protocol number, is identified in RFC 3692 as "reserved" Read more >>

Policy based routing with NAT

Static NAT configuration with the route-map option can be used to implement destination-based NAT scenarios where the same inside local address needs to be translated to more than one inside global addresses, depending on where the traffic is destined.

But, how NAT works with Route-map?  If we need to configure source-base NAT where each inside local address needs to be translated to different inside global address of a different ISP.

Also, if there is a Remote Server where no need to NAT inside addresses. Read more >>

.

BGP-received-route Tracking and Fast Peering Deactivation:

By: Sajid Ali Pathan

This is quite new think that we have ever done with BGP. In a BGP dual multi-home scenario we configured "Selective Route Tracking" with "neighbor fall-over" command under BGP process. Actually we were facing some kind of unusual issue during internet outage from primary ISP. We lost internet connectivity but local peering with ISP remains up.

“When you configured Neighbor fall-over command under BGP process, it monitors RIB and if route to peer is not present in routing table it will immediately deactivate peer session without waiting for hold down timer.”  Read more >>