1. 13 May, 2014 1 commit
    • Leigh Stoller's avatar
      Add IPV6 changes, contributed by Brecht and lightly modified by me. · 7de150c4
      Leigh Stoller authored
      To define, in the defs file:
      
      	IPV6_ENABLED=1
      	IPV6_SUBNET_PREFIX="2011:1948:0417:0004"
      
      A /64 network is always assumed, don't do anything else. We generate
      appropriate foward and reverse entries in the zone files, but
      otherwise rely on the on the upstream router to provide the prefix
      when asked for it by nodes when they wish to configure an IPV6
      interface.
      
      Important caveats:
      
      1. The infrastructure is ipv4 only. We do not dupport dual stack or
         ipv6 only on any infrastructure.
      
      2. We do not support ipv6 only on the control plane; ipv4 or dual stack.
      7de150c4
  2. 10 Dec, 2012 1 commit
  3. 22 Dec, 2010 1 commit
  4. 16 Jul, 2007 1 commit
  5. 29 Nov, 2006 1 commit
    • Leigh Stoller's avatar
      A bunch of changes attempting to deal with testbed networks that are · baab5fc2
      Leigh Stoller authored
      bigger then a /24 network, as in Utah's network. Mostly the changes
      are how we deal with the reverse zone file creation and what gets
      stuck into the named.conf file. Prior to this commit, we assumed a
      single /24 network, cause thats how it looks in an elabinelab
      experiment (which is where its critical to have the named config files
      generated automatically).
      
      But with the changes to support a single control network, the named
      setup inside elabinelab is bigger then a /24 and the reverse files
      have to be created and populated correctly.
      baab5fc2
  6. 07 Jan, 2005 1 commit
    • Leigh Stoller's avatar
      Named setup gets a serious collagen injection ... As per Mike/Rob · cff2421e
      Leigh Stoller authored
      request, beef up named setup so that sites like DETER are handled
      properly. I have added 4 new defs variables:
      
          #
          # If your boss/ops nodes are multihomed (and typically, one of the
          # networks is a public routable network, and the other is an internal
          # unroutable network), then define the the external addresses here (and
          # the internal addresses above).
          #
          EXTERNAL_BOSSNODE_IP=$BOSSNODE_IP
          EXTERNAL_USERNODE_IP=$USERNODE_IP
      
          #
          # As above, if you have internal and external networks, define the
          # external network here, and the internal network above.
          #
          EXTERNAL_TESTBED_NETWORK=$TESTBED_NETWORK
          EXTERNAL_TESTBED_NETMASK=$TESTBED_NETMASK
      
      which if not set default to the internal values. When the external and
      internal networks are different, generate two sets of reverse zone
      files and two forward files (one internal and one external).
      cff2421e
  7. 21 Dec, 2004 1 commit
  8. 07 Oct, 2004 1 commit