public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug 1001944] New: The  DHCPREQUEST message should contain the same 'xid' as the DHCPOFFER message.
@ 2014-02-16 22:05 bugzilla-daemon
  0 siblings, 0 replies; only message in thread
From: bugzilla-daemon @ 2014-02-16 22:05 UTC (permalink / raw)
  To: ecos-bugs

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001944

            Bug ID: 1001944
           Summary: The  DHCPREQUEST message should contain the same 'xid'
                    as the DHCPOFFER message.
           Product: eCos
           Version: CVS
            Target: All
  Architecture/Host All
                OS:
            Status: UNCONFIRMED
          Severity: minor
          Priority: low
         Component: TCP/IP
          Assignee: unassigned@bugs.ecos.sourceware.org
          Reporter: J.Lambrecht@televic.com
                CC: ecos-bugs@ecos.sourceware.org

Created attachment 2450
  --> http://bugs.ecos.sourceware.org/attachment.cgi?id=2450&action=edit
patch that fixes this bug

According to RFC 2131 (http://www.faqs.org/rfcs/rfc2131.html): "The 
DHCPREQUEST message contains the same 'xid' as the DHCPOFFER message."
So in a DHCP DORA cycle (Discover-Offer-Request-Acknowledge) the same 
transaction ID should be used ('xid' in C code).
Now the next 'xid' is taken: "Happy to advance, so new XID"

-- 
You are receiving this mail because:
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2014-02-16 22:05 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-16 22:05 [Bug 1001944] New: The DHCPREQUEST message should contain the same 'xid' as the DHCPOFFER message bugzilla-daemon

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).