Message-ID: <1359374145.8120.8.camel@jlt4.sipsolutions.net> (sfid-20130128_125530_817060_F0AB72F2)
Subject: TCP connection in suspend (to RAM)
From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Date: Mon, 28 Jan 2013 12:55:45 +0100
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Sender: linux-wireless-owner@vger.kernel.org

Hi,

I'm working on a feature by which our device (Intel WiFi) will establish
a TCP connection while the host is asleep, in order to receive a wakeup
signal over the connection. There are a few configuration parameters,
but it's basically pretty simple, it establishes a connection, sending
configurable data in a configurable interval on it and wakes up the host
if it receives (certain) data on the connection or the connection breaks
(or we get disconnected from the AP, yadda yadda.)

The implementation is complex, but I've narrowed the configuration down
to configuring the IP addresses (v4 only), ports, and the data related
parameters like the interval etc.

I have two questions:
 1) I'm currently making userspace configure the destination/gateway MAC
    address. I could look up the route at configuration time, but it
    might have changed by the time we suspend and use it. At suspend
    time, I can no longer look up the route since that might require ARP
    queries. Does that seem reasonable, or is there a trick I could use?

 2) I'm making userspace configure the source port, and while some
    special cases might want this it seems like normally the kernel
    should pick an unused port. Does it seem acceptable to create a
    socket at configuration time, use inet_csk_get_port() to get an
    unused port and hang on to it until the configuration is removed
    again some time later (after suspend/resume)?

Thanks,
johannes