[iodine-users] Error: Discarded data, uncompress() result: -3

Shervin Khastoo shervinkh145 at gmail.com
Tue May 15 09:49:20 CEST 2018


Fixed!
I was running iodined with argument mydomain.com instead of iod.mydomain.com
.

On Tue, 15 May 2018 at 04:02 Shervin Khastoo <shervinkh145 at gmail.com> wrote:

> I believe that is not the case. Packets that are not being fragmented
> (short packets) reach the server correctly. Also, I investigated some of
> the packets manually by running the Wireshark both on the server and the
> client and packets were the same.
>
> It's just so weird. I can download a file from the server via
> wget (because it has small http headers and no packet will be more than 255
> bytes), but I cannot view that page in chromium (because of the large
> headers and the fragmentation).
>
> By the way, I'm using the last version in the repos on archlinux. Could it
> be something like the incompatibility between zlib and iodine? is anyone
> running iodine on the latest archlinux?
>
> Also, I am currently forwarding requests to iodine via bind. I tried
> removing bind and running the iodine directly on port 53 but the problem
> still persisted. But in "raw udp mode" the problem is gone.
>
> On Tue, 15 May 2018 at 03:33 Shelvacu <shelvacu at gmail.com> wrote:
>
>> Error -3 is Z_DATA_ERROR, which is returned "if the input data was
>> corrupted or incomplete."
>>
>> My guess would be that the data is getting mangled on its journey through
>> DNS. If you run wireshark on both ends (iodine <-> wireshark <-> The
>> Internet <-> wireshark <-> iodined), does the same data that came in come
>> out of The Internet?
>>
>> On Mon, May 14, 2018 at 3:51 PM, Shervin Khastoo <shervinkh145 at gmail.com>
>> wrote:
>>
>>> Hello all,
>>>
>>> I have set up an iodine client and server pair. I can ping both sides
>>> from one another but I cannot do SSH. I investigated the traffic using
>>> Wireshark and I realized that all packets that are being fragmented, will
>>> not reach the server. I ran the server with -DDD and I found that the
>>> "uncompress" function from ZLib fails with error -3.
>>>
>>> Can you help me fix the problem?
>>>
>>> Here are the verbose logs:
>>>
>>> iodined[2807]: [288B blob data]
>>> iodined[2807]: INpack with upstream 5/0, we are going to ack upstream 5/0
>>> iodined[2807]: IN   pkt seq# 5, frag 0 (last=0), fragsize 202, total
>>> 202, from user 0
>>> iodined[2807]: OUT  pkt seq# 2, frag 0 (last=0), offset 0, fragsize 0,
>>> total 0, to user 0
>>> iodined[2807]: TX: client 127.0.0.1, type 10, name
>>> paaqayva.my.domain.org, 2 bytes data
>>> iodined[2807]: [282B blob data]
>>> iodined[2807]: INpack with upstream 5/1, we are going to ack upstream 5/1
>>> iodined[2807]: IN   pkt seq# 5, frag 1 (last=1), fragsize 196, total
>>> 398, from user 0
>>> iodined[2807]: Discarded data, uncompress() result: -3
>>> iodined[2807]: OUT  pkt seq# 2, frag 0 (last=0), offset 0, fragsize 0,
>>> total 0, to user 0
>>>
>>>
>>> _______________________________________________
>>> iodine-users mailing lists
>>> iodine-users at lists.wpkg.org
>>> https://lists.wpkg.org/mailman/listinfo/iodine-users
>>>
>>>
>>
>>
>> --
>> ~~~~~~~~~
>> Shelvacu
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/iodine-users/attachments/20180515/3c3d14c3/attachment-0001.html>


More information about the iodine-users mailing list