Hi JZr,
to your question at the meeting regarding routing in HelenOS:
- For an API to configure routes look at uspace/lib/c/include/inet/inetcfg.h
functions inet_sroute_*(). These are used by the inet command. It's not a
perfect match, we might want to distinguish between persistent configuration
made by the administrator and dynamic routes created by a routing daemon,
but it should be a good start.
- Currently HelenOS does not forward received datagrams and it's not
possible to enable it using a configuration option. It should be rather easy
to enable forwarding and just a little bit more work to make it
configurable. The gist is that there are two places in inetsrv where we call
inet_recv_dgram_local() - this function delivers the datagram locally. These
should be replaced with a call to another function that decides whether the
datagram is for local delivery or for forwarding. Then there should be a
forward function that decreases (and checks) TTL and calls inet_route_packet
(), depending on whether forwarding is enabled or not.
I'll look into the changes needed to enable forwarding soon (tm).
Regards,
Jiri
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel
