[ovs-dev] [PATCH 2/2] lib: Show tunnel egress interface in ovsdb

Ethan Jackson ethan at nicira.com
Wed Dec 29 20:38:37 UTC 2010


The short of it is that it doesn't.  Basically what I implemented is
equivalent to the "ip address" command and I didn't do anything
special with default routes.  There are definitely opportunities to
make this more robust/complicated.  I figured this is sufficient for
the requirements, but I could parse the routing table directly if we
need it.

Ethan

On Wed, Dec 29, 2010 at 2:15 PM, Justin Pettit <jpettit at nicira.com> wrote:
> On Dec 29, 2010, at 10:07 AM, Ethan Jackson wrote:
>
>>> It looks like this only considers addresses assigned to network devices.
>>> Is that sufficient?  Should we be looking at the routing table
>>> (e.g. RTM_*ROUTE) instead or in addition?
>>
>> That's definitely an option, I ended up going this route because it's
>> a little bit simpler and I think it's robust enough considering how
>> fuzzy the feature is anyways (especially if it evaluates to a bridge
>> port).    If we use RTM_*ROUTE we will need to maintain an RTM_*ADDR
>> created table to allow us to translate kernel interface indicies to
>> names as the route code only gives you the numeric index.  Do you
>> think it's worth the added complexity?
>
> How does it handle default routes?
>
> --Justin
>
>
>




More information about the dev mailing list