Social Feed

For anybody interested, here is the back of the Arris:



And the back of the Ericsson (below it is an old Tandberg receiver)

Does anybody have any experience with that Octagon SF8008 Supreme dual tuner receiver that Rick is selling? Can it output TS files? It appears to be similar to the Edision receivers that have a WebIf interface and streaming capabilities.

I was tempted to buy an eBay International Datacasting Superflex receiver solely for snooping satellite data.
They also make the Novra series of data receivers used to NOAAPORT ground stations.
I''m not sure if a particular router that is tailored for multicasting is necessary. And the apparent UDP used here means one-way only LAN coms.
But....multicasting is a subject that is still very very foggy to me. YouTube videos just don't spark my understanding so far.
If the Arris needs to use a multicast address to send a stream to a remote device. Then one_db get's my attention.

Comf. Yeah. You are correct. Your Arris management console IP allows configuration of its parameters and operation.
On the send side. In the Output Config. screen. Try what one_db said. I would have no idea how you would "tune into" the stream on a multicast address. But for gits and shiggles what if you set an IP in your scope that is something several octets different from the management console IP. And a known port. 8080 (common webcam port).
My Asus router has apparent multicast capability and settings for it. And an IPTV section that I have no clue how to use. Only because I never used it.
I mean. Configuring the output section won't screw anything up. There must be an operators/configuration manual for the industry standard streaming protocol. I mean, the Arris itself shouldn't mean for the output to work you need Arris peripherls to do it. Like if you used the ASI output to an ASI>HDMI converter.

Page 53 of the Users Guide posted above clearly states "destination multicast IP address" in Figure 38.

Most firewalls/routers that have multicast support is exactly for supporting provider IPTV, which is really access into the provider's private multicast network via an internet last-mile. The majority will be running a piece of free code named igmpproxy or will implement similar IGMP proxying functionality on their own. GitHub - pali/igmpproxy: IGMP multicast routing daemon

igmpproxy is a clever piece of software, however it is typically used to participate in an existing multicast network on the WAN side and to help facilitate the inbound NAT of the multicast UDP packets and their retransmission on the LAN side. It may or may not be able to help in this case and the nerd knobs in the configuration file that I have on my BSD firewall will likely be unavailable in a GUI-driven consumer product.

Mileage guarantees are still variable...

My apologies. At the moment multicast is way above me. But found a few things. In Windows to enable it's usage in the network stack you need to go into programs and features, additional Windows features. And use the drop down in MSMQ to find enable multicasting support.
My router does support mc routing. Thing is. Trying to get my osmio4k running openvix will get me over to their place to ask about mc. Suggesting using an private IP and port in the commercial receiver seems to be 100% incorrect;
Looks like the range of IPv4 is 224.0.0.0 to 239.255.255.255. And those ranges each have their own specifics.
Then there is IPv6. Whew! A TBS DVB-S2 PCIe card in a pc sure makes TS analysis easy.
Commercial users of these rack mount receivers using the GigE port have their day cut out for them.

I never gave it a thought why the machine vision racks at my previous industry used "funky" hard coded IP addresses.
I just accepted it. A stack of 6 pc's all talking to each other. I "built" the LAN from the ground up. To grab reports, etc.
And it worked. Never gave the...224.0.0.XXX vision system a second thought. Knew nothing, didn't know why.
Then the powers that be decided to contract Level 3 to come in and take over the networking to a central location deep inside of the Federal Reserve on Jacksonville.
"Stay out of their way" they said. I did. That was during a Friday evening to Sunday evening complete plant move down the street. What a cluster you-know-what.
The Level 3 geeks did their thing. Evening crew scheduled. All pertinent machines setup and running.
Looks ok. Sweaty, crusty, stressed, tired. Thinking it was all over. Done. Get it working, make it pretty later.
Long story short. Plant manager calls. Nope. Spotty working machines. Then they worked.
CEO slash whatever calls a bit later. You gotta' come in. I complied.
Grabbed spools of Cat6 and everything needed to build and certify cabling the way it used to be.
Put on the blinders. CEO asks me to teach him how to terminate cabling. I just said stay away, I got this. Asked me how he could help. In front of the evening crew I slapped my right Levis pocket hard and just said you can help me right here.
Anyway. Stripped out the Level 3 networking and wired the machines the way they used to be.
I could go on.I kept my job. My way worked. We walked past each other in the shop on either side for a week or so.
I could go on.
Now those funky IP's are multicast! Wow. And Level 3 never asked, never knew that they needed to add that to the routing/firewall/throw-in-a-coathanger to the mess. All I had used were PnP business class switches.
Sorry for the rant.