Using both Lan port on Intel I210-AT, one in the switch and the other in the Streamer

[bobzy]

Hi everyone,

I need of your help about one thing.

I want to use both of my Lan port on my motherboard (Supermicro X10SBA-L with Dual LAN Intel I210-AT).

eth0 connected to my switch
eth1 connected to my streamer (Linn DS)

My current network path :
NAS -> Switch -> Music Server (snakeoil) -> Switch -> Streamer (Linn DS)

What I want :
NAS -> Switch -> Music Server (snakeoil) -> Streamer (Linn DS)

Basicly, Music Server sending directly to the Streamer.

I have not test too much thing since my knowledge in network is not so good.
But, I have already asign static IPv4 with my Router (Apple Airport Extreme) to both ports on the motherboard (xx.0.1.23 and xx.0.1.24) and the Streamer (xx.0.1.4).

But when I plug both Lan, my Linn DS don’t appear on the network, the only way is to plug directly the Linn DS to my switch.

So, with my small understanding of network, it’s seem that Snakeoil os dont make automatic connection with a device like a standard switch do.

Also, when I start the computer, not always, but often, the phrase « A start job is running for raise ne… interfaces (… / 5min 2s) take the full 5min 2s to complete the reboot.

I know that configuration can work, because I based my server on a well know server using the same Motherboard.

Here a picture of the network tab.




jpg to url

Any thoughts about that ?

Thank a lot for your help.

Bob

[agent_kith]

I know that configuration can work, because I based my server on a well know server using the same Motherboard.

Hi Bob, to do what you want, you can either:

1. Use the "full stack" kernel and enable bridging. This will bridge the two network cards together as one. In this setup you only set the IP on the bridged interface (usually called bond0).
   
2. Use a different subnet on the two network interfaces. 192.168.1.x on the switch side, and 192.168.2.x on the other.
   
3. Use VLANs and route between the VLANs. This is the only way to properly seggegrate traffic.
   

With #1. Bridging technically is no different from connecting the streamer to a switch. You're using a good Intel NIC so the performance will  be similiar to a switch, but on other network chipsets (e.g. broadcom) it will be worse.

For most use cases, I would recommend #2. Have a look at this thread, it will have snippets of infomation you need to set this up.

Currently I'm doing #3.

[bobzy]

Thank Agent Kith, I will read this thread.

Which one is sonically the best, at your thought, #2 or #3?

[agent_kith]

Thank Agent Kith, I will read this thread.

Which one is sonically the best, at your thought, #2 or #3?

#3 is ideal management wise, but no change in audio per se. Changing switch brands have a far bigger impact so far.

[bobzy]

For most use cases, I would recommend #2. Have a look at this thread, it will have snippets of infomation you need to set this up.

Currently I'm doing #3. 

Hi agent kith,

I have follow the thread about the #2 solution.

Still don't work... The Minimserver (Snakeoil) appear in my controller (Kazoo), but I not able to see file or play anything. Also, the Linn DS dont appear on the network. 

Since the Linn DS is a Controller and a Renderer at same time, the DS need to be on Internet, or at least communicating with my Rooter. 

FYI, my switch is a Netgear GS108 with ifi ipower Psu...

Here a print screen of SnakeOil...




Thank again for your help

BOB

[agent_kith]

Still don't work... The Minimserver (Snakeoil) appear in my controller (Kazoo), but I not able to see file or play anything. Also, the Linn DS dont appear on the network. 

Since the Linn DS is a Controller and a Renderer at same time, the DS need to be on Internet, or at least communicating with my Rooter. 

Hi Bob, since you want the Linn DS to be on the Internet as well, you have to use the "bridge" solution (Option #1 I believe).

Download and install the Ethernet full stack kernel and reboot to that. Right now you can only configure the bridge from SSH (there are lots of information on the Internet on how to do that).

In the future I'd incorporate bridge configuration in the web app. That'll make it easier for you to experiment the different network toplogies for audio playback.

[bobzy]

Where I can download the Ethernet full stack kernel ?

I install it in the terminal mode ?

Sorry for my lack of knowledge, I'm new to Linux.

[agent_kith]

Where I can download the Ethernet full stack kernel ?

I install it in the terminal mode ?

Sorry for my lack of knowledge, I'm new to Linux.

Go to this thread, scroll down and download the "full network stack".

Refer to the Snakeoil reference guide on how to switch to a different kernel (Make sure you're using the latest Snakeoil firmware before proceeding).

[bobzy]

1. Use the "full stack" kernel and enable bridging. This will bridge the two network cards together as one. In this setup you only set the IP on the bridged interface (usually called bond0).
   

Done, full stack kernel installed  

how I do for the bridged interface, bond0 ?

I put the same static IPv4 for both eth0 and eth1 ?

[agent_kith]

Done, full stack kernel installed  

how I do for the bridged interface, bond0 ?

it's br0. br as in bridge. bond is for teaming/LACP (trunking).
 

I put the same static IPv4 for both eth0 and eth1 ? 

Not quite. Refer here.

As an example, it'll be something like:

Code:

auto lo
iface lo inet loopback

# Bridge between eth0 and eth1
auto br0
iface br0 inet dhcp
   address 192.168.1.10
   netmask 255.255.255.0
   gateway 192.168.1.1
   dns-nameservers 192.168.1.1
   bridge_ports eth0 eth1
   bridge_stp off
   bridge_fd 0
   bridge_maxwait 0

So what this does is both eth0 and eth1 are bridged into br0, and br0 has an IP address of 192.168.1.10. Remember to install the bridge-utils package.

If your home network is very "chatty", there will be a lot of traffic being "cut & pasted" between eth0 and eth1. This more or less will affect the latency of your PC so AQ will be YMMV. What this bridge can do however is it'll potentially isolate any electrical noise on the LAN side (e.g. if you switch/router is running a dirty SMPS).

So if you have a lousy switch, there is potential of an improvement.

However, once you get better switches down the road, there'll be a flip - this bridge is potentially going to be a bottle neck.

Almost worth writing a blog article on this. Just not too sure where/how to begin as there're so many topics to cover.