This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug network/21657] New: Parse interface zone id for node-local multicast


https://sourceware.org/bugzilla/show_bug.cgi?id=21657

            Bug ID: 21657
           Summary: Parse interface zone id for node-local multicast
           Product: glibc
           Version: 2.26
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: network
          Assignee: unassigned at sourceware dot org
          Reporter: b.cama at kerlink dot fr
  Target Milestone: ---

Created attachment 10212
  --> https://sourceware.org/bugzilla/attachment.cgi?id=10212&action=edit
[PATCH] Parse interface zone id for node-local multicast

I stumbled upon programs not able to send to an interface-local multicast
address; at first, it was because Linux kernel since 3.10 (see
842df0739776fc9af7ac15968b44415a31ba9be4) *requires* a zone id for
interface-local multicast addresses, while I thought it did not (I think there
is some confusion here, as they are often qualified “node-local”, which seems
to imply they do not need scope qualification). But then, currently, glibc does
not parse interface names to zone id (sometimes called “scope id” too) for
interface-local multicast addresses, so they are a bit difficult to use; e.g.:

  $ ping6 ff01::1%lo
  unknown host
  $ ping6 ff01::1%1
  PING ff01::1%1(ff01::1) 56 data bytes
  64 bytes from ::1: icmp_seq=1 ttl=64 time=0.018 ms
  ^C

The attached patch proposes to allow it. Proposed commit message following.

[copied from <https://sourceware.org/ml/libc-alpha/2017-05/msg00836.html>]

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

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]