NetUDP server and client library

[agraham]

This library supercedes, and includes the fuctionality of, the NetUDPclient library. This new version includes a UDP server object and a DNS lookup capability. I removed "client" from the name of the library to better reflect its broader capability.

Sources, help and demos are included in the archive as usual.

 

[Byak@]

Hello Agraham. i don't understand what happend if
1)2 or more clients send data an ONE moment?how work event in this situation?
2)one client sent data.event fired and subprogram in event begin.and in this moment (subprogram not ended) second cliend sent data.what happend?
:sign0104:

 

[agraham]

I assume the server's networking stack can cope and queues the packets, or throws them away, as it is UDP after all and delivery is not guaranteed.

 

[micro]

Hi Agraham
but client works only with localname of the server and not with IP address?

 

[agraham]

Sorry, I don't understand the question, if it is a question

 

[micro]

the client connects to the server when I enter the server name and not the ip

 

[agraham]

It should accept either

IPAddress.Parse Method (System.Net)

public void Start(String URLorIP, int txPort, int rxPort)
        {
            if (!connected)
            {

                try
                {
                    txendpoint = new IPEndPoint(IPAddress.Parse(URLorIP), txPort);
                }
                catch (FormatException)
                {
                    //not an ip address... try resolving through DNS
                    IPHostEntry entry = System.Net.Dns.GetHostEntry(URLorIP);
                    txendpoint = new IPEndPoint(entry.AddressList[0], txPort);
                }
                client = new UdpClient(rxPort);
                client.Connect(txendpoint);
                rxthread = new System.Threading.Thread(new ThreadStart(ReceiveThread));
                connected = true;
                rxthread.Start();
            }
        }

 

[micro]

Ok Agraham, work fine.

 

[Zenerdiode]

Hello Andrew,

I'm trying to use your NetUDP library to talk to a small logging device. The connection is just a direct cross-over CAT5 network cable. The device has an in-built webserver and I can connect to that just fine. However it also accepst commands via UDP for administrative tasks.

I am able to send a UDP request with your Library; also I know the device responds as I have looked at the network traffic with Wireshark. However the _Received event is never fired. The Wireshark traffic is identical when I use the logger manufacturer's tool, so the attached screenshot is indeed identical if I use the manufacturer's tool or my program.

I have tried all combinations of having txPort and rxPort set to 40134 and 3003.

 

[agraham]

From that Wireshark capture it looks like your device is replying to the wrong port. The device is replying to 10.0.1.1:40134 but the UDP client code is expecting the reply to come in on 10.0.1.1:41034 . By the way the client sends through the same port as it is told to listen on.

 

[Zenerdiode]

In the nicest possible way, you may have directed me to a little bit of 'number dyslexia' I checked to make sure I spelled 'Received' correctly in the event sub too.

I'll try when I get in from work tonight.