[zebra 22832] Re: Miredo together with Zebra ??

On Sat, 2006-04-08 at 13:49 +0700, Dwiagusta Taiiiii wrote:
> hi all ,,

> thanks for yesterday ,, all PC's is connected ,, but i had some
> trouble again ;) ,, i working on IPv6 tunnelling using teredo ( miredo
> exactly coz i'm using linux ) ,, the topology is the same with
> yesterday ( i put it in the attachment ) ,,
 
> i'm really confuse to run the miredo on linux ,, what should i use for
> my topology ,, just a miredo-server ,, or i have to add a
> miredo-relay ??? i have tried to use miredo-server in both of the
> router & miredo-client in pc1 and pc2 ,, it's not working ,, i have
> tried to use miredo-server in router 1 and miredo-relay in router 2 ,,
> and miredo-client in both of the PC ,, and none of it working ,, i
> need some advice here ?? emm if u have some manual for using miredo ,,
> i'd be very happy if i can get it ,, i only have manual from miredo's
> website ,,
 
> i'm almost forget ,, emm i have run the zebra ,, and miredo-server &
> miredo-relay in all of the Router-PC ,, and miredo-client in PC1 and
> PC2 ,, but why the tunnellling isn't working ?? both of the PC cannot
> ping each other ( using ipv6 ) but if i'm using ping ( using ipv4 )
> it's working ,, and also ,,why i cannot run miredo-server in my
> router-PC ??   

	You don't need Zebra to run Teredo/Miredo unless you are going to
advertise your Teredo /64 prefix to the outside world over BGP, which
you probably DON'T want to do, so this is rather off topic in this list.
Be that as it may...  I also didn't see a single solitary Teredo address
in your diagram (which would be a 2001:0:... address for the official
Teredo prefix - the old 6bone addresses are going away, real damn soon
now).

	You need a server on IPv4 global unicast addresses somewhere.  You
actually need two (preferably consecutive) IPv4 addresses for the server
for the NAT qualification logic (similar to STUN) to work (if you are
dealing purely Linux, you don't need them to be consecutive - Windows,
OTOH, REQUIRES it).  I currently run one on 130.205.32.4 / 130.205.32.5
(2001:0:82cd:2004::/64).  The server basically mediates the variation of
the "STUN" (Simple Transition of UDP over NAT) like protocol used by
Teredo for transiting NAT and mediating communications between Teredo
clients.  The server, itself, carries no "production" traffic, only
coordination traffic like "bubbles".  You have to have it in order for
the two clients to find each other and figure out how to talk to each
other behind their respective NAT gateways.  It will assign addresses to
the "teredo" interface on each client on Linux (ifconfig teredo) which
will incorporate the address of the Teredo server.

	The Teredo Relay is used as a Teredo agent (basically a client without
an actual Teredo address) for communicating with the non-Teredo IPv6
network.  When a relay receives a packet from a non-Teredo address with
a destination address on a Teredo prefix, it acts as a Teredo
gateway/client and routes it to the Teredo destination accordingly.
That needs to be on a system that is advertising your teredo prefix,
2001:0:82cd:2004::/64 in my case, and handles routing from the global v6
internet to the Teredo clients.  If you are not routing to/from other
prefixes, you don't need a relay.  I have a relay, but it's not
advertised and only acts to relay from my internal global unicast
addresses to my Teredo clients and sits ON the default route out of my
IPv6 networks, so it doesn't need to be advertised in the routing
protocols.  You probably DON'T want to advertise a Teredo prefix until
you really REALLY know what you are doing with both BGP and Teredo (I'm
not there, yet).

	Sooo...  To answer your question.  In the simplest form, you need one
Teredo server, on a global IPv4 addresses with multiple Teredo clients,
optionally behind NATs or stateful firewalls.  Configure your clients to
point to that one Teredo server and they SHOULD be able to qualify their
NATs, configure their addresses and then communicate with each other.
Add a relay along your IPv6 default route to communicate with any
systems YOU have on a global prefix.  Worry about BGP AFTER you have all
that working.

> sincerely yours , 

> dwiagusta   
> 
> ______________________________________________________________________
> Apakah Anda Yahoo!?
> Kunjungi halaman depan Yahoo! Indonesia yang baru!

	Regards,
	Mike
-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  [email protected]
   /\/\|=mhw=|\/\/          | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9          | An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471        | possible worlds.  A pessimist is sure of it!

_______________________________________________
Zebra mailing list
[email protected]
http://ml.zebra.org/mailman/listinfo/zebra

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iQCVAwUAREg2AeHJS0bfHdRxAQKw2AQAnU03DRZB9fE8vpYqJyB5DvxUZykwH2xu
X4hZUrfnpSqyWhqax44LvSnG2WAX1xuMjyUVCo6WFmZIgOfg1yykscSgLidSL108
+DEvHrOLdYwKrU4Bjt+c6yUXSv4xgbO7V/OsUBCAziGrv4//Fa6e+PXTt1ka4/lM
dN3Rhhnh7OM=
=EdhY
-----END PGP SIGNATURE-----