9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sirnewton_01@yahoo.ca (Chris McGee)
Subject: [9fans] IP Multicast - Results
Date: Wed, 14 Sep 2016 20:33:58 -0700	[thread overview]
Message-ID: <1473910438.87613.YahooMailMobile@web161805.mail.bf1.yahoo.com> (raw)

After some investigation and trial and error I&#39;m left with the sense that multicast is not entirely implemented on plan9. Here&#39;s what I tried.

I tried setting up a udp announce directly against /net/udp for port 564. Before listening I sent an addmulti message as described in the ip manual page. According to /net/iproute there is a new route for my multicast address but it is not bound to any of my interfaces despite specifying the ip of my adapter in the addmulti. There doesn&#39;t seem to be a way to specify the interface number in the iproute protocol. My process waits but when another process on another machine sends on that multicast address it is not received.

I tried pinging 224.0.01 from another machine and my plan 9 box doesn&#39;t respond to the ping like other machines with multicast enabled.

Finally, after looking at the code in /sys/src/9/ip I find that while a queue of multicast IPmulti structs are assembled nothing at the Ethernet/ARP layer seems to register the multicast with the adapter so that it can receive packets.

Something else that&#39;s puzzling is that I can&#39;t seem to have multiple processes on the plan9 machine listening on the same udp port. On other OSes there are flags that can be set to allow reuse. I&#39;m not seeing anything similar here.

I&#39;m hoping that there&#39;s something that I&#39;m missing. Has anyone else had success setting multicast servers up in any of the plan 9 variants? Otherwise, it would be a project to write the code for it. Perhaps ARP will suit my need better for detecting hosts on the same Ethernet switch.

Thanks,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.9fans.net/private/9fans/attachments/20160914/fc25e840/attachment.html>


             reply	other threads:[~2016-09-15  3:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15  3:33 Chris McGee [this message]
2016-09-15  4:23 ` Alex Musolino
     [not found]   ` <CAEVxPTMkyn3tzFNYMS73zQhse_mXx0KjjD9okYw2ezhGTVsJhA@mail.gmail.com>
2016-09-15  5:05     ` Jules Merit
2016-09-15 19:06   ` Adriano Verardo
2016-09-15 20:01     ` Jules Merit
2016-09-15 23:19   ` Chris McGee
2016-09-16  3:33     ` Chris McGee
2016-09-16  3:45       ` Alex Musolino
2016-09-16  3:52       ` Alex Musolino
2016-09-16 11:12         ` Chris McGee
2016-09-16  7:09       ` cinap_lenrek
2016-09-16 15:00         ` Alex Musolino
2016-09-16 16:33           ` Chris McGee
2016-09-16 19:26             ` Richard Miller
2016-09-16 21:26             ` cinap_lenrek
2016-09-16 22:44               ` Chris McGee
2016-09-16 23:41                 ` cinap_lenrek
2016-09-17 11:53                   ` Chris McGee
2016-09-21  3:20                     ` Chris McGee
2016-09-21  7:41                       ` cinap_lenrek

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=1473910438.87613.YahooMailMobile@web161805.mail.bf1.yahoo.com \
    --to=sirnewton_01@yahoo.ca \
    /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).