This is sent to hint the server about the gap in the sequence.

Packet number 35 is another acknowledgement of packet 32. The sequence number of this packet does not match the next sequence number, which Wireshark computed.

Then packet number 34 is the next packet from the server. Packet number 33 is an acknowledgement of packet 32, which in itself is not very interesting.

If Wireshark is configured to display relative sequence numbers, the value shows up as 234. Based on the packet contents Wireshark will compute the expected sequence number of the next packet. Now we look at packet 32, which is a packet from the server to the client. From this value we expect to subtract 12 bytes for a timestamp option, thus the server can send 1408 bytes of IRC payload in each TCP packet. It tells the server that it is not allowed to send more than 1420 bytes to the client in each packet. In this packet the MSS option is interesting. First of all packet number 11 is your SYN packet to the server. I'll explain what relevant information I found in this dump. As long as you don't know what to look for, you really can't do much better than just provide the entire dump.

Use wireshark to find irc servers