The gateway MAC address of <B>devB>. It will not be set automatically. Due to the implementation of ARP lookup within <B>Net::PacketB>, we cant do it within this module. It is done within <B>Net::Packet::DescL3B> under Windows, to automatically build the layer 2 header.

This attribute controls <B>Net::Packet::FrameB> behaviour regarding <B>Net::Packet::DescB> autocreation. If set to 0, when a <B>Net::Packet::FrameB> is created for the first time, a <B>Net::Packet::DescB> object will be created if none has been set in <B>descB> attribute for default <B>B>$Env<B>B> object. Setting it to 1 avoids this behaviour.

This attribute controls <B>Net::Packet::DescB> behaviour regarding global <B>B>$Env<B>B> autosetting behaviour. If set to 0, when a <B>Net::Packet::DescB> is created for the first time, the created <B>Net::Packet::DescB> object will have a pointer to it stored in <B>descB> attribute of <B>B>$Env<B>B> default object. Setting it to 1 avoids this behaviour.

By default, when a <B>Net::Packet::FrameB> object is created from analyzing a raw string (either by taking from <B>Net::Packet::DumpB> object or from user), padding is achieved to complete the size of 60 bytes. Set this attribute to 1 if you do not want this behaviour.

By default, when a <B>Net::Packet::FrameB> object is created from analyzing a raw string (either by taking from <B>Net::Packet::DumpB> object or from user), only the first found frame is returned. If you set it to true, an arrayref of <B>Net::Packet::FrameB> objects will be returned. For example, if you put an IPv6 frame within IPv4, or you get one from network, you will need to use this attribute.

By default, when a <B>Net::Packet::FrameB> object is packed, all layers checksums and lengths are computed (if respective layers implement that). If you want to do it yourself, set this to true. See <B>doIPv4ChecksumB> for the exception.

This parameter exists to improve performances of the framework. When you send an IPv4 frame at layer 3 (using a <B>Net::Packet::DescL3B> object), under Unix systems, you MUST not compute IPv4 checksum. The kernel does it. Because this is the more general case (sending IPv4 at layer 3), this parameter is set to false by default. Note: under Windows, because <B>Net::Packet::DescL3B> is a wrapper around <B>Net::Packet::DescL2B>, this parameter will be set to true on <B>Net::Packet::DescL3B> object creation.

So, even if you let the framework compute checksums, IPv4 checksum will not be computed. If you want to send IPv4 frames at layer 2, you will need to also set this parameter to true.

By default, no memory optimizations are made to improve speed. You can enable those optimizations (mostly done in <B>Net::Packet::FrameB>) in order to gain ~ 10% in memory, at the cost of ~ 10% in speed.