configuration - What's the appropriate strategy to remotely assign static IP addresses to a bunch of embedded devices in an un-managed network -


My company is currently developing an embedded device running uClinux, in both non-managed and managed networks Should be deployed.

We are looking for the best strategy to assign static IP addresses (and subnet masks) to those devices (from Windows computers on the network) when no DHCP (or BOOTP) server is available and Saves those values ​​for a configuration file in the device.

This strategy should be avoided using SSH, Telnet or any similar interface. The device will be set with factory default IP address and netmask (such as some object like 19 2.168.1.1). Ideally, Strategy Woudel also enables us to activate or deactivate DHCP support in those devices. MAC addresses of devices will be given a known information that can be used in any device running on any Windows computer.

Does anyone know that there is a standard way to do this? Any recommendations for ensuring potential future portability on the other platform are more welcome than UCILLINX. A combination of standard sellbox device or UCLINX available tools would be ideal.

Thank you in advance,

Francois

I think That is to use the best strategy, which can be obtained in embedded Linux. The idea is that the device automatically provides IPv4 or IPv6 address itself and if necessary, resolve the conflicts of the address

Devices can be searched on the network and you can access them, even if you Confidence is running on the Services Division. The strategy should be an IP alias with a zeroconf address on the network card and you prefer the address on the main interface


Comments

Popular posts from this blog

import - Python ImportError: No module named wmi -

Editing Python Class in Shell and SQLAlchemy -

c# - MySQL Parameterized Select Query joining tables issue -