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 1001508] Add freebsd CDL option to allow broadcast packets to be sent to 255.255.255.255
Date: Sat, 03 Mar 2012 04:12:00 -0000	[thread overview]
Message-ID: <20120303041228.6A24A2FB082C@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001508-13@http.bugs.ecos.sourceware.org/>

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001508

Jonathan Larmour <jifl@ecoscentric.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jifl@ecoscentric.com
         AssignedTo|unassigned@bugs.ecos.source |jifl@ecoscentric.com
                   |ware.org                    |

--- Comment #3 from Jonathan Larmour <jifl@ecoscentric.com> 2012-03-03 04:12:25 GMT ---
There's nothing wrong with the patch in principle, but the description of the
CDL option, while accurate, could be clarified. In fact what you wrote in the
first and last paragraphs of comment #0 is quite clear. So how about something
like:

            In line with other IP stack implementations, the BSD network stack
            has historically converted packets sent to the INADDR_BROADCAST
            destination addresses (255.255.255.255) into a more specific
            directed broadcast address according to the address configuration
of
            the primary network interface. For example if your network
interface
            is configured as 192.168.100.33/24 and you send a UDP broadcast
            packet to 255.255.255.255, it will actually be sent with a
            destination IP address of 192.168.100.255. Over time, this behavior
            has been criticized for various reasons.  The primary reason is
that
            it becomes impossible to send UDP packets to 255.255.255.255 once
the
            primary network (broadcast) interface is configured with address
            information. For this reason, it is possible to disable this
behavior
            with this option so that packets will be sent explicitly to
            INADDR_BROADCAST when that destination address is specified."

Something along those lines would be fine by me anyway. If you're happy with
that, then go ahead and check it in with that text.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-03-03  4:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 21:23 [Bug 1001508] New: " bugzilla-daemon
2012-03-02 21:26 ` [Bug 1001508] " bugzilla-daemon
2012-03-02 21:29 ` bugzilla-daemon
2012-03-03  4:12 ` bugzilla-daemon [this message]
2012-03-06 19:15 ` bugzilla-daemon
2012-03-02 21:23 [Bug 1001508] New: " bugzilla-daemon
2012-03-02 21:26 ` [Bug 1001508] " bugzilla-daemon
2012-03-02 21:29 ` bugzilla-daemon
2012-03-03  4:12 ` 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=20120303041228.6A24A2FB082C@mail.ecoscentric.com \
    --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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).