From: Walter Huf <hufman@gmail.com>
To: grub-devel@gnu.org
Subject: Randomized TCP client ports
Date: Wed, 23 Nov 2016 13:04:20 -0800 [thread overview]
Message-ID: <CAFfisSzOga8_XBe2=9oDMq1tRQv=uPSELCqN6ncoCwD_JzD+jA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
In the course of developing netboot menus, and rebooting my virtual machine
often, I am running into a problem where Grub is reusing the same TCP
client ports across reboots, and my server (because of TCP TIME_WAIT)
objects to this.
I have a small change to set the initial client port based on
grub_rtc_get_time_ms(), but I'm not sure if that functionality is available
on all supported platforms. I'd like to provide a general contribution that
works on all platforms.
Is there a general way to get a pseudo-random integer that is different on
each boot?
Thank you very much!
[-- Attachment #2: Type: text/html, Size: 683 bytes --]
next reply other threads:[~2016-11-23 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 21:04 Walter Huf [this message]
2016-11-25 21:47 ` Randomized TCP client ports Daniel Kiper
2016-11-26 6:41 ` Andrei Borzenkov
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='CAFfisSzOga8_XBe2=9oDMq1tRQv=uPSELCqN6ncoCwD_JzD+jA@mail.gmail.com' \
--to=hufman@gmail.com \
--cc=grub-devel@gnu.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: link
Be 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 NNTP newsgroup(s).