SCION - Revision history

MatthewCroughan: Add to Applications and Networking categories

2024-07-03T12:50:26Z

Add to Applications and Networking categories

← Older revision		Revision as of 12:50, 3 July 2024
Line 93:		Line 93:
	rtt min/avg/max/mdev = 36.799/36.799/36.799/0.000 ms		rtt min/avg/max/mdev = 36.799/36.799/36.799/0.000 ms
	</syntaxhighlight>Additionally, you can try using the <code>scion-apps</code> as described in the upstream documentation https://docs.scionlab.org/content/apps/.		</syntaxhighlight>Additionally, you can try using the <code>scion-apps</code> as described in the upstream documentation https://docs.scionlab.org/content/apps/.

			[[Category:Networking]]
			[[Category:Applications]]

MatthewCroughan: Added section "Checking that everything worked" as well as "Usage Tips"

2024-06-25T12:55:00Z

Added section "Checking that everything worked" as well as "Usage Tips"

@@ Line 1: / Line 1: @@
 '''SCION (Scalability, Control, and Isolation On Next-Generation Networks)''' is a modern Future Internet architecture that aims to offer high availability and efficient point-to-point packet delivery, even in the presence of actively malicious network operators and devices. As of 2018 it is an ongoing research project led by researchers at ETH Zurich and, among other ''Future Internet'' proposals, is being explored in the Internet Engineering Task Force research group for path-aware networking.<ref>https://en.wikipedia.org/w/index.php?title=SCION_(Internet_architecture)&oldid=1154623316</ref>
 == Connecting to SCIONLab ==
 SCIONLab is a global research network to test the SCION next-generation internet architecture.<ref>https://www.scionlab.org/</ref> and allows you to connect to a pre-existing network without bootstrapping your own cryptographic material or Isolation Domain as a '''non-core AS (Autonomous System)'''. Once you have configured a '''non-core AS''' on your LAN, other hosts on this LAN can then use it to connect to the broader SCIONLab network, without having to run the <code>scion-control</code> or <code>scion-router</code> daemons. A SCION end-host only requires the <code>scion-dispatcher</code> and <code>scion-daemon</code> services. In a future release of SCION, the dispatcher will be deprecated and this requirement is reduced to only a single daemon. <ref>https://github.com/scionproto/scion/pull/4344</ref>
 To connect to SCIONLab:
@@ Line 13: / Line 23: @@
 . Fill out the following form, making sure to select <code>SCION installation from sources</code>
-[[File:SCIONLab AS Form.png|none|thumb]]
+[[File:SCIONLab AS Form.png|none|thumb]]4. Click <code>Create AS</code>
 . Once your AS is created, you should be able to click <code>Download configuration</code> on the page. This will yield a tarball like <code>scion_lab_user@myemail.com_20-ffaa_1_1155.tar.gz</code> Inside is a folder named <code>gen</code> which contains the necessary information we need to connect to the SCIONLab test network.
@@ Line 71: / Line 77: @@
+}
 </syntaxhighlight>

MatthewCroughan: formatting

2024-06-25T12:36:31Z

formatting

← Older revision		Revision as of 12:36, 25 June 2024
Line 19:		Line 19:
	4. Click <code>Create AS</code>		4. Click <code>Create AS</code>

	5. Once your AS is created, you should be able to click <code>Download configuration</code> on the page. This will yield a tarball like <code>scion_lab_user@myemail.com_20-ffaa_1_1155.tar.gz</code> Inside is a folder named <code>gen which contains the necessary information we need to connect to the SCIONLab test network.~~</code>~~		5. Once your AS is created, you should be able to click <code>Download configuration</code> on the page. This will yield a tarball like <code>scion_lab_user@myemail.com_20-ffaa_1_1155.tar.gz</code> Inside is a folder named <code>gen</code> which contains the necessary information we need to connect to the SCIONLab test network.

	=== Fixing SCIONLab Provided topology.json ===		=== Fixing SCIONLab Provided topology.json ===

MatthewCroughan: formatting

2024-06-25T12:33:45Z

formatting

← Older revision		Revision as of 12:33, 25 June 2024
Line 22:		Line 22:

	=== Fixing SCIONLab Provided topology.json ===		=== Fixing SCIONLab Provided topology.json ===
	The SCIONLab generated configuration contains some default incorrect assumptions though, that we need to either '''accomodate''' or '''fix'''. Inside of the <code>gen</code> folder provided by SCIONLab, you can correct the `topology.json` by removing `-1` from all occurrences of `br-1~~` `~~cs-1~~` `~~ds-1` and `sig-1`, then you can use the NixOS configuration below with no changes.		The SCIONLab generated configuration contains some default incorrect assumptions though, that we need to either '''accomodate''' or '''fix'''. Inside of the <code>gen</code> folder provided by SCIONLab, you can correct the <code>topology.json</code> by removing <code>-1</code> from all occurrences of <code>br-1</code> <code>cs-1</code> <code>ds-1</code> and <code>sig-1</code>, then you can use the NixOS configuration below with no changes.

	For convenience, you can run <code>sed -i 's/-1//g' gen/*/topology.json</code> to do this replacement.<syntaxhighlight lang="nix">		For convenience, you can run <code>sed -i 's/-1//g' gen/*/topology.json</code> to do this replacement.<syntaxhighlight lang="nix">

MatthewCroughan: formatting

2024-06-25T12:28:23Z

formatting

← Older revision		Revision as of 12:28, 25 June 2024
Line 3:		Line 3:
	== Connecting to SCIONLab ==		== Connecting to SCIONLab ==
	SCIONLab is a global research network to test the SCION next-generation internet architecture.<ref>https://www.scionlab.org/</ref> and allows you to connect to a pre-existing network without bootstrapping your own cryptographic material or Isolation Domain as a '''non-core AS (Autonomous System)'''. Once you have configured a '''non-core AS''' on your LAN, other hosts on this LAN can then use it to connect to the broader SCIONLab network, without having to run the <code>scion-control</code> or <code>scion-router</code> daemons. A SCION end-host only requires the <code>scion-dispatcher</code> and <code>scion-daemon</code> services. In a future release of SCION, the dispatcher will be deprecated and this requirement is reduced to only a single daemon. <ref>https://github.com/scionproto/scion/pull/4344</ref>		SCIONLab is a global research network to test the SCION next-generation internet architecture.<ref>https://www.scionlab.org/</ref> and allows you to connect to a pre-existing network without bootstrapping your own cryptographic material or Isolation Domain as a '''non-core AS (Autonomous System)'''. Once you have configured a '''non-core AS''' on your LAN, other hosts on this LAN can then use it to connect to the broader SCIONLab network, without having to run the <code>scion-control</code> or <code>scion-router</code> daemons. A SCION end-host only requires the <code>scion-dispatcher</code> and <code>scion-daemon</code> services. In a future release of SCION, the dispatcher will be deprecated and this requirement is reduced to only a single daemon. <ref>https://github.com/scionproto/scion/pull/4344</ref>



Line 15:		Line 16:


	4. Click <code>Create AS</code>5. Once your AS is created, you should be able to click <code>Download configuration</code> on the page. This will yield a tarball like <code>scion_lab_user@myemail.com_20-ffaa_1_1155.tar.gz</code> Inside is a folder named <code>gen which contains the necessary information we need to connect to the SCIONLab test network.</code>
			4. Click <code>Create AS</code>

			5. Once your AS is created, you should be able to click <code>Download configuration</code> on the page. This will yield a tarball like <code>scion_lab_user@myemail.com_20-ffaa_1_1155.tar.gz</code> Inside is a folder named <code>gen which contains the necessary information we need to connect to the SCIONLab test network.</code>

	=== Fixing SCIONLab Provided topology.json ===		=== Fixing SCIONLab Provided topology.json ===

MatthewCroughan: Create SCION

2024-06-25T12:23:11Z

Create SCION

New page

'''SCION (Scalability, Control, and Isolation On Next-Generation Networks)''' is a modern Future Internet architecture that aims to offer high availability and efficient point-to-point packet delivery, even in the presence of actively malicious network operators and devices. As of 2018 it is an ongoing research project led by researchers at ETH Zurich and, among other ''Future Internet'' proposals, is being explored in the Internet Engineering Task Force research group for path-aware networking.<ref>https://en.wikipedia.org/w/index.php?title=SCION_(Internet_architecture)&oldid=1154623316</ref>

== Connecting to SCIONLab ==
SCIONLab is a global research network to test the SCION next-generation internet architecture.<ref>https://www.scionlab.org/</ref> and allows you to connect to a pre-existing network without bootstrapping your own cryptographic material or Isolation Domain as a '''non-core AS (Autonomous System)'''. Once you have configured a '''non-core AS''' on your LAN, other hosts on this LAN can then use it to connect to the broader SCIONLab network, without having to run the <code>scion-control</code> or <code>scion-router</code> daemons. A SCION end-host only requires the <code>scion-dispatcher</code> and <code>scion-daemon</code> services. In a future release of SCION, the dispatcher will be deprecated and this requirement is reduced to only a single daemon. <ref>https://github.com/scionproto/scion/pull/4344</ref>

To connect to SCIONLab:

1. Create an account at https://www.scionlab.org/registration/register/

2. Create a new AS at https://www.scionlab.org/user/as/add

3. Fill out the following form, making sure to select <code>SCION installation from sources</code>
[[File:SCIONLab AS Form.png|none|thumb]]

4. Click <code>Create AS</code>5. Once your AS is created, you should be able to click <code>Download configuration</code> on the page. This will yield a tarball like <code>scion_lab_user@myemail.com_20-ffaa_1_1155.tar.gz</code> Inside is a folder named <code>gen which contains the necessary information we need to connect to the SCIONLab test network.</code>

=== Fixing SCIONLab Provided topology.json ===
The SCIONLab generated configuration contains some default incorrect assumptions though, that we need to either '''accomodate''' or '''fix'''. Inside of the <code>gen</code> folder provided by SCIONLab, you can correct the `topology.json` by removing `-1` from all occurrences of `br-1` `cs-1` `ds-1` and `sig-1`, then you can use the NixOS configuration below with no changes.

For convenience, you can run <code>sed -i 's/-1//g' gen/*/topology.json</code> to do this replacement.<syntaxhighlight lang="nix">
{
services = {
scion = {
enable = true; # Enable all SCION daemons
bypassBootstrapWarning = true; # We do not need to generate keys to attach to SCIONLab
};
};

# Pass the SCIONLab generated configuration into `/etc/scion` where the daemons will read from
environment = {
etc = {
"scion/topology.json".source = ./gen/ASffaa_1_1155/topology.json;
"scion/certs".source = ./gen/ASffaa_1_1155/certs;
"scion/keys".source = ./gen/ASffaa_1_1155/keys;
"scion/crypto".source = ./gen/ASffaa_1_1155/crypto;
};
};
}
</syntaxhighlight>

=== Accomodating SCIONLab Provided topology.json ===
Alternatively, if you wish to accomodate SCIONLab's default topology naming assumptions, you can modify the identifiers in each instance of the SCION daemons, and avoid modifying the supplied `topology.json`<syntaxhighlight lang="nix">
{
services = {
scion = {
enable = true; # Enable all SCION daemons
bypassBootstrapWarning = true; # We do not need to generate keys to attach to SCIONLab

# Correct the identifiers to accomodate SCIONLab provided topology.json
scion-control.settings.general = { id = "cs-1"; };
scion-daemon.settings.general = { id = "sd-1"; };
scion-router.settings.general = { id = "br-1"; };
};
};

# Pass the SCIONLab generated configuration into `/etc/scion` where the daemons will read from
environment = {
etc = {
"scion/topology.json".source = ./gen/ASffaa_1_1155/topology.json;
"scion/certs".source = ./gen/ASffaa_1_1155/certs;
"scion/keys".source = ./gen/ASffaa_1_1155/keys;
"scion/crypto".source = ./gen/ASffaa_1_1155/crypto;
};
};
}
</syntaxhighlight>