1. New to Christmas lighting? Get started with the AusChristmasLighting 101 Manual:
    auschristmaslighting.com/wiki/AusChristmasLighting-101

the lastest in Blinky Geek ware.

Discussion in 'The Family Room' started by multicast, Jan 27, 2017.

  1. multicast

    multicast Senior Elf Generous Elf

    Joined:
    Jul 13, 2013
    Messages:
    715
    Likes Received:
    7
  2. Boof63

    Boof63 Senior Elf Generous Elf

    Joined:
    Nov 7, 2011
    Messages:
    549
    Likes Received:
    14
    Location:
    Kadina
    sorry but im dumb- pass dont get it
    cheers Boof63 :-\ :-\
     
  3. djgra79

    djgra79 Senior Elf Generous Elf

    Joined:
    Dec 27, 2011
    Messages:
    813
    Likes Received:
    131
    Location:
    Cranbourne West
    Find Me On:
    makes 2 of us...
     
  4. scamper

    scamper Senior Elf

    Joined:
    Jan 5, 2014
    Messages:
    826
    Likes Received:
    75
    Location:
    collie
    Find Me On:
    OK.
    Being a computer geek.
    Would it be 255 or 11111111?
     
  5. David_AVD

    David_AVD Bite my shiny metal ass!

    Joined:
    Jun 12, 2010
    Messages:
    3,541
    Likes Received:
    81
    Location:
    Victoria Point (Brisbane)
    Find Me On:
  6. OP
    OP
    multicast

    multicast Senior Elf Generous Elf

    Joined:
    Jul 13, 2013
    Messages:
    715
    Likes Received:
    7
    We had a E131 task Group meeting today, One of the thigns we did was allocate the multicast address's for sACN over Ipv6


    Its likely to be FF03::83:00:00:00/16 The last two bytes will get used exactly the same as they do in ipv4. to map your 64000 odd universes to. The 3rd least significant byte is reserved.. ( it gives us 8 more bits for some trickery later ), and we picked 83, becuase we needed to use *something*.


    The address's likely will be a from the link-local scope ( same as ipv4 ) and ( thats what the 03 is ).. FF on teh front means its multicast.


    We need to do some research to confimr that link-local scope is the correct thing to do. What this means is that multicast packets will not cross a l3 routed boundary without being routed.. ( if they were org-local scope they can cross those boundarys without it being routed ). Its a subtle but important thing for us to determine.

    As usual, the invitation is always out there for someone else to join the CPWG, it woudl awesome for someone from this community ( I suspect the Blinkys are probalby the biggest user-group of this standard )... to join.
     

Share This Page