Re: [twsocket] Any BCB users out there?
I'm currently using BCB5, although currently reviewing BDS for a possible upgrade. For installation, I just unzip & then open IcsBcb50.bpk in the IDE & then compile from there. Dave Fastream Technologies wrote: > Hello, > > As far as I can remember, we are not the only BCB users here on this list. > Could you confirm that you are as well using BCB and how do you install and > use the latest versions on your C++ compiler? > > Best Regards, > > SubZ > > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Raw sockets doesn't capture broadcast UDP packets
Hello Arno, >>> I tried a C++ library based on raw socket and it worked. I briefly >>> looked at the C++ code and didn't find anything obvious. > If you have the source it shouldn't be a big deal to find out the > difference between TWsocket's and their API calls. Yeah. I actually compared the part of the code that creates the socket line by line and didn't notice any issues/major differences between the C code and TWSocket... Jack -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Any BCB users out there?
Hi all, > As far as I can remember, we are not the only BCB users here on this list. > Could you confirm that you are as well using BCB and how do you install and > use the latest versions on your C++ compiler? I use BCB6 and BDS2006, but I haven't yet ventured down the path of installing any of the latest releases. However, it's something I'm considering doing within the next month or so (depending on availability of my time). Regards, Bevan -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Raw sockets doesn't capture broadcast UDP packets
Jack wrote: > Hello Arno, > > I know about the components. They use ICS raw sockets. Because > ICS raw sockets does not capture broadcast packets, they don't > either :( >From what I know raw sockets are not reliable, I tried several applications based on raw sockets when I was looking for a sniffer. All those apps. I've been tested didn't satisfy my need, so I ended up with Ethereal which uses Winpcap. >> I tried a C++ library based on raw socket and it worked. I briefly >> looked at the C++ code and didn't find anything obvious. If you have the source it shouldn't be a big deal to find out the difference between TWsocket's and their API calls. --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > > -- > Best regards, > Jack > > Tuesday, March 7, 2006, 9:58:59 AM, you wrote: > >> Jack wrote: >>> Resending ... anyone has any idea why this is happening? > >> These components use ICS: >> http://www.magsys.co.uk/delphi/magmonsock.asp > >> "Raw sockets which are available with Windows 2000 and later. >> This uses WSocket from the François Piette internet component suite, >> from http://www.overbyte.be/. Major benefit is that no other >> software needs to be installed, but raw sockets don't seem to work >> fully with some network adaptors, and ignore non-IP protocols. Some >> adaptors may capture received packets, but ignore anything sent." > >> --- >> Arno Garrels [TeamICS] >> http://www.overbyte.be/eng/overbyte/teamics.html > > >>> >>> ===8<==Original message text=== >>> Hello Francois, >>> >>> I used the code you posted earlier to capture traffic with raw >>> sockets. It's the UDP packets I'm interested. It all works fine >>> with packets specifically addressed to this IP. However, all >>> broadcast packets are not captured, such as 192.168.1.255. >>> I tried a C++ library based on raw socket and it worked. I briefly >>> looked at the C++ code and didn't find anything obvious. Can you think >>> of any reason that the ICS raw sockets is not doing that? >>> >>> WSocket1.ReqVerHigh := 2; >>> WSocket1.ReqVerLow:= 2; >>> WSocket1.Proto:= 'raw_ip'; >>> WSocket1.Port := '0'; >>> WSocket1.ComponentOptions := [wsoSIO_RCVALL]; >>> WSocket1.Addr := '192.168.1.102'; >>> WSocket1.Listen; >>> >>> -- >>> Best regards, >>> Jack >>> ===8<===End of original message text=== -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Raw sockets doesn't capture broadcast UDP packets
Hello Arno, I know about the components. They use ICS raw sockets. Because ICS raw sockets does not capture broadcast packets, they don't either :( -- Best regards, Jack Tuesday, March 7, 2006, 9:58:59 AM, you wrote: > Jack wrote: >> Resending ... anyone has any idea why this is happening? > These components use ICS: > http://www.magsys.co.uk/delphi/magmonsock.asp > "Raw sockets which are available with Windows 2000 and later. > This uses WSocket from the François Piette internet component suite, > from http://www.overbyte.be/. Major benefit is that no other > software needs to be installed, but raw sockets don't seem to work > fully with some network adaptors, and ignore non-IP protocols. Some > adaptors may capture received packets, but ignore anything sent." > --- > Arno Garrels [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html >> >> ===8<==Original message text=== >> Hello Francois, >> >> I used the code you posted earlier to capture traffic with raw >> sockets. It's the UDP packets I'm interested. It all works fine >> with packets specifically addressed to this IP. However, all >> broadcast packets are not captured, such as 192.168.1.255. >> I tried a C++ library based on raw socket and it worked. I briefly >> looked at the C++ code and didn't find anything obvious. Can you think >> of any reason that the ICS raw sockets is not doing that? >> >> WSocket1.ReqVerHigh := 2; >> WSocket1.ReqVerLow:= 2; >> WSocket1.Proto:= 'raw_ip'; >> WSocket1.Port := '0'; >> WSocket1.ComponentOptions := [wsoSIO_RCVALL]; >> WSocket1.Addr := '192.168.1.102'; >> WSocket1.Listen; >> >> -- >> Best regards, >> Jack >> ===8<===End of original message text=== -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Raw sockets doesn't capture broadcast UDP packets
> These components use ICS: > http://www.magsys.co.uk/delphi/magmonsock.asp He's using my components already, he does not want to use WinPcap (which will fix the problem) due to install issues, and I've been unable to help him about raw sockets, support for which seems sporadic on the OSs and hardware I've tested. I guess few other people have tried raw sockets either. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] keepalive
Hi all, Is there a way at the O/S level (unix-linux and windows) to set the keepalive for the O/S. Can you do it by port ? We are losing connections and it seems to be on the server side. Thanks grs -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Raw sockets doesn't capture broadcast UDP packets
Jack wrote: > Resending ... anyone has any idea why this is happening? These components use ICS: http://www.magsys.co.uk/delphi/magmonsock.asp "Raw sockets which are available with Windows 2000 and later. This uses WSocket from the François Piette internet component suite, from http://www.overbyte.be/. Major benefit is that no other software needs to be installed, but raw sockets don't seem to work fully with some network adaptors, and ignore non-IP protocols. Some adaptors may capture received packets, but ignore anything sent." --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > > ===8<==Original message text=== > Hello Francois, > > I used the code you posted earlier to capture traffic with raw > sockets. It's the UDP packets I'm interested. It all works fine > with packets specifically addressed to this IP. However, all > broadcast packets are not captured, such as 192.168.1.255. > I tried a C++ library based on raw socket and it worked. I briefly > looked at the C++ code and didn't find anything obvious. Can you think > of any reason that the ICS raw sockets is not doing that? > > WSocket1.ReqVerHigh := 2; > WSocket1.ReqVerLow:= 2; > WSocket1.Proto:= 'raw_ip'; > WSocket1.Port := '0'; > WSocket1.ComponentOptions := [wsoSIO_RCVALL]; > WSocket1.Addr := '192.168.1.102'; > WSocket1.Listen; > > -- > Best regards, > Jack > ===8<===End of original message text=== -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] Raw sockets doesn't capture broadcast UDP packets
Resending ... anyone has any idea why this is happening? ===8<==Original message text=== Hello Francois, I used the code you posted earlier to capture traffic with raw sockets. It's the UDP packets I'm interested. It all works fine with packets specifically addressed to this IP. However, all broadcast packets are not captured, such as 192.168.1.255. I tried a C++ library based on raw socket and it worked. I briefly looked at the C++ code and didn't find anything obvious. Can you think of any reason that the ICS raw sockets is not doing that? WSocket1.ReqVerHigh := 2; WSocket1.ReqVerLow:= 2; WSocket1.Proto:= 'raw_ip'; WSocket1.Port := '0'; WSocket1.ComponentOptions := [wsoSIO_RCVALL]; WSocket1.Addr := '192.168.1.102'; WSocket1.Listen; -- Best regards, Jack ===8<===End of original message text=== -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] Any BCB users out there?
Hello, As far as I can remember, we are not the only BCB users here on this list. Could you confirm that you are as well using BCB and how do you install and use the latest versions on your C++ compiler? Best Regards, SubZ -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] HTTP POST answer code 401
Hello, I have a question that I am unsure about POST/require authentication. When a request arrives at a HTTP server, unless it already contains valid auth data, a 401 response is returned. This is very easy with GET and HEAD as the request contains data no more than the header. However with POST, the actual form data which can be more than MBs is uploaded immediately by the client without waiting for a response (unlike FTP). So my problem is: - consider a POST request with no auth data and of 1MB size - folder is password protected by digest auth - at TriggerPOSTdocument, the server decides 401 - however even after the 401 is sent, data keeps coming from the client - the next keep-alive request is bad (garbage!!!) Any idea? Best Regards, SubZero -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Odd Behaviour
Allan Fernandes wrote: > P1 denotes port = 5011 and P2 denotes port = 5014 >(I have tried changing ports to 6011 and 6014) What does this mean? Server?, client?, Port?, PasvPortRange or DataPortRange? Are you using Pasv mode? > The Problem: > All Transfers via P1 are perfectly OK, but P2 from > MachA gives error in > RequestDone event RqType of ftpOpenAsync: gives > value of 'not fFTPClient.User' An error 'not fFTPClient.User' is unknown to me, what is the error code of request ftpOpenAsync? Are you using asynchronous methods? --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] ICS V5 Beta. Now include HTTP server authentication
Tried it but there seems to be many more problems particularly with httpcondconf.pas and perhaps -when it is passed- with others. I think there seems to be a BIG drawback for BCB users. Regards, SZ - Original Message - From: "Arno Garrels" <[EMAIL PROTECTED]> To: "ICS support mailing" Sent: Tuesday, March 07, 2006 10:32 AM Subject: Re: [twsocket] ICS V5 Beta. Now include HTTP server authentication > Fastream Technologies wrote: >> Still looking forward to a solution! ;(( > > In Winsock.pas of Delphi these constants are missing thus > they need to be defined in WSocket.pas. > But they are defined in Winsock2.h in C++Builder which > is most likely the problem. What happens if you comment them > out in WSocket.pas? > > /* > * WinSock 2 extension -- manifest constants for WSAIoctl() > */ > #define IOC_UNIX 0x > #define IOC_WS2 0x0800 > #define IOC_PROTOCOL 0x1000 > #define IOC_VENDOR 0x1800 > > > --- > Arno Garrels [TeamICS] > http://www.overbyte.be/eng/overbyte/teamics.html > > >> >> >> - Original Message - >> From: "Fastream Technologies" <[EMAIL PROTECTED]> >> To: "ICS support mailing" >> Sent: Sunday, March 05, 2006 8:02 PM >> Subject: Re: [twsocket] ICS V5 Beta. Now include HTTP server >> authentication >> >> >>> Hello, >>> >>> The problem persists after the following steps: >>> >>> - Moved Program files\ICS to backup, >>> - Created program files\ICS >>> - Downloaded and unzipped to there from Mar 05 ICS beta link >>> successfully >>> - Compiled and installed ICSBCB60.bpk successfully. >>> - Opened a existing project with FTP/HTTP server components and it gives >>> the >>> below errors. I know you are eager to drop the support for BCB6 but >>> please do not do this immediately as the new BCB is just arrived and my >>> order of BDS2006 has not even been delivered yet! Please give us -the >>> mortal BCB guys- some time before dropping support for older compilers >>> and check the situation out with your BCB copy. >>> >>> Thanks, >>> >>> SZ >>> >>> - Original Message - >>> From: "Francois PIETTE" <[EMAIL PROTECTED]> >>> To: "ICS support mailing" >>> Sent: Sunday, March 05, 2006 7:28 PM >>> Subject: Re: [twsocket] ICS V5 Beta. Now include HTTP server >>> authentication >>> >>> > ok, downloaded and installed. What was the problem ? > I now see the same error I saw in v6!: > > static const Shortint IOC_UNIX = 0x0; > static const int IOC_WS2 = 0x800; > static const int IOC_PROTOCOL = 0x1000; > static const int IOC_VENDOR = 0x1800; > > Decleration terminated unexpectantly!!! I see this problem not in > component > compilation but project compilation with THttpServer and TFtpServer. > The Jan > 22 ICS v5 was working fine. As usual, I am using BCB6Pro. Nothing changed in that area. Or is something changed ? Maybe you changed something? Please compare both versions. -- [EMAIL PROTECTED] http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be >>> >>> -- >>> To unsubscribe or change your settings for TWSocket mailing list >>> please goto http://www.elists.org/mailman/listinfo/twsocket >>> Visit our website at http://www.overbyte.be > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] ICS V5 Beta. Now include HTTP server authentication
Fastream Technologies wrote: > Still looking forward to a solution! ;(( In Winsock.pas of Delphi these constants are missing thus they need to be defined in WSocket.pas. But they are defined in Winsock2.h in C++Builder which is most likely the problem. What happens if you comment them out in WSocket.pas? /* * WinSock 2 extension -- manifest constants for WSAIoctl() */ #define IOC_UNIX 0x #define IOC_WS2 0x0800 #define IOC_PROTOCOL 0x1000 #define IOC_VENDOR 0x1800 --- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html > > > - Original Message - > From: "Fastream Technologies" <[EMAIL PROTECTED]> > To: "ICS support mailing" > Sent: Sunday, March 05, 2006 8:02 PM > Subject: Re: [twsocket] ICS V5 Beta. Now include HTTP server > authentication > > >> Hello, >> >> The problem persists after the following steps: >> >> - Moved Program files\ICS to backup, >> - Created program files\ICS >> - Downloaded and unzipped to there from Mar 05 ICS beta link successfully >> - Compiled and installed ICSBCB60.bpk successfully. >> - Opened a existing project with FTP/HTTP server components and it gives >> the >> below errors. I know you are eager to drop the support for BCB6 but >> please do not do this immediately as the new BCB is just arrived and my >> order of BDS2006 has not even been delivered yet! Please give us -the >> mortal BCB guys- some time before dropping support for older compilers >> and check the situation out with your BCB copy. >> >> Thanks, >> >> SZ >> >> - Original Message - >> From: "Francois PIETTE" <[EMAIL PROTECTED]> >> To: "ICS support mailing" >> Sent: Sunday, March 05, 2006 7:28 PM >> Subject: Re: [twsocket] ICS V5 Beta. Now include HTTP server >> authentication >> >> ok, downloaded and installed. >>> >>> What was the problem ? >>> I now see the same error I saw in v6!: static const Shortint IOC_UNIX = 0x0; static const int IOC_WS2 = 0x800; static const int IOC_PROTOCOL = 0x1000; static const int IOC_VENDOR = 0x1800; Decleration terminated unexpectantly!!! I see this problem not in component compilation but project compilation with THttpServer and TFtpServer. The Jan 22 ICS v5 was working fine. As usual, I am using BCB6Pro. >>> >>> Nothing changed in that area. Or is something changed ? >>> Maybe you changed something? Please compare both versions. >>> >>> -- >>> [EMAIL PROTECTED] >>> http://www.overbyte.be >>> >>> -- >>> To unsubscribe or change your settings for TWSocket mailing list >>> please goto http://www.elists.org/mailman/listinfo/twsocket >>> Visit our website at http://www.overbyte.be >> >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://www.elists.org/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
