Thanks! Your patch worked so now there's no problem getting outside
using natd.
I've gone through the checklist in your original message as well, and
have found so far:
0) gif seems to work well (I use freenet6.net as my primary uplink
connection for IPv6)
1) /sbin/route somehow assumes prefixlen 64 instead of 0 for the
``default'' route. I've used this command to establish my default
route: route -n add -inet6 -net default -prefixlen 0 -interface gif0
2) Here's the output you requested:
* ifconfig -a:
ep0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 209.76.108.39 netmask 0xffffff00 broadcast 209.76.108.255
inet6 fe80:1::220:afff:fe1d:bc36 prefixlen 64
ether 00:20:af:1d:bc:36
media: 10baseT/UTP
supported media: 10baseT/UTP 10base5/AUI
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 fe80:2::1 prefixlen 64
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
inet6 fe80:3::220:afff:fe1d:bc36 prefixlen 64
inet6 3ffe:b00:c18:1fff::165 --> 3ffe:b00:c18:1fff::164 prefixlen 127
gif1: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
inet6 fe80:4::220:afff:fe1d:bc36 prefixlen 64
gif2: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
inet6 fe80:5::220:afff:fe1d:bc36 prefixlen 64
gif3: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
inet6 fe80:6::220:afff:fe1d:bc36 prefixlen 64
faith0: flags=8002<BROADCAST,MULTICAST> mtu 1500
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
inet6 fe80:8::2a0:c9ff:feaa:106 prefixlen 64
ether 00:a0:c9:aa:01:06
media: autoselect (100baseTX <full-duplex>) status: active
supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP
<full-duplex> 10baseT/UTP
tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
inet6 fe80:9::220:afff:fe1d:bc36 prefixlen 64
Opened by PID 5749
tun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
inet 10.0.0.4 --> 10.0.2.2 netmask 0xffffff00
Opened by PID 460
* netstat -nrfinet6:
Routing tables
Internet6:
Destination Gateway Flags Netif Expire
default gif0 USc gif0
::1 ::1 UH lo0
3ffe:b00:c18:1fff::164 3ffe:b00:c18:1fff::165 UH gif0
3ffe:b00:c18:1fff::165 ::1 UH lo0
fe80::@ep0/64 link#1 UC ep0
fe80::@lo0/64 fe80::1@lo0 Uc lo0
fe80::@gif0/64 fe80::220:afff:fe1d:bc36@gif0 Uc gif0
fe80::220:afff:fe1d:bc36@gif0 ::1 UH lo0
fe80::@gif1/64 fe80::220:afff:fe1d:bc36@gif1 Uc gif1
fe80::220:afff:fe1d:bc36@gif1 ::1 UH lo0
fe80::@gif2/64 fe80::220:afff:fe1d:bc36@gif2 Uc gif2
fe80::220:afff:fe1d:bc36@gif2 ::1 UH lo0
fe80::@gif3/64 fe80::220:afff:fe1d:bc36@gif3 Uc gif3
fe80::220:afff:fe1d:bc36@gif3 ::1 UH lo0
fe80::@fxp0/64 link#8 UC fxp0
fe80::@tun0/64 fe80::220:afff:fe1d:bc36@tun0 Uc tun0
fe80::220:afff:fe1d:bc36@tun0 ::1 UH lo0
ff01::/32 ::1 U lo0
ff02::@ep0/32 link#1 UC ep0
ff02::@lo0/32 fe80::1@lo0 UC lo0
ff02::@gif0/32 fe80::220:afff:fe1d:bc36@gif0 UC gif0
ff02::@gif1/32 fe80::220:afff:fe1d:bc36@gif1 UC gif1
ff02::@gif2/32 fe80::220:afff:fe1d:bc36@gif2 UC gif2
ff02::@gif3/32 fe80::220:afff:fe1d:bc36@gif3 UC gif3
ff02::@fxp0/32 link#8 UC fxp0
ff02::@tun0/32 fe80::220:afff:fe1d:bc36@tun0 UC tun0
3) IPv6 host autoconfiguration: tried w/o establishing the default
route, but couldn't have my box learn new routes. (Perhaps freenet6.net
doesn't support autoconfig; their setup script explicitly calls route(8)
to add the default route)
In near future, I'll enable IPv6 on another machine inside my box (which
is acting as a router) and try to run rtadvd/rtsol on these two boxes.
But currently still unsure whether it is allowed to run such a thing on
my machine; I'm not that familiar with the IPv6 addressing scheme (i.e.
I don't even know which address to assign to my internal machine), but
FreeNet6 might not like it if I run any routing daemon on my machine).
4) IPv6 communication via IPv6 router: for the same reason as in 3), I
didn't set my machine as IPv6 router (yet). I'll try this time and
circumstances permitting.
5) IPsec between 2 hosts/routers: still studying these topics. :-)
Things have changed since last time I tried IPsec tunneling using KAME,
so I can't set it up quickly (at least it seems that spdadd command of
setkey(8) has been extended a lot).
If there's anything else I can do, I'd be glad to.
Thanks,
Eugene
--
Eugene M. Kim <[EMAIL PROTECTED]>
"Is your music unpopular? Make it popular; make music
which people like, or make people who like your music."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
