[SCION] SCIONLab installation

[Juan A. García-Pardo]

Hi again Hobin,

> Hi SCION Team,
>
> I am resending this email because I noticed that the attachments do not
> appear on the mailing list website.
>
Our emails must have crossed in the air :D I answered your previous email,
but with this new information, let me give you different answers:

I have some trouble installing SCIONLab AS from packages on my
> server(Ubuntu 18.04).
>
> The problem is that no service is operational on port 50000.
> Can I get any advice regarding this issue?
>
> Here is my configuration.
> my AS number: AS ffaa:1:100b
> attachment point: KU(20-ffaa:0:1404)
> AS Public IP: xxx.xxx.xxx.xxx
> Public Port: 50000
>
> This is the command and the result:
> sudo systemctl list-dependencies scionlab.target
>
> scion-border-route at br-1.service mailto:scion-border-route at br-1.service
> scion-colibri-service at co-1.service mailto:
> scion-colibri-service at co-1.service
> scion-control-service at cs-1.service mailto:
> scion-control-service at cs-1.service
> scion-daemon.service
> scion-dispatcher.service
>
> All entries with these services show green.
>
This looks alright.


> the command and the result:
> sudo netstat -tulpn | grep LISTEN | grep scion
>
> tcp 127.0.0.1:30401 scion-border-ro
> tcp 127.0.0.1:30441 scion-dispatche
> tcp 127.0.0.1:30254 scion-control-s
> tcp 127.0.0.1:30255 sciond
> tcp 127.0.0.1:30257 scion-colibri-s
> tcp 127.0.0.1:30454 scion-control-s
> tcp 127.0.0.1:30455 sciond
>
Can you show us your topology? Run:
cat /etc/scion/topology.json


> the command and the result:
> sudo systemctl list-dependencies scion-daemon.service
>
> only NetworkManager-wailt-online.service show red entry point.
>
So as if your network setup is not yet finished? Can you check you have
public IP access in the machine? Does ping to the attachment point work?

command and result:
> curl -sfs localhost:30401/metrics | grep router_interface_up
>
> router_interface_up{interface="1",isd_as="20-ffaa:1:100b",neighbor_isd_as="20-ffaa:0:1404"}
> 0
>
 This is expected from the data you have been sharing so far (the border
router interface is down).

Thanks and let's find out what happens!!!
Best regards,

Juan A.