netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Clark <sclark46@earthlink.net>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Jan Engelhardt <jengelh@medozas.de>,
	David Miller <davem@davemloft.net>,
	netfilter-devel@vger.kernel.org
Subject: Re: rules matching ipv6 prefix addrs
Date: Thu, 04 Nov 2010 08:07:28 -0400	[thread overview]
Message-ID: <4CD2A200.7080204@earthlink.net> (raw)
In-Reply-To: <4CD29913.2040903@plouf.fr.eu.org>

On 11/04/2010 07:29 AM, Pascal Hambourg wrote:
> Stephen Clark a écrit :
>    
>> Won't this break existing tcp connections if all of a sudden you get a
>> new address?
>>      
> Yes, but the same happened already with a variable IPv4 address, so this
> is not a new problem. As I understand HPA, the new problem is that with
> IPv6 the whole prefix can change.
>
>    
Yes but when it happens there some kind of well defined event - like 
dhcp giving you a new address
and can trigger scripts that do the necessary updating of whatever needs 
to be updated. Also
I have a dynamic address that might change once or twice a year since I 
leave my system on 24/7.
This sounds like all of a sudden the ISP gives you a new prefix and "RA" 
(router advertisements ?)
let you know that you have a new address.

-- 

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)



--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-11-04 12:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 20:52 rules matching ipv6 prefix addrs David Miller
2010-11-02 21:24 ` Maciej Żenczykowski
2010-11-03  7:37 ` Patrick McHardy
2010-11-03  9:29 ` Pascal Hambourg
2010-11-03 10:51   ` Jan Engelhardt
2010-11-03 12:19   ` David Miller
2010-11-03 12:32     ` Jan Engelhardt
2010-11-03 21:55       ` David Miller
2010-11-03 22:36         ` H. Peter Anvin
2010-11-03 22:52           ` Jan Engelhardt
2010-11-04  2:12             ` H. Peter Anvin
2010-11-04  4:14               ` Patrick McHardy
2010-11-04  8:58               ` Jan Engelhardt
2010-11-04 11:36                 ` H. Peter Anvin
2010-11-04 11:53                   ` Jan Engelhardt
2010-11-04 14:41                     ` H. Peter Anvin
2010-11-04 20:02                       ` Pascal Hambourg
2010-11-04 12:07                   ` Pascal Hambourg
2010-11-04 11:08               ` Stephen Clark
2010-11-04 11:29                 ` Pascal Hambourg
2010-11-04 12:07                   ` Stephen Clark [this message]
2010-11-04 12:19                     ` Pascal Hambourg
2010-11-04 13:34                 ` Jozsef Kadlecsik
2010-11-04 14:41                 ` H. Peter Anvin
2010-11-04 17:35                   ` Jeff Haran
2010-11-04 18:45                     ` H. Peter Anvin
2010-11-04 19:24                   ` Jan Engelhardt
2010-11-04 19:26                     ` H. Peter Anvin
2010-11-04 11:55               ` Pascal Hambourg
2010-11-04 14:42                 ` H. Peter Anvin
2010-11-04 20:00                   ` Pascal Hambourg
2010-11-03 12:56     ` Pascal Hambourg

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=4CD2A200.7080204@earthlink.net \
    --to=sclark46@earthlink.net \
    --cc=davem@davemloft.net \
    --cc=hpa@zytor.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pascal.mail@plouf.fr.eu.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;
as well as URLs for NNTP newsgroup(s).