I have port 162 forwarded, which is how I'm able to receive the traps in
wireshark. I've briefly tried setting up the Bridged Networking, but so far,
the guest can't connect. My host runs on wifi, and unfortunately, I can't
change that. Reading the user manual, it sounds like it's a more complicated
set up to use bridged to a wireless adapter.
For what I want to do, is Bridged my only option?
Thanks,
Jessica
________________________________
From: Gregory Nowak <[email protected]>
Sent: Tuesday, November 7, 2017 4:40 PM
To: Community mailing list of VirtualBox users
Subject: Re: [VBox-users] Unable to receive snmp trap in trap receiver on linux
guest
On Tue, Nov 07, 2017 at 06:28:13PM +0000, jessica otte wrote:
> I have set up a virtualbox with Fedora 24 as the guest, and running on a
> windows host. The reason I set this up was because I want to use net-snmp on
> the virtualbox (since it's not working for me on windows). The problem is: I
> can see a v2 trap come in using Wireshark, but cannot receive it in the two
> trap receivers that I have tried.
>
>
> In Wireshark, the v2 trap looks correct. I can see the correct source IP and
> the packet looks as I would expect. I am trying to use net-snmp snmptrapd to
> receive the trap, and the daemon starts up but doesn't receive anything sent
> from a real device. I can send a trap within the VitualBox to itself and see
> it get received in the trap daemon, so I know that the receiver is running
> and capable of receiving traps. I have confirmed that the daemon is indeed
> running on port 162 by running 'netstat -anp | grep 162’. The snmptrapd.conf
> file has one line in it: "authCommunity log,net public". I have a coworker
> who set up net-snmp exactly as I have, except that he's running on a VM
> rather than a VirtualBox and he's able to receive traps. I have also tried
> installing WebNMS and using their snmpv3trapd receiver (which I've used
> before on my windows machine), and it's also unable to get the trap in the
> VirtualBox.
>
> There must be some networking type of setting that I'm missing, but at this
> point, I have no idea what it would be. Any help/direction/ideas would be
> greatly appreciated.
>
> Thanks!
If you haven't done so already, you probably need to either forward
the ports you need to the guest, or use bridged networking. See
sections 6.3.1, and 6.5 of the virtualbox users manual.
Greg
--
web site: http://www.gregn.net
gregn.net - Greg's web site<http://www.gregn.net/>
www.gregn.net
Greg's home page. Hello. You have apparently stumbled upon my humble corner of
the world wide web, welcome! You are using IPv4 from 157.55.39.214.
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.
--
Free domains: http://www.eu.org/ or mail [email protected]
EU.org: free domain names since 1996<http://www.eu.org/>
www.eu.org
Free domain names
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:
mailto:[email protected]?subject=unsubscribe
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:
mailto:[email protected]?subject=unsubscribe
