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

[version 2.1] Issues communicating between devices on local server and devices on GNS3 VM #1231

Closed
AJNOURI opened this Issue Nov 26, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@AJNOURI
Contributor

AJNOURI commented Nov 26, 2017

Reproduced a reported issue on community forum:
https://gns3.com/qa/connect-iou-router-in-gns3-vm-to


This is a test with dynamips routers:

  • case1: router on local -to- router on GNS3 VM ==> NOK
  • case2: router on local -to- router on local ==> OK
  • case3: router on GNS3 VM -to- router on GNS3 VM ==> OK

selection_007_26_11

case 1: ping fails, checked interfaces UP/UP
selection_005_26_11

Case1 wireshark on link shows only ARP traffic from local router

selection_003_26_11

Could have the same root problem as here
#1181


GNS3 version is 2.1.0 (compiled)
Python version is 3.6.3 (64-bit) with utf-8 encoding
Qt version is 5.8.0
PyQt version is 5.8
SIP version is 4.19.5

@grossmj

This comment has been minimized.

Member

grossmj commented Nov 26, 2017

The local server and the VM must be on the same network. What are the IP addresses for both?

@grossmj grossmj self-assigned this Nov 26, 2017

@grossmj grossmj added this to the 2.1.1 milestone Nov 26, 2017

@AJNOURI

This comment has been minimized.

Contributor

AJNOURI commented Nov 27, 2017

Indeed Jeremy @grossmj , both addresses where not in the same network.
I changed the local server IP to vmnet1 subnet IP.
Thanks.

image

With all the choices and without any check or warnings, users could easily and silently run into the same issue.

selection_003_27_11

Because already GNS3 VM will default to vmnet1 or the first vbox interface, should we give the user the choice of the local server IP?
If the user choose local server IP in the same hypervisor subnet, the server won't be available to outside gns3 clients.
Otherwise, it won't be possible to communicate with gns3 vm devices.

Shouldn't we for example default the local server to 0.0.0.0 (all interfaces), this way we avoid the previous mentioned issues?

@grossmj grossmj added the Enhancement label Nov 27, 2017

grossmj added a commit that referenced this issue Dec 5, 2017

@grossmj

This comment has been minimized.

Member

grossmj commented Dec 6, 2017

I have implemented a warning now.

@grossmj grossmj closed this Dec 6, 2017

@AJNOURI

This comment has been minimized.

Contributor

AJNOURI commented Dec 6, 2017

Thanks @grossmj

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment