> >> Not really much we can do about the general port space collision problem > >> unless and until the network stack guys are willing to cooperate though. > > I don't think it has anything to do with the network stack code. It's > basically > an Internet license plate, issued by a separate authority.
I just meant that currently, I can bind an iWARP listen and a normal TCP listen to the same port, and a connect attempt to one or the other will fail. _______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
