OSI Layer 6: Presentation Layer
The Presentation Layer is commonly rolled up into a different layer. This layer deals with the formatting of data, e.g. conversion of Extended Binary Coded Decimal Interchange Code (EBCDIC) to American Standard Code for Information Interchange (ASCII).
For example, the HTTP protocol (an Application Layer protocol) has methods for converting character encoding. In other words, this Presentation Layer step happens at the Application Layer.
Many networking stacks and protocols make no distinction between layers 6 and 7.
The Presentation Layer is commonly rolled up into a different layer. This layer deals with the formatting of data, e.g. conversion of Extended Binary Coded Decimal Interchange Code (EBCDIC) to American Standard Code for Information Interchange (ASCII).
For example, the HTTP protocol (an Application Layer protocol) has methods for converting character encoding. In other words, this Presentation Layer step happens at the Application Layer.
Many networking stacks and protocols make no distinction between layers 6 and 7.
OSI Layer 5: Session Layer
The Session Layer deals with managing of session data. It creates a semi-permanent connection, which is then used for communications.
Many of the RPC-type protocols depend on this layer:
NetBIOS: Network Basic Input Output System
RPC: Remote Procedure Call
PPTP: Point to Point Tunneling Protocol.
This layer is used by protocols which need reliable sessions, such as videoconferencing and SOCKS proxy.
If an established connection is lost or disrupted, this layer may try to recover the connection.
If a connection is not used for a long time, the session layer may close and then reopen it.
The Session Layer deals with managing of session data. It creates a semi-permanent connection, which is then used for communications.
Many of the RPC-type protocols depend on this layer:
NetBIOS: Network Basic Input Output System
RPC: Remote Procedure Call
PPTP: Point to Point Tunneling Protocol.
This layer is used by protocols which need reliable sessions, such as videoconferencing and SOCKS proxy.
If an established connection is lost or disrupted, this layer may try to recover the connection.
If a connection is not used for a long time, the session layer may close and then reopen it.
OSI Layer 4: Transport Layer
The Transport Layer is responsible for the end-to-end communication protocols. Data is properly multiplexed by defining the source and destination port numbers. This layer also deals with reliability by adding check sums, doing request repeats, and avoiding congestion.
Some of the common protocols in the Transport Layer are:
TCP: Transmission Control Protocol
It is the main component of the TCP/IP (Internet Protocol Suite) stack. It is useful when data integrity, ordered delivery, and reliability are important. It is the backbone to many of the most popular protocols.
UDP: User Datagram Protocol
This is another popular component of the Internet Protocol Suite stack. It is useful when transmission speed is important and the integrity of the data isn't as important, or is managed by an above layer.
SCTP: Stream Control Transmission Protocol
It uses port numbers to allow for connection multiplexing.
The Transport Layer is responsible for the end-to-end communication protocols. Data is properly multiplexed by defining the source and destination port numbers. This layer also deals with reliability by adding check sums, doing request repeats, and avoiding congestion.
Some of the common protocols in the Transport Layer are:
TCP: Transmission Control Protocol
It is the main component of the TCP/IP (Internet Protocol Suite) stack. It is useful when data integrity, ordered delivery, and reliability are important. It is the backbone to many of the most popular protocols.
UDP: User Datagram Protocol
This is another popular component of the Internet Protocol Suite stack. It is useful when transmission speed is important and the integrity of the data isn't as important, or is managed by an above layer.
SCTP: Stream Control Transmission Protocol
It uses port numbers to allow for connection multiplexing.
Transport Layer Ports
Transport layer protocols use ports to distinguish between different types of traffic or to do multiplexing. The ports are classed in three different ways.
Transport Layer Ports
Well-Known Ports (0-1023)
They are assigned by the Internet Assigned Numbers Authority (IANA), and usually require super-user privilege to be bound. Some of the well-known ports are: 22 TCP: SSH; 25 TCP: SMTP; 80 TCP: HTTP; 443 TCP: HTTPS.
Registered Ports (1024-49151)
Registered ports are also assigned by the IANA. They can be bound on most systems by non-super-user privilege. Some of the registered ports are: 1194 TCP/UDP: OpenVPN; 1293 TCP/UDP: IPSec; 1433 TCP: MSSQL Server.
Dynamic or Ephemeral Ports (49152-65535)
The Ephemeral ports are used as source ports for the client-side of a Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) connection. You can also use the Ephemeral ports for a temporary or non-root service.
Transport layer protocols use ports to distinguish between different types of traffic or to do multiplexing. The ports are classed in three different ways.
Transport Layer Ports
Well-Known Ports (0-1023)
They are assigned by the Internet Assigned Numbers Authority (IANA), and usually require super-user privilege to be bound. Some of the well-known ports are: 22 TCP: SSH; 25 TCP: SMTP; 80 TCP: HTTP; 443 TCP: HTTPS.
Registered Ports (1024-49151)
Registered ports are also assigned by the IANA. They can be bound on most systems by non-super-user privilege. Some of the registered ports are: 1194 TCP/UDP: OpenVPN; 1293 TCP/UDP: IPSec; 1433 TCP: MSSQL Server.
Dynamic or Ephemeral Ports (49152-65535)
The Ephemeral ports are used as source ports for the client-side of a Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) connection. You can also use the Ephemeral ports for a temporary or non-root service.
OSI Layer 3: Network Layer
The Network Layer is all about routing packets. This layer is responsible for getting the packets to the next point in the path to the destination. So, this layer deals with routing and packet forwarding, as well as with managing the quality of service.
In many cases, the final destination is not adjacent to this machine, so the packets are routed based on the local routing table information.
It is connectionless; connection tracking can happen at the layers above. Common protocols are IPv4 and IPv6, and is the backbone of the internet.
Many routing and control protocols live at this layer, such as:
IP: Internet Protocol
OSPF: Open Shortest Path First
IGRP: Interior Gateway Routing Protocol
ICMP: Internet Control Message Protocol.
The Network Layer is all about routing packets. This layer is responsible for getting the packets to the next point in the path to the destination. So, this layer deals with routing and packet forwarding, as well as with managing the quality of service.
In many cases, the final destination is not adjacent to this machine, so the packets are routed based on the local routing table information.
It is connectionless; connection tracking can happen at the layers above. Common protocols are IPv4 and IPv6, and is the backbone of the internet.
Many routing and control protocols live at this layer, such as:
IP: Internet Protocol
OSPF: Open Shortest Path First
IGRP: Interior Gateway Routing Protocol
ICMP: Internet Control Message Protocol.
Originally the datagram service for TCP, the Internet Protocol now transfers many different higher level protocols. The Internet Protocol has two main functions
Addressing
The addressing function examines the address on the incoming packet and decides if the datagram (packet) is for the local system or for another system. If the address indicates the datagram is for the local system, the headers are removed and the datagram is passed up to the next layer in the protocol stack. If the address indicates the datagram is for another machine, then it is passed to the next system in the direction of the final destination.
Fragmentation
The fragmentation component will split and re-assemble the packets if the path to the next system uses a smaller transmission unit size.
Addressing
The addressing function examines the address on the incoming packet and decides if the datagram (packet) is for the local system or for another system. If the address indicates the datagram is for the local system, the headers are removed and the datagram is passed up to the next layer in the protocol stack. If the address indicates the datagram is for another machine, then it is passed to the next system in the direction of the final destination.
Fragmentation
The fragmentation component will split and re-assemble the packets if the path to the next system uses a smaller transmission unit size.
OSI Layer 2: Data Link Layer
The Data Link Layer deals with transferring data between network nodes:
Adjacent nodes in a Wide Area Network (WAN)
Nodes on the same Local Area Network (LAN) segment.
Some of the common Data Link Layer protocols are:
Ethernet
ARP: Address Resolution Protocol
PPP: Point to Point Protocol
STP: Spanning Tree Protocol.
The Data Link Layer deals with transferring data between network nodes:
Adjacent nodes in a Wide Area Network (WAN)
Nodes on the same Local Area Network (LAN) segment.
Some of the common Data Link Layer protocols are:
Ethernet
ARP: Address Resolution Protocol
PPP: Point to Point Protocol
STP: Spanning Tree Protocol.
OSI Layer 1: Physical Layer
The Physical Layer is the lowest possible layer and deals with the actual physical transfer of information. This layer deals with transferring bits over a physical medium:
Electric pulses over copper cables
Laser pulses over fiber optic cables
Frequency modulations over radio waves
Scraps of paper over carrier pigeons (to learn more, review the following memo: A Standard for the Transmission of IP Datagrams on Avian Carriers).
There are various different protocols, hardware types, and standards defined for different types of physical networks (commonly referred to as PHYs):
IEEE 802.3: Copper or fiber connections
IEEE 802.11: Wireless (Wi-Fi) connections
Bluetooth: Wireless connections
USB: Copper connections
RS232: Copper serial connections.
The Physical Layer is the lowest possible layer and deals with the actual physical transfer of information. This layer deals with transferring bits over a physical medium:
Electric pulses over copper cables
Laser pulses over fiber optic cables
Frequency modulations over radio waves
Scraps of paper over carrier pigeons (to learn more, review the following memo: A Standard for the Transmission of IP Datagrams on Avian Carriers).
There are various different protocols, hardware types, and standards defined for different types of physical networks (commonly referred to as PHYs):
IEEE 802.3: Copper or fiber connections
IEEE 802.11: Wireless (Wi-Fi) connections
Bluetooth: Wireless connections
USB: Copper connections
RS232: Copper serial connections.
Security Awareness
Awareness is one of the best ways to combat insecurity. Security-related mailing lists like Common Vulnerabilities and Exposures (CVE) and The United States Computer Emergency Readiness Team (US-CERT) alerts help to inform system and network administrators of currently known vulnerabilities.
It also helps to think like a bad guy. You should have a non-production lab you attempt to break into, do security drills, and use resources like the "2600 Magazine: The Hacker Quarterly" to see how someone could infiltrate your network.
Distribution errata is another security concern.
You should never underestimate the power of human nature. Be aware of phishing scams or other types of social engineering attacks. You should continuously train your users on how to avoid falling prey to these attacks. You should always be aware of the layer 8 (human) errors.
Awareness is one of the best ways to combat insecurity. Security-related mailing lists like Common Vulnerabilities and Exposures (CVE) and The United States Computer Emergency Readiness Team (US-CERT) alerts help to inform system and network administrators of currently known vulnerabilities.
It also helps to think like a bad guy. You should have a non-production lab you attempt to break into, do security drills, and use resources like the "2600 Magazine: The Hacker Quarterly" to see how someone could infiltrate your network.
Distribution errata is another security concern.
You should never underestimate the power of human nature. Be aware of phishing scams or other types of social engineering attacks. You should continuously train your users on how to avoid falling prey to these attacks. You should always be aware of the layer 8 (human) errors.
The following image depicts the conceptual networking components involved when running a VM on a computer then launching a LXC container on that VM.
Be aware that many details have been omitted and would be required to make this a functioning example.
The real machine is connected to an ISP providing DHCP services assigning our adapter an address of 192.168.0.187.
The real machine is using KVM and deployed libvirtd which provides dhcp services in the subnet of 192.168.122.0 on the devices connected to Virt-bridge-1.
Our Virtual Machine is connected to Virt-Bridge-1 via the virtual adapter Virt-NIC-1 and is assigned an IP Address of 192.168.122.223.
Additionally, the Virtual-Machine has a dhcp server provided by its instance of libvirt. The default address of 192.168.122.1 for the dhcp server on Virtual-Machine has to be altered to avoid conflicts with the dhcp server running on the real machine. In this example the dhcp server on the Virtual-Machine was moved to the subnet 192.168.124.0.
Be aware that many details have been omitted and would be required to make this a functioning example.
The real machine is connected to an ISP providing DHCP services assigning our adapter an address of 192.168.0.187.
The real machine is using KVM and deployed libvirtd which provides dhcp services in the subnet of 192.168.122.0 on the devices connected to Virt-bridge-1.
Our Virtual Machine is connected to Virt-Bridge-1 via the virtual adapter Virt-NIC-1 and is assigned an IP Address of 192.168.122.223.
Additionally, the Virtual-Machine has a dhcp server provided by its instance of libvirt. The default address of 192.168.122.1 for the dhcp server on Virtual-Machine has to be altered to avoid conflicts with the dhcp server running on the real machine. In this example the dhcp server on the Virtual-Machine was moved to the subnet 192.168.124.0.
A second virtual bridge, Virt-Bridge-2 and virtual adapter Virt-NIC-2 were created on Virtual-Machine by libvirtd.
The lxc-container default configuration looks for the bridge by name. The libvirtd generated bridge is usually called virbr0. In this example the lxc default bridge was changed from lxbr0 to virbr0.
The LXC-container will receive an IP Address from the dhcp server on the Virtual-Machine. In this example the address is: 192.168.142.223.
The lxc-container default configuration looks for the bridge by name. The libvirtd generated bridge is usually called virbr0. In this example the lxc default bridge was changed from lxbr0 to virbr0.
The LXC-container will receive an IP Address from the dhcp server on the Virtual-Machine. In this example the address is: 192.168.142.223.
“The Complete DevOps RoadMap” by javinpaul https://link.medium.com/12gReCGrcab
Medium
The Complete DevOps RoadMap
An illustrated guide to becoming a Frontend or Backend Developer with links to courses
Знания по linux - это база DevOps!
Что бы подтянуть или начать изучать linux можно с помощью матерьялов по подготовке к LFCS.
https://blog.sedicomm.com/2018/07/23/lfcs-kak-ispolzovat-komandu-sed-gnu-dlya-sozdaniya-redaktirovaniya-i-manipulirovaniya-fajlami-v-linux-lfcs-chast-1/
Что бы подтянуть или начать изучать linux можно с помощью матерьялов по подготовке к LFCS.
https://blog.sedicomm.com/2018/07/23/lfcs-kak-ispolzovat-komandu-sed-gnu-dlya-sozdaniya-redaktirovaniya-i-manipulirovaniya-fajlami-v-linux-lfcs-chast-1/
Блог Университета SEDICOMM
LFCS: как использовать команду «sed» GNU для создания, редактирования и манипулирования файлами в Linux - часть 1
Linux Foundation объявила о сертификации LFCS (Linux Foundation Certified Sysadmin), новой программе, которая направлена на то, чтобы помочь людям во
If you decide to take the LFCS exam here information how not to be mistaken
https://medium.com/@obohovyk/how-to-prepare-and-pass-linux-foundation-certified-system-administrator-lfcs-exam-bd4cad4f6c64
https://medium.com/@obohovyk/how-to-prepare-and-pass-linux-foundation-certified-system-administrator-lfcs-exam-bd4cad4f6c64
Medium
How to prepare and pass Linux Foundation Certified System Administrator (LFCS) exam
Just a couple of days ago I’ve successfully passed LFCS exam and become Certified System Administrator (one step left to become Engineer —…
—-___Kubernetes Networking___——
illustrated guide
https://itnext.io/an-illustrated-guide-to-kubernetes-networking-part-1-d1ede3322727
https://itnext.io/an-illustrated-guide-to-kubernetes-networking-part-2-13fdc6c4e24c
and video guide
https://www.youtube.com/watch?v=WwQ62OyCNz4&ab_channel=VMwareCloudNativeApps
illustrated guide
https://itnext.io/an-illustrated-guide-to-kubernetes-networking-part-1-d1ede3322727
https://itnext.io/an-illustrated-guide-to-kubernetes-networking-part-2-13fdc6c4e24c
and video guide
https://www.youtube.com/watch?v=WwQ62OyCNz4&ab_channel=VMwareCloudNativeApps
Medium
An illustrated guide to Kubernetes Networking [Part 1]
Everything I learned about the Kubernetes Networking