- SCION - mailman3.inf.ethz.ch

Re: [SCION] Typo of SCIONLab tutorial
by Juan A. García-Pardo 08 May '20

08 May '20

Hi Hyok, Thanks for telling us. We are fixing it right now. Best regards, Juan A. On Fri, May 8, 2020 at 11:04 AM Hyok An (안혁) <anhyok(a)korea.ac.kr> wrote: > Dear SCIONLab, > > From https://docs.scionlab.org/content/apps/remote_sig.html : > You can find this sentence [*You need to replace the “" AS id of the remote > AS]* on the tutorial page of SCIONLab. > I think you wanted to write this [*You need to replace the > “<remote_sig_AS>" AS id of the remote AS]*. > > It seems that the <remote_sig_AS> is processed as HTML. > How about to change to "*<*remote_sig_AS*>*"? > > Following sentences also have the same problem for "<remote_sig_IPnet>". > > Best regards, > -- > Hyok An > M.S./Ph.D Integrated Course Student > Computer & Communication Security Lab > Korea University > _______________________________________________ > SCION mailing list > SCION(a)lists.inf.ethz.ch > https://lists.inf.ethz.ch/mailman/listinfo/scion >

1 0

Typo of SCIONLab tutorial
by Hyok An (안혁) 08 May '20

08 May '20

Dear SCIONLab, >From https://docs.scionlab.org/content/apps/remote_sig.html : You can find this sentence [*You need to replace the “" AS id of the remote AS]* on the tutorial page of SCIONLab. I think you wanted to write this [*You need to replace the “<remote_sig_AS>" AS id of the remote AS]*. It seems that the <remote_sig_AS> is processed as HTML. How about to change to "*<*remote_sig_AS*>*"? Following sentences also have the same problem for "<remote_sig_IPnet>". Best regards, -- Hyok An M.S./Ph.D Integrated Course Student Computer & Communication Security Lab Korea University

1 0

[SCIONLab] Package installing is not working properly
by Hyok An (안혁) 06 May '20

06 May '20

Dear SCIONLab, I have installed SCION AS with the document 'Installing packages' on Ubuntu 16.04 after the last update. : https://docs.scionlab.org/content/install/pkg.html However, it is not working properly. The health check of the webapp showed some failed results. : <image1.png> As you can see, it is not working. The message 'VPN is not configured for this AS' seems a hint in my guess. Because I already checked the option 'Use VPN' on the User AS page of SCIONLab as below. : <image2.png> Do you have anything to do with this for me? (I have checked using vagrant and it is working.) Best regards, -- Hyok An M.S./Ph.D Integrated Course Student Computer & Communication Security Lab Korea University

1 0

Some Questions for diploma Thesis (SCIONLab)
by mauro.casanova＠canet.ch 23 Apr '20

23 Apr '20

Hi all I plan to set up a SCIONLab infrastructure as part of my thesis for HF graduation. The aim is to estimate the effort and feasibility for an SME company. After some first experience, I still have some questions for the realization. On this Link <https://1drv.ms/b/s!AkcX1uSBJ03I2gt7VUulVlVpS_iG?e=EgmpTo> you can found an small architecture overview. I will use the SCIONLab infrastructure to build this up. My Questions: * Is it possible to run the scion control service on a VM an the border router service on a separated device? So what is necessary to run just an border router? * Can I as a SCIONLab User already use the path-awareness and multipath features, So can I write my own path- and traffic policies? (The goal is to create some policies like in the presentation on SCION day from Samuel Hitz) If yes, where can I do this? * The same Question I have for the peering link feature. Is this for an SCIONLab user also available? And something else. After the update of SCIONlab my test AS run well (all necessary service are up, SCMP messages are ok), but also after a new installation the SCION Apps / Webapps are just running with failure. Is this an knowing issue, or have I install the wrong apps? I will be very grateful for some answers. Special to know if this test deployment is possible. Thanks for your effort. Best Regards Mauro

1 0

Kickstarter Project - Power Pi: A smart UPS for the Raspberry Pi
by David Hausheer 09 Apr '20

09 Apr '20

Dear SCIONLabers, our Secure IoT team at OVGU Magdeburg has launched a kickstarter project for our "Power Pi: A Smart UPS for the Raspberry Pi", which provides power supply to the Pi in power outage situations. It would be great if you could help us to spread this to people who you believe might be interested to back our project: https://www.kickstarter.com/projects/tjohn327/power-pi-a-smart-ups-for-the-… We are convinced that compared to similar products in the market, Power Pi is offered at a very competitive price without compromising on features such as a wide input voltage range and a high output current. P.S. The estimated delivery time already considers potential delays due to Covid-19, which we clarified with the manufacturer and shipping company. Thanks for your help and best regards, John, Vishnu, and David

1 0

New SCION App for Android
by David Hausheer 02 Apr '20

02 Apr '20

Dear SCION listeners we are glad to announce the new version of the SCION app for Android: https://play.google.com/store/apps/details?id=org.scionlab.scion This version enables to run an entire SCION AS on an Android smartphone. The configuration is very easy (just follow the "How to use" menu within the app) We would be glad to get your feedback! P.S. The source code is available here: https://github.com/ekuiter/scion-android Best regards Elias Kuiter, Tom Heimbrodt, David Hausheer

1 1

Connection failure w/ sciond on local topology.
by Michael A. Flückiger 23 Mar '20

23 Mar '20

Hi all I'm trying to get the simple example found here <https://github.com/netsec-ethz/scion-apps/tree/master/_examples/helloworld> (/_examples/helloworld/) running. But I'm somehow not able to bind to the corresponding instance of the /sciond/. I'm running /ubuntu 16.04/, /go version go1.13.9 /and was able to setup the SCION local network: If I check for the listening sockets of the sciond i find the following: If I now set the S/CION_DEAMON_SOCKET/ environment variable as required when running multiple local ASes and try to run /helloworld.go///I run in the following error: I am at my wit's end and would appreciate any help / hint into the right direction very much. What am I doing wrong? Thanks for your effort. Best, Michi

2 1

Connection failure w/ sciond on local topology.
by Michael A. Flückiger 23 Mar '20

23 Mar '20

Sorry for the spam. I wasn't aware of the fact that images get stripped away. Therefore again my, this time complete, question. Hi all I'm trying to get the simple example found here <https://github.com/netsec-ethz/scion-apps/tree/master/_examples/helloworld> (/_examples/helloworld/) running. But I'm somehow not able to bind to the corresponding instance of the /sciond/. I'm running /ubuntu 16.04/, /go version go1.13.9 /and was able to setup the SCION local network: scion@mptcp-over-scion:~/go/src/github.com/scionproto/scion$ ./scion.sh topology -c topology/Tiny.topo Shutting down: Terminating this run of the SCION infrastructure Shut down Stopping jaeger... Compiling... Starting local Bazel server and connecting to it... INFO: Analyzed target //:build-tools (72 packages loaded, 6366 targets configured). INFO: Found 1 target... INFO: Deleting stale sandbox base /home/scion/.cache/bazel/_bazel_scion/2cdd3e64829d6e4629d18c7d46130b39/sandbox Target //:build-tools up-to-date: bazel-bin/build-tools.tar INFO: Elapsed time: 17.730s, Critical Path: 0.50s INFO: 0 processes. INFO: Build completed successfully, 1 total action INFO: Analyzed 2 targets (312 packages loaded, 5259 targets configured). INFO: Found 2 targets... INFO: Elapsed time: 44.028s, Critical Path: 3.30s INFO: 0 processes. INFO: Build completed successfully, 1 total action Create topology, configuration, and execution files. Running jaeger... Loading customer keys... scion@mptcp-over-scion:~/go/src/github.com/scionproto/scion$ ./scion.sh run Compiling... INFO: Analyzed target //:build-tools (0 packages loaded, 0 targets configured). INFO: Found 1 target... Target //:build-tools up-to-date: bazel-bin/build-tools.tar INFO: Elapsed time: 0.536s, Critical Path: 0.00s INFO: 0 processes. INFO: Build completed successfully, 1 total action INFO: Analyzed 2 targets (0 packages loaded, 0 targets configured). INFO: Found 2 targets... INFO: Elapsed time: 1.368s, Critical Path: 0.09s INFO: 0 processes. INFO: Build completed successfully, 1 total action Running the network... scion@mptcp-over-scion:~/go/src/github.com/scionproto/scion$ ./scion.sh status scion@mptcp-over-scion:~/go/src/github.com/scionproto/scion$ c If I check for the listening sockets of the sciond i find the following: scion@mptcp-over-scion:~$ ss -l -x | grep sciond u_seq LISTEN 0 128 /run/shm/sciond/sd1-ff00_0_111.unix 35072 * 0 u_str LISTEN 0 128 /run/shm/sciond/sd1-ff00_0_112.sock 34952 * 0 u_seq LISTEN 0 128 /run/shm/sciond/sd1-ff00_0_112.unix 34955 * 0 u_str LISTEN 0 128 /run/shm/sciond/sd1-ff00_0_110.sock 35014 * 0 u_seq LISTEN 0 128 /run/shm/sciond/sd1-ff00_0_110.unix 35017 * 0 u_str LISTEN 0 128 /run/shm/sciond/sd1-ff00_0_111.sock 35069 If I now set the S/CION_DEAMON_SOCKET/ environment variable as required when running multiple local ASes and try to run /helloworld.go///I run in the following error: scion@mptcp-over-scion:~/go/src/github.com/netsec-ethz/scion-apps/_examples/helloworld$ export SCION_DAEMON_ADDRESS=/run/shm/sciond/sd1-ff00_0_111.sock:35069 scion@mptcp-over-scion:~/go/src/github.com/netsec-ethz/scion-apps/_examples/helloworld$ go run helloworld.go -remote 1-ff00:0:111,[127.0.0.1]:2727 Error initializing SCION network: unable to connect to SCIOND at /run/shm/sciond/sd1-ff00_0_111.sock:35069 (override with SCION_DAEMON_ADDRESS): unable to connect to SCIOND dial tcp: lookup /run/shm/sciond/sd1-ff00_0_111.sock: no such host lookup /run/shm/sciond/sd1-ff00_0_111.sock: no such host exit status 1 I am at my wit's end and would appreciate any help / hint into the right direction very much. What am I doing wrong? Thanks for your effort. Best, Michi

2 1

scion-apps and rains updates
by Frei Matthias 23 Jan '20

23 Jan '20

Hi devs, This concerns developers with active work on github.com/netsec-ethz/scion-apps or github.com/netsec-ethz/rains. Usually we keep the master branch of these repositories in line with the version of SCION run in SCIONLab. Now, in preparation of the next version update for SCIONLab, we will merge changes to master in both of these repositories to build these applications against the current scionproto/scion master. Once the next version for SCIONLab has been fixed, we'll again keep master building against the version in SCIONLab. The branch scionlab will be kept locked to the current version until the SCIONLab updates are completed. If you are building these applications based on master, please be advised that the binaries may or may not be compatible with SCIONLab. Best Regards, Matthias

1 0

Scionlab offline
by Styger Marc 17 Dec '19

17 Dec '19

Good Morning, I can't connect to the Scionlab website as it seems to be offline. I'm in need of one of the tutorials and would therefore really appreciate if somebody looked into it. Thank you in advance. Kind regards, Marc

3 4