From: Robert White <rwhite@pobox.com>
To: Nick Howitt <nick@howitts.co.uk>, netfilter@vger.kernel.org
Subject: Re: Problem with ipset and --in-interface
Date: Mon, 27 Mar 2017 19:18:19 +0000 [thread overview]
Message-ID: <e562eecf-bca8-4e35-ec40-4b6d00d03fdd@pobox.com> (raw)
In-Reply-To: <58a5ce32-1340-0d3f-666a-fc54519cf448@howitts.co.uk>
On 03/27/17 18:53, Nick Howitt wrote:
> OK I feel a prat but you've pointed out the error. "s" and not "S". I
> could not see the wood from the trees.
It happens to the best of us. I aborted an install the other day because
I was looking at the wrong end of an asymmetric cable. Same shell but
different number of pins. /sigh.
prev parent reply other threads:[~2017-03-27 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 8:06 Problem with ipset and --in-interface Nick Howitt
2017-03-27 18:29 ` Robert White
2017-03-27 18:53 ` Nick Howitt
2017-03-27 19:18 ` Robert White [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e562eecf-bca8-4e35-ec40-4b6d00d03fdd@pobox.com \
--to=rwhite@pobox.com \
--cc=netfilter@vger.kernel.org \
--cc=nick@howitts.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.