Re: ipv6 host part

From: B ($B?_at_L@C#:H(B)
Date: 04/29/05

  • Next message: Jiří Adámek [net.consulting]: "L2TP/IPSec + Racoon" 
    Date: Fri, 29 Apr 2005 18:09:29 +0900
To: Neo-Vortex <root@Neo-Vortex.net>

    >>>>> On Fri, 29 Apr 2005 18:32:48 +1000 (EST),
    >>>>> Neo-Vortex <root@Neo-Vortex.net> said:

    >> >> - assuming the prefix is "P/64", do the followings:
    >> >> # ifconfig IFNAME inet6 P::1 prefixlen 64 alias autoconf
    >> >> # ifconfig IFNAME inet6 P::2 prefixlen 64 alias autoconf
    >> >> # ifconfig IFNAME inet6 P::3 prefixlen 64 alias autoconf
    >>
    >> > IIRC, the first address within the prefix should have a prefixlen of 64,
    >> > (providing the prefixlen is actually 64) but others on the same prefix
    >> > should have 128.
    >>
    >> I don't remember any such restriction. What is your source (e.g.,
    >> RFC) of this information?

    > alias Establish an additional network address for this interface. This
    > is sometimes useful when changing network numbers, and one wishes
    > to accept packets addressed to the old interface. If the address
    > is on the same subnet as the first network address for this
    > interface, a non-conflicting netmask must be given. Usually
    > 0xffffffff is most appropriate.

    > That is for IPv4 taken from ifconfig(8), one would assume for IPv6 it is
    > the same and i use it like that without issues (although i have not tried
    > it the other way)

    The semantics is totally different in IPv6, at least protocol-wise.
    IPv6 allows an interface to have multiple addresses with the same
    prefix (and length). RFC3041 (temporary addresses for privacy) is an
    example.

    You could also assign addresses whose upper 64bits are the same with
    the prefix length of 128 if you want, but it's not a requirement.

    (Perhaps the man page needs a revise, but it's a separate issue.)

                                            JINMEI, Tatuya
                                            Communication Platform Lab.
                                            Corporate R&D Center, Toshiba Corp.
                                            jinmei@isl.rdc.toshiba.co.jp
    _______________________________________________
    freebsd-net@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-net
    To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"

  • Next message: Jiří Adámek [net.consulting]: "L2TP/IPSec + Racoon"

    Relevant Pages

    • RE: Understanding multiple IPv6 interfaces under 8.0 (fwd)
      ... this issue may be due to a bit of regression in the IPv6 prefix management ... When ND6 NS arrives for bce1, due to the interface mismatch of the prefix ... You can try specifying the route manually ...
      (freebsd-net)
    • Re: Secure vs Insecure IP6 address
      ... Also, I don't think "domain" is actually a proper term in the IPv6 context, Could you be referring to how IPv6 has an address space large enough such that every person on Earth currently could have their own /48 _prefix_ so as to assign individual addresses to each of their devices as they see fit? ... by using the MAC address of the network card as well. ... Number 1 requires physical access to the network to install the rogue router, and burglar alarms aside, that is more likely to be noticed the smaller and smaller the network is. ...
      (comp.unix.bsd.openbsd.misc)
    • RE: Understanding multiple IPv6 interfaces under 8.0 (fwd)
      ... this issue may be due to a bit of regression in the IPv6 prefix management ... When ND6 NS arrives for bce1, due to the interface mismatch of the prefix ... I was wondering about the route however I haven't figured out the trick to ...
      (freebsd-net)
    • RE: Understanding multiple IPv6 interfaces under 8.0 (fwd)
      ... this issue may be due to a bit of regression in the IPv6 prefix management ... When ND6 NS arrives for bce1, due to the interface mismatch of the prefix ... You can try specifying the route manually ...
      (freebsd-net)
    • Re: Redefinition Error with NTP-4.2.0 on OpenBSD 3.3
      ... > in config.h if it supports IPv6 and that belongs in the autoconf stuff. ... compliance with the RFC. ... (Minor changes are required in both ../include/ntp_stdlib.h and ... not send unsolicited bulk e-mail or unsolicited commercial e-mail to ...
      (comp.unix.bsd.openbsd.misc)