On Tue, 2013-02-05 at 15:17 +0100, Johannes Berg wrote: > On Tue, 2013-02-05 at 14:50 +0100, Johannes Berg wrote: > > On Tue, 2013-02-05 at 14:47 +0100, Pontus Fuchs wrote: > > > On 2013-02-05 12:06, Johannes Berg wrote: > > > > > > > > Intel Wireless devices are able to make a TCP connection > > > > after suspending, sending some data and waking up when > > > > the connection receives wakeup data (or breaks). Add the > > > > WoWLAN configuration and feature advertising API for it. > > > > > > > > > > What's protecting this feature from stomping on an existing connection > > > when specifying the source port? > > > > Nothing. Presumably if you specify it you know what you're doing, and > > don't also create a connection to the same IP from the same port? > > > > Hmm. Maybe we could allocate the socket anyway and make it allocate the > > chosen port, failing if it isn't available? I guess I need to check the > > APIs. > > I guess this might work: http://p.sipsolutions.net/e5bc789d26b5e34a.txt Yep, seems to work, I'll fold that in. (Tested by having a TCP connection open and requesting the same port to be used) johannes -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
