OpenBSD Journal

IPv6 Test Lab Part 2

Contributed by dwc on from the backman-to-the-future dept.

Will Backman writes:

"In Part 1, I described the creation of a small internal IPv6 network...Now that we had the basics figured out, it was time to connect to the IPv6 Internet..."

Read on for Will's Full Story

(Comments are closed)


Comments
  1. By David Chisnall (82.7.199.50) on

    Can someone explain why 6to4 is disabled in the OpenBSD version of Kame? I've heard that it is a security hole, but the same arguments advanced to explain this seem to apply for accepting any IP packet that has come through a router (i.e. you have to trust the router that it is no allowing people on the other side to spoof IPs). This would make IPv6 deployment a lot easier.

    Comments
    1. By Anonymous Coward (128.171.90.200) on

      > Can someone explain why 6to4 is disabled in the OpenBSD version of Kame? I've heard that it is a security hole, but the same arguments advanced to explain this seem to apply for accepting any IP packet that has come through a router (i.e. you have to trust the router that it is no allowing people on the other side to spoof IPs). This would make IPv6 deployment a lot easier.

      Have a look at RFC 3964

  2. By Anonymous Coward (71.182.176.225) on

    Is it possible to have the OpenBSD box intelligently route traffic through the tunnel or through the link normally depending on whether or not the resulting DNS lookup is an IPv6 or IPv4 address?

    Such as if I go to http://www.sixxs.net/misc/coolstuff/ I connect via the tunnel but if I go to say google.com the openbsd box see it's an IPv4 address and NATs the traffic using 6to4 (I think?) so I don't have to use http://ipv6gate.sixxs.net/?

    Comments
    1. By Anonymous Coward (137.78.212.149) on

      > Is it possible to have the OpenBSD box intelligently route traffic through the tunnel or through the link normally depending on whether or not the resulting DNS lookup is an IPv6 or IPv4 address?

      The router would have nothing to do with this, in this guys setup he did ipv6 ONLY, if you do it normally the client can resolve both ipv4 and ipv6 and connect to which ever works, the router shouldn't have to do anything.

  3. By Venture37 (venture37) venture37<A>hotmail.com on www.geeklan.co.uk

    Configure the WAN interface as usual, create a tunnel, assign a LAN IPv6 gateway address and site local DNS address, allow IPv6 forwarding, enable the router advertising daemon, enable the BIND named, and presto: you can visit seven web sites. :)



    hehehe, good one! :)

    Comments
    1. By Coward (198.62.124.245) on

      > Configure the WAN interface as usual, create a tunnel, assign a LAN IPv6 gateway address and site local DNS address, allow IPv6 forwarding, enable the router advertising daemon, enable the BIND named, and presto: you can visit seven web sites. :)
      >
      >
      >
      > hehehe, good one! :)

      And free porn! http://www.ipv6experiment.com/

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]