2013-11-05 17:42:55 +01:00
|
|
|
%%PERL5_MAN3%%/Net::Frame.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer::ARP.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer::ETH.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer::IPv4.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer::NULL.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer::PPP.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer::RAW.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer::SLL.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer::TCP.3.gz
|
|
|
|
|
%%PERL5_MAN3%%/Net::Frame::Layer::UDP.3.gz
|
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.
WWW: http://search.cpan.org/dist/Net-Frame/
2007-01-09 02:55:40 +01:00
|
|
|
%%SITE_PERL%%/Net/Frame.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer/ARP.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer/ETH.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer/IPv4.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer/NULL.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer/PPP.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer/RAW.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer/SLL.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer/TCP.pm
|
|
|
|
|
%%SITE_PERL%%/Net/Frame/Layer/UDP.pm
|
|
|
|
|
%%SITE_PERL%%/%%PERL_ARCH%%/auto/Net/Frame/.packlist
|
|
|
|
|
@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Net/Frame
|
|
|
|
|
@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Net
|
2013-11-05 17:42:55 +01:00
|
|
|
@dirrmtry %%SITE_PERL%%/Net/Frame/Layer
|
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.
WWW: http://search.cpan.org/dist/Net-Frame/
2007-01-09 02:55:40 +01:00
|
|
|
@dirrmtry %%SITE_PERL%%/Net/Frame
|
|
|
|
|
@dirrmtry %%SITE_PERL%%/Net
|
