From: Die Optimisten <inform@die-optimisten.net>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: Netfilter Users Mailing list <netfilter@vger.kernel.org>
Subject: Re: iptables Qu: how to specify !dst:port
Date: Fri, 12 Jul 2013 18:09:24 +0200 [thread overview]
Message-ID: <51E02A34.2080101@die-optimisten.net> (raw)
In-Reply-To: <CAOkSjBhV9YE=hrX4+OcF++F_dDvtRZVd94sSP=4m-rynPZJ6gQ@mail.gmail.com>
On 2013-07-12 14:50, Arturo Borrero Gonzalez wrote:
> 2013/7/12 Die Optimisten <inform@die-optimisten.net>:
>
>> Hi!
>> Thanks for your fast answer!!
>>
>> How can I write -t nat
>> [all except these 2:] (! -d 127.0.0.1 -and ! -d 192.168.0.0/16) ?
>>
>>
> I would do it with ipset(8).
>
> --
> Arturo Borrero González
>
Hello
Aha, seems it is not possible with iptables (alone)?
- Is it also possible to check against 1000 IPs with ipset (performance) ?
How to check against 1000 MACs (no mactables?!, only aprtables)
Another question (yes, I know this is a iptables-list, but perhaps
interesting to all):
I've heard it is possible to have a tunnel, which doesn't disconnect the
inside running (tcp-) sessions, if connection is lost.
How can this be done?
Is there a max (inner) timeout, within that you have to reconnect the
outer tunnel? How can the timeout be changed?
Or is there a possibility to reopen the tunnel next day without breaking
the inner connections?That would be fine!
Sg. existing already?
Idea: a tool that "simulates" the other end and takes over the
connection, when other side doesn't respond (just ACKs, without data?)
Please also reply to me directly inform@die-optimisten DOT net
thanks again!
Andrew
prev parent reply other threads:[~2013-07-12 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 12:00 iptables Qu: how to specify !dst:port Die Optimisten
2013-07-12 12:10 ` Arturo Borrero Gonzalez
2013-07-12 12:31 ` Die Optimisten
2013-07-12 12:50 ` Arturo Borrero Gonzalez
2013-07-12 13:00 ` Pascal Hambourg
2013-07-12 16:09 ` Die Optimisten [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=51E02A34.2080101@die-optimisten.net \
--to=inform@die-optimisten.net \
--cc=arturo.borrero.glez@gmail.com \
--cc=netfilter@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox