DTCP Client -- dtcpc

Testing Connection

It is a good idea to test if you can connect to a server by executing dtcpc from command line. With -d option, you can see more debug informations.

The comman line is like follows:

dtcpc -t network -u hoge -d dtcp.example.org
Server: dtcp.example.org
User: hoge (-u)
network tunnel type (-t)
Debug output (-d)
When you excute dtcpc, you are asked your password. Answer it.

When connection is established, a tunnel should be established and an IPv6 default route should be set up toward a tunnel. The following is an example output under FreeBSD: 

ume@cheer:1003% ifconfig gif0
gif0: flags=8051 mtu 1280
        tunnel inet 218.45.20.185 --> 210.161.150.9
        inet6 fe80::240:c7ff:fe99:81eb%gif0 prefixlen 64 scopeid 0x4
ume@cheer:1004% netstat -rnfinet6 | grep gif0
default                           ::1                           UGSc       gif0
fe80::%gif0/64                    link#4                        UC         gif0
fe80::240:c7ff:fe99:81eb%gif0     link#4                        UHL         lo0
ff02::%gif0/32                    link#4                        UC         gif0
An interface for an IPv6 over IPv4 tunnel should be set up toward an interface specified by TUNIF. If you wish to custmize this behavior, specify an appropriate interface by -i option.

If you don't want the behavior that an IPv6 default route is set up automatically, specify appropriate routes by -R option.

The dtcpc doesn't set an IPv6 global address up automatically with above settings. If you know a prefix delegated from a server. you can set it up statically. Or, please refer Configuring Prefix Delegetion.

All Rights Reserved, Copyright (C) 2004 Hajimu UMEMOTO
Last Modified Jun 8, 2004
ume@mahoroba.org