-----Original Message-----
From: <[email protected]> on behalf of Joo Kim 
<[email protected]>
Date: Thursday, August 3, 2017 at 12:18 PM
To: Darrell Ball <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [ovs-dev] Multiple ARP cache entries for one same dest IP?

    Darrell,
    
    I guess you said link-local addresses is one scenario where multiple
    entries for a given IP may exist.
    But, could you elaborate a bit more on  'routing space segmentation is
    another'?

consider two logical or physical networks that never can reach each other, 
because your forwarding rules don’t allow it; in this case, you could use the 
same 
ip address for them
Sometimes, this is realized formally by VRFs, but does not have to be – it can 
be more
flexible.


    
    Thanks
    
    On Wed, Aug 2, 2017 at 5:32 PM, Darrell Ball <[email protected]> wrote:
    
    >
    >
    > On Wed, Aug 2, 2017 at 3:51 PM, Joo Kim <[email protected]> wrote:
    >
    >> Hello,
    >>
    >> In OVS userspace implementation(See below), looks like, given a dest IP,
    >> multiple ARP entries are allowed as long as bridge-names are different 
for
    >> the same dest IP.
    >> But, is there real scenario where multiple ARP entries for the same dest
    >> IP
    >> (because of different bridge-name)?
    >>
    >
    >
    > link-local addresses is one way
    > routing space segmentation is another
    >
    >
    >
    >>
    >>
    >> int
    >> tnl_neigh_lookup(const char br_name[IFNAMSIZ], const struct in6_addr 
*dst,
    >>                  struct eth_addr *mac)
    >> {
    >>     struct tnl_neigh_entry *neigh;
    >>     int res = ENOENT;
    >>     neigh = tnl_neigh_lookup__(br_name, dst);
    >>     if (neigh) {
    >>         *mac = neigh->mac;
    >>         res = 0;
    >>     }
    >>     return res;
    >> }
    >>
    >> static struct tnl_neigh_entry *
    >> tnl_neigh_lookup__(const char br_name[IFNAMSIZ], const struct in6_addr
    >> *dst)
    >> {
    >>     struct tnl_neigh_entry *neigh;
    >>     uint32_t hash;
    >>     hash = tnl_neigh_hash(dst);
    >>     CMAP_FOR_EACH_WITH_HASH (neigh, cmap_node, hash, &table) {
    >>         if (ipv6_addr_equals(&neigh->ip, dst) && !strcmp(neigh->br_name,
    >> br_name)) {
    >>             neigh->expires = time_now() + NEIGH_ENTRY_DEFAULT_IDLE_TIME;
    >>             return neigh;
    >>         }
    >>     }
    >>     return NULL;
    >> }
    >> _______________________________________________
    >> dev mailing list
    >> [email protected]
    >> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=VDio1NuY7rTttIy4vQzfQa4lTuY8ZEPzUng6qDrrpoA&s=QL1uFnFYZ4DEj2VFVOxkeZU7TDV0CcIoO7nMZZjdOvU&e=
 
    >>
    >
    >
    _______________________________________________
    dev mailing list
    [email protected]
    
https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=VDio1NuY7rTttIy4vQzfQa4lTuY8ZEPzUng6qDrrpoA&s=QL1uFnFYZ4DEj2VFVOxkeZU7TDV0CcIoO7nMZZjdOvU&e=
 
    

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to