urgent help reqd: modifying routing table using ioctl( ) function

[Abid Ghufran]

This application is conceptually trying to copy a mechanism, from the
ForCES (Forwardind and Control Element Separation) IETF protocol. The
server is the control element and clients are the forwading element,
sort of a distrubuted network element.

Abid Ghufran.

On 8/9/06, Jeroen van Meeuwen <kanarip at kanarip.com> wrote:
> Abid Ghufran wrote:
> > I am trying to use ioctl( ), with the appropriate flag for the
> > addition and deletion of routing entries, to modify the routing table.
> >
> > I have an application where a client takes its interface information
> > and sends it to the server. The server then sends it to other clients.
> > Clients receiving that information are to integrate that information
> > in their routing tables.
> >
> > Now, the problem is that, I am getting very strange behaviour from the
> > system, when I use the ioctl( ) function.It successfully adds the
> > entries but the when i view them in the routing table (using route) I
> > see a REJECT flag ( ! ) with them. Hence the receiving clients cannot
> > use that entry to route traffic to the original client.
> >
> > I am not sure how the ioctl( ) function interacts with the kernel and
> > vice versa.
> >
> > Can anyone help me on this.
> >
> > Thanks,
> >
> > Abid Ghufran.
> >
> As a Network Engineer, I do not completely understand why you should
> have a server (re)distributing routes amongst clients.
>
> That fact aside, could you provide an example?
>
> Kind regards,
>
> Jeroen van Meeuwen
>
> --
> Jeroen van Meeuwen, LPIC-1, MCP
> http://www.kanarip.com/
> C6B0 7FB4 43E6 CDDA D258  F70B 28DE 9FDA 9342 BF08
>
>
>
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
>
>