Multicast Windows Media Center

DaddyGo

@johnpoz said in Multicast Windows Media Center:

Well than that has zero to do with your L3 router at the edge of this network

In the end, I would have told him too (you shot the joke)
I have been dealing with multicast for a thousand years

https://www.audinate.com/

+++edit:

I have a lot of good writing about it here:
https://forums.prosoundweb.com

bryansocko

@daddygo Windows Media Center was ahead of its time and is still superior to any cable offerings. With 2 cable cards that cost 2.95 a month I can record 12 dvr streams at once, have unlimited storage and have extenders at every tv without any additional fees across multiple sites. PS It is not discontinued for Windows 8.1.

bryansocko

@johnpoz That is my understanding as well. However if hook up the old consumer router (netgear RAX200) it "just works" without issue. That is why I ask if I am missing something else that should be obvious. I understand this is not consumer grade routing equipment, I am trying to learn as I go.

DaddyGo

@bryansocko said in Multicast Windows Media Center:

Windows Media Center was ahead of its time and is still superior to any cable offerings.

Good luck with pfSense and multicast stuff...

In the basic case of multicast, it is implemented in L2, if we talk about L3, then the multicast router capabilities are authoritative.

pfSense doesn't have much of this

johnpoz

@bryansocko said in Multicast Windows Media Center:

That is why I ask if I am missing something else

And again - pfsense has zero to do with devices talking to each other on the same L2 - ZERO!!

So unless your not actually on the same L2.. pfsense has zero to do with whatever issue your having..

Turn pfsense off.. Its the same thing since the L3 router has no way to do anything to any traffic at the L2.. be it unicast, or broadcast or multicast..

So either your not actually on the same network like you think, and stated - or you have something else going on.. But I can tell you for FACT, and would bet my left nut on it.. The L3 router has zero to do with L2 traffic.. So there is a piece of the puzzle missing.

DaddyGo

@johnpoz said in Multicast Windows Media Center:

So there is a piece of the puzzle missing.

Hi John, are you nervous?

johnpoz

No just trying to explain that if he says it works with router X but not router Y.. Then there is something missing from the puzzle to explain it.

But from what has been stated..

Did he edit this?

subnet 255.225.224.0/19

Or did I miss it before - what sort of nonsense network is that?? That is not a valid network.. You can not be using that..

You should be using rfc1918 space on your network.. You can not just pull random numbers out of thin air and use them for your network.

bryansocko

@johnpoz that was a typo, 255.255.224.0

DaddyGo

@johnpoz said in Multicast Windows Media Center:

No just trying to explain that if he says it works with router X but not router Y.

The OP is asking you because your reputation is higher, good luck to everyone.

johnpoz

@bryansocko said in Multicast Windows Media Center:

that was a typo, 255.255.224.0

You mean that is the mask? That is not a valid network address space either.. That is a /19 network... Which seems excessively large.. You have some 8000 devices on this network?

But doesn't really matter as long as the actual network is valid space..

Maybe if you draw out how you actually have this connected, if your using some sort of extenders? Maybe they are natting?

But last time - pfsense has zero to do with traffic on the same network.. unicast, multicast or broadcast pfsense has no way to control that or limit that or manipulate that in any way..

Pfsense is used to get off a network.. So if you have some devices on 192.168.0/19 for example - and they are actually on the same L2 network. And they want to talk to each other directly, or exchange multicast/broadcast traffic - pfsense is not part of the conversation..