Historic archive of defunct list cerowrt-users@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: cerowrt-users <cerowrt-users@lists.bufferbloat.net>
Subject: [Cerowrt-users] 6in4 links
Date: Sun, 09 Dec 2012 21:04:44 -0500	[thread overview]
Message-ID: <3147.1355105084@obiwan.sandelman.ca> (raw)


I have a few 6in4 static tunnels on my border machine at home.
This is mostly to avoid stupid non-native v6 paths that do not
follow v4 paths across town.  (I have native v6 at home, but not at
work, go figure...)

I create a 6in4 interface, and added the /48 route across it.

(I happened to have numbered my point to interface with 2002: addresses.
On *BSD, you don't need to create a tunnel interface, you can just use
route add to a 2002: address to make things work if you have stf0
configured... this fails on Linux for reasons I understand, but don't
know how to fix)

The problem is that the interface that is created is a /128, and it's
the ::2, but since it is a /128, the ::1 isn't "On-network", so the
static route fails.

I tried without a target IP address, so that it would be a device route,
but that didn't help either.  I wound up hacking this in the shell, but
that likely won't stick.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 






             reply	other threads:[~2012-12-10  2:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10  2:04 Michael Richardson [this message]
2012-12-10  8:20 ` Dave Taht
2012-12-10  8:45 ` Phil Pennock
2012-12-10  8:47   ` Dave Taht
2012-12-10  9:01     ` Phil Pennock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3147.1355105084@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=cerowrt-users@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox