Hi there!
I tried running the Pingpong server & client on a local topology, however, when starting either the server or client using
./bin/pingpong -mode server -local 1-ff00:0:110,[127.0.0.1]:400022019-02-25 10:01:20.577699+0000 [CRIT] Unable to initialize SCION network err=
> Unable to initialize SCIOND service
> Unable to connect to SCIOND
> dial unix /run/shm/sciond/default.sock: connect: no such file or directory
- My setup is a bare 16.04 ubuntu virtual machine (managed using vagrant, no port forwarding), roughly after running scion_install_script.sh.
- Logfile keeps showing new entries (tail -f $SC/logs/bs*.DEBUG)
- Most tests pass
I’m not sure what I’m missing, however, I am a bit confused that the error mentions default.sock instead of e.g. sd1-ff00_0_110.sock as it is mentioned in the corresponding sciond.toml endhost file.
Could you help me point in a direction to resolve the error?
Am I correct in the assumption that the local topology is able to run without having to be connected to an actual network?
Thank you very much for your time,
Elwin
You are right, the issue is that you are using the pingpong server / client
with the default settings for the sciond socket location.
When running a local topology, a sciond instance gets created for each AS
and since all of them run on the same host, their sockets cannot all be at
the same default location.
To set the sciond socket path for pingpong, use the `-sciond` flag, e.g.
`./bin/pingpong -sciond /run/shm/sciond/sd1-ff00_0_110.sock -mode server -
local 1-ff00:0:110,[127.0.0.1]:40002`
in your example.
You can learn about other supported flag in applications by running them
with `--help`.
You assumption that the local topology can be run without connection to a
network is correct, all services are started on loopback addresses.
If you followed one of our tutorials and some parts were unclear, feel free to let
us know and open an issue / PR against
https://github.com/netsec-ethz/scion-tutorials/.
Cheers