That's a nice switch at a good price, Cisco does things right.
I don't recommend you change anything, since your system is working now, but there is a protocol named DHCP where the switch hands out IP addresses automatically, which makes it unnecessary for users to mess with address ranges, gateways and subnets. Basically you turn the service on in the switch, and again in each PC, and it does all the rest for you. If your network grows and management becomes troublesome, this service can manage IPs and prevent conflicts without requiring you to be Cisco Certified.
Rednet, as well as any other device using the Dante protocol, notes that it is possible to run audio thru the same network you use for data traffic, such as file transfers, internet access, etc, but they also note that performance can suffer if ordinary computer networking traffic hits even moderate levels.
Obviously, audio that has to wait for other network traffic is going to cause big problems during recording or playback. Even more critical is Sync traffic when running Master and Slave AD/DA equipment configurations.
The reason Rednet suggests specific managed switches is that you can prioritize traffic with these switches so that Sync traffic always goes first, and audio gets a high priority too, while the net surfers in the house have to wait a few extra fractions of a second.
Even this may not allow digital audio traffic enough bandwidth to avoid problems, which is why Rednet and others also suggest two networks in parallel, one for data, one for audio. You can add a second (or more) Ethernet port to your DAW and do this easily, which effectively is what you are doing using wireless for net access, but typically wireless is about half the bandwidth of wired fast Ethernet, and roughly a twentieth of wired Gigabit Ethernet. Note that IP addresses are technically assigned to network interfaces, not to computers, which is why you can run multiple parallel networks. Here is where DHCP "set it and forget it" is a big help.
The biggest downside of parallel networks is usually retro-installing the connecting cables for the additional nets after the building is sheetrocked and painted.
I see a day coming where USB/Firewire/Thunderbolt decisions are as outdated and entertaining as Ms. Pearl down at the telephone switchboard, whom you chatted with everytime you asked her to connect your phone call. At some point, everybody is going to have Ethernet interfaces. This is what's coming.
Earlier this morning, I was looking at an SSL device, a 2 Rackspace AD/DA converter with 512 channels of MADI I/O ports, 12 ADAT I/O ports, and 24 analog I/O, for $2500. Effectively an audio interface (using a PCI card) allowing 680 connected devices with a programmable patchbay, and if that's not enough I/O, you can chain up to four of these together to process 2720 audio streams without ever touching a cable.
I don't think this, or even Rednet (as it stands now) will become mainstream in the project studio environment, but some variant of this technology WILL, in the not too distant future. I see a transition period coming, where 1U devices handle AD/DA and a combination of perhaps 24 analog, MIDI, 64 MADI and 16 ADAT I/O, until such time as we get the dinosaurs off their old ADAT decks, and then the home studio will center around analog and a couple MADI ports. (Newbs be advised that MADI encapsulates MID on 1 of its 64 channels, so its not going away, not this week anyway.)
Cdruzeta, its nice for you to be this early in the curve and it should pay off handsomely for a long time to come. Being older, I will probably settle for an early (and therefore subject to obsolescence) solution of a mix of MADI, ADAT, MIDI and analog over Toslink, but I WILL think twice before buying gear OR software that doesn't support both MADI and L3 networking.
If my bread and butter came from planning business models for companies involved in audio hard and software, these are the directions I'd be looking. Its a Brave New World!