[En-Nut-Discussion] Gateway Problems

[Thiago A. Corrêa]

Setting the value to confnet doesn't necessary mean we need to update
the eeprom. Or perhaps I'm not getting the right use of confnet, but
shouldn't it reflect the "current settings"?

If not so, how does one query the current settings? That's not quite clear :)
And what about the initial state, ie: invalid eeprom? I don't like the
DHCP by default approach. In my application I set the default behavior
to be no DHCP and 192.168.0.100/24, 192.168.0.1 as gateway as the
"factory settings". This scenario wasn't easily coded. I think the API
should provide a way to setup this in an easier way, and still be able
to query the current settings, in order to build the output on an web
configuration page.

I've been wanting to submit a doc patch to this issue ever since I
started using ethernut, I guess I will finally have the time to get it
actually done :)

On 4/10/06, Harald Kipp <harald.kipp at egnite.de> wrote:
> Hello Thiago,
>
> At 12:17 10.04.2006 -0300, you wrote:
> >Looking at the sources of NutIpRouteAdd, it doesn't update the confnet
> >struct at all. I would consider this to be a bug, but don't know what
> >the devs think of the issue.
> >NutNetIfSetup does update confnet.
>
> I don't think so. The confnet structure specifies the initialization
> values, which are used during boot with valid EEPROM contents.
> NutIpRouteAdd() is used by the initialization to set the value
> found in the EEPROM or by the application in case the EEPROM
> content is invalid (no MAC address).
>
> Generally this all is a big mess. :-) IMHO, updating the EEPROM
> within NutIpRouteAdd() will not simplify the code but add more
> problems.
>
> Harald
>
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
>