Port Id endianess when using ACN coding
We are communicating a RASTA Board with a Linux VM in a Windows platform in the OSRANET activity. We have found that the Port Id added to the messages used by sporadic interfaces has no endianess treatment. The linux executable crashed due to polyorb code was accessing one of their tables with a very big value.
I had to add a check in the function '__po_hi_get_entity_from_global_port' implemented in 'po_hi_transport.c' and modify the endianess of that field in our driver.