Article 4731 Subject Re: Problem with IdSNMP Trap [Edit] [Edit] on embarcadero.public.delphi.internet.winsock

Article

From:

Nguyen Diep

📋

To:

Remy Lebeau (TeamB)

Subject:

Re: Problem with IdSNMP Trap [Edit] [Edit]

Newsgroup:

embarcadero.public.delphi.internet.winsock

Previous
in thread

19-Aug-2010

Re: Problem with IdSNMP Trap [Edit] [Edit]

> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
> TIdSNMP has been fixed to use both ports now 
> (TIdSNMP has a separate TrapPort property, afterall - it just was not 
> previoiusly using it for anything).  As such, you need to update your code 
> accordingly:
> 
> {code:delphi}
> procedure TfrmMain.bbtStartClick(Sender: TObject);
> begin
>   snmp.TrapPort := 162; // <-- do not use BoundPort for traps!
>   ...
> end;
> {code}
> -- 
> Remy Lebeau (TeamB)

I have checked and confirm with mr Remy that Indy latest version (19 Aug, 2010) has fixed the bug with TrapPort now (my Indy version is a few months old, at that time I navigated source code and saw that TrapPort took no effect, so I must use BoundPort).

> {quote:title=Nguyen Diep wrote:}{quote}
> You must set the property snmp.BoundPort = 162 so that it is listening on this port and can process snmp trap meassage.

To Pierre Dupr__s: of course you do not need to use BoundPort any more

FYI: Phrase searches are enclosed in either single or double quotes