ADDP Updates – NET+OS 6.3

Last Updated: 03/14/07 Fix Count: 1

 
Title
Netosprog/Discover do not display valid IP address
 
Case: 1223502
 
Date Fixed: 03/14/07
 
Description

The ADDP code was acquiring a valid IP address from the device if the IP address was associated with the primary Ethernet interface (eth0). If, on the other hand, the primary Ethernet interface had no IP address but the secondary Ethernet interface (eth0:0) did have a valid IP address, the ADDP code would not sense the address on the secondary Ethernet interface. Therefore, the data returned to netosprog from the device would have an IP address of 0.0.0.0.

The condition of the primary Ethernet interface not having a valid IP address can occur if the unit acquires its IP address from a DHCP server and the DHCP is not available. In addition, the user has enabled auto-IP to provide an IP address on the secondary Ethernet interface when the DHCP server is unavailable.

 
Solution

Fixed logic which prevented ADDP from working when there was only an auto-IP address.  The fix will use a normal address if it is available, but will use an auto-IP address if there is no normal address and auto-IP is enabled.
 

Files: netos\lib\arm7\32b\ghs\libaddp.a

netos\lib\arm7\32b\gnu\libaddp.a

netos\lib\arm9\32b\ghs\libaddp.a

netos\lib\arm9\32b\gnu\libaddp.a

Special Instructions

• Unzip the patch(es) to the root of your NET+OS installation, for example C:\netos63_gnu\.
• Be sure to install any patches listed under Dependencies below
• Rebuild your application.

Patch Link: ADDPUpdates_63

Dependencies

This patch also requires the installation of the following patch(es):

N/A