remove non ascii whitespaces
This commit is contained in:
parent
598a10bc28
commit
5a6d6c4d13
GPG key ID:
901B2ADDF27C2263
117 changed files with 1928 additions and 1928 deletions
|
|
@ -12,7 +12,7 @@ KDE Connect is a multi-platform app that allows your devices to communicate (eg:
|
|||
## Features
|
||||
- **Shared clipboard**: copy and paste between your phone and your computer (or any other device).
|
||||
- **Notification sync**: Read and reply to your [Android](../../systems/Android.md) notifications from the desktop.
|
||||
- **Share files and URLs** instantly from one device to another including some filesystem integration.
|
||||
- **Share files and URLs** instantly from one device to another including some filesystem integration.
|
||||
- **Multimedia remote control**: Use your phone as a remote for [Linux](../../linux/Linux.md) media players.
|
||||
- **Virtual touchpad**: Use your phone screen as your computer's touchpad and keyboard.
|
||||
- **Presentation remote**: Advance your presentation slides straight from your phone.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ os: linux
|
|||
# NetworkManager
|
||||
[NetworkManager](https://networkmanager.dev/) is a program for providing detection and configuration for systems to automatically connect to networks. NetworkManager's functionality can be useful for both wireless and wired networks. For wireless networks, NetworkManager prefers known wireless networks and has the ability to switch to the most reliable network. NetworkManager-aware applications can switch from online and offline mode. NetworkManager also prefers wired connections over wireless ones, has support for modem connections and certain types of VPN. NetworkManager was originally developed by Red Hat and now is hosted by the GNOME project.
|
||||
|
||||
After installation, you should start/enable `NetworkManager.service`. Once the NetworkManager daemon is started, it will automatically connect to any available "system connections" that have already been configured. Any "user connections" or unconfigured connections will need _nmcli_ or an applet to configure and connect.
|
||||
After installation, you should start/enable `NetworkManager.service`. Once the NetworkManager daemon is started, it will automatically connect to any available "system connections" that have already been configured. Any "user connections" or unconfigured connections will need _nmcli_ or an applet to configure and connect.
|
||||
|
||||
## Usage
|
||||
NetworkManager comes with nmcli and nmtui.
|
||||
|
|
@ -20,7 +20,7 @@ Connect to a Wi-Fi network:
|
|||
Connect to a hidden Wi-Fi network:
|
||||
`nmcli device wifi connect SSID_or_BSSID password password hidden yes`
|
||||
|
||||
Connect to a Wi-Fi on the `wlan1` interface:
|
||||
Connect to a Wi-Fi on the `wlan1` interface:
|
||||
`nmcli device wifi connect SSID_or_BSSID password password ifname wlan1 profile_name`
|
||||
|
||||
Disconnect an interface:
|
||||
|
|
@ -42,7 +42,7 @@ Turn off Wi-Fi:
|
|||
`nmcli radio wifi off`
|
||||
|
||||
### Edit a connection
|
||||
For a comprehensive list of settings, see [nm-settings(5)](https://man.archlinux.org/man/nm-settings.5).
|
||||
For a comprehensive list of settings, see [nm-settings(5)](https://man.archlinux.org/man/nm-settings.5).
|
||||
|
||||
Firstly you need to get list of connections:
|
||||
`nmcli connection`
|
||||
|
|
@ -53,34 +53,34 @@ Wired connection 1 997f2782-f0fc-301d-bfba-15421a2735d8 ethernet enp0s25
|
|||
MY-HOME-WIFI-5G 92a0f7b3-2eba-49ab-a899-24d83978f308 wifi
|
||||
```
|
||||
|
||||
Here you can use the first column as connection-id used later. In this example we pick `Wired connection 2` as a connection-id.
|
||||
Here you can use the first column as connection-id used later. In this example we pick `Wired connection 2` as a connection-id.
|
||||
|
||||
You have three methods to configure a connection `Wired connection 2` after it has been created:
|
||||
You have three methods to configure a connection `Wired connection 2` after it has been created:
|
||||
|
||||
nmcli interactive editor
|
||||
`nmcli connection edit 'Wired connection 2'`.
|
||||
Usage is well documented from the editor.
|
||||
|
||||
nmcli command line interface
|
||||
`nmcli connection modify 'Wired connection 2' setting.property value`. See [nmcli(1)](https://man.archlinux.org/man/nmcli.1) for usage. For example you can change its IPv4 route metric to 200 using `nmcli connection modify 'Wired connection 2' ipv4.route-metric 200` command.
|
||||
`nmcli connection modify 'Wired connection 2' setting.property value`. See [nmcli(1)](https://man.archlinux.org/man/nmcli.1) for usage. For example you can change its IPv4 route metric to 200 using `nmcli connection modify 'Wired connection 2' ipv4.route-metric 200` command.
|
||||
|
||||
To remove a setting pass an empty field ("") to it like this:
|
||||
`nmcli connection modify 'Wired connection 2' setting.property ""`
|
||||
`nmcli connection modify 'Wired connection 2' setting.property ""`
|
||||
|
||||
Connection file
|
||||
In `/etc/NetworkManager/system-connections/`, modify the corresponding `Wired connection 2.nmconnection` file .
|
||||
Do not forget to reload the configuration file with `nmcli connection reload`.
|
||||
In `/etc/NetworkManager/system-connections/`, modify the corresponding `Wired connection 2.nmconnection` file .
|
||||
Do not forget to reload the configuration file with `nmcli connection reload`.
|
||||
|
||||
## Configuration
|
||||
NetworkManager will require some additional steps to be able run properly. Make sure you have configured `/etc/hosts`.
|
||||
NetworkManager will require some additional steps to be able run properly. Make sure you have configured `/etc/hosts`.
|
||||
|
||||
NetworkManager has a global configuration file at `/etc/NetworkManager/NetworkManager.conf`. Additional configuration files can be placed in `/etc/NetworkManager/conf.d/`. Usually no configuration needs to be done to the global defaults.
|
||||
NetworkManager has a global configuration file at `/etc/NetworkManager/NetworkManager.conf`. Additional configuration files can be placed in `/etc/NetworkManager/conf.d/`. Usually no configuration needs to be done to the global defaults.
|
||||
|
||||
After editing a configuration file, the changes can be applied by running:
|
||||
`nmcli general reload`
|
||||
|
||||
### DNS
|
||||
> **Note:** If `/etc/resolv.conf` is a symlink to `/run/systemd/resolve/stub-resolv.conf`, `/run/systemd/resolve/resolv.conf`,`/lib/systemd/resolv.conf` or `/usr/lib/systemd/resolv.conf`, NetworkManager will choose [systemd](../../linux/systemd/Systemd.md)-resolved automatically. To use dnsmasq, you must first remove that symlink, then restart NetworkManager.
|
||||
> **Note:** If `/etc/resolv.conf` is a symlink to `/run/systemd/resolve/stub-resolv.conf`, `/run/systemd/resolve/resolv.conf`,`/lib/systemd/resolv.conf` or `/usr/lib/systemd/resolv.conf`, NetworkManager will choose [systemd](../../linux/systemd/Systemd.md)-resolved automatically. To use dnsmasq, you must first remove that symlink, then restart NetworkManager.
|
||||
|
||||
### VPN
|
||||
[WireGuard](Wireguard.md) is natively supported. To import a [WireGuard](Wireguard.md) Config File as a connection:
|
||||
|
|
|
|||
|
|
@ -99,7 +99,7 @@ Corkscrew is a additional programm to tunnel SSH through [HTTP](../../internet/H
|
|||
```
|
||||
|
||||
## Server
|
||||
`sshd` is the OpenSSH server daemon, configured with `/etc/ssh/sshd_config` and managed by `sshd.service`. Whenever changing the configuration, use `sshd` in test mode before restarting the service to ensure it will be able to start cleanly. Valid configurations produce no output.
|
||||
`sshd` is the OpenSSH server daemon, configured with `/etc/ssh/sshd_config` and managed by `sshd.service`. Whenever changing the configuration, use `sshd` in test mode before restarting the service to ensure it will be able to start cleanly. Valid configurations produce no output.
|
||||
```shell
|
||||
sshd -t
|
||||
```
|
||||
|
|
|
|||
|
|
@ -20,9 +20,9 @@ mitmproxy is a set of tools that provide an interactive, SSL/TLS-capable interce
|
|||
|
||||
## 3 Powerful Core Tools
|
||||
The mitmproxy project’s tools are a set of front-ends that expose common underlying functionality. When we talk about “mitmproxy” we usually refer to any of the three tools - they are just different front-ends to the same core proxy.
|
||||
**mitmproxy** is an interactive, SSL/TLS-capable intercepting proxy with a console interface for [HTTP](../../internet/HTTP.md)/1, [HTTP](../../internet/HTTP.md)/2, and WebSockets.
|
||||
**mitmweb** is a web-based interface for mitmproxy.
|
||||
**mitmdump** is the command-line version of mitmproxy. Think tcpdump for [HTTP](../../internet/HTTP.md).
|
||||
**mitmproxy** is an interactive, SSL/TLS-capable intercepting proxy with a console interface for [HTTP](../../internet/HTTP.md)/1, [HTTP](../../internet/HTTP.md)/2, and WebSockets.
|
||||
**mitmweb** is a web-based interface for mitmproxy.
|
||||
**mitmdump** is the command-line version of mitmproxy. Think tcpdump for [HTTP](../../internet/HTTP.md).
|
||||
|
||||
## Usage
|
||||
Mitmproxy starts as a regular [HTTP](../../internet/HTTP.md) proxy by default and listens on http://localhost:8080.
|
||||
|
|
|
|||
|
|
@ -100,20 +100,20 @@ rclone mount remote:path/to/files /path/to/local/mount
|
|||
|
||||
## Storage Providers
|
||||
### Alias
|
||||
The `alias` remote provides a new name for another remote.
|
||||
The `alias` remote provides a new name for another remote.
|
||||
|
||||
### Amazon S3 Storage
|
||||
The S3 backend can be used with a number of compatible providers (including [Minio](../web/Minio.md)).
|
||||
|
||||
## Chunker
|
||||
The `chunker` overlay transparently splits large files into smaller chunks during upload to wrapped remote and transparently assembles them back when the file is downloaded. This allows to effectively overcome size limits imposed by storage providers.
|
||||
The `chunker` overlay transparently splits large files into smaller chunks during upload to wrapped remote and transparently assembles them back when the file is downloaded. This allows to effectively overcome size limits imposed by storage providers.
|
||||
|
||||
## Crypt
|
||||
Rclone `crypt` remotes encrypt and decrypt other remotes.
|
||||
Rclone `crypt` remotes encrypt and decrypt other remotes.
|
||||
|
||||
A remote of type `crypt` does not access a storage system directly, but instead wraps another remote, which in turn accesses the storage system. This is similar to how alias, union, chunker and a few others work. It makes the usage very flexible, as you can add a layer, in this case an encryption layer, on top of any other backend, even in multiple layers. Rclone's functionality can be used as with any other remote, for example you can mount a crypt remote.
|
||||
A remote of type `crypt` does not access a storage system directly, but instead wraps another remote, which in turn accesses the storage system. This is similar to how alias, union, chunker and a few others work. It makes the usage very flexible, as you can add a layer, in this case an encryption layer, on top of any other backend, even in multiple layers. Rclone's functionality can be used as with any other remote, for example you can mount a crypt remote.
|
||||
|
||||
Accessing a storage system through a crypt remote realizes client-side encryption, which makes it safe to keep your data in a location you do not trust will not get compromised. When working against the `crypt` remote, rclone will automatically encrypt (before uploading) and decrypt (after downloading) on your local system as needed on the fly, leaving the data encrypted at rest in the wrapped remote. If you access the storage system using an application other than rclone, or access the wrapped remote directly using rclone, there will not be any encryption/decryption: Downloading existing content will just give you the encrypted (scrambled) format, and anything you upload will _not_ become encrypted.
|
||||
Accessing a storage system through a crypt remote realizes client-side encryption, which makes it safe to keep your data in a location you do not trust will not get compromised. When working against the `crypt` remote, rclone will automatically encrypt (before uploading) and decrypt (after downloading) on your local system as needed on the fly, leaving the data encrypted at rest in the wrapped remote. If you access the storage system using an application other than rclone, or access the wrapped remote directly using rclone, there will not be any encryption/decryption: Downloading existing content will just give you the encrypted (scrambled) format, and anything you upload will _not_ become encrypted.
|
||||
|
||||
## FTP
|
||||
[FTP](../../internet/FTP.md) is the File Transfer Protocol.
|
||||
|
|
@ -129,22 +129,22 @@ This is an rclone backend for Mega which supports the file transfer features of
|
|||
## Memory
|
||||
The memory backend is an in RAM backend. It does not persist its data.
|
||||
|
||||
The memory backend behaves like a bucket-based remote (e.g. like s3). Because it has no parameters you can just use it with the `:memory:` remote name.
|
||||
The memory backend behaves like a bucket-based remote (e.g. like s3). Because it has no parameters you can just use it with the `:memory:` remote name.
|
||||
|
||||
## SMB
|
||||
SMB is a communication protocol to share files over network.
|
||||
|
||||
## Union
|
||||
The `union` backend joins several remotes together to make a single unified view of them.
|
||||
The `union` backend joins several remotes together to make a single unified view of them.
|
||||
|
||||
During the initial setup with `rclone config` you will specify the upstream remotes as a space separated list. The upstream remotes can either be a local paths or other remotes.
|
||||
During the initial setup with `rclone config` you will specify the upstream remotes as a space separated list. The upstream remotes can either be a local paths or other remotes.
|
||||
|
||||
The attributes `:ro`, `:nc` and `:nc` can be attached to the end of the remote to tag the remote as **read only**, **no create** or **writeback**, e.g. `remote:directory/subdirectory:ro` or `remote:directory/subdirectory:nc`.
|
||||
- `:ro` means files will only be read from here and never written
|
||||
- `:nc` means new files or directories won't be created here
|
||||
- `:writeback` means files found in different remotes will be written back here.
|
||||
The attributes `:ro`, `:nc` and `:nc` can be attached to the end of the remote to tag the remote as **read only**, **no create** or **writeback**, e.g. `remote:directory/subdirectory:ro` or `remote:directory/subdirectory:nc`.
|
||||
- `:ro` means files will only be read from here and never written
|
||||
- `:nc` means new files or directories won't be created here
|
||||
- `:writeback` means files found in different remotes will be written back here.
|
||||
|
||||
Subfolders can be used in upstream remotes. Assume a union remote named `backup` with the remotes `mydrive:private/backup`. Invoking `rclone mkdir backup:desktop` is exactly the same as invoking `rclone mkdir mydrive:private/backup/desktop`.
|
||||
Subfolders can be used in upstream remotes. Assume a union remote named `backup` with the remotes `mydrive:private/backup`. Invoking `rclone mkdir backup:desktop` is exactly the same as invoking `rclone mkdir mydrive:private/backup/desktop`.
|
||||
|
||||
## WebDAV
|
||||
To configure the [WebDAV](../../internet/WebDAV.md) remote you will need to have a [URL](../../internet/URL.md) for it, and a username and password
|
||||
|
|
@ -12,7 +12,7 @@ A very simplistic configuration which will deny all by default.
|
|||
ufw default deny
|
||||
```
|
||||
|
||||
The next line is only needed _once_ the first time you install the package:
|
||||
The next line is only needed _once_ the first time you install the package:
|
||||
```shell
|
||||
ufw enable
|
||||
```
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue