
	Where results make sense

Topic: 6to4

Related Topics

Snort

Bodhran

SPECT

Ed

Plagiarism

February 28 Incident

Sega NOMAD

Sokollu

Yanluo

NRX

The Birth of a Nation

Neeme Jarvi

Balzan

Spielberg

Nawab

In the News (Thu 26 Nov 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	6to4 - Wikipedia, the free encyclopedia
		6to4 embeds an IPv6 packet in the payload portion of an IPv4 packet with protocol type 41.
		To avoid the need for users to set this up manually, the 6to4 relay anycast address of 192.88.99.1 (which when wrapped in 6to4 with the subnet and hosts fields zero becomes 2002:c058:6301::) has been allocated for the purpose of sending packets to a relay router.
		Providers willing to provide 6to4 service to their clients or peers should advertise the anycast prefix like any other IP prefix, and route the prefix to their 6to4 relay.
	en.wikipedia.org /wiki/6to4 (923 words)

	6to4 Reverse DNS Delegation Specification
		A 6to4 client network is an isolated IPv6 network composed as a set of IPv6 hosts and a dual stack (IPv4 and IPv6) local router connected to the local IPv6 network and the external IPv4 network.
		When accessed by a 6to4 source address, the interface presented by the delegation server is a standard DNS delegation interface, allowing the client to enter the details of a number of DNS servers for the corresponding reverse domain.
		However it is noted that 6to4 is intended to be a transition mechanism useful for a limited period of time in a limited context of isolated network where other forms of tunnelled connection is not feasible.
	www.potaroo.net /drafts/draft-huston-6to4-reverse-dns-04.html (2670 words)

	RFC 3056 (rfc3056) - Connection of IPv6 Domains via IPv4 Clouds
		In the 6to4 model, this connectivity is accomplished by IPv6 routers which possess both 6to4 and native IPv6 addresses.
		The set of 6to4 routers using a given relay router obtain native IPv6 routes from the relay router using a routing protocol such as BGP4+ [RFC 2283, BGP4+].
		5.8 Coexistence with firewall, NAT or RSIP The 6to4 mechanisms appear to be unaffected by the presence of a firewall at the border router.
	www.faqs.org /rfcs/rfc3056.html (6044 words)

	[No title] (Site not responding. Last check: 2007-10-09)
		When 6to4 usage is determined to have ceased (which may be several years later), remove the 6to4 configuration.
		5.7 Coexistence with firewall, NAT or RSIP The 6to4 mechanisms appear to be unaffected by the presence of a firewall at the border router.
		In any case, any 6to4 traffic whose source or destination address embeds a V4ADDR which is not in the format of a global unicast address MUST be silently discarded by both encapsulators and decapsulators.
	www.lce.org /ipv6/draft-ietf-ngtrans-6to4-06.txt (5581 words)

	6 to 4 - Waikato Linux Users Group
		If you exclusively use 6to4 addresses, then you can use the 192.88.99.1 AnyCast address to get onto the 6bone which is probably far more efficient than using a 6bone tunnel, as the AnyCast address is likely to be far closer to you than FreeNet.
		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.
		RFC:3068 (An Anycast Prefix for 6to4 Relay Routers)
	www.wlug.org.nz /6to4 (1637 words)

	Zvon - RFC 3056 [Connection of IPv6 Domains via IPv4 Clouds] - Unicast scenarios, scaling, and transition to normal ...
		The set of 6to4 routers using a given relay router obtain native IPv6 routes from the relay router using a routing protocol such as BGP4+ [RFC2283, BGP4+].
		A 6to4 site which has no IPv6 connections to the "native" IPv6 Internet can acquire effective connectivity to the v6 Internet via a "configured tunnel" (using the terminology in [MECH]) to a cooperating router which does have IPv6 access, but which does not need to be a 6to4 router.
		The 6to4 mechanisms appear to be unaffected by the presence of a firewall at the border router.
	www.zvon.org /tmRFC/RFC3056/Output/chapter5.html (3359 words)

	RFC 3964 (rfc3964) - Security Considerations for 6to4
		The 6to4 specification outlined a few security considerations and rules but was ambiguous as to their exact requirement level.
		6to4 relays have to consider all 6to4 routers as "on-link", and 3.
		Note that all attacks may not be applicable, as the 6to4 pseudo-interface is assumed not to have a link-layer address (Section 3.8 RFC 2893 [4]).
	www.faqs.org /rfcs/rfc3964.html (8847 words)

	[No title]
		The operation of 6to4 routers requires either that the routers participate in IPv6 inter-domain routing, or that the routers be provisioned with a default route.
		The managers of the 6to4 relay routers should be able to control the sources authorized to use their resource.
		Anycast routing is known to cause operational issues: since the sending 6to4 router does not directly identify the specific 6to4 relay router to which it forwards the packets, it is hard to identify the responsible router in case of failure, in particular when the failure is transient or intermittent.
	www.ietf.org /rfc/rfc3068.txt (2595 words)

	Roxen Community: RFC 3068 An Anycast Prefix for 6to4 Relay Routers (Standards Track)
		According to [RFC3056], there are two deployment options for a 6to4 routing domain, depending on whether or not the domain is using an IPv6 exterior routing protocol.
		The 6to4 relay routers that follow the specification of this memo shall advertise the 6to4 anycast prefix, using the IGP of their IPv4 autonomous system, as if it where a connection to an external network.
		Any 6to4 relay router corresponding to this specification must include a monitoring function, to check that the 6to4 relay function is operational.
	community.roxen.com /developers/idocs/rfc/rfc3068.html (2383 words)

	Daemon News '200101' : '"6to4 IPv6 Explained, or: Flogging a Dead Horse "'
		Thanks to the 6to4 prefix and your worldwide unique IPv4 address, this address block is also unique, and it's mapped to you.
		Your private network is on the left; the uplink in this case is via a v4-connected PPP-link, and the machine on the right is the 6to4 gateway which is connected to the 6bone.
		In contrast to the "tunnel" setup, you usually can't setup packet filters to block 6to4-packets from unauthorized sources, as this is exactly how (and why) 6to4 works at all.
	ezine.daemonnews.org /200101/6to4.html (659 words)

	IPv6 transition-6to4 tunneling \| Linux Gazette
		The first operation is carried out in the source side 6to4 gateway and the second operation is carried out in the destination side 6to4 gateway.
		6to4 gateway is the heart of the 6to4 tunneling mechanism.
		In the destination side 6to4 gateway, the packet is received and checked for the destination address.
	www.linuxgazette.com /node/view/8800 (1942 words)

	Re: 6to4 question
		I would like not to have to use it if that is possible.
		> >> > >>6to4 address are something quite different from a block > >>provided through > >>a tunnel.
		For example, when communicating with my friend, who also uses > >>6to4 and has the IPv4 address 213.132.111.101, I send a packet to her > >>IPv6 address, 2002:d584:6f65::1.
	www.mail-archive.com /users@ipv6.org/msg01836.html (688 words)

	Public 6to4 relay routers
		The 6to4 specification states that the 32 bits after 2002::/16 are the IPv4 address of the gateway machine for the network in question.
		It is possible to use 6to4 with a dynamic address, but this means that your IPv6 prefix will change everytime your IPv4 address does.
		That is a machine that is set up both for 6to4 and a connection to some other address space.
	www.kfu.com /~nsayer/6to4 (884 words)

	Debian -- Debian IPv6 Project - 6 to 4 Setup Instructions (Site not responding. Last check: 2007-10-09)
		These routers advertise routes for either the whole 2002::/16 block or parts of it (for example if they are close to some IPv4 address blocks they may advertise the 6to4 equivalents).
		The 6to4 router knows this is a special packet, so then creates a IPv6 over IPv4 tunnel to your host and sends the packet.
		We'll assume you take the first ipv6 address, 2002:c000:0203::1 There is a special anycast address of 192.88.99.1 that is used for the closest 6to4 router.
	people.debian.org /~csmall/ipv6/setup624.html (401 words)

	Configuring 6to4 Connectivity with Microsoft Research IPv6
		The main requirement for using 6to4 is that you need one globally routable IPv4 address for your site.
		This example assumes that you use subnet 0 for manually configuring a 6to4 address on your 6to4 gateway machine and that you use subnet 1 for automatically configuring addresses on your ethernet.
		In this case it is establishing a default route to the 6to4 relay.
	research.microsoft.com /msripv6/docs/6to4.htm (1039 words)

	[No title]
		Savola & Patel Informational [Page 12] RFC 3964 Security Considerations for 6to4 December 2004 6to4 relays and routers are IPv4 nodes, and there is no way for any 6to4 router to confirm the identity of the IPv4 node from which it receives traffic -- whether from a legitimate 6to4 relay or some other node.
		Note that all attacks may not be applicable, as the 6to4 Savola & Patel Informational [Page 13] RFC 3964 Security Considerations for 6to4 December 2004 pseudo-interface is assumed not to have a link-layer address (Section 3.8 RFC 2893 [4]).
		Savola & Patel Informational [Page 30] RFC 3964 Security Considerations for 6to4 December 2004 Note that, in general, the 6to4 router or relay does not know whether it is acting as a router or relay.
	www.mit.edu /afs/athena/reference/rfc/rfc3964.txt (8876 words)

	RE: 6to4 question
		> >>>>> > >>>>>I keep reading that with 6to4 addresses, they are supposed > >>>>> > >>>>> > >>>>> > >>>>> > >>>>to start with > >>>> > >>>> > >>>> > >>>> > >>>>>2002: prefixes so that autoconfiguration can take place > >>>>> > >>>>> > >>>>> > >>>>> > >>>>with the clients.
		For example, when communicating with my friend, > who also uses > >>>>6to4 and has the IPv4 address 213.132.111.101, I send a > >>>> > >>>> > >>packet to her > >> > >> > >>>>IPv6 address, 2002:d584:6f65::1.
		> >>>> > >>>>So as you see, 6to4 addresses are something quite > different from the > >>>>2001::/48 block that you got from your tunnel provider.
	www.mail-archive.com /users@ipv6.org/msg01851.html (826 words)

	How to configure 6to4 in MacOS X (Site not responding. Last check: 2007-10-09)
		Since as co-author of the spec I naturally think 6to4 should be widely used, I thought I'd take the time to describe how to do this.
		The only reason you need to configure 6to4 is if the default relay router doesn't work and you want to assign a manual one.
		This is actually fairly convenient as you can selectively enable 6to4 on a per-location basis - so I have it enabled for locations where there isn't already IPv6 access and I have it turned off for locations where IPv6 access exists, or where there's a NAT that prevents 6to4 from working.
	www.cs.utk.edu /~moore/hints/howto-6to4-macosx.html (354 words)

	Novell Documentation: NetWare 6.5 - Configuring 6to4 Tunnels
		A 6to4 pseudo-interface is created with an IPv6 address of 2002:AABB:CCDD::AABB:CCDD, where AABB:CCDD is the colon-hexadecimal representation of the IPv4 address a.b.c.d assigned to the node.
		The 6to4 router encapsulates the IPv6 packets received from the private interface into IPv4 packets before forwarding them on the public interface.
		Therefore, the host can acquire the 6to4 prefix from the 6to4 router (which has a public IPv4 address and is connected to the IPv4 Internet) and configure IPv6 addresses.
	www.novell.com /documentation/nw65/ipv6/data/ake7b2y.html (315 words)

	6to4 Info (Site not responding. Last check: 2007-10-09)
		The "6to4" transition mechanism provides a way to connect IPv6 end-site networks by automatically tunnelling over the intervening IPv4 Internet.
		A special IPv6 routing prefix (2002::/16) is used to indicate that the remaining 32-bits of the external routing prefix contain the IPv4 end-point address of a boundary IPv6 router for that site that will respond to IPv6 in IPv4 encapsulation.
		Thus another "6to4" end-site can automatically discover this tunnel endpoint by dint of DNS lookups for any host on that network.
	www.6bone.net /6bone_6to4.html (159 words)

	6bone to 6to4 (Site not responding. Last check: 2007-10-09)
		Greetings, On Mon, 22 Jan 2001, Kurt D. Zeilenga wrote: >> Besides 6bone (BGP) connectivity, I am also playing with the 6to4 >> encapsulation.
		- Routing static route for 2002::/16 to tunnel1 (6to4).
		For the rest, it 'falls back' to the BGP 4+ routing.
	mailman.isi.edu /pipermail/6bone/2001-January/003778.html (415 words)

Try your search on: Qwika (all wikis)