Weirdness with vera

[Mike Andrews]

If you have both IP subnets on the same ethernet, you're not gaining
anything.  You need two routers - one for each network. Then you can make
the surveillance network a separate LAN so the house doesn't see any
traffic from it.  BTW, that's what a switch does, too, but at layer two.

Then you need to add the default routes on both routers, i.e. it knows that
the traffic for opposite IP subnet goes through opposite router.
You'll have all kinds of complication if you intend to still use DHCP to
assign IP addresses.

My advice? Call the whole thing off.  Use as many switches as required and
flatten the IP network be one IP subnet.

In my house, I have a separate WiFi LAN on a distinct channel, but all
internal routers are set up as WiFi access points, and those and all
switches are on a single IP subnet.

--Mike


On Sun, Sep 18, 2016 at 5:09 PM, Charlie P <charlie at pendletonweb.com> wrote:

> James,
>
> No issues whatsoever from the web browser. I can turn everything on, off,
> upgrade firmware from the other subnet with no issues.
>
> The magic happens at the firewall with layer 2/3 switching and enabling
> ports. Presently I have all ports enabled (1-65535 tcp/ udp) just to see if
> anything else changed with the same result.
>
> If you want to remote in some time to see for yourself I can set that up
> for you.
>
> Best,
> Charles Pendleton, Owner-
> CFP Systems, LLC
> www.cfpsystems.com
> https://www.linkedin.com/in/cfpsystems
> 484-284-1234 (o)
> 215-266-8688 (m)
>
> On Sep 18, 2016, 14:50 -0400, James Sentman <james at sentman.com>, wrote:
>
> Can you reach the vera directly from the Mac on the other subnet? I’m not
> entirely sure of the requirements as far as routing tables to be able to
> have more than one local subnet and get the Mac to properly use both of
> them… It’s certainly fine to have a second subnet on the same physical
> wires as the other one, but getting them to talk to each other might be
> interesting. You may need to create another virtual network interface in
> the Mac’s network control panel stuff I don’t know.
>
> But the test would be to hit the Veras built in web server directly from a
> browser running on the XTension mac. Can you enter the IP address of the
> Vera from the Mac and get into it or not? Getting to it through the getvera
> portal doesn’t count because that creates a secure tunnel back to the
> machine through your router, we need to see if it can reach the machine
> directly routing between the 2 local subnets.
>
> I think I recall that you’re using really nice network cams and a DVR type
> device that connects to them over ethernet, but they use so much traffic
> that it makes sense to keep the 2 networks physically separate. But if they
> are physically separate then how is that network and the regular local
> subnet connected together? Or is it just a matter of having the devices on
> a switch so that traffic doesn’t go where it’s not needed? I can’t quite
> picture how that is setup without some more info.
>
>
> On Sep 18, 2016, at 9:27 AM, Charlie Pendleton <charlie at pendletonweb.com>
> wrote:
>
> However, in Xtension (and I even updated to the latest today), it
> initializes but never reads any of the devices from the vera. I know this
> used to work as I had the 4 devices working great all through last
> Christmas and up until a month or so ago.
>
>
> Thanks,
>  James
>
>
> James Sentman                       http://www.PlanetaryGear.org
> <http://www.planetarygear.org> http://MacHomeAutomation.com
> <http://machomeautomation.com>
>
>
>
>
> _______________________________________________
> XTensionList mailing list
> XTensionList at machomeautomation.com
> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist
>
>
> _______________________________________________
> XTensionList mailing list
> XTensionList at machomeautomation.com
> http://mail.machomeautomation.com/mailman/listinfo/xtensionlist
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20160918/0642fcc8/attachment.html>