Goline Logo

News

  • Route RPKI validation April 1st, 2022
    RPKI is a security framework by which network owners can validate and secure the critical route updates or Border Gateway Protocol (BGP) announcements between public Internet networks. BGP is essentially the central nervous system of the Internet and one of its fundamental building blocks. The main function of BGP is to facilitate efficient routing between Autonomous Systems (AS), by building and maintaining the Internet routing table. The Internet routing table is effectively the navigation system of the Internet and without it, traffic would be unable to flow between its constituent networks. Unfortunately, routing equipment alone cannot distinguish between legitimate and malicious routing announcements,...
  • RIPE – Atlas Anchor February 17th, 2022
    We have become an even more integral part of the RIPE Atlas project by hosting an anchor, a device that allows for latency analysis of traffic between autonomous systems.https://atlas.ripe.net/probes/7073/RIPE Atlas anchors play an integral role in the RIPE Atlas network by acting both as enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. Anchors are able to perform many more measurements than a regular RIPE Atlas probe, and the large amount of data they collect is made available to everyone. In addition, anchors act as powerful targets that can...
  • MANRS June 20th, 2020
    GOLINE firmly believes in initiatives to protect networks, improve security and resilience of the global routing system. Therefore we decided to support the MANRS project and join as participants.Mutually Agreed Norms for Routing Security (MANRS) is a global initiative, supported by the Internet Society, that provides crucial fixes to reduce the most common routing threats. MANRS offers specific actions via four programs for Network Operators, Internet Exchange Points, CDN and Cloud Providers, and Equipment Vendors. Requirements for Participation Please read the full MANRS Actions document before applying. You can become a participant if you meet these requirements: You (or your company) support...

Cisco Flexible NetFlow configuration example (Flow templates)

Paolo Caparrelli Cisco 22 June 2022

flow record ipv4_record
match ipv4 tos
match ipv4 source address
match ipv4 destination address
match ipv4 protocol
match transport source-port
match transport destination-port
match interface input
collect interface output
collect counter packets
collect counter bytes
collect transport tcp source-port
collect transport tcp destination-port
collect transport tcp flags
collect routing source as
collect routing destination as
collect ipv4 source mask
collect ipv4 destination mask
collect timestamp sys-uptime first
collect timestamp sys-uptime last

flow record ipv6_record
match ipv6 source address
match ipv6 destination address
match ipv6 protocol
match ipv6 tos
match transport source-port
match transport destination-port
match interface input
collect interface output
collect counter packets
collect counter bytes
collect transport tcp source-port
collect transport tcp destination-port
collect transport tcp flags
collect routing source as
collect routing destination as
collect ipv6 source mask
collect ipv6 destination mask
collect timestamp sys-uptime first
collect timestamp sys-uptime last


flow exporter NFAexporter
destination 185.54.81.20
source GigabitEthernet0/2
transport udp 9996
export-protocol netflow-v9
template data timeout 60

flow monitor NFAmonitorIPv4
record ipv4_record
exporter NFAexporter
cache timeout active 60
cache timeout inactive 60

flow monitor NFAmonitorIPv6
record ipv6_record
exporter NFAexporter
cache timeout active 60
cache timeout inactive 60

==================================

Applicare su ogni interfaccia:

ip flow monitor NFAmonitorIPv4 input
ipv6 flow monitor NFAmonitorIPv6 input

 

Addendum:

flow record ipv4_record
match datalink source-vlan-id
match datalink dot1q priority
match datalink mac source-address
match datalink mac destination-address
match ipv4 version
match ipv4 tos
match ipv4 ttl
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
match transport source-port
match transport destination-port
match interface input physical snmp
collect interface output snmp
collect counter flows
collect counter bytes
collect counter packets
collect timestamp sys-uptime first
collect timestamp sys-uptime last

flow record ipv6_record
match datalink source-vlan-id
match datalink dot1q priority
match datalink mac source-address
match datalink mac destination-address
match ipv6 version
match ipv6 protocol
match ipv6 source address
match ipv6 destination address
match transport source-port
match transport destination-port
match interface input physical snmp
collect interface output snmp
collect counter flows
collect counter bytes
collect counter packets
collect timestamp sys-uptime first
collect timestamp sys-uptime last

flow exporter NFAexporter
destination 192.168.222.59
source interface vlan 10
transport udp 9996
export-protocol netflow-v9
template data timeout 60
option interface-table timeout 60

flow monitor NFAmonitorIPv4
record ipv4_record
exporter NFAexporter
cache timeout active 60
cache timeout inactive 60

flow monitor NFAmonitorIPv6
record ipv6_record
exporter NFAexporter
cache timeout active 60
cache timeout inactive 60

interface te1/1/1
ip flow monitor NFAmonitorIPv4 input
ip flow monitor NFAmonitorIPv6 input

0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x