Issue with Raspberry Pi image

[Khalid.dg]

Hello,

I downloaded the image (Raspberry Pi3 Ubuntu) from scion-lab.org and burned it to SD card, and ran it on a Raspberry Pi3 with the VPN connection.

For some reason the Pi is not connecting to SCION network.  

When issuing the checkbeacons command I get the following output:

2018-06-02 07:50:40.109045+0000 [INFO] (BS._handle_if_timeouts) Issuing revocation: RevInfo: 4-1118 IF: 1 EPOCH: 152792584 TreeTTL: 21600

2018-06-02 07:50:40.184729+0000 [DEBUG] (BS.worker) Expired 1 old entries from /4-1118/bs/rev_cache

2018-06-02 07:50:50.119230+0000 [INFO] (BS._handle_if_timeouts) Issuing revocation: RevInfo: 4-1118 IF: 1 EPOCH: 152792585 TreeTTL: 21600

2018-06-02 07:50:50.196024+0000 [DEBUG] (BS.worker) Expired 1 old entries from /4-1118/bs/rev_cache

2018-06-02 07:51:00.130244+0000 [INFO] (BS._handle_if_timeouts) Issuing revocation: RevInfo: 4-1118 IF: 1 EPOCH: 152792586 TreeTTL: 21600

2018-06-02 07:51:00.206564+0000 [DEBUG] (BS.worker) Expired 1 old entries from /4-1118/bs/rev_cache

2018-06-02 07:51:10.140882+0000 [INFO] (BS._handle_if_timeouts) Issuing revocation: RevInfo: 4-1118 IF: 1 EPOCH: 152792587 TreeTTL: 21600

2018-06-02 07:51:10.216170+0000 [DEBUG] (BS.worker) Expired 1 old entries from /4-1118/bs/rev_cache

The Pi is connected to the internet using an Ethernet cable. I did not update SCION nor Ubuntu after the installation as it was not able to start SCION after updating.

Please help, what is the step I am missing to get it to connect?

Thanks,

Khalid

[David Hausheer]

Hi Khalid,

are you able to ping 10.0.8.1 (the VPN server)?

Moreover, can you check if the time of your Pi is correct?

When you do tcpdump -i tun0, do you see messages arriving from 10.0.8.1?

Did you by any chance apply any iptables command?

Best regards
David

[Khalid.dg]

Hi David, 

I am able to ping the VPN server. 

The time is correct on the raspberry Pi.

After doing tcpdump -i tun0 I receive UDP traffic from 10.0.8.1 to my address on port 50000.

And did not do any iptables command.

I did however notice that whenever I did a command with sudo it would show me the following warning 

sudo: unable to resolve host ubuntu

so I fixed it by modifying the hosts and hostname files. Could this have prevented scion from building correctly? 

[David Hausheer]

Hi Khalid

It looks like you are receiving beacons then. The hostname resolution shouldn't have any influence. At this stage it would be interesting to see the logs of the border router on AS 4-44 to which your AS is connected. I suggest you contact Juan or Jonghoon about it.

Best regards
David

[Adrian Perrig]

Hi Khalid,

Are you seeing entries such as this one in the beacon server debug log
($SC/logs/bs...DEBUG)?
Segment dropped due to path policy: ('DelayTime: 0 <= -30 <= 60' ...

In that case, the time of your VM is incorrect. You can synchronize
the time of your host machine, then that problem should be fixed.
After the next update, this problem will be fixed as we will have the
VM synchronize its time independent of the host's time.

All the best,
Adrian

> --
> SCION Internet Architecture
> https://www.scion-architecture.net
> ---
> You received this message because you are subscribed to the Google Groups
> "SCION community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to scion-communi...@googlegroups.com.
> To post to this group, send email to scion-c...@googlegroups.com.
> Visit this group at https://groups.google.com/group/scion-community.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/scion-community/50d621e9-0864-4732-a9b6-f94526f0cc5c%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.

[Khalid.dg]

Hi Adrain, 

I apologize greatly for the late response, I did not have access to the Pi in the past month. 

I updated the Pi to the new version of SCION with new addresses, I downloaded the new image (Raspberry Pi3 Ubuntu)  and burned it to the SD card.

I ran it again it seems I still have an issue. When I start the scion network it shows this: 

scion@ubuntu:~/go/src/github.com/scionproto/scion$ ./scion.sh start

Compiling...

Running the network...

as20-ffaa_1_76:cs20-ffaa_1_76-1: ERROR (spawn error)

as20-ffaa_1_76:br20-ffaa_1_76-1: ERROR (spawn error)

as20-ffaa_1_76:sd20-ffaa_1_76: ERROR (spawn error)

as20-ffaa_1_76:ps20-ffaa_1_76-1: ERROR (spawn error)

as20-ffaa_1_76:bs20-ffaa_1_76-1: ERROR (spawn error) 

and when I check the beacons it shows the following: 

scion@ubuntu:~$ checkbeacons

2018-07-24 11:09:09.547685+0000 [CRITICAL] (MainThread)     super().__init__(raw)

2018-07-24 11:09:09.549655+0000 [CRITICAL] (MainThread)   File "/home/scion/go/src/github.com/scionproto/scion/python/lib/packet/packet_base.py", line 35, in __init__

2018-07-24 11:09:09.551803+0000 [CRITICAL] (MainThread)     self._parse(raw)

2018-07-24 11:09:09.553761+0000 [CRITICAL] (MainThread)   File "/home/scion/go/src/github.com/scionproto/scion/python/lib/packet/scion_addr.py", line 49, in _parse

2018-07-24 11:09:09.555695+0000 [CRITICAL] (MainThread)     self._parse_str(raw)

2018-07-24 11:09:09.557623+0000 [CRITICAL] (MainThread)   File "/home/scion/go/src/github.com/scionproto/scion/python/lib/packet/scion_addr.py", line 73, in _parse_str

2018-07-24 11:09:09.559532+0000 [CRITICAL] (MainThread)     raise SCIONParseError("Unable to parse AS from string: %s" % raw)

2018-07-24 11:09:09.561544+0000 [CRITICAL] (MainThread) lib.errors.SCIONParseError: Unable to parse AS from string: 20-ffaa:1:76

2018-07-24 11:09:09.563438+0000 [CRITICAL] (MainThread)

2018-07-24 11:09:09.565504+0000 [CRITICAL] (MainThread) Exiting

I checked the logs you mentioned but they had a completely different output. I attached the bs...DEBUG to this post. 

A note, it seems after the fresh install it has an issue with the hostname which makes me unable to run sudo commands, it used to show 

sudo: unable to resolve host ubuntu

I fixed this by adding the following line to /etc/hosts

127.0.1.1 ubuntu

Thank you for the help, 

khalid

[Khalid Aldughayem]

I forgot to mention that the VPN connection is working and I am able to ping the server. But when checking the traffic using tcpdump I get this output: 

scion@ubuntu:~$ sudo tcpdump -i tun0

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on tun0, link-type RAW (Raw IP), capture size 262144 bytes

11:28:31.157830 IP 10.0.8.1.50018 > 10.0.8.7.50000: UDP, length 81

11:28:31.158084 IP 10.0.8.7 > 10.0.8.1: ICMP 10.0.8.7 udp port 50000 unreachable, length 117

11:28:32.156720 IP 10.0.8.1.50018 > 10.0.8.7.50000: UDP, length 81

11:28:32.156959 IP 10.0.8.7 > 10.0.8.1: ICMP 10.0.8.7 udp port 50000 unreachable, length 117

11:28:33.157878 IP 10.0.8.1.50018 > 10.0.8.7.50000: UDP, length 81

The time as I checked is correct. 

Thanks,

Khalid

[Juan A. Garcia Pardo]

Hi Khalid,

Many thanks for following up.

The ARM images are being updated this week (hopefully), we just updated the XU4 minimal image, and after testing that it works correctly we will update the rest.

Aside from that, there seems to be two issues from what I understand in your message: the image is running an old version of SCIONLab and didn't update and there is an issue with the hostname.

Typically the hostname issue would not prevent a command to run, but we will check also this.

About the machine not updating: can you run this please?:

cd $SC ; git branch -vv  

Our SCIONLab version starts with a1b4138, the date is June the 6th 2018.

If it's not up to date (which I fear), you will have to follow the tutorial on https://netsec-ethz.github.io/scion-tutorials/scion_tricks/updating_scion/ ; in particular the steps for ARM devices.

Also, it would be really nice if we can reproduce your issue in house. Did you just downloaded and installed the image from the coordinator? Raspberry Pi 3 for what I read, isn't it? In any case, we are going to try to reproduce on our side.

I will update this thread once we are done with the tests.

Again, many thanks for sharing your finding, if you don't mind, please try the tutorial step above and post your results.

Best regards,

Juan A.

[Khalid Aldughayem]

Hi Juan,

I found that the Pi was not updating, so I followed the steps in the link you mentioned. The patch was applied with no issues, the update commands fails at building (./scion.sh build) but when I try it again or run the infrastructure (./scion.sh start) it seems to be working correctly and I am able to receive beacons normally.  

These were the commands which showed a different output from what expected:

1. ./scion.sh clean: it shows this output

scion@ubuntu:~/go/src/github.com/scionproto/scion$ ./scion.sh clean

Makefile:98: .depend: No such file or directory

warning: "./vendor/..." matched no packages

2. ./scion.sh build: fails at a certain point where it give the following: 

...

github.com/scionproto/scion/go/tools/scmp/cmn

github.com/scionproto/scion/go/sig/base

github.com/scionproto/scion/go/tools/scmp/echo

github.com/scionproto/scion/go/tools/scmp/recordpath

github.com/scionproto/scion/go/tools/scmp/traceroute

github.com/scionproto/scion/go/tools/scmp

github.com/scionproto/scion/go/sig

Error: exit status 1

Makefile:69: recipe for target 'bin' failed

make[1]: *** [bin] Error 2

Makefile:14: recipe for target 'go' failed

make: *** [go] Error 2

Then when I try to build it again or run ./scion.sh start  it executes with no errors. 

Thank you for the help Juan, and to reproduce the issue in house, what should be done for that? 

Thank you very much everyone for all the help it is very much appreciated. 

[Juan A. Garcia Pardo]

Hi Khalid!

Thanks for the information. I was able to reproduce the problem this morning and we have a PR fixing this issue. Indeed the ARM boxes would not update automatically with the current code. The PR that fixes this is https://github.com/netsec-ethz/scion-coord/pull/259 (it also fixes an automated update issue with time sync in VMs), if you want to take a look.

I am also glad to hear that you were able to manually upgrade following the tutorial. It's weird that you had that make error and that it works nevertheless. Can you confirm that your AS works by running bwtestclient against one of the attachment points? in the tutorials we describe how to do so: https://netsec-ethz.github.io/scion-tutorials/sample_projects/bwtester/

Again, many thanks for your collaboration!! Best regards,

Juan A.

[Khalid Aldughayem]

Hi Juan,

No worries, all the thanks to all who replied for the help. 

I was able to run the bwtester client with the servers specified in the page mentioned. I think everything is running smoothly now, thanks again :) 

Regards,

Khalid