gogoNET

IPv6 products, community and services

How to configure the gogoCLIENT to use Freenet6 DSTM on Windows

To connect to the Reverse Tunnel service the gogoCLIENT settings have to be changed. The Server Address must be set to ipv4.freenet6.net and a user name and password has to be entered.
In addition to the basic settings the tunnel mode has to be changed, this done under the Advanced tab. The tunnel mode should be set to IPv4 in IPv6 (DSTM). See the following picture.

Views: 2048

▶ Reply to This

Replies to This Discussion

Permalink Reply by bearson on October 15, 2009 at 1:20pm
Why reverse tunnel is not available under Linux? -.-
Permalink Reply by Mikael Lind on October 15, 2009 at 4:42pm
The Linux client is lacking a IPv4 over IPv6 tunnel interface, with that it could be set to use reverse tunnel.
Permalink Reply by Kaos on March 10, 2010 at 10:50am
No its not. Load the kernel module ip6_tunnel and be sure to have the latest iproute package, but its there.
Permalink Reply by Christin Schmidt on October 25, 2011 at 12:21pm

hmkay, but gogoc says:Failed to resolve server IPv4 address.

 

Permalink Reply by iLgiz Magazov on November 1, 2009 at 9:46am
Trying to use Reverse Tunnel
OS: Windows XP SP3 Pro
I've configured client utility as it shown.

Got this:

16:40:42 Establishing connection to Gateway6 ipv4.freenet6.net using reliable UDPv6.
16:40:42 Using TSP protocol version 2.0.1.
16:40:42 Retrieving TSP capabilities from Gateway6...
16:40:42 RUDP packet 0, RTO 2.000000, sequence 0xf00000f0 timestamp 296.
16:40:42 Reply: RUDP packet 0, RTO 2.000000, sequence 0xf00000f0 timestamp 296.
16:40:42 Authenticating...
16:40:42 Using AUTH-PLAIN authentication mechanism.
16:40:42 RUDP packet 0, RTO 2.158625, sequence 0xf00000f1 timestamp 437.
16:40:42 Reply: RUDP packet 0, RTO 2.158625, sequence 0xf00000f0 timestamp 296.
16:40:42 Failed to write on network socket.
16:40:42 Disconnected. Retrying.
Permalink Reply by iLgiz Magazov on November 1, 2009 at 7:05pm
I tried Reverse Tunnel on vista. It seems working, but no ipv4 assigned
Permalink Reply by Ninho Pessoa on November 1, 2009 at 3:01pm
Similar to Magazov, I believe; can't make the reverse tunnel (DSTM) work either :=(

OS: windows XP SP2.

Status : endlessly jumps from "connecting" to "disconnected/error" and repeating until manually disconnected.
Pop-up 'bubble' saying : "Disconnected from the Gateway6 - A socket input/output error has occurred - see log file"

The log file has :
10:26:31 Failed to write on network socket.
10:26:31 Disconnected. Retrying.
10:26:32 Failed to write on network socket.
10:26:32 Disconnected. Retrying.
etc, endlessly repeated.

I have independent global IPv6 addresses and connectivity.

Please help this newbie !
Permalink Reply by Mikael Lind on November 2, 2009 at 3:47pm
Looks like you can't reach the server at all. Can you ping the server?
Permalink Reply by Ninho Pessoa on November 2, 2009 at 4:30pm
Ping6 ipv4.freenet6.net is OK.

Maybe we're seing a problem specific to Windows XP plus SP2 (SP3).
Permalink Reply by Ninho Pessoa on November 2, 2009 at 3:50pm
Forgot to note : I have the Windows firewall disabled so it doesn't intrude.

Gateway6 client settings :
Gateway address = ipv4.freenet6.net
Tunnel mode = 4in6 (DSTM)
Auth method = Auto (Any)
Connect to best gateway
Obtain IP automatically
Enable Keepalive (30)
Enable Reconnect (30)

Last error (status tab) "The Gateway6 address is invalid or cannot be resolved.
Please verify that the address entered is correct."
Permalink Reply by Mikael Lind on November 2, 2009 at 4:58pm
Changed the setting of the server to do the setup over TCP instead of UDP. Seems to do the trick with failing clients.
Permalink Reply by Ninho Pessoa on November 2, 2009 at 6:12pm
Much better... but still no joy ! Authentication fails (also tried auth plain).
Does the reverse gateway use another user/password base than for 6in4 ? "User" is my email address, right ?


11:21:44 Establishing connection to Gateway6 ipv4.freenet6.net using TCPv6.
11:21:44 Connection to Gateway6 ipv4.freenet6.net successful.
11:21:44 Using TSP protocol version 2.0.1.
11:21:44 Retrieving TSP capabilities from Gateway6...
11:21:45 Authenticating...
11:21:45 Using PASSDSS-3DES-1 authentication mechanism.
11:21:45 Matching Gateway6 key found and used.
11:21:48 The Gateway6 failed to authenticate user ninho@(redacted)
11:21:48 Last status context is: TSP authentication.
11:21:48 Finished.

RSS

© 2013   Created by gogo6.

Badges  |  Report an Issue  |  Terms of Service