<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 31, 2014 at 2:57 PM, jacek burghardt <span dir="ltr"><<a href="mailto:jaceksburghardt@gmail.com" target="_blank">jaceksburghardt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>I think the answer to op question is simple one making mythtbackend acceptable on both networks I have public wifi on 192.168.2.xx for raspberry watering station wifi thermostat and other wifi controling devices and rest of wired and wireless network is on 192.168.0.xx and I have no issue accessing anything on my network. Other option is to install two network cards or setup multiple network ip addresses on single interface arch linux allows you do acomplish this </div><div><pre style="padding:0.8em 1em 1em;border-width:1px;border-style:dashed solid solid;border-color:rgb(187,204,221);line-height:1.1em;overflow:auto;margin-top:0px;background-color:rgb(235,241,245)">Connection='ethernet'
Description=''
Interface='eth0'
IP='static'
Address=('192.168.2.10' '192.168.3.11')
Gateway='192.168.1.1'
DNS=('192.168.1.1')</pre></div></div></div></div>
<br></blockquote><div><br></div><div>Unfortunately this won't work for the OP. <br><br>What your suggesting is running multiple logical subnets on the same physical network, which is easily done... any client plugged into the switch/hub can be in either subnet, just by changing it's IP addressing.<br><br>The OP is using a layer3 switch, and each port is assigned to a VLAN. Ports in different VLANs are, for all intents and purposes, on separate physical networks with a router managing traffic between them.<br></div></div><br></div></div>