compartmentalizing INADDR_ANY

[Shaya Potter]

I'm trying to work on a project to compartmentalize INADDR_ANY so that
an application doesn't have to be modified, but can run in an
environment where it has less access to machine resources.  It's mostly
proof of concept/researchy so solution can be ugly for now, but what
would I have to do to effectively bind a single socket to multiple
adapters, so that one can mimic INADDR_ANY behavior?

I'm not anywhere comfortable with the networking code yet, but in
looking through the code briefly, it seems like there are these "hash
buckets" that get searched through to see if/what socket is bound to a
particular port.  Is it as simple as mucking with those internals and
having multiple of those buckets point to the same socket?

has anyone done anything like this b4, or even thought about it?

oh, and I'd appreciate being CC'd as my l-k backlog is back to over 10k
message :(

thanks,

shaya

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/