deep darc » Teredo for MacOS X » Comments http://www.deepdarc.com/2007/02/21/miredo-osx/ deep and darc stuff Sun, 10 Aug 2008 14:29:28 +0000 http://backend.userland.com/rss092 en RE: Teredo for MacOS X vincent http://www.deepdarc.com/2007/02/21/miredo-osx/#comment-825 Is there a plan to release an OS X package based on a more recent version of miredo any time soon? If I understand things correctly, your package is built against 1.0.6.

]]> Sun, 10 Aug 2008 14:29:28 +0000 RE: Teredo for MacOS X vincent http://www.deepdarc.com/2007/02/21/miredo-osx/#comment-801 I've been playing with teredo (as supplied by you) for quite some time now. And I've been very happy with it. Keep up the good work.

]]> Sun, 11 May 2008 21:35:02 +0000 RE: Teredo for MacOS X darco http://www.deepdarc.com/2007/02/21/miredo-osx/#comment-779 @Greg: The default behavior is that miredo is disabled if a globally routable IPv6 address has already been assigned to at least one interface. So, yes there is hope. :)

However... There is a bug if you put the machine to sleep with a teredo address and it wakes up on a network with native IPv6. In this case, miredo will unfortunately clobber the default IPv6 route when it tries to disable itself. >_<

]]> Fri, 22 Feb 2008 22:51:16 +0000 RE: Teredo for MacOS X Greg Harewood http://www.deepdarc.com/2007/02/21/miredo-osx/#comment-778 I'm hoping that, by default, it only runs when a native LAN IPv6 address is not supplied. Ideally, it would go like this....

  • Native address - use
  • No native, check for legal address, try 6to4.
  • RFC1918? Activate miredo.

    • Any hope?

    ]]>     Fri, 22 Feb 2008 21:33:13 +0000     RE: Teredo for MacOS X Andre http://www.deepdarc.com/2007/02/21/miredo-osx/#comment-712 Between the work done by you here and 'Rémi Denis-Courmont' on Miredo, I think we almost have something that we can let loose on the general public. When you move beyond prerelease mode, I think a discussion forum would be handy, as well as listing on VersionTracker.

    It should be noted that Teredo was created because of NATs. Most 4to6 solutions are designed to work in environments where NAT does not exist, and therefore Microsoft came up with a solution knowing many people are stuck behind NATs these days.

    Keep up the good work!!

    ]]>     Tue, 22 May 2007 13:47:40 +0000