Dynamic DNS (DDNS or DynDNS) is a method of automatically updating a name server in the Domain Name System (DNS), often in real time, with the active DDNS configuration of its configured hostnames, addresses or other information.
Your IP address is just like your phone number, but it is your computers personal phone number on the internet. It is used by your Internet Service Providers to connect your computer to the Internet. Your computer doesn’t have the same number every day, it has a dynamic IP address, meaning it changes. It could change once a month, once a week, or even a few times a day, but it does change. Dynamic IP addresses are very common since they are cost effective for ISPs.
Vagrant is an open source tool for building a complete virtual development environment. Very often, a test environment is required for testing the latest release and new tools. Also, it reduces the time spent in re-building your OS. By default, vagrant uses virtualbox for managing the Virtualization. Vagrant acts as the central configuration for managing/deploying multiple reproducible virtual environments with the same configuration.
Simple bash script to scan open port of any machine in network without any tool like nmap or any other.
File Transfer Protocol
File Transport Protocol, or FTP, is an open protocol standard that is widely used to transport and receive large files. FTP can be used to send and receive large files. FTP can also be used to send configuration files and software updates for network switches and routers. It uses ports for communications and also uses encryption to protect the information being received and sent. In this lesson, we will go over these topics so that you can be familiar with FTP and what it has to offer.
How it Works!
The picture above shows the generic operation of how a client accesses an FTP server. The FTP server listens to Port 21 for connection requests and it sends data from its Port 20.
Simple bash script that while give you the vendor of your device.
A media access control address (MAC address), also called physical address, is a unique identifier assigned to network interfaces for communications on the physical network segment. MAC addresses are used as a network address for most IEEE 802 network technologies, including Ethernet and WiFi. Logically, MAC addresses are used in the media access control protocol sublayer of the OSI reference model.
A universally administered address is uniquely assigned to a device by its manufacturer. The first three octets (in transmission order) identify the organization that issued the identifier and are known as the Organizationally Unique Identifier (OUI).
The PPPoE (Point to Point Protocol over Ethernet) protocol provides extensive user management, network management and accounting benefits to ISPs and network administrators. Currently PPPoE is used mainly by ISPs to control client connections for xDSL and cable modems as well as plain Ethernet networks. PPPoE is an extension of the standard Point to Point Protocol (PPP).
Generally speaking, PPPoE is used to hand out IP addresses to clients based on authentication by username (and also if required, by workstation) as opposed to workstation only authentication where static IP addresses or DHCP are used. It is advised not to use static IP addresses or DHCP on the same interfaces as PPPoE for obvious security reasons.
The PPPoE client and server work over any Layer2 Ethernet level interface on the router – wireless 802.11 (Aironet, Cisco, WaveLan, Prism, Atheros), 10/100/1000 Mbit/s Ethernet, RadioLan and EoIP (Ethernet over IP tunnel).
Nginx (pronounced “engine x”) is a web server. It can act as a reverse proxy server for HTTP, HTTPS, SMTP, POP3, and IMAPprotocols, as well as a load balancer and an HTTP cache.
NGINX is a free, open-source, high-performance HTTP server and reverse proxy, as well as an IMAP/POP3 proxy server. NGINX is known for its high performance, stability, rich feature set, simple configuration, and low resource consumption.
NGINX is one of a handful of servers written to address the C10K problem. Unlike traditional servers, NGINX doesn’t rely on threads to handle requests. Instead it uses a much more scalable event-driven (asynchronous) architecture. This architecture uses small, but more importantly, predictable amounts of memory under load. Even if you don’t expect to handle thousands of simultaneous requests, you can still benefit from NGINX’s high-performance and small memory footprint. NGINX scales in all directions: from the smallest VPS all the way up to large clusters of servers.