Update Cloudflare network docs

Author: hach-que

docs/dedis/securing_your_network.mdx

@@ -44,8 +44,8 @@ You'll most likely want the same people to have SSH access across all of your de
 1. Under "My Team" -> "Groups", click "Add a group".
 1. If you're only using CloudFlare Teams for SSH access, you might want to turn on "Set as default group". You won't need to assign this group manually to applications when you set up each application in the steps below.
 1. Set up the include and require rules to restrict access to your team members. An example set up would be:
-    - Include: "Emails ending in @company.com"
-    - Require: "Login methods - Google Workspace"
+   - Include: "Emails ending in @company.com"
+   - Require: "Login methods - Google Workspace"
 
 ## Create an application for the dedicated server
 
@@ -57,25 +57,26 @@ For each dedicated server you have, you need to create an application in the Clo
 1. Set the session duration to the maximum length of time you want to allow an SSH connection to be open before the user has to re-authenticate. You can lower this from 24 hours to increase security.
 1. Set the domain to the domain you registered (e.g. `companyinternal.dev`). Leave the path blank.
 1. Set the subdomain. As suggested above, it should be something like `west-europe-01`.
-    - Ignore the warning about "No DNS record found for this domain". We'll create one later.
+   - Ignore the warning about "No DNS record found for this domain". We'll create one later.
 1. Untick "Show this app in App Launcher". There's no need for it to be visible there.
 1. Select the identity providers you want to use to authenticate SSH access with at the bottom of the page.
 1. Click "Next".
 1. Set a name for the policy; a suggestion would be "Internal Employee Access".
 1. If you set up an access group above, select this access group. Otherwise, manually add the access rules to only allow team member access.
 1. Click "Next".
 1. Underneath "Additional settings":
-    - Turn on "Enable automatic cloudflared authentication".
-    - Set "Browser rendering" to "SSH".
+   - Turn on "Enable automatic cloudflared authentication".
+   - Set "Browser rendering" to "SSH".
 
 ## Set up an SSH tunnel
 
 For the application we just set up, we now need to create a tunnel configuration so that CloudFlare knows how to route it. This will also install the tunnel software on our dedicated server.
 
-1. Under "Access" -> "Tunnels", click "Create a tunnel".
+1. Under "Network" -> "Tunnels", click "Create a tunnel".
+1. Select "Cloudflared".
 1. Set the tunnel name to match the application name; e.g. `west-europe-01`.
 1. Click "Save tunnel".
-1. For operating system, select "Debian".
+1. For operating system, select "Debian", "64-bit".
 1. Copy the command shown for "If you don’t have cloudflared installed on your machine:".
 1. SSH into your dedicated server via the public Internet. Your local provider will have given you the SSH credentials for the dedicated server when they provisioned it. Usually these credentials are emailed to you. You can SSH to your machine at the command-line like so:
 
@@ -89,10 +90,10 @@ ssh user@host
 1. You should see the connector appear on CloudFlare Teams after a few seconds with a status of "Connected".
 1. Click "Next" in the CloudFlare Teams portal.
 1. Set the public hostname to the same hostname you gave the application in the previous step. That means:
-    - The subdomain should be something like `west-europe-01`.
-    - The domain should be the domain you registered, like `companyinternal.dev`.
-    - The path should be left blank.
-    - Again, ignore the warning about "No DNS record found for this domain". When you save the tunnel in a moment, it will create the DNS record we need automatically.
+   - The subdomain should be something like `west-europe-01`.
+   - The domain should be the domain you registered, like `companyinternal.dev`.
+   - The path should be left blank.
+   - Again, ignore the warning about "No DNS record found for this domain". When you save the tunnel in a moment, it will create the DNS record we need automatically.
 1. For service, set the scheme to "SSH" and the address field to `127.0.0.1:22`.
 1. Click "Save tunnel" at the bottom of the page.
 
@@ -188,6 +189,7 @@ lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
 ```
 
 The interface names might differ slightly, but the important thing is:
+
 - `eth0` is the private network interface. It has an IP address like `10.x.x.x`, `192.168.x.x`, etc.
 - `eth1` is the public network interface. It has an IP address associated with the public Internet. This IP address should also be visible in any management portal that your local provider gives you.