Page 1 of 1

How to bind to two network interfaces simultaneously?

PostPosted: Wed Feb 11, 2015 5:34 pm
by TheBloke
I'm trying Serviio for the first time on my Media PC laptop. Unfortunately I've immediately hit a show-stopping problem - only one of my two DLNA devices can see Serviio at a time.

The issue is that my laptop has two network interfaces - the WiFi, and a wired network port. I am using both - the WiFi connects to the router and the main house network , on which sits one DLNA device (network subnet 192.168.1.0/24). Then I have a second DLNA device which is reachable only via the wired port (network subnet 192.168.2.0/24). The wired port is a point-to-point connection - a network cable running directly between the laptop and the DLNA client, through a wall, with both devices having hardcoded IP addresses.

The reason for this is that the second DLNA device is wired only, and I cannot yet extend my wired network into the room that contains that second device - I have plans to do some better cabling in the house, but it requires expenditure I hadn't wanted to make as yet. And I'm already at my limit of network-over-power interfaces (if I add another pair, the existing ones stop working.)

This was never a problem before today because the DLNA server I was using up until now, J River Media Center, bound to all network interfaces automatically. But it seems Serviio will only bind to one?

I'm hoping there's some config file parameter or service command line switch I can set to tell it to bind to multiple? I am using the Windows service, on a Windows 7 64bit PC.

Thanks in advance

Re: How to bind to two network interfaces simultaneously?

PostPosted: Thu Feb 12, 2015 12:36 am
by atc98092
I don't think it's possible with Serviio. Zip might have a technical reason why, but most IP functions only work on a single subnet without special routing protocols being applied. When you have your two NICs on different networks, that's called multi-homing. With *nix operating systems, you can sometimes make an internal route between the two networks, but without very specific configuration you basically end up bridging the two networks together, and that defeats any purpose of having different subnets.

Now, with your situation, there may be no reason you can't use this connection as a bridge. This page offers some suggestions:
http://helpdeskgeek.com/windows-7/bridg ... windows-7/

In bridge mode you will need to remove your static IP addresses and let your home router assign them. Either that, or change the static IP to be on the same subnet.