Firewall traffic rules: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 52: | Line 52: | ||
====Resolving hostnames to IP addresses==== | ====Resolving hostnames to IP addresses==== | ||
---- | ---- | ||
A command '''‘nslookup <hostname>’''' can be | A command '''‘nslookup <hostname>’''' can be utilized on both Windows and Linux machines to resolve a hostname to its corresponding IP address. This command can be particularly helpful when configuring network traffic rules because these rules require the use of IP addresses instead of hostnames. For instance, the following command can be used to resolve hostname ''''www.wikipedia.org'''' to its IP address: | ||
<pre> | <pre> | ||
nslookup www.wikipedia.org | nslookup www.wikipedia.org | ||
</pre> | </pre> | ||
It is worth noting that this command also functions on RutOS, as RutOS is based on OpenWRT, a Linux distribution. | |||
====Default ports for specific services==== | ====Default ports for specific services==== | ||
---- | ---- | ||
In the realm of networking, many services are assigned a default port number for communication. These are well-known, reserved TCP/IP ports | In the realm of networking, many services are assigned a default port number for communication. These default ports are typically well-known, reserved TCP/IP ports that range from 0 to 1023 and are specific to particular services. In addition to these ports, there are other well-known ports that fall outside of this range. | ||
For example, the MQTT (Message Queuing Telemetry Transport) protocol, which is commonly used in Internet of Things (IoT) applications, uses port number 1883 as its default port. When configuring Teltonika devices to utilize the MQTT protocol, a rule is automatically created to permit traffic on port 1883. | |||
However, if you encounter an issue with MQTT traffic being dropped, it is advisable to verify that the traffic rules are correctly configured to allow traffic on port 1883. You should confirm that the rule which permits traffic on this port exists and is enabled. | |||
Furthermore, it is important to note that these default ports are not set in stone and can be changed. This can be necessary for security reasons, as attackers may target commonly used ports to exploit vulnerabilities in certain services. Therefore, it is crucial to periodically review and update the ports used by your organization's services to prevent security breaches. | |||
==Traffic rules configuration examples== | ==Traffic rules configuration examples== | ||