in reply to Re^2: Problem Sending an IPv6 Packet with Net::Packet Module
in thread Problem Sending an IPv6 Packet with Net::Packet Module

I'm not sure what you mean by the test suite

A Guide to Installing Modules
http://search.cpan.org/src/GOMOR/Net-Packet-3.26/README

To install this module type the following:

   perl Makefile.PL
   make
   make test
   make install
http://search.cpan.org/src/GOMOR/Net-Packet-3.26/test-env.sh
[TXT]09-d2-eth-ipv6-tcp.t        19-Apr-2008 11:37  1.0K  
[TXT]10-d2-eth-ipv6-tcp-opt.t    19-Apr-2008 11:37  1.0K  
[TXT]11-d2-eth-ipv6-tcp-opt-l7.t 19-Apr-2008 11:37  1.1K  
[TXT]12-d2-eth-ipv6-udp.t        19-Apr-2008 11:37  1.0K  
[TXT]13-d2-eth-ipv6-udp-l7.t     19-Apr-2008 11:37  1.1K  
  • Comment on Re^3: Problem Sending an IPv6 Packet with Net::Packet Module

Replies are listed 'Best First'.
Re^4: Problem Sending an IPv6 Packet with Net::Packet Module
by bpa (Novice) on Aug 23, 2008 at 02:52 UTC
    Thank you for your reply, and I should have gotten back sooner. I now know what was meant by test suite, so thanks for that. My problem ended up being that I needed to include the following line for IPv6 use:

    $Env->dev($if);


    Basically, I had to explicitly set the global $Env object's device property to the interface I wanted to use (eth0, wlan0, etc). What I had been doing was creating a separate "New" $env object that I thought would be automaticall used when created, as per the documentation. As I stated before, IPv4 packets had no problem understanding this, and would send just fine. But for IPv6 to work I had to actually start using that global $Env object. From my experience with IPv6 so far, everything is heavily reliant on the user specifying the interface to use. For instance, the ping6 command will not work unless an interface is explicitly specified.

    Thanks for all the help.