Re: bind() not working for outbound socket connections...
Re: bind() not working for outbound socket connections...
- Subject: Re: bind() not working for outbound socket connections...
- From: Philip George <email@hidden>
- Date: Sun, 22 May 2005 05:56:01 -0500
On May 22, 2005, at 3:43 AM, Giuliano Gavazzi wrote:
well, would it not be enough to add manually a route for the
particular remote ip/net going through the dead router (and thus the
interface he wants)?
now THIS is the kind of thinking it's gonna take to get this working!
great suggestion, and creative.
it requires that my app will have to be set to run as root
unfortunately, but at this point i'm desperate.
plus, i've buttoned up all possible places where buffers are flooded
with user input. everything's bounds-checked.
i have a couple of questions about this suggestion:
[1] if i add a route, how do i make sure that the new
route is chosen and nothing else?
[2] after using it, does the route need to be removed
explicitly, or is closing the socket i used thru it
enough?
[3] does adding a new route or deleting a route only
apply to the context of my app or does it affect
the entire system?
[4] i have already played with this a little, but the
examples i'm going off of are a little over-the-top.
if you know of a simple example of how this is done
in C, please post a link.
and by the way, Giuliano, thanks for actually helping out instead of
talking down to me and then giving me a reading assignment. i've been
plagued with unhelpful responses on this issue on three lists... mostly
from the same guy chasing me from list to list.
Giuliano, you rock.
- philip
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden