The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

problem with multiple nics


  • Subject: problem with multiple nics
  • From: Pierre Schmitz <pierre_schmitz@xxxxxxxxx>
  • Date: Tue, 3 Jan 2006 17:04:36 +0100 (CET)

Hi all,

I am very new to xAP (2 weeks) and to this list (just
joined) and first want to say a big thank you to the
developers for all their enthusiasm!!!

Concerning my problem...:
I have a Windows XP SP2 PC with 2 nics:
- a "real" nic with the ip 192.168.1.19 (eth1)
- a virtual nic which is generated and used by a
videodriver 192.168.238.20 (eth0)

As the virtual nic (eth0) is the first in the list,
all applications seem to bind automatcally to the
wrong IP adress.

I use Stuart Booth's GUI hub, which is running on the
correct adress by adding the following lines to the
configuration file:
<add key="xAPBroadcastIP" value="192.168.1.19" />
<add key="xAPListeningIP" value="192.168.1.19" />

When I start a new xAP application (tried it with xAP
Speech and xAP Floorplan), the application connects to
the hub (the hub receives the heartbeat and is
forwarding it), but the application doesn't receive
any message from the hub. The heartbeat is als
received from 192.168.238.20:49153 (wrong adress).

My guess is that the xAP Speech application binds to
the wrong IP adress (how could I change the it?) but
somehow connects to the hub. The hub then can't
connect to the "wrong" IP adress.

Any help is really appreciated, cheers

Pierre








___________________________________________________________
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de




xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.