Changes between Version 6 and Version 7 of UMPA/Documentation/Tutorials/YourFirstPackets

Timestamp:

08/28/08 23:29:12 (5 years ago)

Author:

getxsick (IP: 83.27.164.133)

Comment:

--

UMPA/Documentation/Tutorials/YourFirstPackets

@@ -303 +303 @@
 Now, we can simple create a new packet and use already created {{{sock}}} object to send it out, but before we will do that, lets change TTL field of the IP protocol.
 
-Some common fields like TTL or ports in TCP/UDP headers are {{{EnumField}}} objects. What does mean? Well, this is a simple numeric field but with special behaviour.
+Some common fields like TTL or ports in TCP/UDP headers are {{{EnumField}}} objects. What does it mean? Well, this is a simple numeric field but with special behaviour.
 We can pass common names instead of numbers (what is easier to remember). Let's do it on the TTL example.
 
@@ -328 +328 @@
 }}}
 
-Why we can't use {{{ip.time_to_live.enumerable}}} in the first line? Well, attributes like object.''name_of_field'' are reserved only to get/set values of them. They handle only with values. To get a reference to the field's object we need to use {{{get_field()}}} method.
+Why can't we use {{{ip.time_to_live.enumerable}}} in the first line? Well, attributes like object.''name_of_field'' are reserved only to get/set values of them. They handle only with values. To get a reference to the field's object we need to use {{{get_field()}}} method.
 
 ===== print statement is sooo cool =====