Unable to connect

[ukleinek]

Unable to connect

[yvesf]

This looks similar to #4 , maybe it is related to the new iodine version.

Can you observe the same problem with using iodine 0.6 on the serverside?

[ukleinek]

I had the same problem already before switching from 0.6-rc1 to 0.7. If you have a hint how to debug that, or need a tcpdump of a failing session, just tell me what you need (and how I can do it[1])

[1] I know about network stuff, but not android, don't even know how I would generate the stack trace that appears in #4.

Thanks
Uwe

[yvesf]

You can "generate" the display by running 'adb logcat' while executing the program.

I'm closing this as a duplicate of #4, please re-open if you think that this is a different issue.

The workaround for #4 is to force the iodined server to use a higher MTU. The next version of andiodine will give you a dedicated warning about that.

[ukleinek]

I didn't had the opportunity to do the logging, but also after switching the server to use -m 1280 I still got strange failures. http://www.kleine-koenig.org/tmp/andiodine-m1280.png
I failed to connect with the upstream console client, but at least this one gets the output right.
http://www.kleine-koenig.org/tmp/iodine-m1280.png.