[En-Nut-Discussion] Bootmon uses different network name than Nut/OS
Ernst Stippl
ernst at stippl.org
Sun Apr 6 23:53:15 CEST 2008
Hi all!
Bootmon (1.0.2) contains init-data for the "confnet" structure in config.c
which is used by BootConfigWrite() when new ip/mask/gateway values are
entered:
<snip>
/*!
* \brief Nut/OS network configuration.
*/
CONFNET confnet = {
0,
{'E', 'T', 'H', 'E', 'R', 'N', 'U', 'T', 0}
,
{0x00, 0x06, 0x98, 0x30, 0x00, 0x00}
,
0, 0, 0, 0
};
</snip>
Here, the netwok name is "ETHERNUT" while Nut/OS (or at least those apps I
have seen so far) uses "eth0".
This causes an app which is loaded by bootmon not to find a valid
network-config in case the (default) name "eth0" is used with the
NutNetLoadConfig (name);
function call.
Is this done on purpose while \NUT\INCLUDE\DEV\BOARD.H contains:
#define DEV_ETHER_NAME "eth0"
??
Regards
Ernst
More information about the En-Nut-Discussion
mailing list