Re: [mpls-linux-general] (no subject)

[James R. L. <jl...@mi...>]

What version of ldp-portable and can you get a stack trace or trace output
from 'mplsd'

Enable trace output:

uml1-mpls# conf t
uml1-mpls(config)# mpls ldp
uml1-mpls(config-ldp)# tr
uml1-mpls(config-ldp)# trace all
uml1-mpls(config-ldp)# trace all
uml1-mpls(config-ldp)#

The tracing info is sent to standard out of the mplsd program (don't use -d
and make sure to redirect the output someplace)

Getting a stack trace:

[jleu jleu-laptop 10:45pm] ~-> gdb /usr/sbin/mplsd core
<snip>
(gdb) where
<stack trace>


On Wed, Apr 30, 2003 at 10:49:43AM +0200, Mattias Persson wrote:
> The following setup results in a segmentation fault of mplsd:
> 
> .105               .106  .10             .9
> X----10.1.0.104/29------A---10.7.2.8/29----B
> 
> Router A is a Cisco 3620 and router B is a linux machine. 
> Both run OSPF, BGP and MPLS. A and B are bgp peers. They are in the same
> BGP AS and in the same BGP and OSPF areas.
> 
> Router X runs BGP. It is in another BGP AS and peers with router A.
> 
> mplsd on B crashes when it receives some routes from
> the bgp protocol. I have traced the problem and it
> occurs because of the way bgp announces it routes:
> Router A tells router B that network 10.1.0.8/29 can be
> reached on nexthop 10.1.0.105. mplsd on Router B
> however, can not handle this because it
> does not have a direct connection to 10.1.0.105.
> 
> This results in a seg fault in mplsd (if_handle is null for the nexthop).
> 
> /Mattias Persson
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu