Differences between version 59 and revision by previous author of 6to4.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 59 | Last edited on Saturday, April 5, 2008 4:58:29 pm | by JohnMcPherson | Revert |
| Older page: | version 58 | Last edited on Friday, April 4, 2008 7:24:59 am | by MattBrown | Revert |
@@ -154,14 +154,12 @@
First you need to configure radvd. Zebra is not recommended as it cannot handle dynamic 6to4 address advertising (as radvd can) and also has a bug where it will write out a configuration to it's file that is invalid and then die when it tries to reload it again.
Your config file should look something like:
-
<pre>
-
interface eth0
{
- !
AdvSendAdvert on;
+ ~
AdvSendAdvert on;
prefix fec0::/64
{
};
@@ -177,13 +175,13 @@
{
Base6to4Interface lo:1;
};
};
-
</pre>
+
You can omit any of the prefix stanza's you don't like.
-In the config above the timers have been turned down in anticipation that you are advertising a 6to4 address generated from a dynamic IP on ppp0. Note that if you do this you __must__ turn down the retransmit time on the unsolicited announcements. In particular ensure that ''!
MaxRtrAdvInterval'' and ''!
AdvPreferredLifetime'' are less than ''!
AdvValidLifetime''. If you don't understand why this is important then you can just go with what is shown above.
+In the config above the timers have been turned down in anticipation that you are advertising a 6to4 address generated from a dynamic IP on ppp0. Note that if you do this you __must__ turn down the retransmit time on the unsolicited announcements. In particular ensure that ''~
MaxRtrAdvInterval'' and ''~
AdvPreferredLifetime'' are less than ''~
AdvValidLifetime''. If you don't understand why this is important then you can just go with what is shown above.
You also need at least one SIT tunnel with a "remote any local any". It doesn't need an ipv6 (or ipv4) address associated with it. This is used for transpanret deencapsulation of IPv6 packets that are forwarded to your internal network.
If you've done all this, it should just work. In practise, it requires some tinkering.
