-
Notifications
You must be signed in to change notification settings - Fork 264
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
Snmpd on the gns3 vm for gns3 version 3 please #2095
Comments
Dragging in two gns3-endhost I get sudo netstat -tunlp Well, maybe such a public function exists to get.... |
No, it is too much of a security risk to add snmpd to 1000s of gns3 vm's. Yes, the port number a node on an interface uses is not accessible in the gns3 api documentation for nodes or links. |
Hold. let me put 2 ubuntu devices (ubuntu-ssh-snmpd) in a gns3 project on a gns3 vm in vmware workstation on windows 10 and reverse engineer the network to get the tcp ports. i will just manually get the tcp port numbers. then let me see if i can get powershell to inspect the devices remotely and get the input and output rate with something like |
Oh, I will use new-object -comobject as a backup. |
Ok, let me know if you need snmpd on the GNS3 VM, I guess I could just add it... |
Some gns3 users get upset in the community over security. They might get upset. gns3-vm-snmpd is perfectly fine for me. |
and the gns3 vm console is expensive real estate so i would not add it into the gns3 vm console menu. |
Could always add it but not start it. I don't run the VM but couldn't you always just add it via apt as well assuming the GNS3 VM has internet access? |
oh yeah, i forgot that some people do not have access with their gns3 vm. |
Done :) |
I messed up this post by not following the "suggestion template. Sorry.
it up. This should be a suggestion:
/etc/rc.d/init.d/snmpd status
bash: /etc/rc.d/init.d/snmpd: No such file or directory
service snmpd status
Unit snmpd.service could not be found.
re: #2092
I would need "snmpd" on the gns3 vm to handle situations like 2092.
I do have a "GNS3-VM-exp" (i.e. exp is for experimental), but I am not putting snmpd on my main gns3 vm.
As far as putting snmpd on the main GNS3 VM that is distributed to thousands of gns3 users is concerned, that is not my call.
But, if snmpd is running on the main gns3 vm, then I should be able to obliterate 2092 in an effortless fashion.
So, as far as OID value: 1.3.6.1.2.1.2.2.1.1, I might need some public access to whatever ports a node is running on. When i mean public access, it has to be an official documented way to access what a port a node is running in, as opposed to me going in and reverse engineering something.
Edit: Hrmmmm...I will go with GNS3-VM-snmpd for now. Yeah. That's the way for me to go.
The text was updated successfully, but these errors were encountered: