Skip to main content

CCIE-LAB-RTBH

I - DESTINATION BASED

ATTACKER:
 
R1:
router rip
 version 2
 no auto-summary
 network 136.1.0.0
 network 150.1.0.0

TRIGGER:
 
R2:
router rip
 version 2
 no auto-summary
 network 136.1.0.0
 network 150.1.0.0
!
router bgp 23
 neighbor 136.1.23.3 remote-as 23
 neighbor 136.1.23.3 send-community
 redistribute static route-map STATIC_TO_BGP
!
route-map STATIC_TO_BGP permit 10
 match tag 23
 set local-preference 200
 set origin igp
 set community no-export
 set ip next-hop 192.0.2.1
!
ip route 192.0.2.1 255.255.255.255 Null0

when attack start add below acl (with IP of the destination - local server):
 
ip route 10.1.0.100 255.255.255.255 Null0 tag 23

EDGE:
 
R3:
router rip
 version 2
 no auto-summary
 network 136.1.0.0
 network 150.1.0.0
 network 10.0.0.0
!
router bgp 23
 neighbor 136.1.23.2 remote-as 23
!
ip route 192.0.2.1 255.255.255.255 Null0
!
interface Null0
 no ip unreachables

I - SOURCE BASED

TRIGGER:

when attack start add below acl (with source IP of the attacker):
 
ip route 170.170.170.170 255.255.255.255 Null0 tag 23

EDGE:
 
interface FastEthernet0/0.13
 ip verify unicast source reachable-via any

For networks which are not in the routing table or the next hop is Null0 - they are silently dropped.

Comments

Post a Comment

Popular posts from this blog

What should you know about HA 'override enabled' setting on Fortigate?

High availability is mandatory in most of today's network designs. Only very small companies or branches can run their business without redundancy. When you have Fortigate firewall in your network you have many options to increase network availability. You can use Fortigate Clustering Protocol ( FGCP ) or Virtual Router Redundancy Protocol ( VRRP ). FGCP has two modes: 'override' disabled (default) and 'override' enabled . I'm not going to explain how to set up HA as you can find many resources on Fortinet websites: https://cookbook.fortinet.com/high-availability-two-fortigates-56/ https://cookbook.fortinet.com/high-availability-with-fgcp-56/ Let's recap what is the main difference between them. The default HA setting is 'override' disabled and this is an order of selection an active unit: 1) number of monitored interfaces - when both units have the same number of working (up) interfaces check next parameter 2) HA uptime - an ...
8 comments
Read more

FortiGate and GRE tunnel

Recently I worked on one project where a client requested to re-route web traffic to the GRE tunnel to perform traffic inspection. I would like to share with you what is required if you configure it on FortiGate. We need a new GRE interface and policy base routing (PBR) to change the route for specific source IPs. Of course you need firewall policies to permit the traffic. Let's start with GRE interface. Unfortunately you can't configure it using the GUI, only CLI is the option: config system gre-tunnel edit "gre1" set interface "port1" set local-gw 55.55.55.55 set remote-gw 44.44.44.44 next end When the end peer is Cisco router, you need to set the IP for the GRE interface: config system interface edit gre1 set ip 192.168.10.10 255.255.255.255 set remote-ip192.168.10.20 end In next step we need to fix routing. We need the alternate path via GRE but to keep the route in the active routing table you need to set the same AD (adminis...
Post a Comment
Read more

Inpection of asymmetric sessions on FortiGate

There is one feature available on FortiGate, and I think you should know it, as it modifies a bit what we know about stateful firewalls. In past every packet was treated individually and you had to create policies in both directions. With stateful firewalls we can track connections, and by checking couple of attributes, we can treat them as part of the same session. For example when you initiate connection from a host1 to host2, the returning connection from host2 to host1 will be treated as part of the same connection (session). They have to have the same source/destination and destination/source IPs, port numbers and interfaces.There is an exception from this rule and FortiGate in some specific cases can accept connections on port which was not used in the initial connection. Let me explain how it works on the below example:      The host1 has a default gateway on R1 (10.0.1.2), but you may notice that it is not the optimal path to host2 subnet. When we analyze ...
1 comment
Read more