Sound Reinforcement - Forums for Live Sound Professionals - Your Displayed Name Must Be Your Real Full Name To Post In The Live Sound Forums > LAB: The Classic Live Audio Board

TCP/IP networking primer - Please Read and Add Questions and Comments

<< < (6/8) > >>

Tom Burgess:
My brain hurts.

Scott Holtzman:

--- Quote from: Tom Burgess on July 10, 2014, 12:28:39 PM ---My brain hurts.

--- End quote ---

That's what I was trying to avoid, the take away here is if you don't populate the gateway field in your device or in the DHCP scope then you will never have an issue of two default gateways.  It's that simple.

Tom Burgess:

--- Quote from: Scott Holtzman on July 10, 2014, 01:55:32 PM ---That's what I was trying to avoid, the take away here is if you don't populate the gateway field in your device or in the DHCP scope then you will never have an issue of two default gateways.  It's that simple.

--- End quote ---
OK, I was actually just being a smartass about the brain thing... or maybe I was channeling an old Monty Python skit, hmmmm.   :o

It's been several years since I've had much to do with IT on a regular basis but I was actually able to follow enough of the commentary here to glean some excellent information.  Thanks to all for the great info!  :) 

Scott Helmke:
The question of "gateway" is a very weird one in the context of networked audio device control. Recent Yamaha mixers (M7CL and later) have a setting for gateway IP address, and you do have to put in something in the same subnet. But what the heck is it for? It's not like an LS9 is going onto the Internet to download its own firmware updates.

And beyond that, you really can't use the Yamaha control software (Studio Manager, CL Editor, etc) across subnets anyways because they use a protocol that also needs MAC address. I've got a kickass little L-Com wireless access point / router at work that we can't use for remote mixing because there are no "local" hardware ports. I've been able to tweak things enough to mostly control a Meyer Galileo... but that's beyond anything we could expect a show tech or rental customer to set up in the field.

Josh Millward:

--- Quote from: Scott Helmke on July 11, 2014, 07:02:37 PM ---The question of "gateway" is a very weird one in the context of networked audio device control.

--- End quote ---
I guess I don't think it is that weird. There are plenty of devices out there that can use the default gateway to reach out to something elsewhere on the network. Working from my personal knowledge of the MediaMatrix NIONs I deal with daily, if you have them connected to a larger network that is accessed through a router, you can keep the NION's multicast traffic between themselves down within the context of your larger network. IT guys seemingly hate multicast traffic because it is too easily abused, so they like to filter and block it when they can. However, I can still use a tablet to bring up a user control screen through the web interface since there is a WiFi access point on the network and using the router on the network I can still access the NIONs and manipulate the system remotely. Likewise, the NIONs can also send control information to other devices on other parts of the network that are on the other side of the router if you give them the default gateway.


--- Quote from: Scott Helmke on July 11, 2014, 07:02:37 PM ---Recent Yamaha mixers (M7CL and later) have a setting for gateway IP address, and you do have to put in something in the same subnet. But what the heck is it for? It's not like an LS9 is going onto the Internet to download its own firmware updates.

--- End quote ---
It is just a part of the standard network stack. I'm glad to see that Yamaha has thought far enough ahead to include it. It should be in there because it is part of the IP communications protocol. Your device needs to know where to send requests when it doesn't already know where to send them. Whether your device needs that ability is another question altogether. With the NION platform you can just leave the field blank if you do not have a router on the network for it to communicate with.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version