[snmp] wanted Information regarding the PORT from whichInformResponseis sendout

[Gejo.Thayil at aricent.com]

Hi Birjit,

         Thanks for your guidance, I could make this work
I was trying all nonsense by creating and deleting sockets a number of 
times. which i later found to be stupid
now that i added a method in DefaultInformContext (to send the Pdu) and 
then call it from Pdu.sendme( )
(I'm adding a check to ensure only INFORM Response pdu is send through 
DefaultInformContext)
currently Stack uses only the method in Abstract SnmpContext to send 
packets

Now my Stack works fine and the RESPONSE to INFORM is send out from 
Received Port (162)



Regards

Gejo Joseph
Flextronics Software Systems
18/1, Outer Ring Road
Panathur Post, Bangalore

"I would love to change the world, but no one would give me the source 
code"



Birgit Arkesteijn <birgit at westhawk.co.uk> 
Sent by: snmp-bounces at snmp.westhawk.co.uk
11/15/2006 08:18 PM

Please respond to
List for discussion of the Westhawk SNMP stack<snmp at snmp.westhawk.co.uk>


To
List for discussion of the Westhawk SNMP stack <snmp at snmp.westhawk.co.uk>
cc

Subject
Re: [snmp] wanted Information regarding the PORT from 
whichInformResponseis sendout






Hi Gejo,

I'm not sure I follow what you try to do.
The stack gives you no control over the source transport address.
Also, I feel you're trying to solve it at a low level.

However, if you get it work, good for you!
All the best.

Cheers, Birgit


On Wed, Nov 15, 2006 at 07:34:25PM +0530, Gejo.Thayil at aricent.com wrote:
> Hi Birjit,
> 
>     Thanks for your Immediate Response to my mail, I was thinking of a 
> simple workaround to this problem 
> and is still trying on it
> 
> - what I was trying is that to close the socket once we receive an 
INFORM, 
> then create it to send the RESPONSE
>   so that IPSec now sees the packet coming from the same port (SNMP TRAP 

> Port). 
> - Again close the socket after sending RESPONSE, 
> - DefaultInformContext(DefaultTrapContext) comes to know when socket is 
> closed 
>   Now try to create the Socket after a delay. Thread.sleep(An optimum 
> time); 
>   (This will takecare of the timegap between receiving and sending 
packet 
> )
> 
> 
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>  with this i could send out a RESPONSE to INFORM (for the first time 
from 
> Received Port(162)),
> it again started listening on the same PORT(162) after sleeping for an 
> optimum time
> received a 2nd INFORM but some socket creation error came before sending 

> RESPONSE (I'm working on this)
> 
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
> I think if we try this way, the only drawback is it will drop any packet 

> that comes while the stack is processing a RESPONSE to a received 
INFORM.
> Now that stack takes a processing time < 300mS (calculated by capturing 
> INFORM and RESPONSE on ethereal) this is not a drawback at all
> 
> 
> Sadly I'm not an expert on Sockets, so its taking some time for me, will 

> let you know if i can make this work
> 
> 
> 
> Regards
> 
> Gejo Joseph
> Flextronics Software Systems
> 18/1, Outer Ring Road
> Panathur Post, Bangalore
> 
> "I would love to change the world, but no one would give me the source 
> code"


-- 
-- Birgit Arkesteijn, birgit at westhawk.co.uk,
-- Westhawk Ltd, Albion Wharf, 19 Albion Street, Manchester M1 5LN, UK
-- tel.: +44 (0)161 237 0660
-- <URL: http://www.westhawk.co.uk>
_______________________________________________
snmp mailing list
snmp at snmp.westhawk.co.uk
http://snmp.westhawk.co.uk/mailman/listinfo/snmp



***********************  Aricent-Unclassified   ***********************
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of 
the individual to whom it is addressed. It may contain privileged or confidential information and should not be 
circulated or used for any purpose other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for 
loss or damage arising from the use of the information transmitted by this email including damage from virus."