At 16:52 21.02.2001, Dave Marquardt wrote:
>On Tue, Feb 20, 2001 at 03:48:37PM +0530, Niveda Monyvannan wrote:
> > Should configured tunnel always be a duplex one?
>
>Are you talking about tunneling IPv6 over IPv4? I don't think you
>need to have a duplex tunnel. Try considering the tunnel "interface"
>to be transmit only, i.e. half duplex. The tunneling RFCs (2893 and
>2473) treat tunneling as an encapsulation mechanism and decapsulation
>is just "normal" protocol operation. So I would say, no, you don't
>need to have a full duplex tunnel.
>
> > A-------------B========C--------------------D
> >
> > Let us say B is configured to encaptulate v6 packet to C. Should C have
> > a configured tunnel interface towards B to receive a encaptulated
> > packets from B?
>
>No, I don't think so.
Hmm, but C have to know about the IPv6 network between A and B and must
route/tunnel such (response from D) packets to IPv4-B back again.
>One thing this made me wonder about, though. Let's say we have your
>ABCD scenario above:
>
> A-------------B========C--------------------D
>
>C is a router. All nodes have IPv6 addresses, call them A6, B6, C6,
>and D6. B and C have IPv4 addresses, B4 and C4. Is it "legal" to
>configure a tunnel from B to D by using B4 as the local IPv4 address
>and C4 as the remote address, and configuring the local IPv6 address
>as B6 and the remote IPv6 address as D6?
Why would you setup D6 on C? What is the reason for that?
> Packets to D would get
>encapsulated at B in an IPv4 packet with B4 as source and C4 as
>destination. When the packet reached C, it would be decapsulated.
>Since C is a router, it would forward the packet on to D. Is this
>allowed? It's confusing, but I don't see why it wouldn't work.
Perhaps it's better to clarify such szenarios using unnumbered tunnels
first (for routing/tunneling issues this is enough IMHO).
On Linux using NBMA tunnels are the IMHO easiest method to setup tunneling.
Only needed information for tunnel: IPv6 network of destination and IPv4 of
tunnel endpoint, e.g.
C must know about IPv6net(A-B) and IPv4(B)
B must know about IPv6net(C-D) and IPv4(C)
That's all
Setup on Linux: route -A inet6 add $IPv6net(foreign) gw ::$IPv4(foreign
tunnel) dev sit0
Perhaps on Solaris the same way can be done.
Peter
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
