LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How does the udp-handshaking protocol in the labview-TCP connect function work?

 
0 Kudos
Message 1 of 6
(4,572 Views)
Could you be a bit more specific?
0 Kudos
Message 2 of 6
(4,565 Views)
Normally a tcp-connection is set up by sending tcp-syn-packets, but when i run the labview tcp-connect function, my pc sends a udp-packet.
0 Kudos
Message 3 of 6
(4,557 Views)
This is not my experience. How do you monitor the packets? Are you using a packet sniffer (e.g. ethereal)?

Could you attach an example that shows this behavior? What are the destination ports of the UDP packet?

(I can think of several reasons why you might see an UDP packet, but they should not depend directly on the TCP open.
(1) If you specify the target with a hostname, you'll force a DNS lookup (UDP port 53 to your DNS server).
(2) Does your code try a reverse lookup anywhere? (IP--> hostname)? If this fails, (e.g. if you use a private host name that is not listed with the DNS server), the lookup mechanism will probe the target IP directly on port 137/UDP.)
0 Kudos
Message 4 of 6
(4,551 Views)
I'm programming a microcontroller demo-board(demo9s12ne64 in c)to communicate over ethernet. This mcu is directly connected to a LAN-wire with my pc. So i see the udp-packet coming in is a udp-packet of port 67 when i start the tcp-connect function. Port 67 is dhcp udp port, so i was thinking, maybe my pc first tries to acquire its own ip-address. Nevertheless i gave my pc a static address at the internet-options.
Anyway, I get a ERROR42:generic error message in labview.
0 Kudos
Message 5 of 6
(4,539 Views)
I don't think that a DHCP request is in any way related to your TCP-open.
(Initial DHCP requests are broadcasts to the generic broadcast address 255.255.255.255, thus any device on the subnet will see it. Unless the receiver is a DHCP server, it will be simply ignored. This cannot have anything to do with your generic errors, because LabVIW will never be aware of this packet).

Your description is not clear enough. Are you seeing the UDP packet incoming on the PC or on the microcontroller (In other words, does it originate on the PC or the microcontroller)? Look at the source MAC address in the ethernet header to make sure where it originates.

How many NICs are on your PC? How do you usually communicate with the microcontroller, is this also via ethernet? Can you ping it? What happens if you try to telnet to the TCP target port, do you get any kind of banner?

Are you sure TCP/IP is configured correctly?
0 Kudos
Message 6 of 6
(4,531 Views)