Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - ipv4 Router alert workaround.: (3 Items)
   
ipv4 Router alert workaround.  
with reference to the post

http://community.qnx.com/sf/discussion/do/listPosts/projects.networking/discussion.technology.topc6252

We are considering modifying ip_input.c on our own as a temporary fix to handle the router alert option. Since nothing 
is passed back from ip_dooptions, we set a global variable inside it if router alert option is spotted. In ip_input(), 
we use the global variable to decide whether to treat the packet as one directed to us.

This seems to be working, but we are not sure whether it is safe to use a global variable. So we would like to know 
whether ip_input() is a re-entrant ?
Re: ipv4 Router alert workaround.  
On Tue, Mar 03, 2009 at 02:48:34AM -0500, Rosen Rosen wrote:
> with reference to the post
> 
> http://community.qnx.com/sf/discussion/do/listPosts/projects.networking/discussion.technology.topc6252
> 
> We are considering modifying ip_input.c on our own as a temporary fix to handle the router alert option. Since nothing
 is passed back from ip_dooptions, we set a global variable inside it if router alert option is spotted. In ip_input(), 
we use the global variable to decide whether to treat the packet as one directed to us.
> 
> This seems to be working, but we are not sure whether it is safe to use a global variable. So we would like to know 
whether ip_input() is a re-entrant ?

A global is OK currently. ip_input is not currently re-entrant.

-seanb
Re: ipv4 Router alert workaround.  
Thanks for the quick response.