<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Allposts on </title>
    <link>https://wassimaouadi.com/tags/allposts/</link>
    <description>Recent content in Allposts on </description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 30 Jul 2026 21:31:13 +0200</lastBuildDate>
    <atom:link href="https://wassimaouadi.com/tags/allposts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Firewalls</title>
      <link>https://wassimaouadi.com/posts/firewalls/</link>
      <pubDate>Thu, 30 Jul 2026 21:31:13 +0200</pubDate>
      <guid>https://wassimaouadi.com/posts/firewalls/</guid>
      <description>&lt;h1 id=&#34;firewall-integration-in-cisco-aci&#34;&gt;firewall integration in Cisco ACI&lt;/h1&gt;&#xA;&lt;p&gt;(do a blog search for &amp;ldquo;service_insertion&amp;rdquo;)&lt;/p&gt;&#xA;&lt;h1 id=&#34;firewalls-in-linux&#34;&gt;firewalls in Linux&lt;/h1&gt;&#xA;&lt;p&gt;The default host-based firewall in RHEL allows all outgoing connections and blocks all incoming ones, except those explicitely permitted.&lt;/p&gt;&#xA;&lt;p&gt;The firewall daemon is called &lt;em&gt;firewalld&lt;/em&gt;. To interact with it, use the &lt;code&gt;firewall-cmd&lt;/code&gt; tool. The &lt;em&gt;firewalld&lt;/em&gt; daemon translates the instructions of &lt;code&gt;firewall-cmd&lt;/code&gt; into policies that use the syntax of the kernel&amp;rsquo;s &lt;em&gt;netfilter&lt;/em&gt; and &lt;em&gt;nftables&lt;/em&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;firewall-rules&#34;&gt;firewall rules&lt;/h2&gt;&#xA;&lt;p&gt;A rule dictates that a service is allowed to be accessed by an inbound connection. A &lt;em&gt;firewalld&lt;/em&gt; service is added with &lt;code&gt;firewall-cmd --add-service&lt;/code&gt; or removed with &lt;code&gt;firewall-cmd --remove-service&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Configuring PKI</title>
      <link>https://wassimaouadi.com/posts/pki/</link>
      <pubDate>Sun, 09 Feb 2025 21:31:13 +0200</pubDate>
      <guid>https://wassimaouadi.com/posts/pki/</guid>
      <description>&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;Technology&lt;/th&gt;&#xA;          &lt;th&gt;Definitions&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;CSR&lt;/td&gt;&#xA;          &lt;td&gt;Certificate Signing Request&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;h1 id=&#34;certificates&#34;&gt;Certificates&lt;/h1&gt;&#xA;&lt;h2 id=&#34;issuing-a-digital-certificate&#34;&gt;Issuing a Digital Certificate&lt;/h2&gt;&#xA;&lt;p&gt;Certificate server, Certificate Authority.&#xA;The entities that want the CA to issue a digital certificate for them must send their public key, their IP address and their FQDN to the CA.&#xA;The CA replies with a &lt;em&gt;digital certificate&lt;/em&gt;, aka &lt;em&gt;identity certificate&lt;/em&gt;, aka &lt;em&gt;public key certificate&lt;/em&gt; which means &amp;lsquo;I certify that the entity named in this certificate own the public key mentioned in this digital certificate.&amp;rsquo;&#xA;The digital certificate does not last forever; It has a validity period.&#xA;The digital certificate is a file with the extension &lt;strong&gt;.cer&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>VMware vSphere Networking Concepts</title>
      <link>https://wassimaouadi.com/posts/vspherevcenterconcepts/</link>
      <pubDate>Wed, 24 Apr 2024 21:31:13 +0200</pubDate>
      <guid>https://wassimaouadi.com/posts/vspherevcenterconcepts/</guid>
      <description>&lt;p&gt;In VMware, a good practice is to configure ESXi hosts in a cluster, then present the LUNs to the ESXi cluster.&#xA;A VMware datastore is a LUN that has been formatted with a filesystem like VMFS.&#xA;A VMware VM can access the datastore but has no awareness of the underlying LUN or its constituing storage disks.&#xA;Any protocol that carries the SCSI Command descriptor Block (like FC, FCoE, iSCSI, SAS) uses the LUN concept.&#xA;A successor to SCSI is NVMe.&#xA;When I configure a new datastore in a vCenter datacenter, I am presented by a menu to choose a ESXi from. (sc) This is because vCenter simply does not have direct access to the storage devices; it asks that selected ESXi server (can be seen as a &amp;rsquo;temporary agent&amp;rsquo;) to access the storage devices ot its behalf, format the access storage as VMFS disks and make them available in the datastore to many ESXi hosts. This action is only required once during the configuration of the datastore. This interaction takes place on the management vmkernel of the ESXi host. Later when I attach the datastore to the ESXI hosts, they will be able to access the VMFS disks directly, and they will access the storage devices.&lt;/p&gt;</description>
    </item>
    <item>
      <title>NSX-T Concepts</title>
      <link>https://wassimaouadi.com/posts/nsxtconcepts/</link>
      <pubDate>Mon, 08 Apr 2024 21:31:13 +0200</pubDate>
      <guid>https://wassimaouadi.com/posts/nsxtconcepts/</guid>
      <description>&lt;p&gt;VMware NSX-T does not support VXLAN!&lt;/p&gt;&#xA;&lt;h1 id=&#34;nsx-t-segments&#34;&gt;NSX-T Segments&lt;/h1&gt;&#xA;&lt;p&gt;a VM is connected to a segment.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;is a layer-2 domain.&lt;/li&gt;&#xA;&lt;li&gt;invokes a transport zone.&lt;/li&gt;&#xA;&lt;li&gt;once the transport zone configured, you can no longer edit it later.&lt;/li&gt;&#xA;&lt;li&gt;VLAN-based segments are equivalent to VLAN IDs&lt;/li&gt;&#xA;&lt;li&gt;VLAN-based segments are not permitted to connect to Tier-0 or Tier-1 gateways.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;edge-uplink-segments&#34;&gt;Edge Uplink Segments&lt;/h3&gt;&#xA;&lt;p&gt;require VLAN transport zones.&#xA;A single Edge Uplink segment can be used more than once.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SSH</title>
      <link>https://wassimaouadi.com/posts/ssh/</link>
      <pubDate>Wed, 20 Dec 2023 21:31:13 +0200</pubDate>
      <guid>https://wassimaouadi.com/posts/ssh/</guid>
      <description>&lt;h1 id=&#34;ssh-on-cisco-devices&#34;&gt;SSH on Cisco devices&lt;/h1&gt;&#xA;&lt;h2 id=&#34;ssh-terminal-line-access-feature&#34;&gt;SSH Terminal-Line Access Feature&lt;/h2&gt;&#xA;&lt;p&gt;replaces reverse Telnet feature that was typically configured on terminal services routers.&lt;/p&gt;&#xA;&lt;p&gt;provides secure console access for servers physically connected to a terminal services router.&lt;/p&gt;&#xA;&lt;p&gt;introduces the concept of &amp;lsquo;rotary&amp;rsquo;.&lt;/p&gt;&#xA;&lt;p&gt;Remember that each physical Async port has an associated logical line to it.&lt;/p&gt;&#xA;&lt;p&gt;Each router line (not the Async ports) must be configured with a unique rotary number.&lt;/p&gt;&#xA;&lt;p&gt;Number of rotaries == number of lines&lt;/p&gt;</description>
    </item>
    <item>
      <title>Basic MPLS L3 VPN Concepts</title>
      <link>https://wassimaouadi.com/posts/mplsl3vpn/</link>
      <pubDate>Mon, 12 Jun 2023 21:31:13 +0200</pubDate>
      <guid>https://wassimaouadi.com/posts/mplsl3vpn/</guid>
      <description>&lt;h1 id=&#34;vpn-advantage&#34;&gt;VPN Advantage&lt;/h1&gt;&#xA;&lt;p&gt;A VPN is a network where private network services are provided to one or more customers over a public network, Internet, or a private network. &lt;/p&gt;&#xA;&lt;p&gt;A VPN consists of one or more VPN tunnels! &lt;/p&gt;&#xA;&lt;p&gt;VPN connects sites of a same customer together.  A set of &amp;ldquo;policies&amp;rdquo; determine which sites communicate with each other and which not;  &lt;/p&gt;&#xA;&lt;p&gt;In one scenario, the customer itself defines and implements them, in collaboration with the SP. The customer may for example want to force traffic from site S1 to traverse site S2, because the latter has a firewall installation. &lt;/p&gt;</description>
    </item>
  </channel>
</rss>
