You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

46 lines
1.4 KiB

4 years ago
= host vs containerized connection
Apostolos rootApostolos@swarmlab.io
// Metadata:
:description: Intro and Install
:keywords: sec, tcpdump
:data-uri:
:icons: font
{empty} +
Combine network hardware and software resources and network functionality into a single software-based management entity, a virtual network
== host
.network_mode=host
image::yesconnection.png[containerized,650,role=left]
The *host* option is used to make the interface look like they are running on the host itself. It allows the *Virtual Network Interface* greater network access than it can normally get.
If you use *host* then you'll get all ports listening on the host. This means you will need to check the services you runninf closely (especially if it's not yours, e.g. an official one provided by a software project) to make sure you don't inadvertently expose extra services on the network.
TIP: With this option you cann access and viceverse the other perticipante on the network directly from host
== container
.network_mode=container
image::noconnection.png[host,650,role=right]
A *container* option is used to isolate the services from different container and the *host* itself
TIP: With this option you cann *NOT* access and viceverse the other perticipante on the network directly from host
== share app
You can create applications and attach them to this network.
NOTE: More info here