On Wed, 22 May 2024 at 01:58, Bart Van Assche wrote:
> The attached patch in combination with a patch that reduces code
> duplication have been applied. Please retest.
>
> Hello Bart,
That is a nice update to reduce code duplication, and thanks for applying
the patch plus the update.
I've teste
On 5/21/24 5:14 AM, Teus Benschop wrote:
Thank you for the go-ahead.
I went ahead and created the patch for the UDP domain.
In line with the previous patch where you had added support for IPv6, I
have added that support to this patch too.
It was tested and works fine when the snmpd listens on ud
On Mon, 13 May 2024 at 14:26, Bart Van Assche wrote:
> On 5/13/24 03:05, Teus Benschop wrote:
>
>
> The patches work for the TCP domain, and that certainly is sufficient for
> us, and we are happy.
>
> Would it also be helpful if I would create similar patches for the *UDP*
> domain?
>
> Generali
On 5/13/24 03:05, Teus Benschop wrote:
The patches work for the TCP domain, and that certainly is sufficient
for us, and we are happy.
Would it also be helpful if I would create similar patches for the
*UDP* domain?
Generalizing this work by adding UDP support for this mechanism sounds
go
On Thu, 9 May 2024 at 18:20, Teus Benschop wrote:
>
> I have tested the master branch on GitHub, including branch V5-9, on
> getting the local listening port number of the agent.
> It works well for TCP over IPv4 and also over IPv6.
> In both cases I get to see the local listening port number whe
Hello Bart,
Thank you for adding IPv6 support to the patch, and for integrating all the
changes into the V5-9 branch.
We are so glad about that.
I have tested the master branch on GitHub, including branch V5-9, on
getting the local listening port number of the agent.
It works well for TCP over I
On 5/8/24 1:42 AM, Teus Benschop wrote:
I have implemented the f_setup_session() callback in
the snmpTCPBaseDomain.h/.c files.
This callback obtains the port number and copies that into the session
object.
Then from the session object, the local_port is available while
processing the SNMP req
On Wed, 3 Apr 2024 at 18:45, Bart Van Assche wrote:
> I think this is the callchain for registering the ports that the agent
> listens on:
>
> init_master_agent()
> netsnmp_agent_listen_on()
> netsnmp_transport_open_server()
> netsnmp_register_agent_nsap()
> netsnmp_sess_config_tr
On Wed, 3 Apr 2024 at 18:45, Bart Van Assche wrote:
>
> I think this is the callchain for registering the ports that the agent
> listens on:
>
[...]
> One possible approach is to implement the .f_setup_session() callback in
> the TCP transport and to make it copy the port information from the
>
On 4/3/24 02:35, Teus Benschop wrote:
A snmpd was set to listen on 10 ports through multiple entries like
“agentaddress tcp:” in the snmpd.conf file.
It was verified through snmpget that the snmpd listens on all 10 ports.
Function “netsnmp_callback_open” in file
snmplib/transports/snmpCallba
On Thu, 28 Mar 2024 at 00:13, Bart Van Assche wrote:
> Thanks for the background information. I'm not sure the Net-SNMP API needs
> to be modified to realize this. How about the following approach:
>
>- Use netsnmp_register_handler() in MIB implementations to associate
>OIDs with callback
On Thu, 28 Mar 2024 at 00:13, Bart Van Assche wrote:
> Hi Teus,
>
> Thanks for the background information. I'm not sure the Net-SNMP API needs
> to be modified to realize this. How about the following approach:
>
>- Use netsnmp_register_handler() in MIB implementations to associate
>OIDs
On 3/27/24 00:15, Teus Benschop wrote:
On Wed, 27 Mar 2024 at 00:58, Bart Van Assche wrote:
Please explain why you want to obtain that information and also
how you plan to use it. Which APIs to modify will depend on the
answer to that question.
Hello Bert,
Thank you for asking t
On Wed, 27 Mar 2024 at 00:58, Bart Van Assche wrote:
> Please explain why you want to obtain that information and also how you
> plan to use it. Which APIs to modify will depend on the answer to that
> question.
>
>
>
Hello Bert,
Thank you for asking this question.
The background to this is tha
On 3/25/24 11:26, Teus Benschop wrote:
2. What are the ideas to expose this agent_tcp_port_number via the
API? (Possibly I could add a function in the public API, that gets
this variable and exposes it as a call.) Ideas?
Please explain why you want to obtain that information and also how you
Hello again,
On the topic of getting the agent listening port number while processing a
SNMP equest, discussed in previous emails:
I am working on a proposal for a patch, and have this code already, as a
first possible partial solution to the above wish.
File: snmplib/transports/snmpTCPBaseDomai
On Tue, 5 Sept 2023 at 22:16, Teus Benschop wrote:
> I could not find a way to display the port number, also not using the
> various debug tokens.
>
I ran snmpd as
snmpd -f -Le -Dnetsnmp_udp 2000,3000
and got
netsnmp_udp: recvfrom fd 6 got 41 bytes (from UDP:
[127.0.0.1]:36600->[127.0.0.1]:2000)
Hello,
I've been digging around in the library for a while to check out
whether the port number that the agent listens on, if it listens on
multiple ports, can be retrieved via the API, while the snmpd
processes a request via snmpget or snmpset.
I could not find a way to display the port number,
18 matches
Mail list logo
