SCION AS Visualization - Socket Timeout
38 views
Skip to first unread message
Siddharth Mehrotra
May 10, 2019, 5:50:18 AM5/10/19
to SCION community
Hello everyone,
I am a newbie to SCION and interested in learning more about it :)
I'm trying to run Browser AS Visualization in my system but it is always returning the error of Socket Timeout.
I am Connected to SCIONLab via VPN. The command I am using for visualization is python3 ./manage.py runserver 127.0.0.1:2222
Also, I'm putting same IP + Port in browser. However, when I put 127.0.0.1:8000/, 127.0.0.1 refused to connect.
Am I doing something wrong with IP address listing?
Thanks!
Michael W. Farb
May 10, 2019, 10:08:38 AM5/10/19
to SCION community
Hi Siddharth,
It looks like the 'Socket Timeout' message is coming from a failure to find granular path segments data. Sorry about that. The error is a bit erroneous and we'll work to eliminate it. If you see paths rendered in the graph however, even though the 'Socket Timeout' message is at the top of the screen, the communication between ASes is working as expected.
In our VMs we are running
automatically. So that 127.0.0.1:8000 should show the visualization in the browser.
Running 2 instances of the webserver at manage.py under separate ports will have unexpected results.
In your VMs host folder, the vagrantfile defines which ports will allow traffic through. We have opened port 8000 for the visualization. Port 2222 is not forwarded in the vagrantfile, and so communication would be prevented by default.
Let me know if the following is correct:
- The VM is running with "vagrant up"
- The browser window is pointed to 127.0.0.1:8000
- 'Socket Error' may be visible on the page.
- Your VMs AS is entered in the source field.
- Another AS is entered into the destination field. Sample destinations can be found on: https://netsec-ethz.github.io/scion-tutorials/sample_projects/bwtester/
- Clicking 'Request Data" produces 'Socket Error' even though a set of paths through the network is shown.
Cheers,
Mike
It looks like the 'Socket Timeout' message is coming from a failure to find granular path segments data. Sorry about that. The error is a bit erroneous and we'll work to eliminate it. If you see paths rendered in the graph however, even though the 'Socket Timeout' message is at the top of the screen, the communication between ASes is working as expected.
In our VMs we are running
python3 ./manage.py runserver 0.0.0.0:8000 &
automatically. So that 127.0.0.1:8000 should show the visualization in the browser.
Running 2 instances of the webserver at manage.py under separate ports will have unexpected results.
In your VMs host folder, the vagrantfile defines which ports will allow traffic through. We have opened port 8000 for the visualization. Port 2222 is not forwarded in the vagrantfile, and so communication would be prevented by default.
Let me know if the following is correct:
- The VM is running with "vagrant up"
- The browser window is pointed to 127.0.0.1:8000
- 'Socket Error' may be visible on the page.
- Your VMs AS is entered in the source field.
- Another AS is entered into the destination field. Sample destinations can be found on: https://netsec-ethz.github.io/scion-tutorials/sample_projects/bwtester/
- Clicking 'Request Data" produces 'Socket Error' even though a set of paths through the network is shown.
Cheers,
Mike
Siddharth Mehrotra
May 13, 2019, 6:00:34 AM5/13/19
to SCION community
Hi Mike,
Thanks for reverting back! It is solved now :), however "Socket Error" message is still there (granular path issue).
I also have an issue related to webapp, which I have posted on https://github.com/netsec-ethz/scion-apps/issues/66
Can you help me with that?
PS: I am working on usability and privacy issues for SCION, so covering as many topics as I can for same.
Best,
Sid
Reply all
Reply to author
Forward
0 new messages