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 modlist
> > 0 ip
> > 1 pfil
> > 2 6to4tun
> > 3 ip
>
> Ok, so this is the right interface name to use.
>
> If you snd traffic over this interface, do you see numbers go up
> in any of the other columns for ip.6to4un.pfil0 ? Of most interest
> are nr and nw (read and write).
# 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.
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)
Just FYI:
# 6to4relay
6to4relay: 6to4 Relay Router communication support is enabled.
IPv4 destination address of Relay Router = 192.88.99.1
# ping 192.88.99.1
192.88.99.1 is alive
--
Peter Eriksson <[EMAIL PROTECTED]>
