WG: [Xorp-hackers] Bugzilla #161

Kristian Larsson kristian@juniks.net
Wed, 7 Sep 2005 09:56:24 +0200


On Tue, Sep 06, 2005 at 06:47:15PM +0200, Patrick Preuss wrote:
> 
> 
> Hello 
> 
> Many thanks for you answer. 
> 
> I have a question about the time, route tags are they currenly known by the
> rib if seen nothing so far? 
> 
> Is equal cost and unequal cost load balancing supported or is it planed?
> 
> Some questions is it possible to get informations from the modules like are
> they running, how many memory they use how and so one? So I will do some
> work in this direction, I think it is nessesay to get more information about
> the router from the cli.
> 
> And at last I think it is not optimal to determine the protocol from witch a
> 
> Route was learn by the admin distance, there should be a sepperate field,
> because in production environment sometimes you have the need to change the
> ad for a protocol when you transit from a protocol to another. And If xorp 
> Should support more then one vrf, or mpls, more then one ospf daemon there 
> Should be a way to decide from witch we have learned the route.  
Sorry for dual posts here but I couldn't confirm
this before as I did not have access to a xorp box
When doing show route table ipv4 unicast final I
see:
 Xorp> show route table ipv4 unicast final 
Network 10.0.0.0/24
   Nexthop := 192.168.77.1
   Metric := 0    Protocol := static Interface := eth0 Vif := eth0
Network 192.168.77.0/24
   Nexthop := 192.168.77.90
   Metric := 0    Protocol := connected Interface := eth0 Vif := eth0

Isn't that information enough?

Regards,
Kristian

> 
> Gruss 
>    Patrick Marc Preuss 
>    Nordstrasse 28
> 41569 Rommerskirchen
>  
>    
> 
> -----Ursprüngliche Nachricht-----
> Von: xorp-hackers-admin@icir.org [mailto:xorp-hackers-admin@icir.org] Im
> Auftrag von Pavlin Radoslavov
> Gesendet: Dienstag, 6. September 2005 17:31
> An: "Patrick Preuß"
> Cc: xorp-hackers@icir.org; patrick.preuss@retail-sc.com
> Betreff: Re: [Xorp-hackers] Bugzilla #161 
> 
> > i have written a small patch for some problems described in bug 161 
> >  http://www.xorp.org/bugzilla/show_bug.cgi?id=161
> 
> As a general advice for all Bugzilla entries related patches,
> please upload the patch as an attachment to the appropriate bugzilla
> entry, so it is easier to track it and apply it.
> 
> Thanks,
> Pavlin
> 
> P.S. With apology to everyone who has posted to the xorp-hackers in
> the last few days and is still waiting for an answer. All emails
> will be answered within few days or so after some urgent tasks are
> out of the way.
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers@icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
> 
> 
> 
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers@icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers