Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.2 : bug when starting of vpcs stopped with "quit" #3110

Closed
Raizo62 opened this issue Dec 12, 2020 · 4 comments
Closed

2.2 : bug when starting of vpcs stopped with "quit" #3110

Raizo62 opened this issue Dec 12, 2020 · 4 comments
Labels
Milestone

Comments

@Raizo62
Copy link

Raizo62 commented Dec 12, 2020

Hi

I put on GNS3 a VPCS

I start the VPCS

On the VPCS, i use the command quit

GNS3 shows that the VPCS is stopped (red button)

But, if i start again this VPCS, GNS3 shows an error :

2020-12-12 10:55:42 ERROR node.py:237 error while starting PC1: Could not start VPCS /usr/bin/vpcs: [Errno 98] error while attempting to bind on address ('0.0.0.0', 5000): address already in use

2020-12-12 10:55:42 CRITICAL __init__.py:1637 Could not start VPCS /usr/bin/vpcs: [Errno 98] error while attempting to bind on address ('0.0.0.0', 5000): address already in use
@Raizo62 Raizo62 added the Bug label Dec 12, 2020
@grossmj grossmj added this to the 2.2.18 milestone Dec 13, 2020
@grossmj
Copy link
Member

grossmj commented Jan 26, 2021

I think this is because VPCS hasn't set the port to be immediately reusable (SO_REUSEADDR)

https://hea-www.harvard.edu/~fine/Tech/addrinuse.html

Please can you use the quit command again but this time wait 5 minutes before restarting VPCS. This will validate the root of the issue. Thanks!

@Raizo62
Copy link
Author

Raizo62 commented Jan 27, 2021

I think this is because VPCS hasn't set the port to be immediately reusable (SO_REUSEADDR)

https://hea-www.harvard.edu/~fine/Tech/addrinuse.html

I think this link does not recommend to use SO_REUSEADDR

Please can you use the quit command again but this time wait 5 minutes before restarting VPCS. This will validate the root of the issue. Thanks!

I have tested (with 9 minutes) and i have now this error :

=> error while starting PC1: Error while sending command 'bridge create VPCS-21f94403-a183-4a11-98b9-d1660b4786d6': bridge 'VPCS-21f94403-a183-4a11-98b9-d1660b4786d6' already exist: uBridge version 0.9.19 running with libpcap version 1.10.0 (with TPACKET_V3)
Hypervisor TCP control server started (IP 127.0.0.1 port 33313).
UDP tunnel connecting from local port 10003 to IPv4 address 127.0.0.1 on port 10002
UDP tunnel connecting from local port 10000 to IPv4 address 127.0.0.1 on port 10001
Source NIO listener thread for VPCS-21f94403-a183-4a11-98b9-d1660b4786d6 has started
Destination NIO listener thread for VPCS-21f94403-a183-4a11-98b9-d1660b4786d6 has started

Error while sending command 'bridge create VPCS-21f94403-a183-4a11-98b9-d1660b4786d6': bridge 'VPCS-21f94403-a183-4a11-98b9-d1660b4786d6' already exist: uBridge version 0.9.19 running with libpcap version 1.10.0 (with TPACKET_V3)
Hypervisor TCP control server started (IP 127.0.0.1 port 33313).
UDP tunnel connecting from local port 10003 to IPv4 address 127.0.0.1 on port 10002
UDP tunnel connecting from local port 10000 to IPv4 address 127.0.0.1 on port 10001
Source NIO listener thread for VPCS-21f94403-a183-4a11-98b9-d1660b4786d6 has started
Destination NIO listener thread for VPCS-21f94403-a183-4a11-98b9-d1660b4786d6 has started

@grossmj
Copy link
Member

grossmj commented Jan 27, 2021

Ok, looks like the problem is with uBridge which is not shutdown when vpcs is stopped.

@grossmj
Copy link
Member

grossmj commented Feb 14, 2021

Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants