[ee122] MNL doesn't transmit Ack

Lisa Fowler fowler at eecs.berkeley.edu
Sun Dec 9 00:00:02 PST 2007

Please read the FAQ regarding MNL and port numbers.  This has been
discussed several times on the list as well.

MNL_sendto() allows the MNL subsystem to drop packets.  TestRecv
doesn't care to drop ACKs so it does not use MNL_sendto().

You do need to build support for MNL_sendto() into both your receiver
and your sender, but this necessitates the use of two MNLDaemons.
Please see the FAQ as well.

I hope this helps.


On Dec 8, 2007 9:43 PM, Haley Nguyen <haley.ng at gmail.com> wrote:
> I use MNL_sendto() to send the ack, but I noticed TestRecv use sendto() to
> send the reply. Is there is reason that TestRecv use sendto() and not
> MNL_sendto()?
> On Dec 8, 2007 8:36 PM, Haley Nguyen < haley.ng at gmail.com> wrote:
> > I have a receiver and a sender running. The sender send a packet to the
> receiver, and the receiver sends an Ack back.
> >
> > My program runs ok with UDP sendto(), but after I change it to use
> MNL_sendto(), only the receiver receive the packet from sender, but the
> sender doesn't get the ack. In the MNLDaemon, it shows that the ack was
> transmitted just like the data, but the receiver hung waiting for the ack. I
> don't know what I do wrong.
> >
> > --
> > Haley Nguyen
> --
> Haley Nguyen
> _______________________________________________
> ee122 mailing list
> ee122 at mailman.ICSI.Berkeley.EDU
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/ee122

More information about the ee122 mailing list