Setting preferred IP with 2 NIC

[strikermed]

Hi guys... I'm hoping someone has run into this same problem and found a solution.

I have 2 network interface cards. One is a 1gigabit (192.168.1.240) connection which connects to the internet and my local network. The other connection is a 10gigabit (192.168.2.1) connection which connects directly to my PC for fast network attached storage.

The problem is when Homeseer setup it auto assigned to 192.168.2.1. I went into the network tab in setup to set up the preferred network and chose 192.168.1.240.

As you can imagine, using Myhs.homeseer.com doesn't connect to the system due to homeseer choosing a connection that is not connected to the internet. This also becomes and issue if you want to use myhs.homeseer.com through the app. Also, using ztool+ on iphone also fails bc it looks for an IP that isn't on the LAN network that my phone is on. Finally... Alexa won't work due to them not being connected tot he internet or LAN

I'm wondering how to change how Homeseer chooses the IP Address. Right now the only way to fool it into choosing the IP I want is to shut down Homeseer, disable the 10gigabit network card, and then start Homeseer again. Is there something I'm missing? How can I fix this issue?

Current Date/Time: 2/1/2017 11:20:02 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.298
Operating System: Microsoft Windows 10 Pro - Work Station
System Uptime: 1 Day 10 Hours 4 Minutes 0 Seconds
IP Address: 192.168.2.1
Number of Devices: 141
Number of Events: 33
Available Threads: 1023

Enabled Plug-Ins
3.0.0.1: Alexa
3.0.21.28949: Blue-Iris
3.0.0.68: HSTouch Server
3.0.1.0: IFTTT
0.0.0.28: Pushover 3P
3.0.1.87: Z-Wave

[Rupp]

Did you try binding the ipaddress using Tools > Setup > Network tab?

[Pete]

You have to configure the two nics differently.

One being a host only and the other one being used by Homeseer.

So the one for Homeseer just configure it regularly with an ip, subnet, gateway and dns.

The other host IP just configure it with an IP, subnet and no gateway or DNS.

By default on boot the computer will utilize the first nic and not the second nic. You can though remote to the second nic address for anything.

Note this is what I do for Linux. I am guessing it would work the same way for windows.

[strikermed]

I have already binded server to IP of 192.168.1.240....

I've attempted to change up the settings with in the NIC.

The only things I've configured is the IP (192.168.2.1) and the subnet (255.255.255.0) which is the same as my 192.168.1.1 DNS server. I've ensured that there is no DNS set up on the 192.168.2.1, but prior to that I had it set up with 192.168.2.1 being the DNS since it's the server IP and the client PC would be on 192.168.2.2 IP.

It seems a restart and configuring it the way you mentioned does not solve my problem. It still auto locates 192.168.2.1 as the IP for Homeseer.

[Pete]

Go to the settings file in the config directory and make sure the web IP is correct.

do a cmd / ipcfg and print it here. (copy and paste).

Homeseer should use only the IP configured with a gw and dns.

There isn't any IP configuration in the Linux version of HS3 Pro but there is the web gui configuration with port number.

Is the 192.168.1.240 IP a static or DHCP address.

Do you have DHCP running on the subnet 192.168.2.0/24? If it is just a cable between the two computers there shouldn't be any GW or DNS on it.

Make that subnet 255.255.255.252 (/30) and the HSBox static IP 192.168.2.253 and the other side NAS staic IP 192.168.2.254 so that there are only two IPs on it.

[Pete]

Is it working now?

[strikermed]

Hi Pete,

Thanks for your help...

I opened the HS3 Settings config file and the gServerAddressBind=192.168.1.240


Windows IP Configuration


Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::d8c2:1fca:b06b:7398%4
IPv4 Address. . . . . . . . . . . : 192.168.2.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 0.0.0.0

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::b457:82ba:a8f0:3fe3%5
IPv4 Address. . . . . . . . . . . : 192.168.1.240
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1



My IP is a static IP for the Server according to my router, and I manually entered the IP(192.168.1.240), subnet (255.255.255.0), and DNS (192.168.1.1) in the 1 gigabit NIC configuration.

For the 10 gigabit (192.168.2.1) NIC I do not have a DNS set up, I'm not sure what you mean by GW, and it is a static IP with the card configuration entered by me: IP (192.168.2.1), Subnet (255.255.255.0) and DNS blank


I'll see if changing the subnet.... forgive me for being on the noob side of networking, but doesn't changing the subnet change how many available IP you can? Also, what does the "(/30)" mean when after the subnet you typed below?

Thanks again for your help... I'll try the subnet change tonight!

[Pete]

Yes GW=GW address

A gateway is just utilized to go to the Internet or another subnet.
DNS (D.omain N.ame S.ystem) just assigns names to IP addresses.

Via ARP (address resolution protocol) in the windows command line you can see a few ip's on your network by typing arp -a (arp all).

For just one Host to one PC connection you do not need a gateway or DNS. That said if it is a larger subnet then you can still just use IP to host IP without a gateway or DNS entry.

/30 is the subnet mask (sort of short hand) which is equal to 255.255.255.252 and that does define how many IPs are in the subnet. Here in this instance you can utilize IP address 253 and 254 (last numbers are called octets and referenced as 4th octets).

Use the online calculator here to calculate and size your subnet.

IP Subnet Calculator

[strikermed]

Gotcha... So I'm still not figuring out what the issue is here.


My Ip is set to the correct IP in the settings file (found in the config directory).

I'm curious why my PC is utilizing the expansion card NIC as my first IP and not the onboard NIC which was the first NIC on the system...

So far the only way to get the proper IP to register with Homeseer is to disable the 10gigabit connection and then restart homeseer. Once that's done I can I can then enable the 10gigabit connection.

Right now I'm convinced either it's a feature that isn't available in Homeseer to truly select which NIC you want to use...

And the only solution is to somehow choose through windows which network card is the preferred/number 0 card in my system.

[zwolfpack]

https://www.google.com/search?q=wind...utf-8&oe=utf-8

Check out the 1st result. If that doesn't help, a couple of the others look promising.

[Pete]

Right now I'm convinced either it's a feature that isn't available in Homeseer to truly select which NIC you want to use...

Yup it isn't part of Homeseer's feature set to choose a NIC card. It is more of an OS type feature.

David in post #10 mentions metrics.

Another thing you can do is manually add a routing table. IE: if the IP is this then route the traffic to this gateway.

You may also be able to write a line or two in the Homeseer start up script that points to your first NIC card (or defined gateway or DNS?)