On Sun, Jul 10, 2011 at 1:59 PM, Littlefield, Tyler wrote:
> Hello all:
> I'm working on a server that will need to parse packets sent from a client,
> and construct it's own packets.
>
I like to use this module (I wrote while in the employ of UCI, so it's under
a UCI - BSDesque - license, but th
On Mon, Jul 11, 2011 at 5:05 AM, Thomas Rachel <
nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa...@spamschutz.glglgl.de> wrote:
> Am 10.07.2011 22:59 schrieb Littlefield, Tyler:
>
> Hello all:
>> I'm working on a server that will need to parse packets sent from a
>> client, and construct it's own pac
Am 10.07.2011 22:59 schrieb Littlefield, Tyler:
Hello all:
I'm working on a server that will need to parse packets sent from a
client, and construct it's own packets.
Are these packets sent as separate UDP packets or embedded in a TCP
stream? In the first case, you already have packets and onl
Contents of Python-list digest..."
>
> Today's Topics:
>
> 1. Re: parsing packets (Michael Hrivnak)
> 2. Re: Wgy isn't there a good RAD Gui tool fo python (CM)
> 3. Re: Function docstring as a local variable (Ben Finney)
> 4. Re: Function docstring as a lo
In order to find the end of the packet, include a field that is the
packet length. This is what IP packets do to find the end of their
header.
http://en.wikipedia.org/wiki/IPv4#Header
And the TCP header (see "data offset") does the same:
http://en.wikipedia.org/wiki/Transmission_Control_Protoco
On Sun, Jul 10, 2011 at 4:59 PM, Littlefield, Tyler wrote:
> Hello all:
> I'm working on a server that will need to parse packets sent from a client,
> and construct it's own packets.
> The setup is something like this: the first two bytes is the type of the
> packet.
> So, lets say we have a pack
Hello all:
I'm working on a server that will need to parse packets sent from a
client, and construct it's own packets.
The setup is something like this: the first two bytes is the type of the
packet.
So, lets say we have a packet set to connect. There are two types of
connect packet: a auth pac
