Introduction

There are several ways to configure your device to connect to a network. If a DHCP server in running on the local network, then the module will automatically use the DHCP server when the factory application is running. If you do not have a DHCP server running on your local network, then you may need to configure the network settings of the device. Listed below are the options available for network configuration.

Dynamic IP Address (DHCP)

When the factory application boots, it will first attempt to obtain an address from a DHCP server. If you are connected to a network with a DHCP server, then the device IP address, network mask and gateway should be configured automatically. If your PC is on the same DHCP network, you will be able to communicate with the device after a short boot period of 2-3 seconds.

Static IP Address

If the module is plugged in to a network that does not have a DHCP server, you must provide a static IP address, network mask and gateway. These addresses should be provided by your network administrator. Ensure that the IP address and mask selected are able to communicate with the static IP settings of your PC.

Auto IP Address (APIPA)

The default factory application contains an auto IP negotiation system. This allows the device to automatically configure its address in the absence of a central DHCP server, and without the need or a static IP address. This scheme is utilized as a fallback that will activate when both dynamic and static IP addresses fail to initialize. In order to communicate with a device in auto IP mode, the host system must support auto IP. auto IP support is included in both Windows and OS X operating systems. By default, auto IP addressing starts in the 169.XXX.XXX.XXX address range.

Find your Device

To begin, you need to find out the IP address of your module. There are several ways to do this. The recommended option is to locate your device using our online discovery service. You can do this by opening a browser and navigating to https://discover.netburner.com. This webpage should load a table that shows devices on your local area network which are running applications built with NNDK 3.x. From this table, you can access the web interface served from the device by clicking on the link in the "Web Page" column. To access a device's configuration record, click on the link in the "Config" column.

If you don't have internet access from your location, you can run our utility, Local Discovery. This program is available from our tools in <NNDK Install>\pcbin\localdiscover.exe, and sends out a request to all NetBurner devices on the local network. It opens a browser page on the first device to respond that lists all of the discovered devices, or a page that shows that no devices were found.

Another option to find the IP address of your device is to use the NBEclipse IDE. As before, ensure that your device is powered on and plugged into the same network as your PC. Open NBEclipse, and in the bottom left of the workspace, NBFind can be found running. NBFind lists the IP, application, and MAC address of all NetBurner devices on your local network.

A final option is to use the included utility IPSetup. If the device is powered on and plugged into the same network as your PC, run IPSetup. This application shows all NetBurner devices on your network. Be aware that as of NNDK 3.x, IPSetup can not be used to configure your device. Our configuration system now handles this, as described later in this guide.

You can find the IPSetup tool on our website, here.

Note: If these options are failing, there may be a firewall issue blocking the applications from sending the UDP broadcast that is used to locate NetBurner devices. Always grant NetBurner applications the ability to get through your OS firewall and ensure that UDP port 20034 is open for use.