[iodine-users] iodine mtu corrupted at 229

[Sean Schneeweiß]

Hello,


Iodine ist working fine from one laptop (Windows Vista). But the other computers (Windows 7, Windows 7 Starter, Windows 8, Android) have problems getting a proper fragsize, although it works.
When iodine on the client side is testing the maximum fragsize it shows this message: 768 corrupted at 229 ...


Maybe someone knows the problem and can help me, thanks.


Log:
Enter password:
Opening device LAN-Verbindung
Opened UDP socket
Opened UDP socket
Sending DNS queries for my.domain.com to dns-ip
Autodetecting DNS query type (use -T to override).Opened UDP socket


Using DNS type NULL queries
Version ok, both using protocol v 0x00000502. You are user #0
Enabling interface 'LAN-Verbindung'
Setting IP of interface 'LAN-Verbindung' to 192.168.233.2 (can take a few second
s)...


Server tunnel IP is 192.168.233.1
Skipping raw mode
Using EDNS0 extension
Switching upstream to codec Base64u
Server switched upstream to codec Base64u
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 corrupted at 229.. 768 not ok.. 384 corrupted at 229.. 384 not ok.. 192 ok..
 288 corrupted at 229.. 288 not ok.. 240 corrupted at 229.. 240 not ok.. 216 ok.
. 228 ok.. 234 corrupted at 229.. 234 not ok.. 231 corrupted at 229.. 231 not ok
.. 230 corrupted at 229.. 230 not ok.. will use 228-2=226
Setting downstream fragment size to max 226...
Connection setup complete, transmitting data.
Got SERVFAIL as reply: server failed or recursion timeout
Hmm, that's 2620372. Your data should still go through...
Got SERVFAIL as reply: server failed or recursion timeout
Hmm, that's 2620372. Your data should still go through...
Got SERVFAIL as reply: server failed or recursion timeout
Hmm, that's 2620372. Your data should still go through...
Got SERVFAIL as reply: server failed or recursion timeout
Hmm, that's 2620372. Your data should still go through...
Got SERVFAIL as reply: server failed or recursion timeout
I think 2620372 is too many. Setting interval to 1 to hopefully reduce SERVFAILs
. But just ignore them if data still comes through. (Use -I1 next time on this n
etwork.)




Best regards
-Sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/iodine-users/attachments/20130803/41f388c6/attachment-0003.html>