-------------------
1.15 Sun Feb 15 18:09:23 CET 2015
- BUGFIX: IPv4 header length calculation on Mac OS X and OpenBSD
=> Read: support for OpenBSD and Mac OS X now ok
- bugfix: check if inet_ntop/getaddrinfo are *really* supported by trying to use them.
1.14 Wed Jan 28 20:01:48 CET 2015
- BUGFIX: getHostIpv6addr: not working on FreeBSD/Socket because of nasty getaddrinfo()
- tests: added tests for getHost* subs and inet* subs
1.13 Wed Jan 28 07:49:11 CET 2015
- BUGFIX: getHostIpv6Addr: use getaddrinfo/getnameinfo from Socket or Socket6
where available
=> Thanks to Vince
1.12 Tue Jan 20 19:33:06 CET 2015
- bugfix: TCP/UDP computeChecksums() so 6to4 and other encapsulations work
=> Thanks to Vince
- update: copyright notice
- update: Kwalitee
1.11 Tue Apr 8 15:33:43 CEST 2014
- bugfix: https://rt.cpan.org/Public/Bug/Display.html?id=94035
- bugfix: on making Socket6 optional, bugfix contributed by Andrew Feren
- optimization: convertMac() contributed by Andrew Feren
- optimization: inetChecksum() contributed by Andrew Feren
1.10 Mon Mar 10 13:26:53 CET 2014
- UPDATE: makes Socket6 optional, contributed by Andrew Feren
- update: copyright notice
1.09 Wed Jan 25 22:48:18 CET 2012
- UPDATE: %Next in UDP and TCP layers are now empty by default. The
developper who wants to add a new layer 7 seven will have to fill the
variable straight from his module.
1.08 Sat Jan 14 09:49:09 CET 2012
- bugfix: TCP and UDP checksum computation when using another
Net::Frame::Layer object (instead of plain payload).
=> Thanks to Vince
- update: copyright notice
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
PR pkg/45720.
Net::Frame is a fork of Net::Packet. The goal here was to greatly simplify
the use of the frame crafting framework. Net::Packet does many things
undercover, and it was difficult to document all the thingies.
Also, Net::Packet may suffer from unease of use, because frames were assembled
using layers stored in L2, L3, L4 and L7 attributes. Net::Frame removes all
this, and is splitted in different modules, for those who only want to use part
of the framework, and not whole framework.
Finally, anyone can create a layer, and put it on his CPAN space, because of
the modularity Net::Frame offers. For an example, see Net::Frame::Layer::ICMPv4
on my CPAN space.
Net::Frame does ship with basic layers, to start playing.
