A novel way to massively improve the SQ of computer audio streaming14 hours ago, HeeBroG said:
Did you use the setup "wizard" WAN+2LAN or WAN+2LAN2?
Geoff, I used this as the baseline for my setup:
Far more complex than most folks need, but you can filter down from here. My mods were to connect a second ERX-SFP (configured as a generic switch) to one of the ethernet ports for the home network, and connect my WiFi access point (with my WiFi VLANs) and home wired ethernet to the second ERX (this optically isolated my home ethernet and WiFi network from the first ERX)
I also configured one of the other ethernet ports on the first ERX to have its own subnet and DHCP server, for my audio network.
Basically, on the first ERX I have the above setup, with my audio net configured on its own subnet on the home network (192.168.9.x), the SFP port on the first ERX configured as part of the home network and connected to a second ERX via fiber (configured as generic switch) where the rest of my home network plugs in (WiFi, and wired ethernet)
My first ERX is powered by a DXPWR dual regulated 12V supply, energized by a PowerAdd Pilot2 battery. Same supply is powering my ISP-provided ONT (basically the equivalent of a cable modem for fiber). My audio network is ERX ethernet port to Sonore opticalModule (powered by DXPWR dual regulated 5V supply, energized by PowerAdd Pilot2 battery) to Finisar SFP module to single mode fiber to Sinisar SFP module to StarTech optical NIC in my Extreme. See below for details
A novel way to massively improve the SQ of computer audio streaming6 hours ago, jacky5555 said:
I'm interested in an Edgerouter X for making a vlan for audio server. My question is: if we isolate the audio server from others, how the Roon remote (on my iphone) connected via wifi access point can talk to the server? Can you pls share you solution!
I think the term VLAN can be confusing...it is a specific way to configure a network, while most folks are speaking to the general concept of isolating (fully or partially) a network, not setting up an actual VLAN.
With the goal of minimizing network traffic seen by my music server (mainly background broadcast traffic), I looked at the following approaches:
1 (LAN) - Isolate my audio server on a dedicated audio network by configuring a dedicated network for a specific ethernet port on my ERX
2 (VLAN) - Isolate my audio server on a dedicated audio network by configuring a VLAN
3 (Subnet) - Isolate my audio server on a dedicated audio subnetwork
I started with 1. In this situation, there was a firewall between my home network and my audio network. To allow my laptop (running Roon remote) to connect to my audio server, I set up a firewall rule that said that if I initiate a network session from my laptop to the music server, the firewall will allow traffic between the computers. Worked well, but I had to ping the music server to initiate a session before being able to use Roon remote. OK for me, but definitely not civilian friendly. I did however hear a marked improvement in SQ with the music server isolated from all the background network traffic, so I was encouraged to keep moving forward.
With 2, in a VLAN you configure the network interface on devices to assign them a VLAN ID (1, 2, 3, etc). The router can then use the VLAN ID to configure virtual networks where only devices with the same VLAN ID can see each other. Same idea as 1, but you don't need a shared physical ethernet connection to manage isolation, so easier to move wired devices between VLANs without having to rewire the network. From a routing perspective, you need to play the same firewall rule tricks to allow traffic from one VLAN to the other VLAN. No net benefit to me over 1
I ended up with 3. I configured my ERX to have the ethernet port for my audio network on its own subnetwork (I happen to use 192.168.9.x), with a DHCP server for that subnet. In this configuration, routed network traffic can freely go between the subnet with my laptop/phone etc and the subnet with my music server (no firewall hacks needed). However, broadcast network traffic is not routed between subnets. Works like a charm.
I should note that in all these scenarios, Roon relies on broadcast packets to discover roon devices/remotes/endpoints on the network. When you fire up Roon on your laptop, you will not see the Roon server on its own LAN/VLAN/subnet. On the Choose Your Roon Core it will sit there looking and nothing will show up. The trick is to hit the help link, which will allow you to enter the IP address of your Roon Core (on a different network). Once you do that, Roon will use routed traffic to make the connection with the Roon Core, and it will show up and work as normal.
Net net, at this point if I disconnect the network connection to my music server, I honestly can not tell the difference (maybe the barest hint of a difference, but so vanishingly small that I have zero confidence in calling it a difference).