> On Wed, 10 May 2006, Darren Reed wrote: > > # ndd -get /dev/pfil qif_status > ifname ill q OTHERQ ipmp num sap hl nr nw bad copy copyfail drop notip nodata > notdata > ip.6to4tun.pfil0 0xf6147324 0xf6329a18 0xf6329a9c 0x0 13 86dd 0 0 0 0 0 0 0 0 > 0 0 .. > # ifconfig ip.6to4tun.pfil0 inet6 > ip.6to4tun.pfil0: flags=2200041<UP,RUNNING,NONUD,IPv6> mtu 1480 index 8 > inet tunnel src 81.216.104.103 > tunnel hop limit 60 > inet6 fe80::32:0:10/10 > # ndd -get /dev/pfil qif_status | egrep 6to4tun > ip.6to4tun.pfil0 0xf6348dac 0xf6082000 0xf6082084 0x0 13 86dd 0 0 0 0 0 0 0 0 > 0 0 > # ping -ns fe80::32:0:10:1 > PING fe80::32:0:10:1 (fe80::32:0:10:1): 56 data bytes > ^C > ----fe80::32:0:10:1 PING Statistics---- > 6 packets transmitted, 0 packets received, 100% packet loss > ip.6to4tun.pfil0 0xf6348dac 0xf6082000 0xf6082084 0x0 13 86dd 52 0 6 0 0 0 0 > 0 0 0 > > > Ie, "nw" increases for each PING packet I try to send.
That makes sense. Are there any counters in "ipfstat" or "netstat -s" output that increase in step with the "nw" column? > I also got this kernel warning: > > May 9 22:23:57 bose tun: tun_wdata_v6: ip.6to4tun0 (inet6) tun: invalid IPv6 > src (fe80::32:0:10) Do you get that if IPFilter/pfil isn't part of the equation? Darren
