public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001633] New: DHCP Client may hang Date: Thu, 26 Jul 2012 09:22:00 -0000 [thread overview] Message-ID: <bug-1001633-777@http.bugs.ecos.sourceware.org/> (raw) Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001633 Summary: DHCP Client may hang Product: eCos Version: CVS Platform: All OS/Version: All Status: UNCONFIRMED Severity: normal Priority: normal Component: Ethernet AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: bernd.edlinger@hotmail.de CC: ecos-bugs@ecos.sourceware.org Class: Advice Request Bernd Edlinger <bernd.edlinger@hotmail.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |Patch_or_Contribution+ Created an attachment (id=1847) --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1847) proposed patch to fix this defect when a DHCP Response is received it should contain a time slice value. however if the time slice value is zero, the device enters an endless loop. Hence, this configuration error in the DHCP server crashes the devices. Reproduce: install tftpd32 on an own subnet, and configure the dhcp server to use zero-length time slices. The time slice value is not checked by the dhcp server, and just used as is. When the eCos DHCP Client is booted, it gets an address assigned, and freezes immediately, for instance no ping or arp responses are sent. Additionally, the code that sends new dhcp requests uses a wrong formula for bp_secs: bp_secs = cyg_current_time() / 100; But that is only correct for 100 Ticks/second. bp_secs = cyg_current_time() / ((1000000000LL*CYGNUM_HAL_RTC_DENOMINATOR)/CYGNUM_HAL_RTC_NUMERATOR); Howto Fix: Attached you will find a patch for the file "ecos/packages/net/common/current/src/dhcp_prot.c" which checks for zero timeout and silently changes this to 1 second timeout. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next reply other threads:[~2012-07-26 9:22 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-26 9:22 bugzilla-daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-07-26 9:22 bugzilla-daemon
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-1001633-777@http.bugs.ecos.sourceware.org/ \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@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).