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


Groups > linux.debian.user > #210154

Re: IPv4 v IPv6

From Pascal Hambourg <pascal@plouf.fr.eu.org>
Newsgroups linux.debian.user
Subject Re: IPv4 v IPv6
Date 2019-06-20 20:40 +0200
Message-ID <yba8x-20Q-5@gated-at.bofh.it> (permalink)
References (5 earlier) <yajGV-3D7-1@gated-at.bofh.it> <yakMG-4g3-3@gated-at.bofh.it> <yan7P-5PN-1@gated-at.bofh.it> <yanAR-5Zx-3@gated-at.bofh.it> <yaoZY-6YN-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Le 18/06/2019 à 18:19, Reco a écrit :
> On Tue, Jun 18, 2019 at 04:45:59PM +0200, Pascal Hambourg wrote:
>> Le 18/06/2019 à 16:11, Reco a écrit :
>>>
>>> The problem can be 'solved' by announcing specific IP routes to each and
>>> every host on both sites. Yes, it's gross.
>>
>> Not all hosts accept route announcements (using which protocol ?).
> 
> DHCP seems to be the most straightforward way of doing this.

DHCP provides two options to advertise static routes.

The old "static-routes" option assumes classfull routing and does not 
advertise a netmask or prefix length. It is derived by the client from 
the address class :
class A -> /8
class B -> /16
class C -> /24
If the actual netmask does not match the classful one, the option is 
unusable.

The newer "classless-static-routes" option advertises the netmask (or 
prefix length, not sure), but is not supported by all DHCP clients and 
servers. IIRC, the ISC DHCP client and server do not natively support 
it, you have to define it as a custom option.

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