Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 14 additions & 9 deletions docs/nodes/compute/installation/debian-12.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,25 +64,27 @@ ALEPH_VM_DOMAIN_NAME=vm.example.org

#### IPv6 address pool

The range of IPv6 addresses usable by the virtual machines must be specified manually.
The range of IPv6 addresses usable by the virtual machines must be specified manually. This is required to enable IPv6
egress.

According to the IPv6 specifications, a system is expected to receive an IPv6 with a /64
mask and all addresses inside that mask should simply be routed to the host.

The option takes the form of:

```
ALEPH_VM_IPV6_ADDRESS_POOL="2a01:4f8:171:787::/64"
```

Assuming hosting provider follows the specification, the procedure is the following:

1. Obtain the IPv6 address of your node.
2. Remove the trailing number after `::` if present, for example `2a01:4f8:171:787::2/64` becomes `2a01:4f8:171:787::/64`.
1. Obtain the IPv6 address of your node, the one used by the ALEPH_VM_NETWORK_INTERFACE setting below. You can find it
via the `ip a` command.
2. Remove the trailing number after `::` if present, for example `2a01:4f8:171:787::2/64` becomes
`2a01:4f8:171:787::/64`.
3. Add the IPv6 range you obtained under the setting `ALEPH_VM_IPV6_ADDRESS_POOL` in the configuration.



#### Network Interface
#### Network Interface (optional)

The default network interface is detected automatically from the IP routes.
You can configure the default interface manually instead by adding:
Expand All @@ -94,9 +96,12 @@ ALEPH_VM_NETWORK_INTERFACE=enp0s1
(don't forget to replace `enp0s1` with the name of your default network interface).


#### Domain Name Servers

You can configure the DNS resolver manually by using one of the following options:
#### Domain Name Servers (optional)

The DNS server used by the VM are detected automatically and doesn't need to be set manually.

But you can set the DNS resolver used for automatic detection manually by using one of the following options:

```
ALEPH_VM_DNS_RESOLUTION=resolvectl
Expand Down Expand Up @@ -139,7 +144,7 @@ This is a simple configuration. For more options, check [CONFIGURE_CADDY](config
Again, run these commands as `root`:

```shell
apt install -y debian-keyring debian-archive-keyring apt-transport-https
apt install -y debian-keyring debian-archive-keyring apt-transport-https
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | tee /etc/apt/sources.list.d/caddy-stable.list
apt update
Expand Down
14 changes: 8 additions & 6 deletions docs/nodes/compute/installation/ubuntu-22.04.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,25 +64,27 @@ ALEPH_VM_DOMAIN_NAME=vm.example.org

#### IPv6 address pool

The range of IPv6 addresses usable by the virtual machines must be specified manually.
The range of IPv6 addresses usable by the virtual machines must be specified manually. This is required to enable IPv6
egress.

According to the IPv6 specifications, a system is expected to receive an IPv6 with a /64
mask and all addresses inside that mask should simply be routed to the host.

The option takes the form of:

```
ALEPH_VM_IPV6_ADDRESS_POOL="2a01:4f8:171:787::/64"
```

Assuming hosting provider follows the specification, the procedure is the following:

1. Obtain the IPv6 address of your node.
2. Remove the trailing number after `::` if present, for example `2a01:4f8:171:787::2/64` becomes `2a01:4f8:171:787::/64`.
1. Obtain the IPv6 address of your node, the one used by the ALEPH_VM_NETWORK_INTERFACE setting below. You can find it
via the `ip a` command.
2. Remove the trailing number after `::` if present, for example `2a01:4f8:171:787::2/64` becomes
`2a01:4f8:171:787::/64`.
3. Add the IPv6 range you obtained under the setting `ALEPH_VM_IPV6_ADDRESS_POOL` in the configuration.



#### Network Interface
#### Network Interface (optional)

The default network interface is detected automatically from the IP routes.
You can configure the default interface manually instead by adding:
Expand Down
16 changes: 10 additions & 6 deletions docs/nodes/compute/installation/ubuntu-24.04.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,25 +64,29 @@ ALEPH_VM_DOMAIN_NAME=vm.example.org

#### IPv6 address pool

The range of IPv6 addresses usable by the virtual machines must be specified manually.
#### IPv6 address pool

The range of IPv6 addresses usable by the virtual machines must be specified manually. This is required to enable IPv6
egress.

According to the IPv6 specifications, a system is expected to receive an IPv6 with a /64
mask and all addresses inside that mask should simply be routed to the host.

The option takes the form of:

```
ALEPH_VM_IPV6_ADDRESS_POOL="2a01:4f8:171:787::/64"
```

Assuming hosting provider follows the specification, the procedure is the following:

1. Obtain the IPv6 address of your node.
2. Remove the trailing number after `::` if present, for example `2a01:4f8:171:787::2/64` becomes `2a01:4f8:171:787::/64`.
1. Obtain the IPv6 address of your node, the one used by the ALEPH_VM_NETWORK_INTERFACE setting below. You can find it
via the `ip a` command.
2. Remove the trailing number after `::` if present, for example `2a01:4f8:171:787::2/64` becomes
`2a01:4f8:171:787::/64`.
3. Add the IPv6 range you obtained under the setting `ALEPH_VM_IPV6_ADDRESS_POOL` in the configuration.



#### Network Interface
#### Network Interface (optional)

The default network interface is detected automatically from the IP routes.
You can configure the default interface manually instead by adding:
Expand Down
18 changes: 18 additions & 0 deletions docs/nodes/compute/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -241,6 +241,24 @@ When a diagnostic virtual machine happens to be stopped while writing data to th
https://$YOUR_CRN_HOSTNAME/vm/$CHECK_FASTAPI_VM_ID/state/increment
```

## IPv6 egress not working
Be sure you have set the `ALEPH_VM_IPV6_ADDRESS_POOL` configuration setting properly, check the IPv6 address pool section of your distribution installation guide.

Be aware that IPv6 egress is not working everywhere, and we are currently improving the IPv6 support to be compatible with more Hosting providers

The following infra providers are known to works:
* Hetzner
* OVH
* Fiberstate
* Ipax


The following infra providers are known not to works:
* Scaleway
* Ikoula
* Ionos
* Mevspace

## Found an issue?

If the documentation didn't help, you can [report an issue](https://github.com/aleph-im/support/issues).
2 changes: 1 addition & 1 deletion pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ dependencies = [
"ruff==0.3.4",
"pytest==8.1.1",
"mktestdocs==0.2.1",
"aleph-sdk-python==1.0.0rc1",
"aleph-sdk-python==2.0.0",
"matplotlib",
"numpy",
]
Expand Down