IMASY NLA1 Report 2000

Network Name

IMASY (Internet Mutual Aid Society, YOKOHAMA)

History

IPv4 serve start at 1995/4
One of Internet Mutual Aid Societies
800 IPv4 people
IPv6 connected to 6bone-jp at 1998/2
NLA1 of WIDE pTLA (3ffe:505::/32)
Connectivity service (IMASY<->home) start at 1998/6
15 IPv6 people = 1.9%
CVSup mirror start at 1998/7
KAME, FreeBSD
but still IPv4 only ;-)
PAO+KAME CVS Repository Tree service start at 1998/8
easy to track current source from laptop
support CVSup based updating
Obtain NLA1 of WIDE sTLA at 2000/1
2001:200:300::/40
DTCP (Dynamic Tunnel Configuration Protocol) service start at 2000/6
tunnel type `tunnelroute' has been added
5 sites are connected using DTCP
include CATV, FLET's ISDN and dialup
Updated from FreeBSD 3.5-RELEASE + KAME to FreeBSD 4.2-RELEASE at 2000/11

Nwtwork topology

3ffe:505::/32 and 2001:200:300::/40 are assigned.
Our upstream is gif tunnel to pc6.otemachi.wide.ad.jp.
We have connection to INTEC and JENS which are NLA1 holder.
All of our neighbor are connected via gif tunnel.
DTCP is available to connect to IMASY for whos don't have fixed IPv4 global address. This saves CATV, FLET's, dialup and mobile users.

Routing

BGP4+ for externel and internal
RIPng for internal
static routing for dialup or DTCP users

Address assignment

We have been allocated NLA2 mainly individual sites.

3ffe:505:N::/48 from 3ffe:505::/32
52 sites (include 5 sites returned)
2001:200:3nn::/48 from 2001:200:300::/40
2 sites

Trouble

IPv6 over IPv4 tunnel was blocked by NAT
Many people suffered this problem.
Nat facility provided by FreeBSD's userland ppp is trouble-maker. It seems working fine with ppp and ipnat combination.
IPv6 over IPv4 tunnel was not established
Some version of FreeBSD 3.5-RELEASE + KAME broke IPv6 over IPv4 tunnel. We did update the router to 4.2-RELEASE and this problem was gone.

Contact

IMASY-6bone Web page
http://www.v6.imasy.or.jp/
IPv6 address request and comment
ipv6-contact@imasy.or.jp