public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001944] New: The DHCPREQUEST message should contain the same 'xid' as the DHCPOFFER message. Date: Sun, 16 Feb 2014 22:05:00 -0000 [thread overview] Message-ID: <bug-1001944-13@http.bugs.ecos.sourceware.org/> (raw) 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.
reply other threads:[~2014-02-16 22:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-1001944-13@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).