sockfd = socket(AF_ROUTE,SOCK_RAW,0);
Please let me know if anything else needs to be done.
Rgds
sai
--
Hwa Jin Bae
mailto:h...@pso.com
http://www.pso.com
"Hwa Jin Bae" <h...@pso.com> wrote in message news:<u9fk4j7...@corp.supernews.com>...
> PF_ROUTE is not supported as far as I know. The support can be added, but
> you need source code.
Not true; there is a component called INCLUDE_NETINET_RTSOCK that adds
support for routing sockets. This is in AE, and should be in later
versions of T2 (the first date in the source file is '96).
Rgds,
John...
doug
"John" <john_...@yahoo.com> wrote in message
news:488e459a.02032...@posting.google.com...
Trivia: rtsock is not really absolutely necessary in vxWorks, a lot of
route.c functions are directly accessible to programmers. (Undocumented
though). rtsock is really needed for systems like Unix where there is a
clear division between user and kernel mode. User programs can't call
route.c functions or access data structures directly. So they use rtsock
instead on Unix. But in VxWorks, it is really not a requirement -- other
than for competibility.
Stuck me it was there because of lazyness.....
Seems a 'useful' way to increase the code size :-)
I also looked at all the uses of the 'System buffer pool'.
Apart from one bit of the routing code (which probably
never happens) these are always used with the semantics
of malloc() and free() - except that the memory overhead
is significantly larger.
David
Check whether your system has AF_ROUTE defined. Mine (5.3) doesn't.
Speaking only for myself,
Joe Durusau