goo3 woes..

[putinhead]

I have successfully configured goo3 onto my WRT54G v6 router. Which I did because I could not get IKS4SUNS to work at this location either.
My first route I have working well using IKS4SUNS at my other home. But nothing seems to prevail with my second route. Can you help?


Startup Command (from example):

# - User preferences
server_timeout=10
server_retries=0
ignore_caid=0
log=1

# - Private service provider information
server_0="XXXXXXXXXXXXX:[email protected]:50066/12:34:12:34:12:34:12:34:12:34:12:34:12:34"

# - Command to take the information above and create ini's xx-client can understand
. make_inis

# - Launch Command
xx-client

Via telnet:

XX-Client NF Edition v1.0

 [-CLI-] Connecting to s1.iks66.tv.
 [-CLI-] Connected to s1.iks66.tv.
 [-SER-] Failed to read network stream.
 [-SER-] Server response not received.

 [04/24 @ 07:39:44] - Waiting for requests...

 -------------------------------------------------
               SID: 0328 - CaID: 1816
 -------------------------------------------------
  8F 07 8D 0F CD 2F 87 8F C8 47 96 EE B5 D6 6A 35 
  73 C2 C0 F3 23 E1 87 53 EC 29 68 A3 B9 93 E1 7D 
  45 A1 12 A7 ED 76 1A 5C 75 15 1B F7 C0 32 2B 66 
  86 59 F8 62 74 5C 0B BC 98 D3 4D EC E0 AE EE CD 
  AB 60 A2 33 7B 67 46 31 94 5B B7 C0 98 9A D6 BD 
  99 C4 3F E2 4C 3E D2 1D 2E CC 33 50 80 35 D8 38 
  CF D1 9B 99 C0 FE BF C0 0B 84 2F AA 3B 34 85 92 
  97 9A 70 5C 12 BA AC C6 FE 13 14 EF C7 48 E2 AF 
  9A D6 94 74 2A 64 00 52 DD BF 65 64 62 60 B2 7D 
 -------------------------------------------------
 [-REC-> ECM received from 192.168.1.120.
 [-CLI-] Connecting to s1.iks66.tv.
 [-CLI-] Connected to s1.iks66.tv.
 [-SER-] Failed to read network stream.
 [-SER-] Server response not received.
 [-CLI-] No server available.

[putinhead]

Updating thread as SOLVED

The issues were rather trivial in that IKS4SUNS and goo3 are both particular in how they expect the DES key.
Whereas IKS4SUNS requires the colons in the key: 12:34:12:34:12:34:12:34:12:34:12:34:12:34
and goo3 requires it to NOT have colons in the key: 1234123412341234123412341234

Updating the goo3 startup script reflecting this will proceed as expected.