[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using raw to post data



   Thanks Paul. I thought that was the case. I'll get with my network guy
   and see about getting the device and a PC with Wireshark on the same
   hub (if possible), or have the switch port mirror.

   On Tue, Mar 3, 2015 at 10:44 AM, <[1]paul.roy@xxxxxxx> wrote:

     � �You can only see the traffic between other computer if they are
     on the
     � �same segment./ hub but probably you are using a switched
     network. so
     � �you need a special configuration in your switch to mirror the
     port...
     � �the equivalent of wireshark on IBMi� is the TRCCNN command
     � �Paul
     � �From:� � � � Michael Ryan <[2]michaelrtr@xxxxxxxxx>
     � �To:� � � � HTTPAPI and FTPAPI Projects
     <[3]ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
     � �Date:� � � � 03/03/2015 15:38
     � �Subject:� � � � Re: Using raw to post data
     � �Sent by:� � � � [4]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
     � �     �__________________________________________________________________

   � �Ok...I'm using Wireshark to capture the packets, but I seem to be
   � �having
   � �problems. There's a test program that runs on my PC. I'm able to
   � �capture
   � �and display the packets between my PC and the device. That process
   � �works,
   � �and the packets are what I expect.
   � �I'm having a problem specifying two different hosts (the IBMi and
   the
   � �device) for either capturing just those packets (capture filter)
   or
   � �displaying just those packets (display filter). Any ideas? What do
   I
   � �need
   � �to specify for capture and/or display filters to see all the
   packets on
   � �the
   � �network that are between these two IP addresses?
   � �Thanks!
   � �On Mon, Mar 2, 2015 at 2:14 PM, Michael Ryan
   <[5]michaelrtr@xxxxxxxxx>
   � �wrote:
   � �> All good thoughts Mike. I plan on getting the traces tomorrow
   with
   � �> Wireshark. I'll share what I get in hopes you all can help!
   Thanks!
   � �>
   � �> On Mon, Mar 2, 2015 at 2:01 PM, Mike Krebs
   � �<[6]mkrebs@xxxxxxxxxxxxxxxxxx>
   � �> wrote:
   � �>
   � �>> Do you have the C# code running? Or are you using it as
   template to
   � �work
   � �>> from? If you have working code and are not sure of the
   parameters,
   � �then
   � �>> wireshark is probably a good idea.� If it is just a template,
   share
   � �the C#
   � �>> code if you can and one of the multi-lingual programmers will
   help
   � �>> interpret.
   � �>>
   � �>> Considering it appears to be some sort of error with the
   � �communication, I
   � �>> would go back to the "am I hitting a valid url?" question. And
   that,
   � �the
   � �>> wireshark will help with. You should clearly see the POST
   � �information being
   � �>> sent in the wireshark.
   � �>>
   � �>> Since appears to be a credit/debit system, I assume the data
   itself
   � �is
   � �>> going to be encrypted by TLS in the wireshark. So, that is not
   going
   � �to be
   � �>> much help.
   � �>>

     � �>> Should your URL be [1]https:?

   � �>>
   � �>>
   � �>> -----Original Message-----
   � �>> From: [7]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:
   � �>> [8]ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Michael
   Ryan
   � �>> Sent: Monday, March 2, 2015 11:07 AM
   � �>> To: HTTPAPI and FTPAPI Projects
   � �>> Subject: Re: Using raw to post data
   � �>>
   � �>> Ok...I'm getting a -1 here in recvresp:
   � �>>
   � �>> eval� � � wwRec = comm_lineread( peComm
   � �>>� � � � � � � � � � � � � � � � : wwPos
   � �>>� � � � � � � � � � � � � � � � : wwLeft
   � �>>� � � � � � � � � � � � � � � � : peTimeout )
   � �>>
   � �>> It then throws the 'recvresp(): end with err message.
   � �>>
   � �>> Wireshark is my option?
   � �>>
   � �>> Thanks...
   � �>>
   � �>> On Fri, Feb 27, 2015 at 4:30 PM, Charles Wilt
   � �<[9]charles.wilt@xxxxxxxxx>
   � �>> wrote:
   � �>>
   � �>> >� � The C# code might be helpful...
   � �>> >� � I'd guess if it's doing a HTTP post, you'll be able to
   use HTTP
   � �>> API...
   � �>> >� � The wireshark capture certainly will.
   � �>> >� � Charles
   � �>> >� � On Fri, Feb 27, 2015 at 3:37 PM, Michael Ryan <[1]
   � �>> [10]michaelrtr@xxxxxxxxx>
   � �>> >� � wrote:
   � �>> >
   � �>> >� � � �  �I think you're right. I just asked them for
   what is
   � �actually
   � �>> >� � � sent and
   � �>> >� � � �  �received by the device, and they gave me some
   C# code
   � �(with
   � �>> >� � � does do an
   � �>> >� � � �  �HTTP POST) and the XML.
   � �>> >
   � �>> > References
   � �>> >

     � �>> >� � 1. [2]mailto:[11]michaelrtr@xxxxxxxxx
     � �>> >
     � �>> >
     �     �------------------------------------------------------------------
     ----
     � �>> > - This is the FTPAPI mailing list.� To unsubscribe,
     please go to:
     � �>> > [3][12]http://www.scottklement.com/mailman/listinfo/ftpapi
     � �>> >
     �     �------------------------------------------------------------------
     ----
     � �>> > -
     � �>> >
     � �>> >
     � �>>
     �     �------------------------------------------------------------------
     -----
     � �>> This is the FTPAPI mailing list.� To unsubscribe, please go
     to:
     � �>> [4][13]http://www.scottklement.com/mailman/listinfo/ftpapi
     � �>>
     �     �------------------------------------------------------------------
     -----
     � �>>
     � �>
     � �>
     �     �------------------------------------------------------------------
     -----
     � �This is the FTPAPI mailing list.� To unsubscribe, please go
     to:
     � �[5][14]http://www.scottklement.com/mailman/listinfo/ftpapi
     �     �------------------------------------------------------------------
     -----
     References
     � �1. https:?
     � �2. mailto:[15]michaelrtr@xxxxxxxxx
     � �3. [16]http://www.scottklement.com/mailman/listinfo/ftpapi
     � �4. [17]http://www.scottklement.com/mailman/listinfo/ftpapi
     � �5. [18]http://www.scottklement.com/mailman/listinfo/ftpapi
     --------------------------------------------------------------------
     ---
     This is the FTPAPI mailing list.� To unsubscribe, please go to:
     [19]http://www.scottklement.com/mailman/listinfo/ftpapi
     --------------------------------------------------------------------
     ---

References

   1. mailto:paul.roy@xxxxxxx
   2. mailto:michaelrtr@xxxxxxxxx
   3. mailto:ftpapi@xxxxxxxxxxxxxxxxxxxxxx
   4. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   5. mailto:michaelrtr@xxxxxxxxx
   6. mailto:mkrebs@xxxxxxxxxxxxxxxxxx
   7. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   8. mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   9. mailto:charles.wilt@xxxxxxxxx
  10. mailto:michaelrtr@xxxxxxxxx
  11. mailto:michaelrtr@xxxxxxxxx
  12. http://www.scottklement.com/mailman/listinfo/ftpapi
  13. http://www.scottklement.com/mailman/listinfo/ftpapi
  14. http://www.scottklement.com/mailman/listinfo/ftpapi
  15. mailto:michaelrtr@xxxxxxxxx
  16. http://www.scottklement.com/mailman/listinfo/ftpapi
  17. http://www.scottklement.com/mailman/listinfo/ftpapi
  18. http://www.scottklement.com/mailman/listinfo/ftpapi
  19. http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------