#2Lots of devices, especially tablets that we use to manage the sound gear expect to find the Internet on the other side of a networks gateway. Since only the largest fixed installations may need a gateway you should always leave your gateway blank or 0.0.0.0 - This goes for when setting up the DHCP on the network, most routers will put the interface IP (the IP assigned to the LAN port on the device) in the gateway field. You should delete or use 0.0.0.0The other good thing about rule #2 is you can turn on your Cellular connection on your tablet and get to the Internet and your console. Fear no security because your device can't forward a packet between interfaces (just trust me on this one)If you know a sound guy who is a network geek during the day ask them for help. They will fall over backwards (at least I will) to help a seasoned pro and possibly learn something from them.
Aside from isolating your audio gear from the internet, what is the advantage of this? (Perhaps I am missing it) legitimate question -- I have network printers who ask for a gateway, I've never understood why -- so I end up plugging it in even though it works without it.I also agree with the subnet point. If you have more than 254 networked devices you should probably have someone who knows what they are doing for reasons beyond address space. Following these instructions will make your life easier.Along those lines sometimes the subnet mask of 255.255.255.0 is referee to as /24 in what is known as CIDR notation, though I can't say I've seen CIDR pop up in home/small audio networking.
1 - You can't have two gateways so if you populate the gateway in a closed system you can't have Internet on another interface2 - I would not even bring up CIDR notation, then you have to explain why 255^8+255^8+255^8=24
First let me state that functionally a lot of what has been said so far is sound advice in terms of the world "today"I do feel its important to put the pedants hat on... As often times people reference something as the gospel out of context and confusion occurs. You can have more than one gateway - this is very important when constructing a scalable internetwork. You likely do not NEED to have multiple gateways in most deployed audio networks today... but that is a long way from the existence or not thereof.I totally Agree - if you know what CIDR notation is... good for you... I hope you understand it and VLSM... if you don't know what these terms are and what there significance is then you probably have more interesting things to do with your time A full discussion on subnetting is best done elsewhere.a machine does not expect to see "the Internet" the other side of a router. The machine hopes that packets that are not delivered within the LAN will reach their destination IP address by going through the (or a) gateway to their destination... whether they do this or not is purely down to whether an internet exists (note the deliberate difference in the capital and lowercase i)
Kieren - It's important to be specific, it's not a gateway it's a default gateway of last resort for the 0.0.0.0/0 network. If you have two interfaces, such as a 4G and a wifi on a tablet and you put a default gateway on both interfaces at the least Internet connectivity will "flap" between the two equally costed routes. At the worst the OS will think one connection is unstable and go in search of another. Then you lose you network in the middle of show. If running a headless mixer like a Behringer x32 core or rack or a Mackie DL-1608 all of a sudden you have no control over your system. If feedback starts it could turn ugly really fast.
My brain hurts.
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.
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.
Page created in 0.112 seconds with 17 queries.