Hi Team,
Hope you are doing great.
We are getting DTLS handshake failure errors since rtpengine sends dtls client hello (fragmented). Due to this The browser (Edge : version 40) sends error » Client Hello[Reassembly error, protocol DTLS: New fragment overlaps old data (retransmission?)]»
Is there any way that Rtpengine sends only plain client hello DTLS packet.
Could you please guide us how to resolve this issue.
Thanks in advance
Can you post a pcap of this? The DTLS packets are coming straight out of OpenSSL so I’m not sure what the issue could be.
unsuccesswithoutdtlspassive.zip
Thanks For your quick response.
We are using openssl version 1.0.2g and Ubuntu version 16.04 ..
Find the attached pcap file for your reference
I don’t believe the «fragmented» aspect is a problem, since the browser does respond to the initial Client Hello. The initial Client Hello is packet 591. The browser responds with a Hello Verify Request as it should in packet 592. Rtpengine then responds to that with another Client Hello in packet 594, now with the cookie from the Verify Request included. However, this second Client Hello is then ignored by the browser. The flagged packets 864 and 1010 are actually retransmits of 594, because the browser never responded.
Since the only difference between packets 591 and 594 is the cookie from 592, I see no reason why the DTLS fragmentation should be a problem, since the browser responded to 591 just fine. Also these packets are generated by OpenSSL and not touched by rtpengine in any way. I would investigate on the browser side of things for this issue.
Thanks for your response..
Please suggest us how to do once you are done your R&D
I can’t tell you how to debug your browser. I can only suggest to try other browsers, see what happens there and compare.
we tried other browsers like firefox, chrome, Safari but we got this error only in Microsoft Edge browser
I am able to reproduce this issue on CentOS 7.4.1708 using OpenSSL 1.0.2k-fips. It seems that OpenSSL isn’t determining the OS’ MTU, causing the packet fragmentation seen the the pcap trace.
I was able to ‘fix’ the issue by modifying dtls.c dtls_connection_init() to call:
SSL_CTX_set_options(d->ssl_ctx, SSL_OP_NO_QUERY_MTU);
SSL_set_mtu(d->ssl, 1500);
to prevent OpenSSL trying to set the MTU by itself and hard-coding the MTU. The pcap shows that the Hello packets have the IP flag Don’t Fragment set, but the flag for More Fragments unset, so I assume that schannel used by Edge is unable to reassemble the packets.
I haven’t investigated further but I believe the issue is with OpenSSL and I am not sure whether this issue is addressed in a later version.
AFAIU this fragmentation is the DTLS fragmentation, not IP fragmentation. @jamesaylett can you confirm that setting the MTU like this actually makes a difference? Do you have a pcap for comparison? As I already mentioned, the pcap posted by @raviraja0969 doesn’t actually seem to show a problem with fragmented packets, as the packets are responded to.
See the attached pcap traces. With the above mentioned modification to rtpengine-5.5.1.1 and without. The packet fragmentation in the without case looks to be identical to @raviraja0969 issue. You are correct that in the failed case Edge does respond to the first Hello, so perhaps my assumptions about Edge not handling the fragmented packets is wrong.
Either way it does seem like the modification does fix the issue. Discussion of a similar issue in the OpenSSL github.
withmodification.zip
withoutmodification.zip
Interesting, looks like a bug in certain versions of OpenSSL. Thanks for this.
Hi Sorry for restart this thread but i have exactly the same problem. I use OpenSSL 1.0.2h and a sip stack (pjProject) and i always get the fragmentation in the handshake from the client. I tried to set the MTU but it is not working. Do you have any hint or any advise how i can test the MTU in Openssl?
` SSL_CTX_set_options(ossock->ossl_ctx , SSL_OP_NO_QUERY_MTU);
SSL_set_mtu(ossock->ossl_ssl, 1500);
DTLS_set_link_mtu(ossock->ossl_ssl, 1500);`
Can anyone help me to analyze the packet file and give a concrete explaination about «New fragment overlaps old data»?
https://www.cloudshark.org/captures/c…
There must be something wrong with the network between client and server of postgresql.
The discontinuous change about IPID from server to client support this suppose.
But I failed to understand the Expert Info on TCP layer.
The related code lines:
https://gitlab.com/wireshark/wireshar…
1 Answer
Looks like a bug in Wireshark to me. I believe there have been some changes in this area, so maybe a regression.
Please report this as an Issue at the GitLab Issue page, attaching the capture file and providing all the other requested info.
Your Answer
Please start posting anonymously — your entry will be published after you log in or create a new account.
Question Tools
1 follower
- Title: Reassembly
- Release Date:
- Developer:
- Publisher:
Since the release of the Reassembly, players have been reporting several issues. Some of these issues are the Reassembly crashing, and worse, the game crashes during startup. This makes Reassembly totally unplayable. Fortunately, there’s still a way to fix these crashing issues in Reassembly. Below, you will find the most effective ways to fix these problems.
Check Reassembly System Requirements
Before we start with the actual troubleshooting, make sure that your PC meets the minimum requirements of Reassembly. If you did not meet at least the Reassembly minimum system requirements, it’s not a surprise why Reassembly is crashing on your PC. Upgrading your hardware is the best option to make Reassembly playable.
Update Your Drivers
Assuming that your PC was able to handle the system requirements of Reassembly, another reason why the game is crashing is due to the outdated drivers.
An outdated graphics driver, DirectX, and some unmonitored drivers are the reasons why Reassembly is crashing. It is highly recommended that you download the latest driver updates for your PC. If you don’t have enough time, patience, or skills to do a manual driver update, you can do it automatically with Driver Booster.
Driver Booster will automatically recognize your computer’s system and find the correct drivers for it. You don’t need to know exactly what your system is running as Driver Booster will handle all the technical stuff. Check the steps below on how to use this driver update tool.
Step 1: Download and install Driver Booster
Step 2: Run Driver Booster and click the “Scan” button. Driver Booster will then scan and detect any driver-related problems.
Step 3: Click the “Update Now” button to automatically download and install the correct drivers for your computer.
Step 4: Restart your PC for the update changes to take effect.
Step 5: Launch Reassembly and check if these crashing issues have been solved.
If the Reassembly crashing issue persists, you can try the next step.
Verify Game Integrity on Steam
Steam has a built-in feature that will allow you to verify the integrity of the game. Once performed, Steam will check if the files on your local machine are the same as the files on Steam servers. In case something is unsynchronized, Steam will download and repair any file-related concerns.
Here’s how you can perform this method:
- Open Steam and go to Library
- Right-click Reassembly and select Properties
- Go to the Local Files option then click Verify integrity of game files…
- Wait for Steam to validate Reassembly’s files
- Re-launch Reassembly to see if you can play it properly.
Perform Clean Boot
There’s a chance that another program, such as your antivirus, is causing these crashing issues. You can try performing a clean boot to make sure that no other programs are running in the background. To perform a clean boot, you can follow the steps below.
- Open the Run tool by pressing the Windows Key + R
- Type msconfig and hit Enter
- Go to the Services tab section
- Check Hide all Microsoft services
- Click the Disable all button
- Click apply and restart your computer
Run the game after the restart and check if there’s still a crashing issue.
Download and Install the Latest Patch
Reassembly crash is likely to be a bug that comes along with the previously released patch. Installing the latest patch could fix these problems. You can download the newest Reassembly update by simply launching the game on Steam.
Reinstall Reassembly and Steam
If you already tried all the recommended fixes above but the issue still sticks around, it’s likely that the current version of Reassembly or Steam installed on your PC is the main culprit. The uninstall-reinstall method may work for you.
This site contains affiliate links to products. We may receive a commission for purchases made through these links.
В этой статье вы узнаете что делать если Reassembly зависает с ошибками. Я расскажу о причинах и покажу решение.
Причины зависания игр
- Баг и вина разработчиков, необходимо установить патч (смотрите ниже)|Разработчики накосячили, у всех бывает, тут необходима установка патча (грубо говоря заплатки) чтобы избавиться от вылетающих ошибок и зависаний, доступно ниже}.
- Операционная система со временем засоряется, после некорректного удаления программ в реестре остаётся мусор, всё это нарастает, система работает не так быстро как в начале.
- Низкая производительность вашего компьютера, здесь думаю понятно, что необходим апгрейд вашего ПК.
- Плохая оптимизация операционной системы.
Для устранения проблемы необходимо поставить этот патч, инструкция идёт вместе с ним внутри, это избавит вас от проблемы.
А ещё можно улучшить производительность ПК если есть желание и лишнее время.
Установите совместимость с более ранней операционной системой
Если игра запускалась на более ранней операционной системе без глюков и ошибок, вы можете установить с ней совместимость, выбрав из списка. А также установите галочку запуск от имени администратора. Нажмите применить и ОК.
Если причина в слабом ПК
- Для начала можно заменить жёсткий диск на твердотельный накопитель SSD (это самое узкое место в производительности) и установить на него систему и игру, что даст колоссальный прирост производительности. А также заменить другие компоненты или же собрать новый ПК, смотреть по обстоятельствам.
- Оптимизировать систему Windows программой твикером если не умеете вручную, допустим через WinTuning 8 и любые другие. Независимо от комплектации вашего ПК вы улучшите производительность.
- Запускать систему с RAM диска, дорого и не для всех требуется солидное количество оперативной памяти.
- Если у вас HDD, рекомендуем регулярно делать дефрагментацию диска, раз в 2 месяца, например.
Если операционная система установлена давно
- Рекомендую вам хотя бы раз в несколько месяцев чистить реестр
- Лучший вариант — переустановка Windows может решить многие софтовые проблемы и в целом всё будет работать пошустрее.
I wrote a proxy server which support http and https connection, When I use with http all work fine, but when I work with https , wireshark report this error
‘Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)’
Although the browsing work fine but performance is impacted as after this I see TCP RST and because of that SSL negotiation happen again.
Any clue on what could be wrong ?
169.254.119.252 169.254.1.66 TCP 66 54589 > ff-fms [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=4 SACK_PERM=1
169.254.1.66 169.254.119.252 TCP 60 ff-fms > 54589 [SYN, ACK] Seq=0 Ack=1 Win=16384 Len=0 MSS=1456
169.254.119.252 169.254.1.66 TCP 54 54589 > ff-fms [ACK] Seq=1 Ack=1 Win=65520 Len=0
169.254.119.252 169.254.1.66 TCP 245 [TCP segment of a reassembled PDU]
169.254.1.66 169.254.119.252 TCP 912 [TCP segment of a reassembled PDU]
169.254.119.252 169.254.1.66 TCP 252 54588 > ff-fms [PSH, ACK] Seq=192 Ack=859 Win=64662 Len=198[Reassembly error, protocol TCP: New fragment overlaps old data (retransmission?)]
169.254.1.66 169.254.119.252 TCP 91 [TCP segment of a reassembled PDU]
169.254.119.252 169.254.1.66 TCP 54 54587 > ff-fms [RST, ACK] Seq=391 Ack=955 Win=0 Len=0