Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #210058

Re: IPv4 v IPv6

From Richard Hector <richard@walnut.gen.nz>
Newsgroups linux.debian.user
Subject Re: IPv4 v IPv6
Date 2019-06-18 18:20 +0200
Message-ID <yaoZY-6YN-9@gated-at.bofh.it> (permalink)
References (3 earlier) <ya1TH-1el-1@gated-at.bofh.it> <yaj4d-3aX-3@gated-at.bofh.it> <yajGV-3D7-1@gated-at.bofh.it> <yakMG-4g3-3@gated-at.bofh.it> <yan7P-5PN-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On 19/06/19 2:11 AM, Reco wrote:
> 	Hi.
> 
> On Tue, Jun 18, 2019 at 11:47:08PM +1200, Richard Hector wrote:
>> On 18/06/19 10:32 PM, Reco wrote:

>>
>> Custom routes? When routing between 2 networks using the same range,
>> either with a VPN or some kind of direct connection? It's going to need
>> some evil double NAT sorcery, especially if the same actual addresses
>> are in use on both.
> 
> As long as:
> 
> a) It's L3 VPN, so ARP is not a concern.
> b) There are no duplicate IPs on both sites combined.
> 
> The problem can be 'solved' by announcing specific IP routes to each and
> every host on both sites. Yes, it's gross.

Eww. And people who have chosen 'obvious' blocks (like 192.168.1.0/24)
are probably going to start numbering at the bottom, too. So duplicates
are almost inevitable.

I think we agree here.

> 
>>>> There are online random ULA generators - but I'm not convinced one of
>>>> them didn't give me the same block twice, or whether it was my own error.
>>>
>>> Never used one. IPv6 /8 block consists of 2^56 unique /64 subnets.
>>> Surely it's possible to choose several unique /64 subnets by using, say,
>>> ipv6calc.
>>
>> Yes, but there is a recommendation to use random ones, and even a
>> suggestion of how to do it, in RFC 4193.
> 
> But this RFC's "random" cannot mean "I start each day with selecting
> new, custom /64 IPv6 ULA prefix for my site". ipv6calc fills this
> nicely, try it some day.

Every day? Of course not. Just when you set up a new network.

I made the mistake of doing it for every subnet, which is unnecessary; I
should have generated one /48 and split that up manually - and probably
simplified my (static) routing.

I should get round to renumbering one day ... though I now have a real
/48 from one of my VPSs to use for some of it.

Richard

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

IPv4 v IPv6 mick crane <mick.crane@gmail.com> - 2019-06-17 11:10 +0200
  Re: IPv4 v IPv6 <tomas@tuxteam.de> - 2019-06-17 11:20 +0200
    Re: IPv4 v IPv6 Aidan Gauland <aidalgol@fastmail.net> - 2019-06-17 12:30 +0200
      Re: IPv4 v IPv6 Rob van der Putten <rob@sput.nl> - 2019-06-18 09:30 +0200
  Re: IPv4 v IPv6 Jonathan Dowland <jmtd@debian.org> - 2019-06-17 12:10 +0200
    Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-17 16:40 +0200
      Re: IPv4 v IPv6 Dan Ritter <dsr@randomstring.org> - 2019-06-17 17:00 +0200
        Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-17 18:30 +0200
        Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-17 19:00 +0200
          Re: IPv4 v IPv6 Greg Wooledge <wooledg@eeg.ccf.org> - 2019-06-17 19:10 +0200
            Re: SOLVED was IPv4 v IPv6 discussion that went off the rails. Gene Heskett <gheskett@shentel.net> - 2019-06-18 02:10 +0200
          Re: IPv4 v IPv6 Dan Ritter <dsr@randomstring.org> - 2019-06-17 19:10 +0200
            Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-17 19:40 +0200
              Re: IPv4 v IPv6 Dan Ritter <dsr@randomstring.org> - 2019-06-17 20:00 +0200
            Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-17 20:00 +0200
            Re: IPv4 v IPv6 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-18 14:50 +0200
              Re: IPv4 v IPv6 Greg Wooledge <wooledg@eeg.ccf.org> - 2019-06-18 14:50 +0200
                Re: IPv4 v IPv6 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-18 15:10 +0200
          Re: IPv4 v IPv6 Dennis Wicks <wix@mgssub.com> - 2019-06-27 22:40 +0200
            Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-27 23:30 +0200
        Re: IPv4 v IPv6 John Hasler <jhasler@newsguy.com> - 2019-06-17 20:30 +0200
          Re: IPv4 v IPv6 Dan Ritter <dsr@randomstring.org> - 2019-06-17 22:10 +0200
            Re: IPv4 v IPv6 Robin Hammond <rdhdroid@gmail.com> - 2019-06-17 22:20 +0200
              Re: IPv4 v IPv6 Andy Smith <andy@strugglers.net> - 2019-06-18 00:50 +0200
              Re: IPv4 v IPv6 John Hasler <jhasler@newsguy.com> - 2019-06-18 04:10 +0200
          Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-18 02:20 +0200
      Re: IPv4 v IPv6 Reco <recoverym4n@enotuniq.net> - 2019-06-17 17:40 +0200
        Re: IPv4 v IPv6 Richard Hector <richard@walnut.gen.nz> - 2019-06-18 12:00 +0200
          Re: IPv4 v IPv6 Reco <recoverym4n@enotuniq.net> - 2019-06-18 12:40 +0200
            Re: IPv4 v IPv6 Richard Hector <richard@walnut.gen.nz> - 2019-06-18 13:50 +0200
              Re: IPv4 v IPv6 Reco <recoverym4n@enotuniq.net> - 2019-06-18 16:20 +0200
                Re: IPv4 v IPv6 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-18 16:50 +0200
                Re: IPv4 v IPv6 Reco <recoverym4n@enotuniq.net> - 2019-06-18 18:20 +0200
                Re: IPv4 v IPv6 Linux Dave <mckisicd@gmail.com> - 2019-06-20 20:40 +0200
                Re: IPv4 v IPv6 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-20 20:40 +0200
                Re: IPv4 v IPv6 Erwan David <erwan@rail.eu.org> - 2019-06-20 20:50 +0200
                Re: IPv4 v IPv6 Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-06-20 21:00 +0200
                Re: IPv4 v IPv6 Reco <recoverym4n@enotuniq.net> - 2019-06-20 21:10 +0200
                Re: IPv4 v IPv6 Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-06-18 17:40 +0200
                Re: IPv4 v IPv6 Reco <recoverym4n@enotuniq.net> - 2019-06-18 18:30 +0200
                Re: IPv4 v IPv6 Richard Hector <richard@walnut.gen.nz> - 2019-06-18 18:20 +0200
                Re: IPv4 v IPv6 Reco <recoverym4n@enotuniq.net> - 2019-06-18 18:30 +0200
      Re: IPv4 v IPv6 David Wright <deblis@lionunicorn.co.uk> - 2019-06-18 18:20 +0200
        Re: IPv4 v IPv6 Richard Hector <richard@walnut.gen.nz> - 2019-06-18 18:30 +0200
          Re: IPv4 v IPv6 Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-06-18 18:40 +0200
          Re: IPv4 v IPv6 David Wright <deblis@lionunicorn.co.uk> - 2019-06-22 05:10 +0200
            Re: IPv4 v IPv6 Richard Hector <richard@walnut.gen.nz> - 2019-06-22 10:50 +0200
              Re: IPv4 v IPv6 David Wright <deblis@lionunicorn.co.uk> - 2019-06-24 20:20 +0200
            Re: IPv4 v IPv6 Andy Smith <andy@strugglers.net> - 2019-06-22 21:40 +0200
              Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-22 22:50 +0200
                Re: IPv4 v IPv6 John Hasler <jhasler@newsguy.com> - 2019-06-22 23:40 +0200
                Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-23 02:30 +0200
                Re: IPv4 v IPv6 John Hasler <jhasler@newsguy.com> - 2019-06-23 05:00 +0200
                Re: IPv4 v IPv6 Gene Heskett <gheskett@shentel.net> - 2019-06-23 08:30 +0200
                Re: IPv4 v IPv6 Pascal Hambourg <pascal@plouf.fr.eu.org> - 2019-06-23 11:20 +0200
              Re: IPv4 v IPv6 Andy Smith <andy@strugglers.net> - 2019-06-26 20:40 +0200
                Re: IPv4 v IPv6 Michael Stone <mstone@debian.org> - 2019-06-26 21:00 +0200
    Re: IPv4 v IPv6 Richard Hector <richard@walnut.gen.nz> - 2019-06-18 11:50 +0200
      Re: IPv4 v IPv6 Jonathan Dowland <jmtd@debian.org> - 2019-06-21 17:30 +0200
  Re: IPv4 v IPv6 andreimpopescu@gmail.com - 2019-07-02 11:10 +0200

csiph-web