On Thu, Sep 1, 2016 at 4:47 PM, Kevin Cernekee <cernekee@xxxxxxxxxxxx> wrote: > The patch that I sent out last night is able to handle scenarios in > which the event occurs shortly after the subscription is established. > But in my testing I am noticing two other problems: > > 1) Approximately two minutes after the subscription is set up, the > expectation abruptly disappears. This even happens if I set the > timeout to 3600; it shows up in `conntrack -L expect` until the time > column drops to ~3480, then it is gone. This may be caused by the > master conntrack expiring. Is there a way to set up the expectation > so that it persists for the entire timeout period? > > 2) The timeout is not extended when there is activity on the > expectation. It would be good if it was extended any time there is > new activity, in order to support long-lived subscriptions. Friendly ping... Do you think I'm on the right track with this approach, and if so, what is the best way to establish long-lived expectations for UPnP? http://marc.info/?l=netfilter-devel&m=147270416910580&w=2 Thanks. -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
