[iodine-users] Andriod iodine client partly working

Marcel Bokhorst marcel at bokhorst.biz
Thu Mar 10 22:38:19 CET 2011


After a lot of research and some hacks I have communication from a Android 
iodine client with a know to work iodine server.
I am stuck at 'Warning found no accepted fragment size'. Does anybody have an 
idea what could be wrong?

This is the output so far:

# ./iodine -f <removed>
Enter password: 
Opened dns0
Opened UDP socket
Sending DNS queries for <removed> to 8.8.4.4
Autodetecting DNS query type (use -T to override).
Using DNS type NULL queries
Version ok, both using protocol v 0x00000502. You are user #1
Setting IP of dns0 to 10.0.0.3
Setting MTU of dns0 to 1130
Server tunnel IP is 10.0.0.1
Testing raw UDP data to the server (skip with -r)
Server is at 192.168.178.1, trying raw login: ....failed
Using EDNS0 extension
Switching upstream to codec Base128
Server switched upstream to codec Base128
No alternative downstream codec available, using default (Raw)
Switching to lazy mode for low-latency
Server switched to lazy mode
Autoprobing max downstream fragment size... (skip with -m fragsize)
...768 not ok.. ...384 not ok.. ...192 not ok.. ...96 not ok.. ...48 not ok.. 
...24 not ok.. ...12 not ok.. ...6 not ok.. ...3 not ok.. ...2 not ok.. 

Warning found no accepted fragment size.
Warning try setting -M to 200 or lower, or try other -T or -O options.


And yes, I will document the whole process when everything works.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/iodine-users/attachments/20110310/68ca112b/attachment-0002.html>


More information about the iodine-users mailing list