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.

Sign up for GitHub

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

Jump to bottom

The Nat node should be available only for GNS3 VM #1448

Closed
julien-duponchelle opened this issue Aug 26, 2016 · 2 comments
Closed

The Nat node should be available only for GNS3 VM #1448

julien-duponchelle opened this issue Aug 26, 2016 · 2 comments
Assignees
@julien-duponchelle
Labels
Bug
Milestone
2.0.1

Comments

@julien-duponchelle
Copy link
Contributor

The NAT node work fine but actually when you drop it on the topology you have the choice of the compute node.

It should be only the GNS3 VM for the moment.
@julien-duponchelle julien-duponchelle added this to the 2.0 milestone Aug 26, 2016
@julien-duponchelle
Copy link
Contributor Author

The correct way to handle that is to return in the compute the capabilities of the server

@julien-duponchelle julien-duponchelle self-assigned this Aug 29, 2016
julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Aug 29, 2016
@julien-duponchelle
Return what is supported by a compute node
bbc1505 
Ref GNS3/gns3-gui#1448
@julien-duponchelle
Copy link
Contributor Author

Now the compute return this information:
http://api.gns3.net/en/2.0/api/v2/compute/capabilities/capabilities.html

And it's include in the Compute object returned by the controller

julien-duponchelle added a commit to GNS3/gns3-server that referenced this issue Aug 29, 2016
@julien-duponchelle
Nat node is only on the GNS3 VM for the moment
36d2e80 
Fix GNS3/gns3-gui#1448
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@julien-duponchelle julien-duponchelle

Labels
Bug
Projects
None yet
Milestone
2.0.1
Development

No branches or pull requests
1 participant
@julien-duponchelle