Migration Broker™
Web Interface

Powered by the

Migration Broker™

[Home] - [Account creation] - [TSP client download] - [TSP client FAQ] - [Tunnel request] - [Help]

TSP client Frequently Asked Questions (FAQ)

  • How do I install IPv6 on Windows XP?

    Simply type “ipv6 install” on a Windows command prompt. To get a prompt, go to the Start menu, Run... and type “cmd”. The “exit” command will close the window.

  • On Windows XP, the TSP client runs correctly, but the interface does not work. I can't even ping the other end of the tunnel in IPv6.

    If you installed the Microsoft Advanced Networking Pack for Windows XP, an IPv6 firewall has been activated by default on all interfaces. You may completely disable the firewall on the tunnel interface or configure the firewall parameters. In order to disable the firewall, use the following command on a Windows prompt : netsh.exe firewall set adapter "Automatic Tunneling Pseudo-Interface" filtering=disable

  • When I run tspc, I get “Error code 301: No more tunnels available”.
    The client might be configured to ask for a tunnel mode the broker does not offer. In that case, no tunnel of this type is available. Make sure the tunnel_mode ? parameter is set to v6anyv4 in the configuration file. If the error persists with this tunnel mode value, contact the administrator of the tunnel broker.

  • I get a “No common authentication method found” error when running the TSP Client.

    This usually happens when a tunnel broker does not allow anonymous users and the client configuration does not contain a valid username ?. You must get a valid username and password and add this information to the configuration file.

  • I upgraded to a new version of the TSP client and now I get an authentication error: "No success: Authentication failed".

    Make sure you have a registered username on the server you are trying to connect to. The line in the client config is "server=dren-broker.v6.dren.net" ? where the address of the broker is specified by your provider.

  • I was delegated a prefix but it doesn't seem to be routed anymore since I upgraded the TSP client.

    Verify that the prefix option is still turned on ? and that the prefix length is the same as what you had previously defined. If a prefix was not requested, the broker keeps the prefix information but does not route it. If a prefix of a different length is requested, a new one is assigned.

Copyrights Hexago © 2003-2004