Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
06-24-2007, 09:47 PM
|
#1
|
Member
Registered: Dec 2004
Posts: 92
Rep:
|
ack retransmission
during a tcp communication, when will ack be retransmited?
If never, could some one give me a hint to implement that?
|
|
|
06-25-2007, 03:00 PM
|
#2
|
Senior Member
Registered: Jan 2005
Location: Manalapan, NJ
Distribution: Fedora x86 and x86_64, Debian PPC and ARM, Android
Posts: 4,593
|
There shouldn't be a need to retransmit an ACK ever. The sender will timeout on the missing ACK and retransmit.
|
|
|
07-01-2007, 09:36 PM
|
#3
|
Member
Registered: Dec 2004
Posts: 92
Original Poster
Rep:
|
but the sender RTO(64s) make the recver wait too long, that's why I want the recver re-send several dup-acks to trigger the retransmission.
|
|
|
07-01-2007, 09:48 PM
|
#4
|
Senior Member
Registered: Jan 2005
Location: Manalapan, NJ
Distribution: Fedora x86 and x86_64, Debian PPC and ARM, Android
Posts: 4,593
|
If you send multiple ACKs, you won't get a retransmission, you'll get the next transmission.
|
|
|
07-05-2007, 01:00 AM
|
#5
|
Member
Registered: Dec 2004
Posts: 92
Original Poster
Rep:
|
according to rfc793:
----------snd.una---------snd.max---------
if the sender get enough dup-ack(snd.una), it will thought that packet been lost and resend it, doesn't it?
|
|
|
07-05-2007, 06:04 AM
|
#6
|
Senior Member
Registered: Jan 2005
Location: Manalapan, NJ
Distribution: Fedora x86 and x86_64, Debian PPC and ARM, Android
Posts: 4,593
|
Good luck with that. You'll end up breaking state and resetting to return to a synchronized state. Your transmission will essentially come to a stop briefly. Try it with a sniffer running to see the result, but remember that all TCP stacks are not created equal.
Maybe you want to use a UDP-based protocol for your transmission?
|
|
|
All times are GMT -5. The time now is 05:14 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|