Opening the thread again.

In my server I have #19 vlans configured on 10Gb Ethernet card.
I don't know on which vlan the destination link-local address is.

1. As a user am I supposed to do ping6 on all of them one by one?

2. How does the TCP will work? Open #19 connections to the destination 
link-local address with different scope id??
How does the application running on top of TCP stack know about the physical 
interfaces of the system?

Regards,
Parav Pandit


--- On Wed, 4/14/10, Mohacsi Janos <[email protected]> wrote:

> From: Mohacsi Janos <[email protected]>
> Subject: Re: which interface to choose to send to destination link-local 
> address - any RFC?
> To: "Parav Pandit" <[email protected]>
> Cc: [email protected]
> Date: Wednesday, April 14, 2010, 3:01 PM
> 
> 
> 
> On Wed, 14 Apr 2010, Parav Pandit wrote:
> 
> > Hi,
> > 
> > In IPv6 stack implementation,
> > 
> > How IPv6 stack should select the outgoing interface to
> choose (when multiple interfaces) are available?
> > Typically when the destination is the link-local
> address which may be on-link on both the interfaces (before
> > the neighbor discovery) is done?
> > 
> > Should IPv6 stack do Neighbor discovery on all
> multiple interfaces in the host?
> > 
> > Which RFC defines this behavior? I referred RFC 3484
> (Default Address Selection for IPv6) but doesn't seem to
> > define this.
> > 
> > I hope I am asking on the right mailing list. If not
> please divert me to the correct one.
> 
> 
> The application should know which interface/link to choose
> in case of link-local address. The link-local is relevant to
> a specific link only.
> 
> e.g.
> 
> ping6 -I bge0 fe80::21b:63ff:fe9f:4527
> PING6(56=40+8+8 bytes) fe80::206:5bff:fef2:41c1%bge0 -->
> fe80::21b:63ff:fe9f:4527
> 16 bytes from fe80::21b:63ff:fe9f:4527%bge0, icmp_seq=0
> hlim=64 time=7.292 ms
> 16 bytes from fe80::21b:63ff:fe9f:4527%bge0, icmp_seq=1
> hlim=64 time=0.656 ms
> ^C
> --- fe80::21b:63ff:fe9f:4527 ping6 statistics ---
> 2 packets transmitted, 2 packets received, 0.0% packet
> loss
> round-trip min/avg/max/std-dev = 0.656/3.974/7.292/3.318
> ms
> 
> 
> ping6 fe80::21b:63ff:fe9f:4527
> ping6: UDP connect: Network is unreachable
> 
> If the application knows which link to use then IPv6
> protocol stack might use ND to dicover/reach the node.
> 
> Best Regards,
>         Janos Mohacsi
> 


      
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to