05-28-2013 09:26 AM - edited 05-28-2013 09:30 AM
Hello,
I'm using a PXI 8109 running Pharlap.
I'm trying to use the second ethernet interface of my PXI to send UDP and TCP packets. The primary interface is used to manage Veristand Channels.
Here is the configuration of my two ethernet interfaces:
- eth0 (primary):
IP : 10.0.0.3
subnet mask : 255.0.0.0
- eth1 :
IP : 192.168.10.9
subnet mask : 255.255.255.0
For UDP, I have no problems, packets are sent to the second interface as I want. I think it work because there is a "network address" input on the "UDP Open" VI so the system can choose the right interface.
For TCP, I use the "TCP Open a connection" VI but there is no this kind of input. And it is not working : I assume the system is trying to use the primary interface but it can't route packets...
For information, my two networks are physically independant.
Can you help me finding out what's going on ? Is it possible to use TCP on the second ethernet interface ?
Many thanks,
Regards,
Laurent
Solved! Go to Solution.
05-28-2013 11:18 AM
I'm seeing this thread:
http://digital.ni.com/public.nsf/websearch/AE69890A3DB5329386256C4F006F7A5E?OpenDocument
It seems this is the operating system which choose the right card. Is there any knew bug in Phar Lap about that?
05-29-2013 04:01 AM
Hello Elboucher!
I didn't understand why you said there wasn't no ipnut "Network Adress" when you use the Open TCP function.
Are you sure?
When i use the TCP open function , i have an input named "Adresss" type = String.
Best regards
Aurélien Corbin
National Instruments France
05-29-2013 04:06 AM
Sorry, I did a traduction mistake, I was talking about the "net adress" input.
05-29-2013 07:13 AM
Sorry but i don't understand your Input problem!!!
Could you give me more details?
The link below can maybe be help you:
http://digital.ni.com/public.nsf/allkb/67F94BB93BCE32CF86257367006B3659?OpenDocument
Best regards
Aurélien Corbin
National Instruments France
05-29-2013 07:33 AM - edited 05-29-2013 07:43 AM
Sorry but, this is not a problem of input. I was just saying that maybe this is not working because "TCP Opens" VI don't have any "net adress" input.
My main problem is that I cannot succefully use the second port of my PXI, for TCP connections. I can use it for UDP but not for TCP.
Thanks for the link, but I already visited it and I did everything that is said here.
From what I've read, Phar Lap is supposed to choose the right ethernet port according to locals IPs and the destination IP. But this is not the case. I get no errors and the connection isn't made ...
05-29-2013 08:54 AM
TCP open vi has a Adress input named " Adress"
adress input for the TCP open VI = net adress for the UDP open VI
If you use the TCP open VI, you must create a constant with the IP Adress of your remote host.
Did you do this?
Aurélien Corbin
National Instruments France
05-29-2013 08:58 AM
Also, I just noticed an other problem :
I use the second ethernet port for TCP (as I said before) and also for UDP broadcasting.
I though it was working for UDP but in fact I have also a problem : UDP messages are sent to both ethernet port ...
I use "UDP Open" with "net address" set to "192.168.10.9" (this is the address of the 2nd ethernet port) and I use "UDP Write" with "255.255.255.255" for the "address" input (because I want it broadcasted).
Why is the system sending packets to both ethernet ports instead of only the 2nd port ?
Regards,
Laurent
05-29-2013 09:03 AM
Yes I'm doing this, the address input of my TCP Open VI is "192.168.10.10" which is the board that I need to reach.
TCP open vi has a Adress input named " Adress"
adress input for the TCP open VI = net adress for the UDP open VI
If you use the TCP open VI, you must create a constant with the IP Adress of your remote host.
Did you do this?
Aurélien Corbin
05-29-2013 09:12 AM
Ok, your Network configuration sounds fine!
What port number do you use?
Aurélien Corbin
National Instruments France