- SCION - mailman3.inf.ethz.ch

Re: [SCION] VPN configuration failure
by Mateusz Kowalski 12 Dec '19

12 Dec '19

https://docs.scionlab.org/content/faq/troubleshooting.html -- You see the part about `systemctl status openvpn@client` and `ip address show dev tun0` Cheers On 11/12/2019 21:15, Matthew McCormack wrote: > Thanks! > > How do I test if "VPN connection to the AP is established correctly"? > > On Wed, Dec 11, 2019 at 2:52 PM Kowalski Mateusz > <mateusz.kowalski(a)inf.ethz.ch <mailto:mateusz.kowalski@inf.ethz.ch>> > wrote: > > Hi guys, > > Please do one if the following > > 1) test whether your VPN connection to the AP is established > correctly; without it the border router will not start > 2) configure your user AS properly i.e. without using a VPN; if > the problem persists with the direct connection to the AP, the > problem will be either AP’s configuration or the SCION itself > > Statistically speaking I bet you don’t have a working VPN, but > this statement is not backed by any logs > > Cheers, > Mateusz > ------------------------------------------------------------------------ > *From:* SCION <scion-bounces(a)lists.inf.ethz.ch > <mailto:scion-bounces@lists.inf.ethz.ch>> on behalf of Matthew > McCormack <mmccorm1(a)andrew.cmu.edu <mailto:mmccorm1@andrew.cmu.edu>> > *Sent:* 11 December 2019 19:31:09 > *To:* scion(a)lists.inf.ethz.ch <mailto:scion@lists.inf.ethz.ch> > *Subject:* Re: [SCION] VPN configuration failure > As a follow-up, while debugging with Michael a key item we noted > was that > the border-router service is not running (also not listed when running > systemctl list-dependencies): > > $ sudo systemctl list-dependencies scionlab.target > scionlab.target > ● ├─scion-beacon-server(a)17-ffaa_1_d13-1.service > ● ├─scion-beacon-server(a)17-ffaa_1_d13-1.service > ● ├─scion-certificate-server(a)17-ffaa_1_d13-1.service > ● ├─scion-certificate-server(a)17-ffaa_1_d13-1.service > ● ├─scion-daemon(a)17-ffaa_1_d13.service > ● ├─scion-daemon(a)17-ffaa_1_d13.service > ● ├─scion-dispatcher.service > ● ├─scion-dispatcher.service > ● ├─scion-path-server(a)17-ffaa_1_d13-1.service > ● ├─scion-path-server(a)17-ffaa_1_d13-1.service > ● └─scion-webapp.service > > When I attempt to manually start the border-router, it fails: > > $ sudo systemctl status scion-border-router(a)17-ffaa_1_d13-1.service > > *●* scion-border-router(a)17-ffaa_1_d13-1.service - SCION Border Router > > Loaded: loaded (/lib/systemd/system/scion-border-router@.service; > disabled; vendor preset: enabled) > > Active: *failed* (Result: start-limit-hit) since Wed 2019-12-11 > 12:23:43 CST; 46s ago > > Docs: https://www.scionlab.org > > Process: 28270 ExecStart=/usr/bin/scion-systemd-wrapper > /usr/bin/border /etc/scion/gen/ISD-isd-/AS-as-/br%i/br.toml %i > *(code=exited, status=1/* > > Main PID: 28270 (code=exited, status=1/FAILURE) > > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us > <http://dataplane.scion.psi-pg0.wisc.cloudlab.us> systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Unit entered failed > state.* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us > <http://dataplane.scion.psi-pg0.wisc.cloudlab.us> systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Failed with result > 'exit-code'* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us > <http://dataplane.scion.psi-pg0.wisc.cloudlab.us> systemd[1]: > scion-border-router(a)17-ffaa_1_d13-1.service: Service hold-off time > over, scheduling restart > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us > <http://dataplane.scion.psi-pg0.wisc.cloudlab.us> systemd[1]: > Stopped SCION Border Router. > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us > <http://dataplane.scion.psi-pg0.wisc.cloudlab.us> systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Start request repeated > too quickly* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us > <http://dataplane.scion.psi-pg0.wisc.cloudlab.us> systemd[1]: > *Failed to start SCION Border Router.* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us > <http://dataplane.scion.psi-pg0.wisc.cloudlab.us> systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Unit entered failed > state.* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us > <http://dataplane.scion.psi-pg0.wisc.cloudlab.us> systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Failed with result > 'start-limit-hit'.* > > > Thanks for the help! > > -Matt > > > On Wed, Dec 11, 2019 at 12:07 PM Matthew McCormack > <mmccorm1(a)andrew.cmu.edu <mailto:mmccorm1@andrew.cmu.edu>> > wrote: > > > Hello, > > > > In attempting to setup an AS (attached to the ETHZ-AP), I am > experiencing > > an issue (at least one reported by the webapp) with the VPN. I > built the AS > > from debian packages. I can ping a SCION AP, but when I attempt > to send an > > SCMP echo message, I receive the following error message: CRIT: > > SCIOND unable to retrieve paths: SCIOND experienced an internal > error > > > > The webapp reports that the VPN configuration test fails with the > > following message: > > Traceback (most recent call last): > > File \"\", line 3, in > > StopIteration > > > > As a side note, the webapp reports that the SCMP test passes, > but does not > > report the host's public IP address but the address of a > different NIC on > > the machine. When I attempt to manually send an SCMP echo, I > receive the > > error message above about SCIONd not being able to retrieve paths. > > > > I am not receiving any SCION beacon messages. The only items in > the log > > are for starting periodic tasks. > > > > -- > > Thank you for your time and consideration. > > > > Very Respectfully, > > Matt McCormack > > > > > -- > Thank you for your time and consideration. > > Very Respectfully, > Matt McCormack > _______________________________________________ > SCION mailing list > SCION(a)lists.inf.ethz.ch <mailto:SCION@lists.inf.ethz.ch> > https://lists.inf.ethz.ch/mailman/listinfo/scion > > > > -- > Thank you for your time and consideration. > > Very Respectfully, > Matt McCormack

1 0

Re: [SCION] VPN configuration failure
by Matthew McCormack 11 Dec '19

11 Dec '19

All of the issues go away when configured to use direct connect to the AP (without the VPN). After re-running scionlab-config, the border-router service is running, and SCMP echo succeeds to SCION APs. I'm confused why I had VPN issues, as I installed openVPN from the debian packages and ran scionlab-config then started the services (openvpn@client, scionlab.target). As a note, when reverting from the direct connect back to the VPN configuration for the AS, the issues do not return. The border-router service runs and the webapp does not identify the VPN as being misconfigured. On Wed, Dec 11, 2019 at 2:52 PM Kowalski Mateusz < mateusz.kowalski(a)inf.ethz.ch> wrote: > Hi guys, > > Please do one if the following > > 1) test whether your VPN connection to the AP is established correctly; > without it the border router will not start > 2) configure your user AS properly i.e. without using a VPN; if the > problem persists with the direct connection to the AP, the problem will be > either AP’s configuration or the SCION itself > > Statistically speaking I bet you don’t have a working VPN, but this > statement is not backed by any logs > > Cheers, > Mateusz > ------------------------------ > *From:* SCION <scion-bounces(a)lists.inf.ethz.ch> on behalf of Matthew > McCormack <mmccorm1(a)andrew.cmu.edu> > *Sent:* 11 December 2019 19:31:09 > *To:* scion(a)lists.inf.ethz.ch > *Subject:* Re: [SCION] VPN configuration failure > > As a follow-up, while debugging with Michael a key item we noted was that > the border-router service is not running (also not listed when running > systemctl list-dependencies): > > $ sudo systemctl list-dependencies scionlab.target > scionlab.target > ● ├─scion-beacon-server(a)17-ffaa_1_d13-1.service > ● ├─scion-beacon-server(a)17-ffaa_1_d13-1.service > ● ├─scion-certificate-server(a)17-ffaa_1_d13-1.service > ● ├─scion-certificate-server(a)17-ffaa_1_d13-1.service > ● ├─scion-daemon(a)17-ffaa_1_d13.service > ● ├─scion-daemon(a)17-ffaa_1_d13.service > ● ├─scion-dispatcher.service > ● ├─scion-dispatcher.service > ● ├─scion-path-server(a)17-ffaa_1_d13-1.service > ● ├─scion-path-server(a)17-ffaa_1_d13-1.service > ● └─scion-webapp.service > > When I attempt to manually start the border-router, it fails: > > $ sudo systemctl status scion-border-router(a)17-ffaa_1_d13-1.service > > *●* scion-border-router(a)17-ffaa_1_d13-1.service - SCION Border Router > > Loaded: loaded (/lib/systemd/system/scion-border-router@.service; > disabled; vendor preset: enabled) > > Active: *failed* (Result: start-limit-hit) since Wed 2019-12-11 > 12:23:43 CST; 46s ago > > Docs: https://www.scionlab.org > > Process: 28270 ExecStart=/usr/bin/scion-systemd-wrapper > /usr/bin/border /etc/scion/gen/ISD-isd-/AS-as-/br%i/br.toml %i > *(code=exited, status=1/* > > Main PID: 28270 (code=exited, status=1/FAILURE) > > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Unit entered failed > state.* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Failed with result > 'exit-code'* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us systemd[1]: > scion-border-router(a)17-ffaa_1_d13-1.service: Service hold-off time > over, scheduling restart > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us systemd[1]: > Stopped SCION Border Router. > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Start request repeated > too quickly* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us systemd[1]: > *Failed to start SCION Border Router.* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Unit entered failed > state.* > > Dec 11 12:23:43 dataplane.scion.psi-pg0.wisc.cloudlab.us systemd[1]: > *scion-border-router(a)17-ffaa_1_d13-1.service: Failed with result > 'start-limit-hit'.* > > > Thanks for the help! > > -Matt > > > On Wed, Dec 11, 2019 at 12:07 PM Matthew McCormack < > mmccorm1(a)andrew.cmu.edu> > wrote: > > > Hello, > > > > In attempting to setup an AS (attached to the ETHZ-AP), I am experiencing > > an issue (at least one reported by the webapp) with the VPN. I built the > AS > > from debian packages. I can ping a SCION AP, but when I attempt to send > an > > SCMP echo message, I receive the following error message: CRIT: > > SCIOND unable to retrieve paths: SCIOND experienced an internal error > > > > The webapp reports that the VPN configuration test fails with the > > following message: > > Traceback (most recent call last): > > File \"\", line 3, in > > StopIteration > > > > As a side note, the webapp reports that the SCMP test passes, but does > not > > report the host's public IP address but the address of a different NIC on > > the machine. When I attempt to manually send an SCMP echo, I receive the > > error message above about SCIONd not being able to retrieve paths. > > > > I am not receiving any SCION beacon messages. The only items in the log > > are for starting periodic tasks. > > > > -- > > Thank you for your time and consideration. > > > > Very Respectfully, > > Matt McCormack > > > > > -- > Thank you for your time and consideration. > > Very Respectfully, > Matt McCormack > _______________________________________________ > SCION mailing list > SCION(a)lists.inf.ethz.ch > https://lists.inf.ethz.ch/mailman/listinfo/scion > -- Thank you for your time and consideration. Very Respectfully, Matt McCormack

1 0

VPN configuration failure
by Matthew McCormack 11 Dec '19

11 Dec '19

Hello, In attempting to setup an AS (attached to the ETHZ-AP), I am experiencing an issue (at least one reported by the webapp) with the VPN. I built the AS from debian packages. I can ping a SCION AP, but when I attempt to send an SCMP echo message, I receive the following error message: CRIT: SCIOND unable to retrieve paths: SCIOND experienced an internal error The webapp reports that the VPN configuration test fails with the following message: Traceback (most recent call last): File \"\", line 3, in StopIteration As a side note, the webapp reports that the SCMP test passes, but does not report the host's public IP address but the address of a different NIC on the machine. When I attempt to manually send an SCMP echo, I receive the error message above about SCIONd not being able to retrieve paths. I am not receiving any SCION beacon messages. The only items in the log are for starting periodic tasks. -- Thank you for your time and consideration. Very Respectfully, Matt McCormack

1 1

Intermittent ICMP/SCMP message failures
by Matthew McCormack 10 Dec '19

10 Dec '19

Hello, I created an AS (attached to the 19-ffaa:0:1303 (Magdeburg AP) using the debian packages on a baremetal hosting service (cloudlab.us) where I am running Ubuntu 16.04 (and using openVPN for the overlay link). When I check the health of this AS using the webapp, I receive intermittent failures for ICMP/SCMP. These results are similarly repeated when I repeat the tests on the command line (where attempting to ping a border router, e.g. 10.0.8.1, I might experience 100 dropped packets, or return an RTT of ~120 mseconds for each packet). The SCMP messages upon failure return: "ERROR: SCMP validation" and succeeds after 65 echo attempts. However, this returns to a failed state after a short time period (~10 seconds of inactivity). Do you have any insights as to why I am experiencing this intermittent failure? I'm happy to provide any additional descriptions of the setup that might help in debugging (e.g., log data, other configurations, etc). -- Thank you for your time and consideration. Very Respectfully, Matt McCormack

1 0

Not receiving paths
by Fischer Joel 13 Nov '19

13 Nov '19

Hi I have built SCION from source according to the tutorial (https://netsec-ethz.github.io/scion-tutorials/install/src/) and setup the VPN client. The local topology worked fine, but when I try to connect to scionlab and run scmp echo, I get the following error: ./bin/scmp echo -local 17-ffaa:1:ceb,[127.0.0.1] -remote 20-ffaa:0:1404,[0.0.0.0] CRIT: SCIOND unable to retrieve paths: SCIOND experienced an internal error The log of sciond is: cat logs/sd17-ffaa_1_ceb.log 2019-11-11 12:48:16.863748+0000 [INFO] =====================> Service started SD sd17-ffaa_1_ceb Scion version: v2019.09-15-gd7eebae In docker: false pid: 30036 euid/egid: 168638 261978 cmd line: ["bin/sciond" "-config" "gen/ISD17/ASffaa_1_ceb/endhost/sd.toml"] 2019-11-11 12:48:16.864077+0000 [INFO] Connecting PathDB backend=sqlite connection=gen-cache/sd17-ffaa_1_ceb.path.db 2019-11-11 12:48:16.979552+0000 [INFO] Connecting RevCache backend=mem connection="" 2019-11-11 12:48:16.979577+0000 [INFO] Connecting TrustDB backend=sqlite connection=gen-cache/sd17-ffaa_1_ceb.trust.db 2019-11-11 12:48:17.074049+0000 [DBUG] Registered with dispatcher addr="17-ffaa:1:ceb,[127.0.0.1]:1025 (UDP)" 2019-11-11 12:48:17.074488+0000 [DBUG] Registered with dispatcher addr="17-ffaa:1:ceb,[127.0.0.1]:1026 (UDP)" 2019-11-11 12:48:17.074772+0000 [INFO] DRKey enabled=false 2019-11-11 12:48:17.074811+0000 [INFO] Starting periodic task debug_id=02c025e1 task="Cleaner for segments" 2019-11-11 12:48:17.074838+0000 [INFO] Starting periodic task debug_id=550ed7d9 task="Cleaner for revocations" 2019-11-11 12:48:17.074877+0000 [INFO] Exporting prometheus metrics addr=[127.0.0.1]:30455 2019-11-11 12:48:17.978093+0000 [DBUG] [PathRequestHandler] Received request debug_id=c9b1d73c req="17-ffaa:1:ceb -> 17-ffaa:0:1101, maxPaths=5, flags={false false}" 2019-11-11 12:48:17.978313+0000 [DBUG] Requesting segments debug_id=c9b1d73c ps="17-ffaa:1:ceb,[PS A (0x0001)]:0 (UDP)" 2019-11-11 12:48:27.978601+0000 [DBUG] Unclassified RPC error debug_id=c9b1d73c msg= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:48:27.978649+0000 [EROR] Unable to retrieve paths from network debug_id=c9b1d73c err= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:48:27.978665+0000 [EROR] Unable to get paths debug_id=c9b1d73c err="No result" 2019-11-11 12:48:27.978742+0000 [DBUG] Replied with paths debug_id=c9b1d73c num_paths=0 2019-11-11 12:48:27.993341+0000 [DBUG] [PathRequestHandler] Received request debug_id=c547de4a req="17-ffaa:1:ceb -> 17-ffaa:0:1101, maxPaths=5, flags={false false}" 2019-11-11 12:48:27.993509+0000 [DBUG] Requesting segments debug_id=c547de4a ps="17-ffaa:1:ceb,[PS A (0x0001)]:0 (UDP)" 2019-11-11 12:48:37.993748+0000 [DBUG] Unclassified RPC error debug_id=c547de4a msg= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:48:37.993790+0000 [EROR] Unable to retrieve paths from network debug_id=c547de4a err= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:48:37.993804+0000 [EROR] Unable to get paths debug_id=c547de4a err="No result" 2019-11-11 12:48:37.993886+0000 [WARN] Unable to reply to client debug_id=c547de4a client=<nil> err="write unix /run/shm/sciond/default.sock->@: write: broken pipe" 2019-11-11 12:48:38.990405+0000 [DBUG] [PathRequestHandler] Received request debug_id=6dcac452 req="17-ffaa:1:ceb -> 17-ffaa:0:1101, maxPaths=5, flags={false false}" 2019-11-11 12:48:38.990592+0000 [DBUG] Requesting segments debug_id=6dcac452 ps="17-ffaa:1:ceb,[PS A (0x0001)]:0 (UDP)" 2019-11-11 12:48:48.990833+0000 [DBUG] Unclassified RPC error debug_id=6dcac452 msg= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:48:48.990871+0000 [EROR] Unable to retrieve paths from network debug_id=6dcac452 err= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:48:48.990883+0000 [EROR] Unable to get paths debug_id=6dcac452 err="No result" 2019-11-11 12:48:48.991041+0000 [DBUG] Replied with paths debug_id=6dcac452 num_paths=0 2019-11-11 12:48:48.997702+0000 [DBUG] [PathRequestHandler] Received request debug_id=faede431 req="17-ffaa:1:ceb -> 17-ffaa:0:1101, maxPaths=5, flags={false false}" 2019-11-11 12:48:48.997887+0000 [DBUG] Requesting segments debug_id=faede431 ps="17-ffaa:1:ceb,[PS A (0x0001)]:0 (UDP)" 2019-11-11 12:48:58.998161+0000 [DBUG] Unclassified RPC error debug_id=faede431 msg= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:48:58.998196+0000 [EROR] Unable to retrieve paths from network debug_id=faede431 err= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:48:58.998212+0000 [EROR] Unable to get paths debug_id=faede431 err="No result" 2019-11-11 12:48:58.998294+0000 [WARN] Unable to reply to client debug_id=faede431 client=<nil> err="write unix /run/shm/sciond/default.sock->@: write: broken pipe" 2019-11-11 12:49:00.988075+0000 [DBUG] [PathRequestHandler] Received request debug_id=05b6f631 req="17-ffaa:1:ceb -> 17-ffaa:0:1101, maxPaths=5, flags={false false}" 2019-11-11 12:49:00.988237+0000 [DBUG] Requesting segments debug_id=05b6f631 ps="17-ffaa:1:ceb,[PS A (0x0001)]:0 (UDP)" 2019-11-11 12:49:10.988537+0000 [DBUG] Unclassified RPC error debug_id=05b6f631 msg= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:49:10.988574+0000 [EROR] Unable to retrieve paths from network debug_id=05b6f631 err= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:49:10.988587+0000 [EROR] Unable to get paths debug_id=05b6f631 err="No result" 2019-11-11 12:49:10.988666+0000 [DBUG] Replied with paths debug_id=05b6f631 num_paths=0 2019-11-11 12:49:10.989849+0000 [DBUG] [PathRequestHandler] Received request debug_id=f95b4e4f req="17-ffaa:1:ceb -> 17-ffaa:0:1101, maxPaths=5, flags={false false}" 2019-11-11 12:49:10.990062+0000 [DBUG] Requesting segments debug_id=f95b4e4f ps="17-ffaa:1:ceb,[PS A (0x0001)]:0 (UDP)" 2019-11-11 12:49:20.990241+0000 [DBUG] Unclassified RPC error debug_id=f95b4e4f msg= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:49:20.990277+0000 [EROR] Unable to retrieve paths from network debug_id=f95b4e4f err= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:49:20.990290+0000 [EROR] Unable to get paths debug_id=f95b4e4f err="No result" 2019-11-11 12:49:20.993752+0000 [WARN] Unable to reply to client debug_id=f95b4e4f client=<nil> err="write unix /run/shm/sciond/default.sock->@: write: broken pipe" 2019-11-11 12:52:33.750095+0000 [DBUG] [PathRequestHandler] Received request debug_id=91c23029 req="17-ffaa:1:ceb -> 20-ffaa:0:1404, maxPaths=0, flags={false false}" 2019-11-11 12:52:33.750315+0000 [DBUG] Requesting segments debug_id=91c23029 ps="17-ffaa:1:ceb,[PS A (0x0001)]:0 (UDP)" 2019-11-11 12:52:43.750614+0000 [DBUG] Unclassified RPC error debug_id=91c23029 msg= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:52:43.750686+0000 [EROR] Unable to retrieve paths from network debug_id=91c23029 err= > [Messenger] Request error req_type="SegRequest" > Read on stream 0 canceled with error code 1 2019-11-11 12:52:43.750701+0000 [EROR] Unable to get paths debug_id=91c23029 err="No result" 2019-11-11 12:52:43.750784+0000 [DBUG] Replied with paths debug_id=91c23029 num_paths=0 Restarting as described in the troubleshooting section and a fresh install have both not helped. What else could I try? Thanks for your help. Cheers, Joel

3 5

Re: [Scion] Missing default.sock
by Juan A. García-Pardo 12 Nov '19

12 Nov '19

Hi Marc, The file /run/shm/sciond/default.sock is created by the sciond process. Can you check the log file for sciond to see what's going on? It should be in ./logs/sd*.log Best regards, Juan A. On Mon, Nov 11, 2019 at 3:46 PM Styger Marc <stygerma(a)student.ethz.ch> wrote: > Hi, > > > I tried to build SCION according to the tutorial ( > https://netsec-ethz.github.io/scion-tutorials/install/src/) but I can't > get it to work properly. I tried to look at the result in the SCION webapp > and also ran scmp echo. The file /run/shm/sciond/default.sock is missing > and I don't know how to obtain it. Does anyone know what the issue could be? > > > Thank you for any kind of help. > > > Kind regards, > > > Marc > _______________________________________________ > Scion mailing list > Scion(a)lists.inf.ethz.ch > https://lists.inf.ethz.ch/mailman/listinfo/scion >

4 4

Missing default.sock
by Styger Marc 11 Nov '19

11 Nov '19

Hi, I tried to build SCION according to the tutorial (https://netsec-ethz.github.io/scion-tutorials/install/src/) but I can't get it to work properly. I tried to look at the result in the SCION webapp and also ran scmp echo. The file /run/shm/sciond/default.sock is missing and I don't know how to obtain it. Does anyone know what the issue could be? Thank you for any kind of help. Kind regards, Marc

1 0

Re: [Scion] [SCION] Scion IP Gateway problem
by Juan A. García-Pardo 04 Nov '19

04 Nov '19

Hi YoonJong, Our SIG tutorial misses one small step, that we are fixing right now. You have to add a service in the topology.json files of the SCIONLab user AS machine, that tells the services where the SIG is. This is the block: "SIG": { "sig": { "Addrs": { "IPv4": { "Public": { "Addr": "127.0.0.1", "L4Port": 31056 } } } } }, There was a message in this list some weeks ago from a user that had the same issue and he solved it like mentioned. http://lists.inf.ethz.ch/pipermail/scion/2019-October/000050.html Good luck! Juan A. On Thu, Oct 31, 2019 at 11:54 AM YoonJong, Na <nooryyaa(a)korea.ac.kr> wrote: > Hi > > I'm currently working on SCION IP gateway(sig) from > https://netsec-ethz.github.io/scion-tutorials/apps/remote_sig/ > > Currently running two SCION AS from different server with different IP > using "SCION installation from sources" option > I checked bwtester is working between two servers (20-ffaa:1:c42, > 20-ffaa:1:c5d), followed every step in the tutorial and double checked > config file > But I couldn't get "Hello World" message when I run curl command > > the following is the sig logs I got > > > 2019-10-31 10:25:55.993263+0000 [INFO] sessMonitor: New remote > ia=20-ffaa:1:c5d sessId=0x00 remote="Sig: 20-ffaa:1:c5d,[SIG A > (0x0004)]:0:0 Path: Key: > 6295594fc261a84071eeda3006017e03d0011da4000080c5aee9249c47149c30 Hops: > [20-ffaa:1:c42 1>2 20-ffaa:0:1404 8>1 20-ffaa:1:c5d] Mtu: 1472" > 2019-10-31 10:25:55.995533+0000 [DBUG] Ignoring scmp packet > hdr="Class=ROUTING(1) Type=UNREACH_HOST(1) TotalLen=64B Checksum=309b > Timestamp=2019-10-31 10:25:55.995729 +0000 UTC" src="{IA:20-ffaa:1:c5d > Host:127.0.0.1}" > 2019-10-31 10:25:56.003207+0000 [EROR] EgressReader: unable to find dest IA > ip=ff02::2 > 2019-10-31 10:25:56.493114+0000 [INFO] sessMonitor: Remote SIG timeout > ia=20-ffaa:1:c5d sessId=0x00 remote="Sig: 20-ffaa:1:c5d,[SIG A > (0x0004)]:0:0 Path: Key: > 6295594fc261a84071eeda3006017e03d0011da4000080c5aee9249c47149c30 Hops: > [20-ffaa:1:c42 1>2 20-ffaa:0:1404 8>1 20-ffaa:1:c5d] Mtu: 1472" > duration=4.500080099s > 2019-10-31 10:25:56.493327+0000 [INFO] sessMonitor: New remote > ia=20-ffaa:1:c5d sessId=0x00 remote="Sig: 20-ffaa:1:c5d,[SIG A > (0x0004)]:0:0 Path: Key: > 6295594fc261a84071eeda3006017e03d0011da4000080c5aee9249c47149c30 Hops: > [20-ffaa:1:c42 1>2 20-ffaa:0:1404 8>1 20-ffaa:1:c5d] Mtu: 1472" > 2019-10-31 10:25:56.495726+0000 [DBUG] Ignoring scmp packet > hdr="Class=ROUTING(1) Type=UNREACH_HOST(1) TotalLen=64B Checksum=4091 > Timestamp=2019-10-31 10:25:56.495968 +0000 UTC" src="{IA:20-ffaa:1:c5d > Host:127.0.0.1}" > > > Both of the servers are showing the similar log > Is there any misconfiguration possibly made? > > > Best regards, > Yoonjong > _______________________________________________ > Scion mailing list > Scion(a)lists.inf.ethz.ch > https://lists.inf.ethz.ch/mailman/listinfo/scion >

1 0

[SCION] Scion IP Gateway problem
by YoonJong, Na 31 Oct '19

31 Oct '19

Hi I'm currently working on SCION IP gateway(sig) from https://netsec-ethz.github.io/scion-tutorials/apps/remote_sig/ Currently running two SCION AS from different server with different IP using "SCION installation from sources" option I checked bwtester is working between two servers (20-ffaa:1:c42, 20-ffaa:1:c5d), followed every step in the tutorial and double checked config file But I couldn't get "Hello World" message when I run curl command the following is the sig logs I got 2019-10-31 10:25:55.993263+0000 [INFO] sessMonitor: New remote ia=20-ffaa:1:c5d sessId=0x00 remote="Sig: 20-ffaa:1:c5d,[SIG A (0x0004)]:0:0 Path: Key: 6295594fc261a84071eeda3006017e03d0011da4000080c5aee9249c47149c30 Hops: [20-ffaa:1:c42 1>2 20-ffaa:0:1404 8>1 20-ffaa:1:c5d] Mtu: 1472" 2019-10-31 10:25:55.995533+0000 [DBUG] Ignoring scmp packet hdr="Class=ROUTING(1) Type=UNREACH_HOST(1) TotalLen=64B Checksum=309b Timestamp=2019-10-31 10:25:55.995729 +0000 UTC" src="{IA:20-ffaa:1:c5d Host:127.0.0.1}" 2019-10-31 10:25:56.003207+0000 [EROR] EgressReader: unable to find dest IA ip=ff02::2 2019-10-31 10:25:56.493114+0000 [INFO] sessMonitor: Remote SIG timeout ia=20-ffaa:1:c5d sessId=0x00 remote="Sig: 20-ffaa:1:c5d,[SIG A (0x0004)]:0:0 Path: Key: 6295594fc261a84071eeda3006017e03d0011da4000080c5aee9249c47149c30 Hops: [20-ffaa:1:c42 1>2 20-ffaa:0:1404 8>1 20-ffaa:1:c5d] Mtu: 1472" duration=4.500080099s 2019-10-31 10:25:56.493327+0000 [INFO] sessMonitor: New remote ia=20-ffaa:1:c5d sessId=0x00 remote="Sig: 20-ffaa:1:c5d,[SIG A (0x0004)]:0:0 Path: Key: 6295594fc261a84071eeda3006017e03d0011da4000080c5aee9249c47149c30 Hops: [20-ffaa:1:c42 1>2 20-ffaa:0:1404 8>1 20-ffaa:1:c5d] Mtu: 1472" 2019-10-31 10:25:56.495726+0000 [DBUG] Ignoring scmp packet hdr="Class=ROUTING(1) Type=UNREACH_HOST(1) TotalLen=64B Checksum=4091 Timestamp=2019-10-31 10:25:56.495968 +0000 UTC" src="{IA:20-ffaa:1:c5d Host:127.0.0.1}" Both of the servers are showing the similar log Is there any misconfiguration possibly made? Best regards, Yoonjong

1 0

Starting self built fails with downloaded config
by Fischer Joel 29 Oct '19

29 Oct '19

Hi In the tutorial for building SCION from sources (https://netsec-ethz.github.io/scion-tutorials/install/src/) I got the following error after running "./scion start" as described in "Configuration > 4. Restart SCION": Traceback (most recent call last): File "python/integration/set_ipv6_addr.py", line 90, in <module> main() File "python/integration/set_ipv6_addr.py", line 71, in main overlay = get_overlay() File "python/integration/set_ipv6_addr.py", line 67, in get_overlay return read_file(file_path).strip() File "/home/fischjoe/go/src/github.com/scionproto/scion2/python/lib/util.py<http://github.com/scionproto/scion2/python/lib/util.py>", line 73, in read_file file_path, e.strerror)) from None lib.errors.SCIONIOError: Unable to open 'gen/overlay': No such file or directory Creating a file called overlay with "UDP/IPv4" in "gen" has solved the issue. Is this a correct configuration or will it break down the road? I am also not sure whether I missed something in the tutorial or whether a step is missing from it. Thanks for your help. Cheers, Joel

2 1