[Scion] Trouble running Scion ip Gateway
tony.john at st.ovgu.de
tony.john at st.ovgu.de
Fri Oct 4 14:50:26 CEST 2019
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 at 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 at 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
More information about the Scion
mailing list