- SCION - mailman3.inf.ethz.ch

Trouble setting up SCION on Ubuntu 16.04
by Fritz Steinmann 19 Oct '19

19 Oct '19

Hi After trying to install SCION on a virgin 16.04 LTS installation I get the following: fritz@scion-test:~$ ./scion_install_script.sh Starting SCION installation... We are running on Ubuntu version 16.04 seems okay [...] INFO: Found 2 targets... INFO: Elapsed time: 3.774s, Critical Path: 0.18s INFO: 0 processes. INFO: Build completed successfully, 1 total action Create topology, configuration, and execution files. usage: generator.py [-h] [-6] [-c TOPO_CONFIG] [-p PATH_POLICY] [-d] [-n NETWORK] [-o OUTPUT_DIR] [-b BIND_ADDR] [-t] [--pseg-ttl PSEG_TTL] [-bs BEACON_SERVER] [-cs CERT_SERVER] [-sd SCIOND] [-ps PATH_SERVER] [-disp DISPATCHER] [-ds] [-f SVCFRAC] [--random-ifids] [--in-docker] [--docker-registry DOCKER_REGISTRY] [--image-tag IMAGE_TAG] [--sig] generator.py: error: unrecognized arguments: nodocker fritz@scion-test:~$ If I try to create a local topology manually this is what I get: fritz@scion-test:~$ cd $SC fritz@scion-test:~/go/src/github.com/scionproto/scion$ ./scion.sh topology Shutting down: Terminating this run of the SCION infrastructure Shut down Compiling... 2019/10/16 15:18:23 main.go:26: Bazel version: 0.26.1 2019/10/16 15:18:23 main.go:32: Found 78 external dependencies 2019/10/16 15:18:23 main.go:38: Created 78 symlinks in go/vendor/ INFO: Analyzed target //:build-tools (1 packages loaded, 2 targets configured). INFO: Found 1 target... Target //:build-tools up-to-date: bazel-bin/build-tools.tar INFO: Elapsed time: 0.665s, Critical Path: 0.24s INFO: 1 process: 1 linux-sandbox. INFO: Build completed successfully, 3 total actions INFO: Analyzed 2 targets (0 packages loaded, 3423 targets configured). INFO: Found 2 targets... INFO: From Compiling external/com_github_mattn_go_sqlite3/linux_amd64_stripped/go_default_library%linux_amd64%cgo_codegen%/sqlite3.cgo2.c: sqlite3.go:73:1: warning: '_sqlite3_exec' defined but not used [-Wunused-function] INFO: Elapsed time: 30.882s, Critical Path: 8.61s INFO: 483 processes: 483 linux-sandbox. INFO: Build completed successfully, 484 total actions Create topology, configuration, and execution files. Traceback (most recent call last): File "python/topology/generator.py", line 100, in <module> main() File "python/topology/generator.py", line 96, in main confgen.generate_all() File "/home/fritz/go/src/ github.com/scionproto/scion/python/topology/config.py", line 144, in generate_all self._generate_with_topo(topo_dicts) File "/home/fritz/go/src/ github.com/scionproto/scion/python/topology/config.py", line 166, in _generate_with_topo self._generate_go(topo_dicts) File "/home/fritz/go/src/ github.com/scionproto/scion/python/topology/config.py", line 194, in _generate_go go_gen.generate_bs() File "/home/fritz/go/src/github.com/scionproto/scion/python/topology/go.py", line 109, in generate_bs bs_conf = self._build_bs_conf(topo_id, topo["ISD_AS"], base, elem_id, elem) File "/home/fritz/go/src/github.com/scionproto/scion/python/topology/go.py", line 124, in _build_bs_conf 'tracing': self._tracing_entry(), File "/home/fritz/go/src/github.com/scionproto/scion/python/topology/go.py", line 275, in _tracing_entry docker_ip = docker_host(self.args.in_docker, self.args.docker) File "/home/fritz/go/src/ github.com/scionproto/scion/python/topology/common.py", line 180, in docker_host addr = docker_ip() File "/home/fritz/go/src/ github.com/scionproto/scion/python/topology/common.py", line 185, in docker_ip return subprocess.check_output(['tools/docker-ip']).decode("utf-8").strip() File "/usr/lib/python3.5/subprocess.py", line 626, in check_output **kwargs).stdout File "/usr/lib/python3.5/subprocess.py", line 708, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['tools/docker-ip']' returned non-zero exit status 1 fritz@scion-test:~/go/src/github.com/scionproto/scion$ It seems that the "nodocker" option is not correctly parsed by scion.sh or it should not be there anymore at all. What to do next? This is some build information: fritz@scion-test:~/go/src/github.com/scionproto/scion$ uname -a Linux scion-test 4.15.0-1057-azure #62-Ubuntu SMP Thu Sep 5 18:25:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux fritz@scion-test:~/go/src/github.com/scionproto/scion$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" fritz@scion-test:~/go/src/github.com/scionproto/scion$ Regards Fritz

2 3

Re: [Scion] Unable to run SCION after update
by Juan A. García-Pardo 14 Oct '19

14 Oct '19

Hi Siddharth, The scion apps should be available in packaged form next week. In the meantime, you can build them with a Go compiler >= 1.11 by cloning the scion-apps repo, running `./depsh.sh` and then `make` I am testing your 17-ffaa:1:cd2 user AS and it works fine. This are my steps: - Get the configuration from the Coordinator, uncompress it in a directory. Chdir to it - Run `vagrant up`. No errors are shown. Only a few red lines but with no real problems. Last line reads "SCIONLab VM ready" - Run `vagrant ssh` to log into the VM. - Run `ifconfig`. It shows the tun0 interface, with IP "10.0.0.44" - Ping the server using tun0 `ping -I tun0 10.0.8.1`. The server echoes back. - List SCION services with `systemctl list-dependencies scionlab.target` . All services are okay (they are shown duplicated, but it's a know systemd bug, no problems there). - Ping a core AS using SCION `scmp echo -local 17-ffaa:1:cd2,[127.0.0.1] -remote 17-ffaa:0:1101,[127.0.0.1]` . It works okay (for me with times ~6ms; that could change for you). Let's focus on this user AS of yours and find out what is not working. I will run this same configuration again this evening from a completely different network, just to check our firewall has not gone crazy again. I will send an email before I check again, but in the mean time, you could send us your Vagrant version and platform (e.g. vagrant for windows), and the complete /var/log/syslog file of your VM after `vagrant up` and `vagrant ssh`. The problem you seem to have is between the VPN client and server (that is the reason that SCION will not work). You can send the files to the mailing list or directly to me. Best regards, Juan A. On Fri, Sep 27, 2019 at 10:58 AM Siddharth Mehrotra <the4daspect(a)gmail.com> wrote: > Hi Juan, > > The problem still persists. I tried with another AS id's as well > 18-ffaa:1:cd3 & 17-ffaa:1:cd2, however result is same (the border router > service does not start & no tun0 found). > > Also, do you have any update on SCION-Apps? If not all, can webapp be > restored as per SCION update ? > > Best regards, > Siddharth > > On Thu, Sep 26, 2019 at 12:35 PM Juan A. García-Pardo <juagargi(a)gmail.com> > wrote: > > > Hi Siddharth, > > I have answered you also to your email directly, but I'm copying the > answer > > here so it gets indexed. > > There were two problems: > > - We had experienced some problems with our firewall and the VPN in the > > attachment point Switzerland. Sometimes it would drop packets. > > - Your user AS ffaa:1:c32 is marked as deactivated. You have to go to > your > > AS list in the Coordinator (https://www.scionlab.org/user/) and click on > > "Activate this AS". Wait 1-2 minutes and run `vagrant up` for that user > AS. > > Now your ASes should be able to start the VPN tunnel without problems > (type > > ifconfig in the VM and you should see an interface called tun0), and the > > active ones will have a working border router. > > Best regards, > > > > Juan A. > > > > > > On Thu, Sep 19, 2019 at 2:28 PM Siddharth Mehrotra < > the4daspect(a)gmail.com> > > wrote: > > > > > Hi Juan, > > > > > > Thanks for the update, it is really helpful. > > > > > > 1) After checking status of my connection to SCION, I see > > > ● ├─scion-border-router(a)17-ffaa_1_c32-1.service > > > ● ├─scion-border-router(a)17-ffaa_1_c32-1.service > > > > > > as marked RED in color. I could not understand why this happened on > first > > > place, just after running vagrant ssh and systemctl list-dependencies > > > scionlab.target > > > > > > This appears even after restarting SCION services. > > > > > > 2) Still I can't find tun0 while running command ip a. The only tunnel > > > interfaces appearing are: lo & enp0s3. > > > > > > 3) Is Scion web-app available? > > > I get this error: -bash: cd: /src/github.com/netsec-ethz: No such file > > or > > > directory while navigating to web-apps. > > > > > > PS: Running SCION in a virtual machine – VPN approach > > > > > > Thanks, > > > Siddharth > > > > > > On Thu, Sep 19, 2019 at 1:01 PM Juan A. García-Pardo < > juagargi(a)gmail.com > > > > > > wrote: > > > > > > > Hi Siddharth, > > > > We have not yet upgraded the tutorials for everything, only the > > "updating > > > > SCION" one: > > > > > > > > > > https://netsec-ethz.github.io/scion-tutorials/scion_tricks/updating_scion/ > > > > That said, almost all that you are seeing is normal: the > configuration > > > TGZ > > > > you get from the Coordinator is very small, because your VM will get > > the > > > > full configuration from the Coordinator for you. Once you have run > > > `vagrant > > > > up`, you will see the directory /etc/scion contains a `gen` directory > > > > inside. That one will have the full configuration. > > > > Also, the services and tools are now packaged. There is no $SC > > directory > > > > anymore. Things you can run to check: > > > > - dpkg -l |grep scion # will list scion packages, hopefully > installed > > in > > > > your system > > > > - systemctl list-dependencies scionlab.target # list status. In > Ubuntu > > > > 16.04 there is a systemd bug and the services will be listed twice > > > > - sudo systemctl restart scionlab.target # restart all SCION > services > > > > - ls -l /var/log/scion # list scion log files > > > > - ls -l /var/lib/scion # list trust databases, etc > > > > - ls -l /etc/scion # list scion configuration. The gen folder has > the > > > > same morphology as before, but the supervisord files are not used > > > > > > > > On the other hand, if you want to not use the packages and go back to > > the > > > > developer way of doing things, you can briefly read about that also > in > > > the > > > > how to update SCION page from SCION tutorials, but basically refers > to > > > > stopping systemd for scionlab.target and cloning/building SCION > > yourself. > > > > > > > > The problem with the VPN is not clear at all though. I would like to > > > > investigate a bit more about that. Can you try again? If you still > see > > > the > > > > problem the second time you try, we'll investigate further. > > > > Thanks and best regards, > > > > > > > > Juan A. > > > > > > > > > > > > On Wed, Sep 18, 2019 at 10:52 AM Siddharth Mehrotra < > > > the4daspect(a)gmail.com> > > > > wrote: > > > > > > > >> Hi all, > > > >> > > > >> I tried to run SCION after update from attachment point with ETHZ-AP > > as > > > >> downloading new configuration. I'm currently installing inside a VM > > with > > > >> use of OPENVPN to connect to SCION Lab. > > > >> > > > >> I observed following scenarios: > > > >> > > > >> 1) After extracting configuration file from SCION coordination > > service, > > > >> the > > > >> contents are reduced to: > > > >> Mode LastWriteTime Length Name > > > >> ---- ------------- ------ ---- > > > >> d----- 18-09-2019 10:25 .vagrant > > > >> d----- 18-09-2019 10:23 gen > > > >> -a---- 13-06-2019 09:25 3618 README.md > > > >> -a---- 13-06-2019 09:25 3068 run.sh > > > >> -a---- 18-09-2019 10:22 3813 > > > >> scion_lab_17-ffaa_1_c32.tar.gz > > > >> -a---- 18-09-2019 10:34 0 > > > >> ubuntu-xenial-16.04-cloudimg-console.log > > > >> -a---- 18-09-2019 10:24 2484 Vagrantfile > > > >> > > > >> Many SCION services are missing. > > > >> > > > >> 2) Although I was able to run the VM successfully and SSH to SCION. > > > >> However, it seems the connection to SCION was not successful. The > > below > > > >> command is after running Vagrant up: > > > >> > > > >> default: WARNING:WARNING!: VPN could be unready. SCION may fail to > > > start. > > > >> default: Created symlink from > > > >> > > > >> > > > > > > /etc/systemd/system/scionlab.target.wants/scion-border-router(a)17-ffaa_1_c32-1.service > > > >> to /lib/systemd/system/scion-border-router@.service. > > > >> default: Created symlink from > > > >> > > > >> > > > > > > /etc/systemd/system/scionlab.target.wants/scion-certificate-server(a)17-ffaa_1_c32-1.service > > > >> to /lib/systemd/system/scion-certificate-server@.service. > > > >> default: Created symlink from > > > >> > > > >> > > > > > > /etc/systemd/system/scionlab.target.wants/scion-path-server(a)17-ffaa_1_c32-1.service > > > >> to /lib/systemd/system/scion-path-server@.service. > > > >> default: Created symlink from > > > >> > > > >> > > > > > > /etc/systemd/system/scionlab.target.wants/scion-beacon-server(a)17-ffaa_1_c32-1.service > > > >> to /lib/systemd/system/scion-beacon-server@.service. > > > >> default: Created symlink from > > > >> > > > >> > > > > > > /etc/systemd/system/scionlab.target.wants/scion-daemon(a)17-ffaa_1_c32.service > > > >> to /lib/systemd/system/scion-daemon@.service. > > > >> default: Created symlink from > > > >> /etc/systemd/system/scionlab.target.wants/scion-dispatcher.service > to > > > >> /lib/systemd/system/scion-dispatcher.service. > > > >> default: configure time sync > > > >> default: ntp.service is not a native service, redirecting to > > > >> systemd-sysv-install > > > >> default: Executing /lib/systemd/systemd-sysv-install enable ntp > > > >> default: configure unattended upgrades (automatic security > > upgrades) > > > >> default: SCIONLab VM ready > > > >> > > > >> 3) When I am inside the VM and I tried to check the connection I was > > > >> surprised to see this: > > > >> > > > >> vagrant@scionlab-ffaa-1-c32:~$ checkbeacons > > > >> checkbeacons: command not found > > > >> > > > >> Also fo this: > > > >> vagrant@scionlab-ffaa-1-c32:~$ tail -f $SC/logs/bs*.DEBUG > > > >> tail: cannot open '/logs/bs*.DEBUG' for reading: No such file or > > > directory > > > >> tail: no files remaining > > > >> > > > >> 4)Memory Test: > > > >> vagrant@scionlab-ffaa-1-c32:~$ df -h > > > >> Filesystem Size Used Avail Use% Mounted on > > > >> udev 992M 0 992M 0% /dev > > > >> tmpfs 200M 3.1M 197M 2% /run > > > >> /dev/sda1 9.7G 1.4G 8.3G 14% / > > > >> tmpfs 1000M 0 1000M 0% /dev/shm > > > >> tmpfs 5.0M 0 5.0M 0% /run/lock > > > >> tmpfs 1000M 0 1000M 0% /sys/fs/cgroup > > > >> vagrant 136G 73G 64G 54% /vagrant > > > >> tmpfs 200M 0 200M 0% /run/user/1000 > > > >> > > > >> 5) tun0 not found after performing ip a command. > > > >> > > > >> PS: I am using Oracle Virtual Box 6.0 , Is it the compatibility > issue > > ? > > > >> PS: I was able to run SCION successfully before the update with same > > > >> Virtual Box version and vagrant also. > > > >> > > > >> Please look into this issue. > > > >> > > > >> Thanks, > > > >> Sid > > > >> _______________________________________________ > > > >> Scion mailing list > > > >> Scion(a)lists.inf.ethz.ch > > > >> https://lists.inf.ethz.ch/mailman/listinfo/scion > > > >> > > > > > > > _______________________________________________ > > > Scion mailing list > > > Scion(a)lists.inf.ethz.ch > > > https://lists.inf.ethz.ch/mailman/listinfo/scion > > > > > _______________________________________________ > > Scion mailing list > > Scion(a)lists.inf.ethz.ch > > https://lists.inf.ethz.ch/mailman/listinfo/scion > > > _______________________________________________ > Scion mailing list > Scion(a)lists.inf.ethz.ch > https://lists.inf.ethz.ch/mailman/listinfo/scion >

6 15

Trouble running Scion ip Gateway
by tony.john＠st.ovgu.de 12 Oct '19

12 Oct '19

Hi, I am trying to establish a SiG connection between to ASs. I am using the latest scion packages on dedicated systems. Using scmp echo I was able to communicate between the two ASs on all paths as you can see below: --------- pi@pi:~$ scmp echo -local 19-ffaa:1:bf9,[127.0.0.1] -remote 19-ffaa:1:cc5,[127.0.0.1] -i Available paths to 19-ffaa:1:cc5 [ 0] Hops: [19-ffaa:1:bf9 3>3 19-ffaa:1:cc5] Mtu: 1472 [ 1] Hops: [19-ffaa:1:bf9 2>2 19-ffaa:1:cc5] Mtu: 1472 [ 2] Hops: [19-ffaa:1:bf9 2>2 19-ffaa:1:cc5] Mtu: 1472 [ 3] Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472 [ 4] Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472 [ 5] Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472 [ 6] Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472 Choose path: 2 Using path: Hops: [19-ffaa:1:bf9 2>2 19-ffaa:1:cc5] Mtu: 1472 104 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=0 time=121.702ms 104 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=1 time=123.761ms 104 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=2 time=43.372ms 104 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=3 time=18.329ms 104 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=4 time=90.571ms ^C --- 19-ffaa:1:cc5,[[127.0.0.1]] statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4.998055s pi@pi:~$ scmp echo -local 19-ffaa:1:bf9,[127.0.0.1] -remote 19-ffaa:1:cc5,[127.0.0.1] -i Available paths to 19-ffaa:1:cc5 [ 0] Hops: [19-ffaa:1:bf9 3>3 19-ffaa:1:cc5] Mtu: 1472 [ 1] Hops: [19-ffaa:1:bf9 2>2 19-ffaa:1:cc5] Mtu: 1472 [ 2] Hops: [19-ffaa:1:bf9 2>2 19-ffaa:1:cc5] Mtu: 1472 [ 3] Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472 [ 4] Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472 [ 5] Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472 [ 6] Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472 Choose path: 3 Using path: Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472 136 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=0 time=13.719ms 136 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=1 time=118.26ms 136 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=2 time=38.635ms 136 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=3 time=10.83ms 136 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=4 time=86.594ms 136 bytes from 19-ffaa:1:cc5,[127.0.0.1] scmp_seq=5 time=11.096ms -------------- But when I try running SiG on both ASs, I am getting the following error: -------------- 2019-10-04 11:50:13.601219+0000 [INFO] =====================> Service started SIG sigA Scion version: v0.3.1-786-g854eb00-dirty In docker: false pid: 16262 euid/egid: 1000 1000 cmd line: ["/home/pi/go/src/github.com/scionproto/scion/bin/sig" "-config=/home/pi/code/sig19-ffaa_1_bf9-1/sigPi.config"] 2019-10-04 11:50:13.603157+0000 [INFO] Startup capabilities caps="{ effective="net_admin" permitted="net_admin" inheritable="empty" bounding="full" }" 2019-10-04 11:50:13.608800+0000 [DBUG] Registered with dispatcher addr="19-ffaa:1:bf9,[172.16.0.11]:10081 (UDP)" 2019-10-04 11:50:13.614848+0000 [INFO] ReloadConfig: Adding AS... ia=19-ffaa:1:cc5 2019-10-04 11:50:14.511594+0000 [INFO] Starting periodic task debug_id=e024f404 task=pathmgr.taskPeriodicChannelWriter 2019-10-04 11:50:14.513580+0000 [DBUG] Registered with dispatcher addr="19-ffaa:1:bf9,[172.16.0.11]:13076 (UDP)" 2019-10-04 11:50:14.514253+0000 [INFO] Network setup done ia=19-ffaa:1:cc5 2019-10-04 11:50:14.514370+0000 [INFO] EgressDispatcher: starting ia=19-ffaa:1:cc5 2019-10-04 11:50:14.514419+0000 [INFO] Added network ia=19-ffaa:1:cc5 net=172.16.12.0/24 2019-10-04 11:50:14.514680+0000 [INFO] ReloadConfig: Added AS ia=19-ffaa:1:cc5 2019-10-04 11:50:14.514308+0000 [INFO] Health monitor starting ia=19-ffaa:1:cc5 2019-10-04 11:50:14.514603+0000 [INFO] EgressWorker: starting ia=19-ffaa:1:cc5 sessId=0x00 2019-10-04 11:50:14.514851+0000 [INFO] PollReqHdlr: starting 2019-10-04 11:50:14.750068+0000 [INFO] EgressReader: starting 2019-10-04 11:50:14.750391+0000 [EROR] EgressReader: unable to find dest IA ip=ff02::2 2019-10-04 11:50:14.750249+0000 [INFO] Exporting prometheus metrics addr=127.0.0.1:1281 2019-10-04 11:50:14.752750+0000 [DBUG] Registered with dispatcher addr="19-ffaa:1:bf9,[172.16.0.11]:10080 (UDP)" 2019-10-04 11:50:15.014610+0000 [INFO] sessMonitor: Path not available ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: <nil>" 2019-10-04 11:50:15.015126+0000 [INFO] sessMonitor: New remote ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: eeacec476eff43e8a209f188639c337c8510f6f819dfd6dc93531624f34809d7 Hops: [19-ffaa:1:bf9 3>3 19-ffaa:1:cc5] Mtu: 1472" 2019-10-04 11:50:15.021469+0000 [INFO] Received SCMP revocation header="Class=PATH(3) Type=REVOKED_IF(4) TotalLen=272B Checksum=a59d Timestamp=2019-10-04 11:50:15.018886 +0000 UTC" payload= Meta: Info=22 CmnHdr=1 AddrHdr=3 PathHdr=4 ExtHdrs=0 L4Hdr=1 L4Proto=UDP Info: InfoF=4 HopF=5 IfID=3 Ingress=false SRev=SignedRevInfo: RevInfo: IA: 19-ffaa:1:bf9 IfID: 3 Link type: parent Timestamp: 2019-10-04 11:50:00+0000 TTL: 20s Sign: SignType: ed25519 Timestamp: 2019-10-04 11:50:00.000000+0000 SignSrc: 44454641554c543a2049413a2031392d666661613a313a62663920434841494e3a2034205452433a2032 Signature: 816541ac8d3aae388aa7b14eacf360275aa4c030bea0b9e9de2edb3a3d62499fc1cec71cf8c7e334e7fdbee7d111b6e935519bc90da49c3e51f98e8c652f9b0f CmnHdr: 00c1008f08040511 AddrHdr: 0013ffaa00010cc50013ffaa00010bf90004ac10000b0000 PathHdr: 025d971331001303003f00300027431f003f001003cfb26a023f001088c2e03f ExtHdrs: L4Hdr: 33140000004f63d9 src="{IA:19-ffaa:1:bf9 Host:127.0.0.2}" 2019-10-04 11:50:15.033965+0000 [EROR] PktDispatcher: Error reading from connection err="Class=PATH(3) Type=REVOKED_IF(4) TotalLen=272B Checksum=a59d Timestamp=2019-10-04 11:50:15.018886 +0000 UTC" 2019-10-04 11:50:15.514720+0000 [INFO] sessMonitor: Remote SIG timeout ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: eeacec476eff43e8a209f188639c337c8510f6f819dfd6dc93531624f34809d7 Hops: [19-ffaa:1:bf9 3>3 19-ffaa:1:cc5] Mtu: 1472" duration=1.000186927s 2019-10-04 11:50:15.515306+0000 [INFO] sessMonitor: New remote ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: 48590cdb71348785f74aa91b7335926767d237b7576c14b3bdac6bd8a36659d9 Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472" 2019-10-04 11:50:15.631439+0000 [DBUG] Ignoring scmp packet hdr="Class=ROUTING(1) Type=UNREACH_HOST(1) TotalLen=64B Checksum=4d5d Timestamp=2019-10-04 11:50:04.768553 +0000 UTC" src="{IA:19-ffaa:1:cc5 Host:127.0.0.1}" 2019-10-04 11:50:16.014680+0000 [INFO] sessMonitor: Remote SIG timeout ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: 48590cdb71348785f74aa91b7335926767d237b7576c14b3bdac6bd8a36659d9 Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472" duration=1.500148281s 2019-10-04 11:50:16.015236+0000 [INFO] sessMonitor: New remote ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: 284d707379218d7d0ab6489aad3633f758bacc4ce9c1ee104236f403c2e7c68f Hops: [19-ffaa:1:bf9 2>2 19-ffaa:1:cc5] Mtu: 1472" 2019-10-04 11:50:16.035066+0000 [DBUG] Ignoring scmp packet hdr="Class=ROUTING(1) Type=UNREACH_HOST(1) TotalLen=64B Checksum=a224 Timestamp=2019-10-04 11:50:05.165012 +0000 UTC" src="{IA:19-ffaa:1:cc5 Host:127.0.0.2}" 2019-10-04 11:50:16.514605+0000 [INFO] sessMonitor: Remote SIG timeout ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: 284d707379218d7d0ab6489aad3633f758bacc4ce9c1ee104236f403c2e7c68f Hops: [19-ffaa:1:bf9 2>2 19-ffaa:1:cc5] Mtu: 1472" duration=2.000074114s 2019-10-04 11:50:16.515046+0000 [INFO] sessMonitor: New remote ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: 48590cdb71348785f74aa91b7335926767d237b7576c14b3bdac6bd8a36659d9 Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472" 2019-10-04 11:50:16.548947+0000 [DBUG] Ignoring scmp packet hdr="Class=ROUTING(1) Type=UNREACH_HOST(1) TotalLen=64B Checksum=0424 Timestamp=2019-10-04 11:50:05.68956 +0000 UTC" src="{IA:19-ffaa:1:cc5 Host:127.0.0.1}" 2019-10-04 11:50:17.014758+0000 [INFO] sessMonitor: Remote SIG timeout ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: 48590cdb71348785f74aa91b7335926767d237b7576c14b3bdac6bd8a36659d9 Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472" duration=2.500223177s 2019-10-04 11:50:17.015689+0000 [INFO] sessMonitor: New remote ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: 284d707379218d7d0ab6489aad3633f758bacc4ce9c1ee104236f403c2e7c68f Hops: [19-ffaa:1:bf9 2>2 19-ffaa:1:cc5] Mtu: 1472" 2019-10-04 11:50:17.051498+0000 [DBUG] Ignoring scmp packet hdr="Class=ROUTING(1) Type=UNREACH_HOST(1) TotalLen=64B Checksum=40fa Timestamp=2019-10-04 11:50:06.165648 +0000 UTC" src="{IA:19-ffaa:1:cc5 Host:127.0.0.2}" 2019-10-04 11:50:17.514665+0000 [INFO] sessMonitor: Remote SIG timeout ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: 284d707379218d7d0ab6489aad3633f758bacc4ce9c1ee104236f403c2e7c68f Hops: [19-ffaa:1:bf9 2>2 19-ffaa:1:cc5] Mtu: 1472" duration=3.000134478s 2019-10-04 11:50:17.515127+0000 [INFO] sessMonitor: New remote ia=19-ffaa:1:cc5 sessId=0x00 remote="Sig: 19-ffaa:1:cc5,[SIG A (0x0004)]:0:0 Path: Key: 48590cdb71348785f74aa91b7335926767d237b7576c14b3bdac6bd8a36659d9 Hops: [19-ffaa:1:bf9 1>101 19-ffaa:0:1303 136>1 19-ffaa:1:cc5] Mtu: 1472" 2019-10-04 11:50:17.539334+0000 [DBUG] Ignoring scmp packet hdr="Class=ROUTING(1) Type=UNREACH_HOST(1) TotalLen=64B Checksum=7092 Timestamp=2019-10-04 ------------------------ I have successfully run sig with these configurations a few months back. Kindly help me understand the problem. Thanks and regards, Tony

1 1

Rebuilding the .deb
by Benjamin Hof 05 Oct '19

05 Oct '19

Hi, I'd like to rebuild the .deb files in the vein of Reproducible Builds [1]. I couldn't find public build instructions and .buildinfo files. Are those available? Kind regards, Benjamin 1: https://reproducible-builds.org/

2 1

Re: [Scion] Unable to run SCION after update
by Juan A. García-Pardo 30 Sep '19

30 Sep '19

Hi Siddharth, The correct path is $HOME/go/src/github.com/netsec-ethz/scion-apps , not $HOME/go/src/scion-apps Best regards, Juan A. On Mon, Sep 30, 2019 at 12:38 PM Siddharth Mehrotra <the4daspect(a)gmail.com> wrote: > Hi Juan & Claude, > > I think Claude is right, I am facing some issue with Go Path. > > So, currently I have cloned scion-apps under go/src/scion-apps. The > ./deps.sh worked perfectly fine. The issue is with make. It can not find > package in $GOPATH. > At github webpage, it is mentioned that run make install to build all > projects and install into $GOPATH/bin > > My GOPATH settings are: > export GOPATH=$HOME/go > export PATH=$PATH:$GOPATH/bin > > Does it mean that I need to clone the scion-apps in go/bin ? Sorry, I am > new to Go Programming. > > Best, > Siddharth > > On Fri, Sep 27, 2019 at 2:33 PM Claude Hähni <claude.haehni(a)gmail.com> > wrote: > > > Hi Siddharth, > > When cloning, please make sure to clone the repository to the correct > > location. In your case this is: > > /home/vagrant/go/src/github.com/netsec-ethz/scion-apps > > > > Best regards, > > Claude > > > > Juan A. García-Pardo <juagargi(a)gmail.com> schrieb am Fr., 27. Sep. 2019, > > 14:21: > > > >> Hi Siddharth, > >> We didn't touch scion-apps/lib/scionutil and it still exists. If you are > >> building scion-apps in a SCIONLab VM, these are the steps you would > need: > >> - install go 1.11 > >> - `go get github.com/kardianos/govendor` > <http://github.com/kardianos/govendor> > >> <http://github.com/kardianos/govendor> > >> - `sudo apt-get install libpam0g-dev` (needed by SCION ssh) > >> - clone scion-apps > >> - `govendor sync -v` (this needs some 5 minutes to complete). You can > run > >> ./deps.sh instead, it is going to do the same. > >> - `make` > >> > >> I just ran these steps myself inside a SCIONLab VM and it worked okay. > >> Best regards, > >> > >> Juan A. > >> > >> > >> On Fri, Sep 27, 2019 at 12:21 PM Siddharth Mehrotra < > >> the4daspect(a)gmail.com> > >> wrote: > >> > >> > Hi Juan, > >> > > >> > Thanks for the help. SCION works now! > >> > > >> > Regarding webapp, I tried to compile all scion-apps by ./deps.sh by > >> > installing go => This is done. > >> > > >> > However, make install command runs into error: > >> > cd helloworld/ && go build > >> > helloworld.go:23:2: cannot find package " > >> > github.com/netsec-ethz/scion-apps/lib/scionutil" in any of: > >> > /home/vagrant/go/src/scion-apps/vendor/ > >> > github.com/netsec-ethz/scion-apps/lib/scionutil (vendor tree) > >> > /usr/local/go/src/ > >> github.com/netsec-ethz/scion-apps/lib/scionutil > >> > (from $GOROOT) > >> > /home/vagrant/go/src/ > >> > github.com/netsec-ethz/scion-apps/lib/scionutil (from $GOPATH) > >> > Makefile:29: recipe for target 'helloworld/helloworld' failed > >> > make: *** [helloworld/helloworld] Error 1 > >> > > >> > This is becaus github.com/netsec-ethz/scion-apps/lib/scionutil does > >> not > >> > exist anymore. I am not sure if this is still required. *Can a quick > >> > update be performed in github code regarding same ?* > >> > > >> > Best Regards, > >> > Siddharth > >> > > >> > On Fri, Sep 27, 2019 at 11:34 AM Juan A. García-Pardo < > >> juagargi(a)gmail.com> > >> > wrote: > >> > > >> >> Hi Siddharth, > >> >> The scion apps should be available in packaged form next week. In the > >> >> meantime, you can build them with a Go compiler >= 1.11 by cloning > the > >> >> scion-apps repo, running `./depsh.sh` and then `make` > >> >> I am testing your 17-ffaa:1:cd2 user AS and it works fine. This are > my > >> >> steps: > >> >> - Get the configuration from the Coordinator, uncompress it in a > >> >> directory. Chdir to it > >> >> - Run `vagrant up`. No errors are shown. Only a few red lines but > with > >> no > >> >> real problems. Last line reads "SCIONLab VM ready" > >> >> - Run `vagrant ssh` to log into the VM. > >> >> - Run `ifconfig`. It shows the tun0 interface, with IP "10.0.0.44" > >> >> - Ping the server using tun0 `ping -I tun0 10.0.8.1`. The server > echoes > >> >> back. > >> >> - List SCION services with `systemctl list-dependencies > >> scionlab.target` > >> >> . All services are okay (they are shown duplicated, but it's a know > >> systemd > >> >> bug, no problems there). > >> >> - Ping a core AS using SCION `scmp echo -local > >> 17-ffaa:1:cd2,[127.0.0.1] > >> >> -remote 17-ffaa:0:1101,[127.0.0.1]` . It works okay (for me with > times > >> >> ~6ms; that could change for you). > >> >> > >> >> Let's focus on this user AS of yours and find out what is not > working. > >> I > >> >> will run this same configuration again this evening from a completely > >> >> different network, just to check our firewall has not gone crazy > >> again. I > >> >> will send an email before I check again, but in the mean time, you > >> could > >> >> send us your Vagrant version and platform (e.g. vagrant for windows), > >> and > >> >> the complete /var/log/syslog file of your VM after `vagrant up` and > >> >> `vagrant ssh`. The problem you seem to have is between the VPN client > >> and > >> >> server (that is the reason that SCION will not work). You can send > the > >> >> files to the mailing list or directly to me. > >> >> Best regards, > >> >> > >> >> Juan A. > >> >> > >> >> > >> >> On Fri, Sep 27, 2019 at 10:58 AM Siddharth Mehrotra < > >> >> the4daspect(a)gmail.com> wrote: > >> >> > >> >>> Hi Juan, > >> >>> > >> >>> The problem still persists. I tried with another AS id's as well > >> >>> 18-ffaa:1:cd3 & 17-ffaa:1:cd2, however result is same (the border > >> router > >> >>> service does not start & no tun0 found). > >> >>> > >> >>> Also, do you have any update on SCION-Apps? If not all, can webapp > be > >> >>> restored as per SCION update ? > >> >>> > >> >>> Best regards, > >> >>> Siddharth > >> >>> > >> >>> On Thu, Sep 26, 2019 at 12:35 PM Juan A. García-Pardo < > >> >>> juagargi(a)gmail.com> > >> >>> wrote: > >> >>> > >> >>> > Hi Siddharth, > >> >>> > I have answered you also to your email directly, but I'm copying > the > >> >>> answer > >> >>> > here so it gets indexed. > >> >>> > There were two problems: > >> >>> > - We had experienced some problems with our firewall and the VPN > in > >> the > >> >>> > attachment point Switzerland. Sometimes it would drop packets. > >> >>> > - Your user AS ffaa:1:c32 is marked as deactivated. You have to go > >> to > >> >>> your > >> >>> > AS list in the Coordinator (https://www.scionlab.org/user/) and > >> click > >> >>> on > >> >>> > "Activate this AS". Wait 1-2 minutes and run `vagrant up` for that > >> >>> user AS. > >> >>> > Now your ASes should be able to start the VPN tunnel without > >> problems > >> >>> (type > >> >>> > ifconfig in the VM and you should see an interface called tun0), > and > >> >>> the > >> >>> > active ones will have a working border router. > >> >>> > Best regards, > >> >>> > > >> >>> > Juan A. > >> >>> > > >> >>> > > >> >>> > On Thu, Sep 19, 2019 at 2:28 PM Siddharth Mehrotra < > >> >>> the4daspect(a)gmail.com> > >> >>> > wrote: > >> >>> > > >> >>> > > Hi Juan, > >> >>> > > > >> >>> > > Thanks for the update, it is really helpful. > >> >>> > > > >> >>> > > 1) After checking status of my connection to SCION, I see > >> >>> > > ● ├─scion-border-router(a)17-ffaa_1_c32-1.service > >> >>> > > ● ├─scion-border-router(a)17-ffaa_1_c32-1.service > >> >>> > > > >> >>> > > as marked RED in color. I could not understand why this happened > >> on > >> >>> first > >> >>> > > place, just after running vagrant ssh and systemctl > >> >>> list-dependencies > >> >>> > > scionlab.target > >> >>> > > > >> >>> > > This appears even after restarting SCION services. > >> >>> > > > >> >>> > > 2) Still I can't find tun0 while running command ip a. The only > >> >>> tunnel > >> >>> > > interfaces appearing are: lo & enp0s3. > >> >>> > > > >> >>> > > 3) Is Scion web-app available? > >> >>> > > I get this error: -bash: cd: /src/github.com/netsec-ethz: No > such > >> >>> file > >> >>> > or > >> >>> > > directory while navigating to web-apps. > >> >>> > > > >> >>> > > PS: Running SCION in a virtual machine – VPN approach > >> >>> > > > >> >>> > > Thanks, > >> >>> > > Siddharth > >> >>> > > > >> >>> > > On Thu, Sep 19, 2019 at 1:01 PM Juan A. García-Pardo < > >> >>> juagargi(a)gmail.com > >> >>> > > > >> >>> > > wrote: > >> >>> > > > >> >>> > > > Hi Siddharth, > >> >>> > > > We have not yet upgraded the tutorials for everything, only > the > >> >>> > "updating > >> >>> > > > SCION" one: > >> >>> > > > > >> >>> > > > >> >>> > > >> >>> > >> > https://netsec-ethz.github.io/scion-tutorials/scion_tricks/updating_scion/ > >> >>> > > > That said, almost all that you are seeing is normal: the > >> >>> configuration > >> >>> > > TGZ > >> >>> > > > you get from the Coordinator is very small, because your VM > will > >> >>> get > >> >>> > the > >> >>> > > > full configuration from the Coordinator for you. Once you have > >> run > >> >>> > > `vagrant > >> >>> > > > up`, you will see the directory /etc/scion contains a `gen` > >> >>> directory > >> >>> > > > inside. That one will have the full configuration. > >> >>> > > > Also, the services and tools are now packaged. There is no $SC > >> >>> > directory > >> >>> > > > anymore. Things you can run to check: > >> >>> > > > - dpkg -l |grep scion # will list scion packages, hopefully > >> >>> installed > >> >>> > in > >> >>> > > > your system > >> >>> > > > - systemctl list-dependencies scionlab.target # list status. > In > >> >>> Ubuntu > >> >>> > > > 16.04 there is a systemd bug and the services will be listed > >> twice > >> >>> > > > - sudo systemctl restart scionlab.target # restart all SCION > >> >>> services > >> >>> > > > - ls -l /var/log/scion # list scion log files > >> >>> > > > - ls -l /var/lib/scion # list trust databases, etc > >> >>> > > > - ls -l /etc/scion # list scion configuration. The gen folder > >> has > >> >>> the > >> >>> > > > same morphology as before, but the supervisord files are not > >> used > >> >>> > > > > >> >>> > > > On the other hand, if you want to not use the packages and go > >> back > >> >>> to > >> >>> > the > >> >>> > > > developer way of doing things, you can briefly read about that > >> >>> also in > >> >>> > > the > >> >>> > > > how to update SCION page from SCION tutorials, but basically > >> >>> refers to > >> >>> > > > stopping systemd for scionlab.target and cloning/building > SCION > >> >>> > yourself. > >> >>> > > > > >> >>> > > > The problem with the VPN is not clear at all though. I would > >> like > >> >>> to > >> >>> > > > investigate a bit more about that. Can you try again? If you > >> still > >> >>> see > >> >>> > > the > >> >>> > > > problem the second time you try, we'll investigate further. > >> >>> > > > Thanks and best regards, > >> >>> > > > > >> >>> > > > Juan A. > >> >>> > > > > >> >>> > > > > >> >>> > > > On Wed, Sep 18, 2019 at 10:52 AM Siddharth Mehrotra < > >> >>> > > the4daspect(a)gmail.com> > >> >>> > > > wrote: > >> >>> > > > > >> >>> > > >> Hi all, > >> >>> > > >> > >> >>> > > >> I tried to run SCION after update from attachment point with > >> >>> ETHZ-AP > >> >>> > as > >> >>> > > >> downloading new configuration. I'm currently installing > inside > >> a > >> >>> VM > >> >>> > with > >> >>> > > >> use of OPENVPN to connect to SCION Lab. > >> >>> > > >> > >> >>> > > >> I observed following scenarios: > >> >>> > > >> > >> >>> > > >> 1) After extracting configuration file from SCION > coordination > >> >>> > service, > >> >>> > > >> the > >> >>> > > >> contents are reduced to: > >> >>> > > >> Mode LastWriteTime Length Name > >> >>> > > >> ---- ------------- ------ ---- > >> >>> > > >> d----- 18-09-2019 10:25 .vagrant > >> >>> > > >> d----- 18-09-2019 10:23 gen > >> >>> > > >> -a---- 13-06-2019 09:25 3618 README.md > >> >>> > > >> -a---- 13-06-2019 09:25 3068 run.sh > >> >>> > > >> -a---- 18-09-2019 10:22 3813 > >> >>> > > >> scion_lab_17-ffaa_1_c32.tar.gz > >> >>> > > >> -a---- 18-09-2019 10:34 0 > >> >>> > > >> ubuntu-xenial-16.04-cloudimg-console.log > >> >>> > > >> -a---- 18-09-2019 10:24 2484 Vagrantfile > >> >>> > > >> > >> >>> > > >> Many SCION services are missing. > >> >>> > > >> > >> >>> > > >> 2) Although I was able to run the VM successfully and SSH to > >> >>> SCION. > >> >>> > > >> However, it seems the connection to SCION was not successful. > >> The > >> >>> > below > >> >>> > > >> command is after running Vagrant up: > >> >>> > > >> > >> >>> > > >> default: WARNING:WARNING!: VPN could be unready. SCION may > >> fail to > >> >>> > > start. > >> >>> > > >> default: Created symlink from > >> >>> > > >> > >> >>> > > >> > >> >>> > > > >> >>> > > >> >>> > >> > /etc/systemd/system/scionlab.target.wants/scion-border-router(a)17-ffaa_1_c32-1.service > >> >>> > > >> to /lib/systemd/system/scion-border-router@.service. > >> >>> > > >> default: Created symlink from > >> >>> > > >> > >> >>> > > >> > >> >>> > > > >> >>> > > >> >>> > >> > /etc/systemd/system/scionlab.target.wants/scion-certificate-server(a)17-ffaa_1_c32-1.service > >> >>> > > >> to /lib/systemd/system/scion-certificate-server@.service. > >> >>> > > >> default: Created symlink from > >> >>> > > >> > >> >>> > > >> > >> >>> > > > >> >>> > > >> >>> > >> > /etc/systemd/system/scionlab.target.wants/scion-path-server(a)17-ffaa_1_c32-1.service > >> >>> > > >> to /lib/systemd/system/scion-path-server@.service. > >> >>> > > >> default: Created symlink from > >> >>> > > >> > >> >>> > > >> > >> >>> > > > >> >>> > > >> >>> > >> > /etc/systemd/system/scionlab.target.wants/scion-beacon-server(a)17-ffaa_1_c32-1.service > >> >>> > > >> to /lib/systemd/system/scion-beacon-server@.service. > >> >>> > > >> default: Created symlink from > >> >>> > > >> > >> >>> > > >> > >> >>> > > > >> >>> > > >> >>> > >> > /etc/systemd/system/scionlab.target.wants/scion-daemon(a)17-ffaa_1_c32.service > >> >>> > > >> to /lib/systemd/system/scion-daemon@.service. > >> >>> > > >> default: Created symlink from > >> >>> > > >> > >> >>> /etc/systemd/system/scionlab.target.wants/scion-dispatcher.service > to > >> >>> > > >> /lib/systemd/system/scion-dispatcher.service. > >> >>> > > >> default: configure time sync > >> >>> > > >> default: ntp.service is not a native service, redirecting > >> to > >> >>> > > >> systemd-sysv-install > >> >>> > > >> default: Executing /lib/systemd/systemd-sysv-install > enable > >> >>> ntp > >> >>> > > >> default: configure unattended upgrades (automatic > security > >> >>> > upgrades) > >> >>> > > >> default: SCIONLab VM ready > >> >>> > > >> > >> >>> > > >> 3) When I am inside the VM and I tried to check the > connection > >> I > >> >>> was > >> >>> > > >> surprised to see this: > >> >>> > > >> > >> >>> > > >> vagrant@scionlab-ffaa-1-c32:~$ checkbeacons > >> >>> > > >> checkbeacons: command not found > >> >>> > > >> > >> >>> > > >> Also fo this: > >> >>> > > >> vagrant@scionlab-ffaa-1-c32:~$ tail -f $SC/logs/bs*.DEBUG > >> >>> > > >> tail: cannot open '/logs/bs*.DEBUG' for reading: No such file > >> or > >> >>> > > directory > >> >>> > > >> tail: no files remaining > >> >>> > > >> > >> >>> > > >> 4)Memory Test: > >> >>> > > >> vagrant@scionlab-ffaa-1-c32:~$ df -h > >> >>> > > >> Filesystem Size Used Avail Use% Mounted on > >> >>> > > >> udev 992M 0 992M 0% /dev > >> >>> > > >> tmpfs 200M 3.1M 197M 2% /run > >> >>> > > >> /dev/sda1 9.7G 1.4G 8.3G 14% / > >> >>> > > >> tmpfs 1000M 0 1000M 0% /dev/shm > >> >>> > > >> tmpfs 5.0M 0 5.0M 0% /run/lock > >> >>> > > >> tmpfs 1000M 0 1000M 0% /sys/fs/cgroup > >> >>> > > >> vagrant 136G 73G 64G 54% /vagrant > >> >>> > > >> tmpfs 200M 0 200M 0% /run/user/1000 > >> >>> > > >> > >> >>> > > >> 5) tun0 not found after performing ip a command. > >> >>> > > >> > >> >>> > > >> PS: I am using Oracle Virtual Box 6.0 , Is it the > compatibility > >> >>> issue > >> >>> > ? > >> >>> > > >> PS: I was able to run SCION successfully before the update > with > >> >>> same > >> >>> > > >> Virtual Box version and vagrant also. > >> >>> > > >> > >> >>> > > >> Please look into this issue. > >> >>> > > >> > >> >>> > > >> Thanks, > >> >>> > > >> Sid > >> >>> > > >> _______________________________________________ > >> >>> > > >> Scion mailing list > >> >>> > > >> Scion(a)lists.inf.ethz.ch > >> >>> > > >> https://lists.inf.ethz.ch/mailman/listinfo/scion > >> >>> > > >> > >> >>> > > > > >> >>> > > _______________________________________________ > >> >>> > > Scion mailing list > >> >>> > > Scion(a)lists.inf.ethz.ch > >> >>> > > https://lists.inf.ethz.ch/mailman/listinfo/scion > >> >>> > > > >> >>> > _______________________________________________ > >> >>> > Scion mailing list > >> >>> > Scion(a)lists.inf.ethz.ch > >> >>> > https://lists.inf.ethz.ch/mailman/listinfo/scion > >> >>> > > >> >>> _______________________________________________ > >> >>> Scion mailing list > >> >>> Scion(a)lists.inf.ethz.ch > >> >>> https://lists.inf.ethz.ch/mailman/listinfo/scion > >> >>> > >> >> > >> _______________________________________________ > >> Scion mailing list > >> Scion(a)lists.inf.ethz.ch > >> https://lists.inf.ethz.ch/mailman/listinfo/scion > >> > > > _______________________________________________ > Scion mailing list > Scion(a)lists.inf.ethz.ch > https://lists.inf.ethz.ch/mailman/listinfo/scion >

1 0

Re: [Scion] Unable to run SCION after update
by Juan A. García-Pardo 27 Sep '19

27 Sep '19

Hi Siddharth, I have answered you also to your email directly, but I'm copying the answer here so it gets indexed. There were two problems: - We had experienced some problems with our firewall and the VPN in the attachment point Switzerland. Sometimes it would drop packets. - Your user AS ffaa:1:c32 is marked as deactivated. You have to go to your AS list in the Coordinator (https://www.scionlab.org/user/) and click on "Activate this AS". Wait 1-2 minutes and run `vagrant up` for that user AS. Now your ASes should be able to start the VPN tunnel without problems (type ifconfig in the VM and you should see an interface called tun0), and the active ones will have a working border router. Best regards, Juan A. On Thu, Sep 19, 2019 at 2:28 PM Siddharth Mehrotra <the4daspect(a)gmail.com> wrote: > Hi Juan, > > Thanks for the update, it is really helpful. > > 1) After checking status of my connection to SCION, I see > ● ├─scion-border-router(a)17-ffaa_1_c32-1.service > ● ├─scion-border-router(a)17-ffaa_1_c32-1.service > > as marked RED in color. I could not understand why this happened on first > place, just after running vagrant ssh and systemctl list-dependencies > scionlab.target > > This appears even after restarting SCION services. > > 2) Still I can't find tun0 while running command ip a. The only tunnel > interfaces appearing are: lo & enp0s3. > > 3) Is Scion web-app available? > I get this error: -bash: cd: /src/github.com/netsec-ethz: No such file or > directory while navigating to web-apps. > > PS: Running SCION in a virtual machine – VPN approach > > Thanks, > Siddharth > > On Thu, Sep 19, 2019 at 1:01 PM Juan A. García-Pardo <juagargi(a)gmail.com> > wrote: > > > Hi Siddharth, > > We have not yet upgraded the tutorials for everything, only the "updating > > SCION" one: > > > https://netsec-ethz.github.io/scion-tutorials/scion_tricks/updating_scion/ > > That said, almost all that you are seeing is normal: the configuration > TGZ > > you get from the Coordinator is very small, because your VM will get the > > full configuration from the Coordinator for you. Once you have run > `vagrant > > up`, you will see the directory /etc/scion contains a `gen` directory > > inside. That one will have the full configuration. > > Also, the services and tools are now packaged. There is no $SC directory > > anymore. Things you can run to check: > > - dpkg -l |grep scion # will list scion packages, hopefully installed in > > your system > > - systemctl list-dependencies scionlab.target # list status. In Ubuntu > > 16.04 there is a systemd bug and the services will be listed twice > > - sudo systemctl restart scionlab.target # restart all SCION services > > - ls -l /var/log/scion # list scion log files > > - ls -l /var/lib/scion # list trust databases, etc > > - ls -l /etc/scion # list scion configuration. The gen folder has the > > same morphology as before, but the supervisord files are not used > > > > On the other hand, if you want to not use the packages and go back to the > > developer way of doing things, you can briefly read about that also in > the > > how to update SCION page from SCION tutorials, but basically refers to > > stopping systemd for scionlab.target and cloning/building SCION yourself. > > > > The problem with the VPN is not clear at all though. I would like to > > investigate a bit more about that. Can you try again? If you still see > the > > problem the second time you try, we'll investigate further. > > Thanks and best regards, > > > > Juan A. > > > > > > On Wed, Sep 18, 2019 at 10:52 AM Siddharth Mehrotra < > the4daspect(a)gmail.com> > > wrote: > > > >> Hi all, > >> > >> I tried to run SCION after update from attachment point with ETHZ-AP as > >> downloading new configuration. I'm currently installing inside a VM with > >> use of OPENVPN to connect to SCION Lab. > >> > >> I observed following scenarios: > >> > >> 1) After extracting configuration file from SCION coordination service, > >> the > >> contents are reduced to: > >> Mode LastWriteTime Length Name > >> ---- ------------- ------ ---- > >> d----- 18-09-2019 10:25 .vagrant > >> d----- 18-09-2019 10:23 gen > >> -a---- 13-06-2019 09:25 3618 README.md > >> -a---- 13-06-2019 09:25 3068 run.sh > >> -a---- 18-09-2019 10:22 3813 > >> scion_lab_17-ffaa_1_c32.tar.gz > >> -a---- 18-09-2019 10:34 0 > >> ubuntu-xenial-16.04-cloudimg-console.log > >> -a---- 18-09-2019 10:24 2484 Vagrantfile > >> > >> Many SCION services are missing. > >> > >> 2) Although I was able to run the VM successfully and SSH to SCION. > >> However, it seems the connection to SCION was not successful. The below > >> command is after running Vagrant up: > >> > >> default: WARNING:WARNING!: VPN could be unready. SCION may fail to > start. > >> default: Created symlink from > >> > >> > /etc/systemd/system/scionlab.target.wants/scion-border-router(a)17-ffaa_1_c32-1.service > >> to /lib/systemd/system/scion-border-router@.service. > >> default: Created symlink from > >> > >> > /etc/systemd/system/scionlab.target.wants/scion-certificate-server(a)17-ffaa_1_c32-1.service > >> to /lib/systemd/system/scion-certificate-server@.service. > >> default: Created symlink from > >> > >> > /etc/systemd/system/scionlab.target.wants/scion-path-server(a)17-ffaa_1_c32-1.service > >> to /lib/systemd/system/scion-path-server@.service. > >> default: Created symlink from > >> > >> > /etc/systemd/system/scionlab.target.wants/scion-beacon-server(a)17-ffaa_1_c32-1.service > >> to /lib/systemd/system/scion-beacon-server@.service. > >> default: Created symlink from > >> > >> > /etc/systemd/system/scionlab.target.wants/scion-daemon(a)17-ffaa_1_c32.service > >> to /lib/systemd/system/scion-daemon@.service. > >> default: Created symlink from > >> /etc/systemd/system/scionlab.target.wants/scion-dispatcher.service to > >> /lib/systemd/system/scion-dispatcher.service. > >> default: configure time sync > >> default: ntp.service is not a native service, redirecting to > >> systemd-sysv-install > >> default: Executing /lib/systemd/systemd-sysv-install enable ntp > >> default: configure unattended upgrades (automatic security upgrades) > >> default: SCIONLab VM ready > >> > >> 3) When I am inside the VM and I tried to check the connection I was > >> surprised to see this: > >> > >> vagrant@scionlab-ffaa-1-c32:~$ checkbeacons > >> checkbeacons: command not found > >> > >> Also fo this: > >> vagrant@scionlab-ffaa-1-c32:~$ tail -f $SC/logs/bs*.DEBUG > >> tail: cannot open '/logs/bs*.DEBUG' for reading: No such file or > directory > >> tail: no files remaining > >> > >> 4)Memory Test: > >> vagrant@scionlab-ffaa-1-c32:~$ df -h > >> Filesystem Size Used Avail Use% Mounted on > >> udev 992M 0 992M 0% /dev > >> tmpfs 200M 3.1M 197M 2% /run > >> /dev/sda1 9.7G 1.4G 8.3G 14% / > >> tmpfs 1000M 0 1000M 0% /dev/shm > >> tmpfs 5.0M 0 5.0M 0% /run/lock > >> tmpfs 1000M 0 1000M 0% /sys/fs/cgroup > >> vagrant 136G 73G 64G 54% /vagrant > >> tmpfs 200M 0 200M 0% /run/user/1000 > >> > >> 5) tun0 not found after performing ip a command. > >> > >> PS: I am using Oracle Virtual Box 6.0 , Is it the compatibility issue ? > >> PS: I was able to run SCION successfully before the update with same > >> Virtual Box version and vagrant also. > >> > >> Please look into this issue. > >> > >> Thanks, > >> Sid > >> _______________________________________________ > >> Scion mailing list > >> Scion(a)lists.inf.ethz.ch > >> https://lists.inf.ethz.ch/mailman/listinfo/scion > >> > > > _______________________________________________ > Scion mailing list > Scion(a)lists.inf.ethz.ch > https://lists.inf.ethz.ch/mailman/listinfo/scion >

2 1

Unable to run SCION after update
by Siddharth Mehrotra 19 Sep '19

19 Sep '19

Hi all, I tried to run SCION after update from attachment point with ETHZ-AP as downloading new configuration. I'm currently installing inside a VM with use of OPENVPN to connect to SCION Lab. I observed following scenarios: 1) After extracting configuration file from SCION coordination service, the contents are reduced to: Mode LastWriteTime Length Name ---- ------------- ------ ---- d----- 18-09-2019 10:25 .vagrant d----- 18-09-2019 10:23 gen -a---- 13-06-2019 09:25 3618 README.md -a---- 13-06-2019 09:25 3068 run.sh -a---- 18-09-2019 10:22 3813 scion_lab_17-ffaa_1_c32.tar.gz -a---- 18-09-2019 10:34 0 ubuntu-xenial-16.04-cloudimg-console.log -a---- 18-09-2019 10:24 2484 Vagrantfile Many SCION services are missing. 2) Although I was able to run the VM successfully and SSH to SCION. However, it seems the connection to SCION was not successful. The below command is after running Vagrant up: default: WARNING:WARNING!: VPN could be unready. SCION may fail to start. default: Created symlink from /etc/systemd/system/scionlab.target.wants/scion-border-router(a)17-ffaa_1_c32-1.service to /lib/systemd/system/scion-border-router@.service. default: Created symlink from /etc/systemd/system/scionlab.target.wants/scion-certificate-server(a)17-ffaa_1_c32-1.service to /lib/systemd/system/scion-certificate-server@.service. default: Created symlink from /etc/systemd/system/scionlab.target.wants/scion-path-server(a)17-ffaa_1_c32-1.service to /lib/systemd/system/scion-path-server@.service. default: Created symlink from /etc/systemd/system/scionlab.target.wants/scion-beacon-server(a)17-ffaa_1_c32-1.service to /lib/systemd/system/scion-beacon-server@.service. default: Created symlink from /etc/systemd/system/scionlab.target.wants/scion-daemon(a)17-ffaa_1_c32.service to /lib/systemd/system/scion-daemon@.service. default: Created symlink from /etc/systemd/system/scionlab.target.wants/scion-dispatcher.service to /lib/systemd/system/scion-dispatcher.service. default: configure time sync default: ntp.service is not a native service, redirecting to systemd-sysv-install default: Executing /lib/systemd/systemd-sysv-install enable ntp default: configure unattended upgrades (automatic security upgrades) default: SCIONLab VM ready 3) When I am inside the VM and I tried to check the connection I was surprised to see this: vagrant@scionlab-ffaa-1-c32:~$ checkbeacons checkbeacons: command not found Also fo this: vagrant@scionlab-ffaa-1-c32:~$ tail -f $SC/logs/bs*.DEBUG tail: cannot open '/logs/bs*.DEBUG' for reading: No such file or directory tail: no files remaining 4)Memory Test: vagrant@scionlab-ffaa-1-c32:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 992M 0 992M 0% /dev tmpfs 200M 3.1M 197M 2% /run /dev/sda1 9.7G 1.4G 8.3G 14% / tmpfs 1000M 0 1000M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 1000M 0 1000M 0% /sys/fs/cgroup vagrant 136G 73G 64G 54% /vagrant tmpfs 200M 0 200M 0% /run/user/1000 5) tun0 not found after performing ip a command. PS: I am using Oracle Virtual Box 6.0 , Is it the compatibility issue ? PS: I was able to run SCION successfully before the update with same Virtual Box version and vagrant also. Please look into this issue. Thanks, Sid

2 3

Unable to Connect to SCION Lab
by Andrew Stock 10 Sep '19

10 Sep '19

Hi, I am using Windows 10 machine and following tutorial to setup VM to connect to SCION. Since, I don't have a static public IP address and cannot receive traffic on UDP port 50000 from the outside network. I choose OPENVPN connection for my config files from SCION Coordination Service. Everything went fine and I was able to install SCION on my VM with vagrant up & ssh command. However, when running SCION-Viz many tests were failed. For this reason, I though to run topology and start SCION with run command. It did not report any errors. However, still the test results in SCION-Viz were failed. I have 2 questions: 1) How do I connect to OPENVPN? I tried installing OPENVPN for Windows but it didn't recognize files. Also, the commands for connecting to SCION Lab are only for Ubuntu machines. Does it mean that I can't connect to SCION Lab if my underlying OS is Windows ? 2) Can I run local topology and somehow connect to SCION Lab without going through OPEN VPN ? Thanks, A

2 1

Issue with installation of SCION Apps
by Siddharth Mehrotra 10 Sep '19

10 Sep '19

Hi, While installing SCION-Apps, following error appeared on running ./deps.sh. Is there any issue with this? ubuntu@scionlab-ffaa-1-c28:~/go/src/github.com/netsec-ethz/scion-apps$ ./deps.sh + printf '\n### Getting govendor ###\n' ### Getting govendor ### + grep v1.0.8 + govendor -version + printf '\n### Getting vendor libraries\n' ### Getting vendor libraries + govendor sync -v fetch "github.com/docker/docker/pkg/term" fetch "github.com/docker/docker/pkg/term/windows" fetch "github.com/netsec-ethz/rains/internal/pkg/algorithmTypes" # cd .; git clone https://github.com/netsec-ethz/rains /home/ubuntu/go/.cache/govendor/github.com/netsec-ethz/rains Cloning into '/home/ubuntu/go/.cache/govendor/github.com/netsec-ethz/rains'. .. error: index-pack died of signal 9 fatal: index-pack failed fetch "github.com/netsec-ethz/rains/internal/pkg/cbor" # cd .; git clone https://github.com/netsec-ethz/rains /home/ubuntu/go/.cache/govendor/github.com/netsec-ethz/rains Cloning into '/home/ubuntu/go/.cache/govendor/github.com/netsec-ethz/rains'. .. error: index-pack died of signal 9 fatal: index-pack failed fetch "github.com/netsec-ethz/rains/internal/pkg/connection" # cd .; git clone https://github.com/netsec-ethz/rains /home/ubuntu/go/.cache/govendor/github.com/netsec-ethz/rains Cloning into '/home/ubuntu/go/.cache/govendor/github.com/netsec-ethz/rains'. .. error: index-pack died of signal 9 fatal: index-pack failed fetch "github.com/netsec-ethz/rains/internal/pkg/datastructures/bitarray" Error appeared while executing *make install command* ubuntu@scionlab-ffaa-1-c28:~/go/src/github.com/netsec-ethz/scion-apps$ make install cd helloworld/ && go build ../lib/scionutil/hosts.go:27:2: cannot find package " github.com/netsec-ethz/rains/pkg/rains" in any of: /home/ubuntu/go/src/ github.com/netsec-ethz/scion-apps/vendor/github.com/netsec-ethz/rains/pkg/r… (vendor tree) /usr/local/go/src/github.com/netsec-ethz/rains/pkg/rains (from $GOROOT) /home/ubuntu/go/src/github.com/netsec-ethz/rains/pkg/rains (from $GOPATH) Makefile:24: recipe for target 'helloworld/helloworld' failed make: *** [helloworld/helloworld] Error 1 In this scenario SCION is running on perfectly and I am unable to install SCION - Apps on the ubuntu machine. Thanks, Siddharth

3 4

Re: [Scion] Unable to connect to OpenVPN server
by Juan A. García-Pardo 06 Sep '19

06 Sep '19

Hi Siddharth, Even if you were able to connect to the VPN using a Windows client, the next step would be to make the SCIONLab AS run in Windows, which is not supported yet. In the future we will want to support Windows and the VPN client file will be one of the things we will need to check. Thanks and best regards, Juan A. On Fri, Sep 6, 2019 at 11:45 AM Siddharth Mehrotra <the4daspect(a)gmail.com> wrote: > Hi Juan, > > It worked in Ubuntu with other ISD. However, I am still wondering why I am > unable to connect using OPENVPN client in windows. > > This is the log created: > > Fri Sep 06 11:37:49 2019 OpenVPN 2.4.7 x86_64-w64-mingw32 [SSL (OpenSSL)] > [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 25 2019 > Fri Sep 06 11:37:49 2019 Windows version 6.2 (Windows 8 or greater) 64bit > Fri Sep 06 11:37:49 2019 library versions: OpenSSL 1.1.0j 20 Nov 2018, LZO > 2.10 > Enter Management Password: > Fri Sep 06 11:37:49 2019 MANAGEMENT: TCP Socket listening on [AF_INET] > 127.0.0.1:25340 > Fri Sep 06 11:37:49 2019 Need hold release from management interface, > waiting... > Fri Sep 06 11:37:49 2019 MANAGEMENT: Client connected from [AF_INET] > 127.0.0.1:25340 > Fri Sep 06 11:37:49 2019 MANAGEMENT: CMD 'state on' > Fri Sep 06 11:37:49 2019 MANAGEMENT: CMD 'log all on' > Fri Sep 06 11:37:49 2019 MANAGEMENT: CMD 'echo all on' > Fri Sep 06 11:37:49 2019 MANAGEMENT: CMD 'bytecount 5' > Fri Sep 06 11:37:49 2019 MANAGEMENT: CMD 'hold off' > Fri Sep 06 11:37:49 2019 MANAGEMENT: CMD 'hold release' > Fri Sep 06 11:37:49 2019 WARNING: No server certificate verification method > has been enabled. See http://openvpn.net/howto.html#mitm for more info. > Fri Sep 06 11:37:49 2019 TCP/UDP: Preserving recently used remote address: > [AF_INET]192.33.93.195:1194 > Fri Sep 06 11:37:49 2019 Socket Buffers: R=[65536->65536] S=[65536->65536] > Fri Sep 06 11:37:49 2019 UDP link local: (not bound) > Fri Sep 06 11:37:49 2019 UDP link remote: [AF_INET]192.33.93.195:1194 > Fri Sep 06 11:37:49 2019 MANAGEMENT: >STATE:1567762669,WAIT,,,,,, > > It keeps waiting on last mentioned step. Is there any way to perform > tutorial mentioned at > > https://netsec-ethz.github.io/scion-tutorials/general_scion_configuration/v… > with > Windows OS ? Open VPN requires .ovpn file extension. > > Best Regards, > Siddharth > > On Fri, Aug 30, 2019 at 3:12 PM Juan A. García-Pardo <juagargi(a)gmail.com> > wrote: > > > Hi Siddharth, > > I just found the problem. Go to the Coordinator and attach your user AS > to > > another point other than ISD18 (WISC). There is a problem with that > > attachment point for some time now, so don't use it. > > Thanks and regards, > > > > Juan A. > > > > > > On Fri, Aug 30, 2019 at 2:50 PM Siddharth Mehrotra < > the4daspect(a)gmail.com> > > wrote: > > > >> HI Juan, > >> > >> I tried with standalone Ubuntu 16.04 machine now and it reports > following > >> same error: > >> > >> Aug 30 14:41:21 siddharth-ThinkPad-T480 anacron[965]: Job `cron.daily' > >> terminated (mailing output) > >> Aug 30 14:41:21 siddharth-ThinkPad-T480 anacron[965]: anacron: Can't > >> find sendmail at /usr/sbin/sendmail, not mailing output > >> Aug 30 14:41:21 siddharth-ThinkPad-T480 anacron[965]: Can't find > >> sendmail at /usr/sbin/sendmail, not mailing output > >> Aug 30 14:41:24 siddharth-ThinkPad-T480 ovpn-client[963]: TLS Error: > >> TLS key negotiation failed to occur within 60 seconds (check your > >> network connectivity) > >> Aug 30 14:41:24 siddharth-ThinkPad-T480 ovpn-client[963]: TLS Error: > >> TLS handshake failed > >> Aug 30 14:41:24 siddharth-ThinkPad-T480 ovpn-client[963]: > >> SIGUSR1[soft,tls-error] received, process restarting > >> Aug 30 14:41:24 siddharth-ThinkPad-T480 ovpn-client[963]: Restart > >> pause, 2 second(s) > >> Aug 30 14:41:26 siddharth-ThinkPad-T480 ovpn-client[963]: WARNING: No > >> server certificate verification method has been enabled. See > >> http://openvpn.net/howto.html#mitm for more info. > >> Aug 30 14:41:26 siddharth-ThinkPad-T480 ovpn-client[963]: Socket > >> Buffers: R=[212992->212992] S=[212992->212992] > >> Aug 30 14:41:26 siddharth-ThinkPad-T480 ovpn-client[963]: UDPv4 link > >> local: [undef] > >> Aug 30 14:41:26 siddharth-ThinkPad-T480 ovpn-client[963]: UDPv4 link > >> remote: [AF_INET]128.105.21.208:1194 > >> Aug 30 14:42:27 siddharth-ThinkPad-T480 ovpn-client[963]: TLS Error: > >> TLS key negotiation failed to occur within 60 seconds (check your > >> network connectivity) > >> Aug 30 14:42:27 siddharth-ThinkPad-T480 ovpn-client[963]: TLS Error: > >> TLS handshake failed > >> Aug 30 14:42:27 siddharth-ThinkPad-T480 ovpn-client[963]: > >> SIGUSR1[soft,tls-error] received, process restarting > >> Aug 30 14:42:27 siddharth-ThinkPad-T480 ovpn-client[963]: Restart > >> pause, 2 second(s) > >> Aug 30 14:42:29 siddharth-ThinkPad-T480 ovpn-client[963]: WARNING: No > >> server certificate verification method has been enabled. See > >> http://openvpn.net/howto.html#mitm for more info. > >> Aug 30 14:42:29 siddharth-ThinkPad-T480 ovpn-client[963]: Socket > >> Buffers: R=[212992->212992] S=[212992->212992] > >> Aug 30 14:42:29 siddharth-ThinkPad-T480 ovpn-client[963]: UDPv4 link > >> local: [undef] > >> Aug 30 14:42:29 siddharth-ThinkPad-T480 ovpn-client[963]: UDPv4 link > >> remote: [AF_INET]128.105.21.208:1194 > >> Aug 30 14:43:29 siddharth-ThinkPad-T480 ovpn-client[963]: TLS Error: > >> TLS key negotiation failed to occur within 60 seconds (check your > >> network connectivity) > >> Aug 30 14:43:29 siddharth-ThinkPad-T480 ovpn-client[963]: TLS Error: > >> TLS handshake failed > >> Aug 30 14:43:29 siddharth-ThinkPad-T480 ovpn-client[963]: > >> SIGUSR1[soft,tls-error] received, process restarting > >> Aug 30 14:43:29 siddharth-ThinkPad-T480 ovpn-client[963]: Restart > >> pause, 2 second(s) > >> Aug 30 14:43:31 siddharth-ThinkPad-T480 ovpn-client[963]: WARNING: No > >> server certificate verification method has been enabled. See > >> http://openvpn.net/howto.html#mitm for more info. > >> Aug 30 14:43:31 siddharth-ThinkPad-T480 ovpn-client[963]: Socket > >> Buffers: R=[212992->212992] S=[212992->212992] > >> Aug 30 14:43:31 siddharth-ThinkPad-T480 ovpn-client[963]: UDPv4 link > >> local: [undef] > >> Aug 30 14:43:31 siddharth-ThinkPad-T480 ovpn-client[963]: UDPv4 link > >> remote: [AF_INET]128.105.21.208:1194 > >> > >> On performing ip a command inside SCION network, I can see only: *lo, > >> enp0s3 and docker0.* > >> > >> While in local machine I have: *lo, enp0s31f6, wlp3s0 and docker0.* > >> > >> Best, > >> Siddharth > >> > >> > >> On Fri, Aug 30, 2019 at 1:05 PM Juan A. García-Pardo < > juagargi(a)gmail.com> > >> wrote: > >> > >> > Hi Siddharth, > >> > We don't have any experience with OpenVPN for Windows. I would suggest > >> > these two steps to troubleshoot your setup: > >> > - Check with a VM that your user AS runs correctly. Since we have lots > >> of > >> > experience in Ubuntu 16.04, install first a VM like that, or eve > better, > >> > install the Vagrant-Virtual Box VM that you see being installed in the > >> > `run.sh` script in your configuration from the Coordinator. > >> > - If the previous step worked, check only the VPN connection. As you > >> were > >> > saying, it will probably fail. Tell us and we will investigate > further. > >> > Thanks and best regards, > >> > > >> > Juan A. > >> > > >> > > >> > On Fri, Aug 30, 2019 at 11:36 AM Siddharth Mehrotra < > >> the4daspect(a)gmail.com> > >> > wrote: > >> > > >> >> Hi all, > >> >> > >> >> I am trying to connect to SCION Lab via VPN. > >> >> > >> >> I am currently using Windows OS and have been able to run SCION > >> >> successfully but can't connect to SCION Lab. I added the config file > >> from > >> >> SCION folder to the OPEN VPN directory however I am unable to > connect & > >> >> can't find tun0. > >> >> > >> >> The error report from OPENVPN GUI is as: > >> >> > >> >> Fri Aug 30 09:24:22 2019 TCP/UDP: Preserving recently used remote > >> address: > >> >> [AF_INET]192.33.93.195:1194 > >> >> Fri Aug 30 09:24:22 2019 Socket Buffers: R=[65536->65536] > >> S=[65536->65536] > >> >> Fri Aug 30 09:24:22 2019 UDP link local: (not bound) > >> >> Fri Aug 30 09:24:22 2019 UDP link remote: [AF_INET] > 192.33.93.195:1194 > >> >> Fri Aug 30 09:24:22 2019 MANAGEMENT: >STATE:1567149862,WAIT,,,,,, > >> >> Fri Aug 30 09:25:22 2019 TLS Error: TLS key negotiation failed to > occur > >> >> within 60 seconds (check your network connectivity) > >> >> Fri Aug 30 09:25:22 2019 TLS Error: TLS handshake failed > >> >> Fri Aug 30 09:25:22 2019 SIGUSR1[soft,tls-error] received, process > >> >> restarting > >> >> Fri Aug 30 09:25:22 2019 MANAGEMENT: > >> >> >STATE:1567149922,RECONNECTING,tls-error,,,,, > >> >> Fri Aug 30 09:25:22 2019 Restart pause, 5 second(s) > >> >> > >> >> Not sure if I am doing something wrong or it's server error. > >> >> > >> >> > >> >> > >> > https://drive.google.com/file/d/1Tz8zgPEGBGmJNumdlj0FGUm1s3QH_6-a/view?usp=… > >> >> : Log File > >> >> > >> >> Best regards, > >> >> Siddharth > >> >> ----------------------------------------- > >> >> Siddharth Mehrotra > >> >> Graduate Student > >> >> Media Computing Group - i10 > >> >> RWTH Aachen University, Germany. > >> >> https://hci.rwth-aachen.de/mehrotra > >> >> < > >> >> > >> > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhci.rwth-… > >> >> > > >> >> _______________________________________________ > >> >> Scion mailing list > >> >> Scion(a)lists.inf.ethz.ch > >> >> https://lists.inf.ethz.ch/mailman/listinfo/scion > >> >> > >> > > >> _______________________________________________ > >> Scion mailing list > >> Scion(a)lists.inf.ethz.ch > >> https://lists.inf.ethz.ch/mailman/listinfo/scion > >> > > > _______________________________________________ > Scion mailing list > Scion(a)lists.inf.ethz.ch > https://lists.inf.ethz.ch/mailman/listinfo/scion >

1 0