[SCION] Connection failure w/ sciond on local topology.

Fischer Joel fischjoe at student.ethz.ch
Mon Mar 23 16:24:01 CET 2020


Hi Michi,

As far as I know, Netsec-scion master has switched to TCP based communication with sciond some time ago. The sciond addresses should now look like this: -sciond 127.0.0.12:30255. You can find the sciond addresses in the ISDx/ASy/endhost/sd.toml folder.

This should work on the tiny topology:

SCION_DAEMON_ADDRESS='127.0.0.12:30255' && export SCION_DAEMON_ADDRESS && ./helloworld -remote 1-ff00:0:110,[127.0.0.1]:40002

Cheers,
Joel

> On 23 Mar 2020, at 16:18, Michael A. Flückiger <fmichael at student.ethz.ch> wrote:
> 
> 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 at 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 at 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 at mptcp-over-scion:~/go/src/github.com/scionproto/scion$ ./scion.sh status
> scion at 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 at 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 at 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 at 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
> 
> _______________________________________________
> SCION mailing list
> SCION at lists.inf.ethz.ch
> https://lists.inf.ethz.ch/mailman/listinfo/scion



More information about the SCION mailing list