Table of Contents
XFI Gateway Review
XFI Gateway review Networks are very complicated, and many times we ignore some concepts.
Others use them for a long time without asking themselves why? And others go unnoticed. It is undoubtedly the case of the Gateway or GateWay.
It goes unnoticed for a lot of time, and one day we have to work with it, configure, assign it.
How do we start?
We start from a base that we must take into account and not only for the Gateway:
- A Gateway is not an IP
- A DNS server is not an IP
- A computer is not an IP
- A DHCP server is not an IP
We must not forget that an IP is a numerical code that helps us identify a specific system on the network and allows us to work with it, but an IP by itself is nothing.
Having this very, very clear, I will try to explain what the Gateway is.
What is a Gateway?
- A gateway is a network system that allows us, through itself, to access another network, or in other words, it serves as a link between two networks.
- The most exact case is a router. A router is not a computer, it is not a server, it is not a coffee maker, it is a router, and one of its primary functions is to route.
- So it becomes the XFI Gateway review to any device that remains—connected to it.
- We continue with the Gateway. I clarify that if a gateway is a device and is not a service, I repeat, a gateway can be a router.
- A server or a laptop, but it is not a service, it is a device of the network that allows us to access another web, and I have to repeat this because a gateway may require assistance to fulfill its role as a gateway.
- But each system will use a series of services called whatever they want to be called.
- As we in this blog work with Windows systems, we must know those services, functions, or roles that will provide the Gateway with its “power.”
- Routing and Remote Access Services or RRAS Routing and Remote Access Service (Windows Server 2003).
- Access services and network policies (ROL of Windows Server 2008, 2008 r2 and Windows Server 8).
- These services are usually configured as NAT, which is the central service of the Gateway and is the service that makes communication between the different networks possible.
What is the IP of the Gateway?
We have a router (which we will consider Modem / Router) with IP 192.168.1.1
We have a server with two IPs, 192.168.1.100 that connects to the router and 192.168.10.100 that connects to a switch.
With this data, we can deduce the following IP addresses.
- Ip: 192.168.1.1
- Subnet Mask. 255.255.255.0
- ISPs provide DNS1 and DNS2
SERVER – WAN network card:
- Ip: 192.168.1.100
- Subnet mask: 255.255.255.0
- Gateway: 192.168.1.1
- DNS 1: 192.168.1.1
SERVER – LAN:
- Ip network card: 192.168.10.100
- Subnet Mask: 255.255.255.0
- DNS 1: 192.168.10.100 (Assuming it is a domain controller and has the DNS role installed)
We can now continue analyzing more things. If we look at both the server’s network card and the router itself, they do not have a specified gateway. Why? Very easy.
The router (I remember it was Modem / Router) does not need a gateway because it is already connected directly to the Internet.
The same thing happens to the server. The LAN card does not require any IP configured in the Gateway field because the server’s second network card.
Which is the one used to communicate with another network, is already configured and ready to access another network.
What IP addresses would the network clients have?
- Ip: 192.168.10.X
- Subnet Mask: 255.255.255.0
- Gateway: 192.168.10.100
- DNS 1: 192.168.10.100
It is a configuration that will work in most cases, but I want to explain why Ip 192.168.10.100 in the Gateway and the DNS before closing the article.
In this case, the Gateway is the server itself that connects to the router through the network card.
Can communicate with another network, which is why even though the client is connected to the LAN card, it will always access the Internet, still Of course.
We have installed and configured the services required for this.
In DNS’s case, this may not always be the case, but they usually will connect to a domain controller with DNS services configured. For these cases, if this will be the IP configuration that we must apply.
And well friends, this is all for now. I hope I have clarified the doubts about this issue of gateways and remember an IP address always points and identifies a machine, pc, server.
Network device or whatever you want to call it should have configured a series of services to control and establish communications correctly.
- Errors in HTTP client connections to Unified Access Gateway Trunk Redirection after installing Update Rollup 1 for Forefront Unified Access Gateway 2010 Service Pack 4.
In addition, you can find more helpful resources at Tockhop.