Ian Firla wrote:
You're right. I think it will. Thanks.
I've got another issue now though which may indeed be a show-stopper.
It seems that while socket_recvfrom is binary safe, there's no way to
send data in any way other than a string... Is that right? Can I not
send data of other types?
no probl
Ian Firla wrote:
> I thought of that too and have since expanded my debugging. The types
> are correct when passed to fwrite. They come out the other end as
> strings:
>
> 16:39:54 SENT 'K' of type string
> 16:39:54 SENT '0' of type integer
> 16:39:54 SENT '0' of type integer
> 16:39:54
To view the terms under which this email is distributed, please go to
http://disclaimer.leedsmet.ac.uk/email.htm
> -Original Message-
> From: Ian Firla
> Sent: 14/12/04 17:52
>
> On Tue, 2004-12-14 at 08:40 -0800, Richard Lynch wrote:
> > Ian Firla wrote:
> > >
> > > Just a follow-up t
On Tue, 2004-12-14 at 08:40 -0800, Richard Lynch wrote:
> Ian Firla wrote:
> >
> > Just a follow-up to myself... I decided to try packet sniffing to see
> > what was going on and ettercap confirms that I'm sending out strings
> > rather than data of the type stored in my array:
> >
> > 16:12:26 19
Ian Firla wrote:
>
> Just a follow-up to myself... I decided to try packet sniffing to see
> what was going on and ettercap confirms that I'm sending out strings
> rather than data of the type stored in my array:
>
> 16:12:26 192.168.0.101:32779 --> 192.168.0.88:32896 | UDP |
>
> : 3331
Just a follow-up to myself... I decided to try packet sniffing to see
what was going on and ettercap confirms that I'm sending out strings
rather than data of the type stored in my array:
16:12:26 192.168.0.101:32779 --> 192.168.0.88:32896 | UDP |
: 3331
Try the unpack function, it should do quite nicely.
Chris
Ian Firla wrote:
Hello All,
I've hit a bit of a show stopper in a project I'm working on.
I'm getting a 65 byte stream of data. 32 of those bytes are of the type
"Byte Array". Is there a way that I can covert that data into something
useful?
[snip]
I'm getting a 65 byte stream of data. 32 of those bytes are of the type
"Byte Array". Is there a way that I can covert that data into something
useful?
For the record, the data stream that I'm getting is in the format:
|ascii|ascii|asciiX10|integerX4|byte arrayX32|
The byte array looks li
You're right. I think it will. Thanks.
I've got another issue now though which may indeed be a show-stopper.
It seems that while socket_recvfrom is binary safe, there's no way to
send data in any way other than a string... Is that right? Can I not
send data of other types?
Ian
On Mon, 2004-12-
Use bit shifting to make sense out of the data.
On Mon, 13 Dec 2004 15:55:54 +0100, Ian Firla <[EMAIL PROTECTED]> wrote:
>
> Hello All,
>
> I've hit a bit of a show stopper in a project I'm working on.
>
> I'm getting a 65 byte stream of data. 32 of those bytes are of the type
> "Byte Array".
Hello All,
I've hit a bit of a show stopper in a project I'm working on.
I'm getting a 65 byte stream of data. 32 of those bytes are of the type
"Byte Array". Is there a way that I can covert that data into something
useful?
For the record, the data stream that I'm getting is in the format:
|a
11 matches
Mail list logo