Sha256: bb181f2583e4ec70ea95fe8bec3c129fc20f705c0eb27c48b137c221b41a29b4
Contents?: true
Size: 1.13 KB
Versions: 1
Compression:
Stored size: 1.13 KB
Contents
Hello Rob, NetFinder uses UDP broadcast to locate and configure GPIB-ETH controllers on a network. You can find an implementation of the protocol in the nfcli utility http://prologix.biz/downloads/nfcli.tar.gz Discovery Create NF_IDENTIFY packet. Set sequence to a random value Set eth_addr to all ones Broadcast NF_IDENTIFY datagram to port 3040/UDP. Listen for NF_IDENTIFY_REPLY datagrams. Verify sequence matches NF_IDENTIFY packet Configuration Create NF*ASSIGNMENT packet Set sequence to a random value Set eth_addr to MAC address of desired device Set ip_type to NF_IP_DYNAMIC or NF_IP_STATIC If ip_type is NF_IP_DYNAMIC specify ip, mask and gateway addresses. Broadcast NF* ASSIGNMENT datagram to port 3040/UDP. Listen for NF_ASSIGNMENT_REPLY datagrams. Verify sequence matches that of NF_ASSIGNMENT packet Check result field for NF_SUCCESS Notes: 1. You may get multiple replies. Discard duplicate replies. 2. All multi-byte values are in network order (big-endian) 3. On multi-homed hosts, make sure broadcasts go out over all interfaces. 4. NetFinder protocol only works within the same subnet as routers will not forward UDP broadcast packets.
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
prologix_gpib-0.5.0 | udp_info.md |