¶ Interface Classification
What is it?
In Made4Flow, a classified interface is used to tell which type of interface or interface group a certain Interface, VLAN, or logical interface on your Router belongs to.
We can also generate summarized graphics of all the interfaces classified in the same group in the initial and customized dashboards.
Depending on how you classify an interface, Made4Flow may process some parts of the data differently from the standard, generating more reliable information and also easier analysis by those who operate our software.
We can cite an example of this behavior in the Spoofing Analysis. If we classify the interface as a Client this interface will check if there is traffic Spoofing in the direction of Inbound (IN) of the traffic. On the other hand, in an interface classified as Transit, the Spoofing classification will be marked in the sense of Exit (OUT).
How to access?
Menu -> Registrations -> Interface Classification
Why classify with the correct type?
It is good practice that the interface classification is configured correctly, so that in the graphics and information of the Software there is no information other than reality, thus giving off the feeling of imprecision in the Software
What are the types of classification?
The classification is an expression of the reality of the product you buy/sell, so imagine that the classification of the interface type is you tell our Software what type (s) this interface is, which can be anything from a Transit, PTT/IX, CDN, and others. We created the main types of classification interfaces, let's give a brief explanation about each of them below:
Customer - This interface can be classified as a client or an interface that is the traffic output for your internal network/internal core.
Transit — This interface is your IP Transit providers/upstreams, generally on this interface you receive your full-routing's and have access to the entire internet through it. Examples of interfaces such as Transit are: Transit with Level3/Century Link, Transit with Cogent, Transit with NTT.
IX/PTT — Internet Exchange/ Traffic Exchange Point are the interfaces that you connect to the IX/PTT, which can be at the ATM (Multilateral Exchange Agreement) and generally IX/PTT have different VLANs for IPv4 and IPv6, you need to classify both IPv4 and IPv6 interfaces for correct operation and analysis of this traffic. Examples of interfaces are: IPv4 VLAN connected to IX.BR São Paulo.
Peering — A peering interface can be an interface connected to a partner or some other ASN that you deliver your traffic through that path, generally Peering interfaces are only for exchange between the ASNs in question. This type of peering can be taxed by the use of bandwidth. Example: Peering between ASN 1 and ASN2 through a direct fiber in the city of São Paulo.
PNI — Large content generators such as: Google, Facebook, Riot, Amazon are connected to several datacenters in the world and allow direct connectivity between your ASN and them. If both have equipment in the same Datacenter, these connections are called PNI. Example: In the Equinix SP4 datacenter, ASN1 and Google have equipment and request a cross-connect (cable/optical fiber between one and the other within the Datacenter) and thus establish a PNI.
Free Peering — You can establish a Peering or connectivity with another ASN free of charge, so the traffic that crosses this connection is not taxed, perhaps improving connectivity and latency between networks. Example: In the city of São Paulo, providers A and B connect so that their customers exchange traffic without having to use transit/IX/PTT links.
CDN — These are the interfaces that connect directly to the CDN Servers sent by major internet generators such as: Google, Netflix, Facebook and Akamai. Example: interface that connects the Router to the Google CDN.
Confined/Restricted IP — Some regional operators and ISPs sell a product containing only access to the local CDN and IX that that operator connects to, in most cases the name of this product is Confined or Restricted. In this type of connectivity, we can see that the traffic is only that it comes through the IX/PTT or through a CDN that is within the Regional Operator or ISP. Example: Operator 8 only sells access to its CDN and IX that it connects to.
CDN Transit — Some regional ISPs sell products that only provide access to their CDN's. Example: ISP 1 sells access to Google and Facebook's CDN through an interface.
IX/PTT Transit — Some regional ISPs sell a product that only delivers the IX/PTT routes it connects to, so this product only has access to these routes, not access to the entire internet. Example: Operator 1 sells only IX/PTT São Paulo and IX/PTT Ceará on this interface.
Intra Routers — This type is used to count the traffic between your routers, an example would be: you have 2 routers and you connect them through an iBGP through this interface, all traffic between the routers is classified as Intra Routers.
CGNAT — This type is used for interfaces connected directly to your CGNAT (Carrier-Grade NAT) equipment. Example: Interface that connects to the A10 Thunder.
Not Classified — This is the standard type of all interfaces. If you don't classify the interfaces, they will be in this type. This type doesn't alter Spoofing behavior.
If you have any other type of classification you can contact our support and we will register for you.
Or if you have questions, you can call our support team through the chat.
See also our video tutorial: