fix code formatting setting

Author: vjdhama

content/blog/container-networking-deep-dive-p1.md

@@ -26,7 +26,7 @@ Here is the [link](https://github.com/arihant-2310/Container-Networking-Deep-Div
 
 To start the VM, go to the directory where you downloaded the vagrant file and then execute the below commands:
 
-```shell
+```bash
 #To start the VM
 vagrant up
 
@@ -95,7 +95,7 @@ Hope you have set up the fresh VM and ssh into it ✌️.
 
 7. To list the interfaces inside `container1`
 
-   ```shell
+   ```bash
    #ip netns exec <network namespace name> <command>
    ip netns exec container1 ip link
    ```
@@ -105,7 +105,7 @@ Hope you have set up the fresh VM and ssh into it ✌️.
 
 8. By default, both ends of the veth pair were down. To enable
 
-   ```shell
+   ```bash
    #To set veth1 up
    ip link set veth1 up
 
@@ -115,7 +115,7 @@ Hope you have set up the fresh VM and ssh into it ✌️.
 
 9. To send packets to container1, we need to assign IP address to ceth1 interface inside `container1`
 
-   ```shell
+   ```bash
    ip netns exec container1 ip addr add 172.16.0.2/24 dev ceth1
    ```
 

content/blog/container-networking-deep-dive-p2.md

@@ -67,7 +67,7 @@ Here is the [link](https://github.com/arihant-2310/Container-Networking-Deep-Div
 file to set up the VM.
 
 To start the VM, go to the directory where you downloaded the vagrant file and then execute the below commands:
-```shell
+```bash
 #To start the VM
 vagrant up
 
@@ -84,33 +84,33 @@ In part 1 of this series, we already saw how to create network namespaces, add r
 I will quickly run the commands. We will focus more on the bridge part to help you understand how containers are attached to it and how packets are sent via it.
 
 1. To create two network namespace container1 and container2
-    ```shell
+    ```bash
     ip netns add container1
     ip netns add containe2
     ```
 
 2. To create two veth pairs
-    ```shell
+    ```bash
     ip link add veth1 type veth peer name ceth1
     ip link add veth2 type veth peer name ceth2
     ```
 
 3. To attach one end of each veth pair with containers
-    ```shell
+    ```bash
     ip link set ceth1 netns container1
     ip link set ceth2 netns container2
     ```
 
 4. To enables the interfaces inside the containers
-    ```shell
+    ```bash
     ip netns exec container1 ip link set lo up
     ip netns exec container2 ip link set lo up
     ip netns exec container1 ip link set ceth1 up
     ip netns exec container2 ip link set ceth2 up
     ```
 
 5. To assign ip address to interface inside containers
-   ```shell
+   ```bash
    ip netns exec container1 ip addr add 172.16.0.2/24 dev ceth1
    ip netns exec container2 ip addr add 172.16.0.3/24 dev ceth2
    ```
@@ -121,14 +121,14 @@ This will create a bridge named br0. Run `ip link` to list the bridge.
 ![Bridge](/images/blog/container-networking-deep-dive-p2/terminal-bridge.png)
 
 7. To attach the veth1 and veth2 to the bridge
-   ```shell
+   ```bash
    ip link set veth1 master br0
    ip link set veth2 master br0
    ```
    ![Veth pair attached to bridge](/images/blog/container-networking-deep-dive-p2/veth-pair-bridge-terminal.png)
 
 8. To enable veth1, veth2 and bridge br0
-   ```shell
+   ```bash
    ip link set veth1 up
    ip link set veth2 up
    ip link set br0 up

content/blog/container-networking-deep-dive-p3.md

@@ -42,7 +42,7 @@ before forwarding the packet to the containers. This can be achieved by adding a
 
 ## Configure ip forwarding and iptables rules to connect containers to the internet
 
-```shell
+```bash
 iptables -t nat -A POSTROUTING -s 172.16.0.0/24 -j MASQUERADE
 ```
 This command means that we are adding a new rule to the `nat` table of the `POSTROUTING` chain to `MASQUERADE` all the
@@ -62,7 +62,7 @@ disabled in Linux, if any incoming network packet arrives at one interface which
 dropped. Enabling ip forwarding will allow the incoming packet meant to be passed on to the another network to be accepted and
 then forwards it accordingly.
 
-```shell
+```bash
 # To see the ip forwarding status
 cat /proc/sys/net/ipv4/ip_forward