If the Bacnet console asks for information that is larger than the frame size, Transport->sendResponse() will use network->sendSegmented instead of network->sendAPDU. sendAPDU works great but sendSegmented is having problems with keys in the waiting room. When it sends the first segment Transport->sendSegments always comes back with a null response. This is causing a lot of hangs in the console as it waits for information. The console appears to be sending the correct response based on Wireshark.

I have multiple devices on the same physical platform. I have added multiple IP addresses to the NIC and then created devices that use the standard port but different address with the "bind address" when creating an UpNetwork object. If I use one device with the primary IP and one with a newly bound address, then send a IAM broadcast, the console sees both devices but can only query the one bound to the primary address. The other one is reporting the same address! Am I missing something here? If I use the same address but increment the port I get the same problem of the first can be queried and the second cannot.
Scott

When creating a series of device objects you are forced to increment the port on each one. If you do not there is a "Cannot create device, address in use" problem. However, the incrementing port is a problem as the BACNET console is not seeing any device that is not on the standard port. Any ideas?

At the moment that is the big hammer approach. I am experimenting with setting up a virtual network on the linux system just for the bacnet devices. I will let you know how that goes. The ifconfig and ip commands can do the same things. the ip command can do more but for this application ifconfig is just fine. I am going to start a blog of my experiences and give some same code once I get this thing working (just about ready).
Scott