From robin@aol.com Wed Mar 5 18:17:36 2003
From: robin@aol.com (Robert)
Date: Wed, 5 Mar 2003 13:17:36 -0500
Subject: [Xorp-users] Lucrative Home Based Business
Message-ID: <200303051816.h25IFqfh098263@wyvern.icir.org>
Hi, Do you want me to show you how you can earn
$1,000 to $5,000 a month
working from home Part Time?
NEXT
I
This e-mail is sent in compliance with our strict anti-abuse regulations. You have received this e-mail because you or someone using your computer has used an FFA List, Safe List or requested other information. If you do not wish to receive any mail from our servers you may permanently block your e-mail address by clicking on the following link. (Please be advised by blocking your e-mail you will not have access to over 900 domains and the thousands of users and services they represent)
.Thank you,
The Postmaster
Unsubscribe
From jackie34@ffa.net Wed Mar 5 19:56:22 2003
From: jackie34@ffa.net (Oscar)
Date: Wed, 5 Mar 2003 14:56:22 -0500
Subject: [Xorp-users] Part time imcome
Message-ID: <200303051955.h25JsMfh099492@wyvern.icir.org>
Hi, Do you want me to show you how you can earn
$1,000 to $5,000 a month
working from home Part Time?
NEXT
I
This e-mail is sent in compliance with our strict anti-abuse regulations. You have received this e-mail because you or someone using your computer has used an FFA List, Safe List or requested other information. If you do not wish to receive any mail from our servers you may permanently block your e-mail address by clicking on the following link. (Please be advised by blocking your e-mail you will not have access to over 900 domains and the thousands of users and services they represent)
.Thank you,
The Postmaster
Unsubscribe
From bogus@does.not.exist.com Thu Mar 6 15:38:25 2003
From: bogus@does.not.exist.com (Terry)
Date: Thu, 6 Mar 2003 10:38:25 -0500
Subject: [Xorp-users] No upfront money needed
Message-ID: <200303061537.h26Fb1fh010086@wyvern.icir.org>
Hi, Do you want me to show you how you can earn
$1,000 to $5,000 a month
working from home Part Time?
NEXT
I
This e-mail is sent in compliance with our strict anti-abuse regulations. You have received this e-mail because you or someone using your computer has used an FFA List, Safe List or requested other information. If you do not wish to receive any mail from our servers you may permanently block your e-mail address by clicking on the following link. (Please be advised by blocking your e-mail you will not have access to over 900 domains and the thousands of users and services they represent)
.Thank you,
The Postmaster
Unsubscribe
From jackie34@ffa.net Fri Mar 7 14:41:03 2003
From: jackie34@ffa.net (ofsOscar)
Date: Fri, 7 Mar 2003 09:41:03 -0500
Subject: [Xorp-users] No cost home based business
Message-ID: <200303071424.h27EO9fh023332@wyvern.icir.org>
Hi, Do you want me to show you how you
can earn
$1,000 to $5,000 a month
working from home Part
Time?
NEXT
This
e-mail is sent in compliance with our strict anti-abuse regulations. You
have received this e-mail because you or someone using your computer has
used an FFA List, Safe List or requested other information. If you do not
wish to receive any mail from our servers you may permanently block your
e-mail address by clicking on the following link. (Please be advised by
blocking your e-mail you will not have access to over 900 domains and the
thousands of users and services they represent)
.Thank
you,
The Postmaster
Unsubscribe
---
From victor02@aol.com Fri Mar 7 15:20:39 2003
From: victor02@aol.com (Oscar)
Date: Fri, 7 Mar 2003 10:20:39 -0500
Subject: [Xorp-users] Please activate your account
Message-ID: <200303071519.h27FJFfh023869@wyvern.icir.org>
Hi, Do you want me to show you how you can earn
$1,000 to $5,000 a month
working from home Part Time?
NEXT
I
This e-mail is sent in compliance with our strict anti-abuse regulations. You have received this e-mail because you or someone using your computer has used an FFA List, Safe List or requested other information. If you do not wish to receive any mail from our servers you may permanently block your e-mail address by clicking on the following link. (Please be advised by blocking your e-mail you will not have access to over 900 domains and the thousands of users and services they represent)
.Thank you,
The Postmaster
Unsubscribe
From mjh@icir.org Fri Mar 7 15:22:00 2003
From: mjh@icir.org (Mark Handley)
Date: Fri, 07 Mar 2003 07:22:00 -0800
Subject: [Xorp-users] list restricted to member-posting
Message-ID: <200303071522.h27FM0Ef001447@nilla.icir.org>
I'm changed the xorp-users list to only allow posting from list
members - postings from others will be bounced to me for approval.
- Mark
From mjh@icir.org Tue Mar 11 04:49:42 2003
From: mjh@icir.org (Mark Handley)
Date: Mon, 10 Mar 2003 20:49:42 -0800
Subject: [Xorp-users] XORP Release 0.2 Available
Message-ID: <54715.1047358182@vulture.icir.org>
On behalf of the XORP team, it is my pleasure to announce that Release
0.2 of the XORP Extensible Open Router Platform is now available.
This is still an alpha-release - it's definitely premature to consider
using this release for any production work - but the functionality and
stability are continously improving. In general, if you're interested
in the XORP code at the current time, you'd be best to track our CVS
archive, as the current version in CVS usually has better
functionality and fewer bugs. However, these alpha releases represent
snapshots where we believe everything is reasonably stable at one time
and the documentation correctly matches the source code.
The release notes below give an overview of what has changed since the
Release 0.1 in December. Amongst other changes, we've a completely
new IPC Finder giving much more flexibility and control over IPC
bindings, improved BGP functionality, and PIM-SM is now getting close
to being complete.
The source code, documentation, CVS access, and a more complete
overview of the current status of the XORP components are all
available via http://www.xorp.org.
- The XORP Team
--------------------------------------------------------------------------
XORP RELEASE NOTES
This file contains XORP release notes (most recent releases first).
Release 0.2 (2003/03/10)
========================
ALL:
- Source code compiles under GCC 3.2.1 and on Mac OS X 10.2.x (GCC 3.1)
in addition to GCC 2.95.x and 2.96.
LIBXORP:
- Add libxorp/ref_trie.hh :
Implementation of a trie to support route
lookups. Based on trie.hh, but with reference-counted storage
supporting delayed deletion.
LIBXIPC:
- Complete re-implementation of the XRL finder, so that
registration/deregistration to the finder uses XRLs.
RTRMGR:
- Add operational-mode commands for monitoring BGP routes and
peers, and VIF/interface state.
- Re-implement how rtrmgr decides when to start processes. This
fixes a fex bugs in the dependency tracking - prior to this the
RIB would not be started because it requires no direct configuration.
FEA:
- Bug fixes.
RIB:
- Ensure that the originating protocol is propagated throughout
the RIB.
- Fix bug where routes for directly connected interfaces were
incorrectly being fed back to the FEA (which didn't expect to
see add_route for these subnets).
BGP:
- XRL interfaces for monitoring BGP peers and the complete BGP
routing table added. Helper programs bgp/tools/show_routes and
bgp/tools/show_peers added, along with versions of these for
running from xorpsh.
- Support for adding/removing MEDs added.
- BGP message handling and Path Attribute handling re-written to
be much cleaner and more efficient.
- Re-structured the BGP peer state machine to make the code easier
to understand.
- Change BGP to use reference-counted tries. This greatly
simplies the implementation of background tasks.
- Correctly handle unrecognized optional transitive attributes.
- Merge isolation tests into a single binary.
- Added BGP/RIB/FEA integration tests.
- Too many bug fixes to list.
MFEA:
- Minor bug fixes.
MLD/IGMP:
- No changes.
PIM-SM:
- PIM-SM Bootstrap mechanism reimplemented and tested.
Note that the Bootstrap-related configuration commands in
pim/configure_pim have changed slightly.
- Detailed testing of the basic protocol and the Bootstrap mechanism
completed and documented in the XORP PIM-SM Test Suite document.
- Numerious bug fixes.
Release 0.1 (2002/12/11)
========================
- First public release.
- CVS repository opened to the world.
From p.trimintzios@eim.surrey.ac.uk Wed Mar 19 13:09:17 2003
From: p.trimintzios@eim.surrey.ac.uk (Panos TRIMINTZIOS)
Date: Wed, 19 Mar 2003 13:09:17 +0000 (GMT)
Subject: [Xorp-users] difference with zebra
Message-ID:
Hi,
I tried to check the archives of this list to see if this question was
answered before but they are unaccessible.
So here it is, what is the difference of Xorp compared with Zebra in terms
of routing (BGP,OSPF, ...)? I understand that Xorp in total is a superset
of Zebra but I am only referring to the common parts.
thanks
Panos
From pavlin@icir.org Fri Mar 21 05:15:08 2003
From: pavlin@icir.org (Pavlin Radoslavov)
Date: Thu, 20 Mar 2003 21:15:08 -0800
Subject: [Xorp-users] difference with zebra
In-Reply-To: Message from Panos TRIMINTZIOS
of "Wed, 19 Mar 2003 13:09:17 GMT."
Message-ID: <200303210515.h2L5F8ix093961@possum.icir.org>
> So here it is, what is the difference of Xorp compared with Zebra in terms
> of routing (BGP,OSPF, ...)? I understand that Xorp in total is a superset
> of Zebra but I am only referring to the common parts.
Panos,
The answer depends on your needs. If all you need is, say, just
OSPF, then practically any solution that implements OSPF only
(e.g., http://www.ospf.org/) should work for you. If, however, you
are looking for a highly modular and extensible solution, then you
need a router that has much more flexible architecture.
For example, the XORP architecture allows you to run your router
components in a distributed fashion: e.g., the FEA (Forwarding
Engine Abstraction) on the machine with the forwarding plane, BGP on
another machine, and OSPF on a third machine. This could be very
valuable if you have CPU and/or memory limitations that could
prevent you from running all of them on a single machine.
If performance is not an issue, but you need a robust and easy way
to upgrade your router, then one thing you may want from your router
is the ability to hot-restart when upgrading each component
separately.
For example, if you want to upgrade a single component without
taking down the rest of the router, it is essential that there are
no API backward compatibility issues. The XORP architecture provides
a mechanism for supporting multiple APIs that is very flexible and
easy to use. Indeed, this is something that is invisible to the
users, but it is very beneficial for the developers. Therefore, this
could have a positive impact on the developers' ability to improve
the implementation and/or to add more features (which of course will
benefit the users as well).
For more information about the XORP architecture and its advantages,
you can read the following paper:
"XORP: An Open Platform for Network Research"
http://www.xorp.org/papers/xorp-hotnets.pdf
To be fair, if you need a routing solution now, currently XORP is
behind Zebra, so right now you don't have much choice.
Indeed, we are actively working on giving you that choice. However,
please bear in mind that the goal of the XORP project is not to give
you a Zebra replacement, but a platform that can be used for
research *and* in production environment. Though, early on it is
more likely that XORP would be used for network research, and when
it becomes stable enough it can be used in production environment as
well.
Regards,
Pavlin
From patrick@caida.org Sat Mar 22 02:37:12 2003
From: patrick@caida.org (Patrick Verkaik)
Date: Fri, 21 Mar 2003 18:37:12 -0800 (PST)
Subject: [Xorp-users] handling of BGP updates with multiple prefixes
Message-ID:
Do you know whether BGP routers (commercial or free) are able to handle
prefixes that are equivalent (in terms of routing) in some intelligent
way? For example, suppose a router has a number of prefixes in its RIB
with the same attributes. Further assume that the router does not have
any particular policy configured that differentiates between those
prefixes. Now it receives a BGP update (announcement or withdrawal)
covering also that same set of prefixes. Is the router capable of
optimising the handling of the BGP update by performing (some of) the
necessary route computations just once for all the prefixes?
Patrick
From Marc@SoftwareHackery.Com Sat Mar 22 23:19:37 2003
From: Marc@SoftwareHackery.Com (Marc Evans)
Date: Sat, 22 Mar 2003 18:19:37 -0500 (EST)
Subject: [Xorp-users] handling of BGP updates with multiple prefixes
In-Reply-To:
Message-ID: <20030322181839.X23199-100000@gw.softwarehackery.com>
Typically, no. Companies like Sockeye Networks, NetVMG, and RouteScience
specialize in equipment that complement routing devices to provide better
decision logic.
- Marc
On Fri, 21 Mar 2003, Patrick Verkaik wrote:
>
> Do you know whether BGP routers (commercial or free) are able to handle
> prefixes that are equivalent (in terms of routing) in some intelligent
> way? For example, suppose a router has a number of prefixes in its RIB
> with the same attributes. Further assume that the router does not have
> any particular policy configured that differentiates between those
> prefixes. Now it receives a BGP update (announcement or withdrawal)
> covering also that same set of prefixes. Is the router capable of
> optimising the handling of the BGP update by performing (some of) the
> necessary route computations just once for all the prefixes?
>
>
> Patrick
>
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users@xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
From brian@wrinklenet.com Tue Mar 25 22:25:10 2003
From: brian@wrinklenet.com (Brian Edwards)
Date: Tue, 25 Mar 2003 16:25:10 -0600
Subject: [Xorp-users] ospf causes rtrmgr to crash
References: <20030322181839.X23199-100000@gw.softwarehackery.com>
Message-ID: <007401c2f31d$66068660$1ac8a8c0@cartwright>
starting up rtrmgr with ospf config causes rtrmgr to crash.
running module: ospf path: ../ospfd/xorp/ospfd
**********************************************************
New module has PID 45710
[ 2003/03/25 16:06:29 INFO ospf OSPF ] Starting v2.16
+[ 2003/03/25 16:06:29 INFO ospf OSPF ] Awaiting router id
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++[ 2003/03/25 16:06:31 WARNING rtrmgr XrlFinderTarget ] Handling method
for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target
does not exist. "Xrl target does not exist."
+++[ 2003/03/25 16:06:31 FATAL rtrmgr:45706 RTRMGR +144 master_conf_tree.cc
config_done ] Startup failed
200 Resolve failed
Abort (core dumped)
cabana# [ 2003/03/25 16:06:33 ERROR ospf:45710 XifFinder +329
finder_ng_client.cc reg_callback ] Failed to register client named ospfd of
class undisclosed: "211 Reply timed out"
cabana# more config.boot
interfaces {
interface xl0 {
description: "Road Runner"
vif xl0 {
address 24.153.152.251 {
prefix-length: 29
broadcast: 24.153.152.255
}
}
}
}
protocols {
ospf {
router-id: 10.10.10.251
area 0.0.0.0 {
stub: false
interface xl0 {
hello-interval: 5
}
}
}
bgp {
bgp-id: 10.10.10.22
local-as: 65222
peer costanza {
local-ip: 24.153.152.251
peer-ip: 24.153.152.250
as: 65223
holdtime: 90
next-hop: 24.153.152.250
}
}
}
cabana# gdb rtrmgr rtrmgr.core
GNU gdb 4.18 (FreeBSD)
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...Deprecated bfd_read
called at
/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line
2627 in elfstab_build_psymtabs
Deprecated bfd_read called at
/usr/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line
933 in fill_symbuf
Core was generated by `rtrmgr'.
Program terminated with signal 6, Abort trap.
Reading symbols from /usr/lib/libstdc++.so.3...done.
Reading symbols from /usr/lib/libm.so.2...done.
Reading symbols from /usr/lib/libc.so.4...done.
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0 0x28233b78 in kill () from /usr/lib/libc.so.4
(gdb) bt
#0 0x28233b78 in kill () from /usr/lib/libc.so.4
#1 0x28274742 in abort () from /usr/lib/libc.so.4
#2 0x8146826 in xlog_fatal (module_name=0x81662d1 "RTRMGR",
where=0xbfbe90ac "+144 master_conf_tree.cc config_done",
fmt=0x8223fe0 "Startup failed\n200 Resolve failed") at xlog.c:420
#3 0x808d06c in MasterConfigTree::config_done (this=0xbfbff7a0, status=-1,
errmsg=@0xbfbeb140) at master_conf_tree.cc:144
#4 0x80915e8 in XorpMemberCallback2B0, __default_alloc_template > const &>::dispatch (this=0x81fd3d0, a1=-1, a2=@0xbfbeb140) at
../libxorp/callback.hh:1672
#5 0x80979cd in XorpBatch::abort_transaction (this=0x818ce60,
errmsg=@0xbfbeb140) at xorp_client.cc:133
#6 0x80978dd in XorpBatch::batch_item_done (this=0x818ce60,
batch_item=0x81f3ac0, success=false, errmsg=@0xbfbeb140)
at xorp_client.cc:121
#7 0x809829a in XorpBatchXrlItem::response_callback (this=0x81f3ac0,
err=@0x818a42c, xrlargs=0x0) at xorp_client.cc:204
#8 0x809b4ac in XorpMemberCallback2B0::dispatch (this=0x81fd770,
a1=@0x818a42c, a2=0x0) at ../libxorp/callback.hh:1672
#9 0x8111e54 in XrlRouterDispatchState::dispatch (this=0x8210ba0,
e=@0x818a42c, a=0x0) at xrl_router.cc:285
#10 0x810ffe2 in XrlRouter::resolve_callback (this=0xbfbff848, e=@0x818a42c,
dbe=0x0, ds=0x8210ba0) at xrl_router.cc:433
#11 0x8111434 in XorpMemberCallback2B1::dispatch
(this=0x8210bc0, a1=@0x818a42c, a2=0x0) at ../libxorp/callback.hh:1764
#12 0x8123ba1 in FinderNGClientQuery::query_callback (this=0x8210be0,
e=@0xbfbf73e0, al=0x0) at finder_ng_client.cc:162
#13 0x811d810 in XorpMemberCallback2B0::dispatch (this=0x81fd840,
a1=@0xbfbf73e0, a2=0x0) at ../libxorp/callback.hh:1672
#14 0x813fc8d in XrlFinderV0p1Client::unmarshall6 (this=0xbfbf9434,
e=@0xbfbf73e0, a=0x0, cb=0xbfbf52a4) at finder_xif.cc:262
#15 0x814390c in XorpMemberCallback2B1 > >::dispatch (this=0x8210c00, a1=@0xbfbf73e0, a2=0x0)
at ../libxorp/callback.hh:1764
#16 0x811433c in FinderMessengerBase::dispatch_xrl_response (this=0x8209900,
seqno=1038, xe=@0xbfbf73e0, args=0x0)
at finder_messenger.cc:51
#17 0x80daacb in FinderTcpMessenger::read_event (this=0x8209900, errval=0,
data=0x81eef00 "Finder 0.2\nMsgType r\nSeqNo 1038\nMsgData 102 /
Xrl+target+does+not+exist.\n://24.153.152.251:1954/bgp/0.2/enable_peer-6356f
d0d5a544f88894aecb56de9", data_bytes=73) at finder_tcp_messenger.cc:69
#18 0x812850c in FinderTcpBase::read_callback (this=0x820991c, ev=DATA,
buffer=0x81eef00 "Finder 0.2\nMsgType r\nSeqNo 1038\nMsgData 102 /
Xrl+target+does+not+exist.\n://24.153.152.251:1954/bgp/0.2/enable_peer-6356f
d0d5a544f88894aecb56de9", buffer_bytes=73, offset=73) at finder_tcp.cc:167
#19 0x81299bc in XorpMemberCallback4B0::dispatch (this=0x81fd850, a1=DATA,
a2=0x81eef00 "Finder 0.2\nMsgType r\nSeqNo 1038\nMsgData 102 /
Xrl+target+does+not+exist.\n://24.153.152.251:1954/bgp/0.2/enable_peer-6356f
d0d5a544f88894aecb56de9", a3=73, a4=73) at ../libxorp/callback.hh:3098
#20 0x81491a2 in AsyncFileReader::BufferInfo::dispatch_callback
(this=0xbfbf9534, e=DATA) at asyncio.hh:183
#21 0x8147946 in AsyncFileReader::complete_transfer (this=0x820992c, err=0,
done=73) at asyncio.cc:107
#22 0x814782b in AsyncFileReader::read (this=0x820992c, fd=10, m=SEL_RD) at
asyncio.cc:88
#23 0x8148904 in XorpMemberCallback2B0::dispatch (this=0x81fd870, a1=10, a2=SEL_RD)
at ../libxorp/callback.hh:1672
#24 0x815a3c8 in SelectorList::Node::run_hooks (this=0x8203168, m=SEL_RD,
fd=10) at selector.cc:97
#25 0x8158db4 in SelectorList::select (this=0xbfbff920, timeout=0xbfbfb7dc)
at selector.cc:237
---Type to continue, or q to quit---
#26 0x814ac5a in EventLoop::run (this=0xbfbff908) at eventloop.cc:34
#27 0x8055e03 in main (argc=1, argv=0xbfbffbd0) at main_rtrmgr.cc:179
(gdb) quit
cabana#
From hodson@icir.org Wed Mar 26 16:57:38 2003
From: hodson@icir.org (Orion Hodson)
Date: Wed, 26 Mar 2003 08:57:38 -0800
Subject: [Xorp-users] ospf causes rtrmgr to crash
In-Reply-To: Your message of "Tue, 25 Mar 2003 16:25:10 CST."
<007401c2f31d$66068660$1ac8a8c0@cartwright>
Message-ID: <200303261657.h2QGvcAT081769@puma.icir.org>
/-- "Brian Edwards" wrote:
| starting up rtrmgr with ospf config causes rtrmgr to crash.
Brian
This is caused by the router manager attempting to send configuration via XRLs
to ospf before ospf is ready to process them. This should now be fixed in the
CVS repository.
Just as a heads-up: we haven't done much work with OSPF so you may hit other
problems fair quickly even if you update to the head of the CVS repository
code.
- Orion
From brian@wrinklenet.com Wed Mar 26 21:57:37 2003
From: brian@wrinklenet.com (Brian Edwards)
Date: Wed, 26 Mar 2003 15:57:37 -0600
Subject: [Xorp-users] ospf causes rtrmgr to crash
References: <200303261657.h2QGvcAT081769@puma.icir.org>
Message-ID: <013301c2f3e2$b73bc020$1ac8a8c0@cartwright>
Orion,
This is what I see now. rtrmgr still crashes, but ospfd is started and I
see the warning message multiple times. BTW, let me know if reporting this
type of stuff is useful or if it's a distraction.
running module: ospf path: ../ospfd/xorp/ospfd
**********************************************************
New module has PID 68264
+[ 2003/03/26 15:39:05 INFO ospf OSPF ] Starting v2.16
[ 2003/03/26 15:39:05 INFO ospf OSPF ] Awaiting router id
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++[ 2003/03/26 15:39:07 WARNING rtrmgr XrlFinderTarget ] Handling method
for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target
does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:07 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:07 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:08 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:08 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:08 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:09 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:09 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:09 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:09 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:10 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:10 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:10 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:10 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:11 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:11 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:11 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:11 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:12 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:12 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:12 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:12 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:13 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:13 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:13 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:13 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:14 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:14 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:14 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:15 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++++++[ 2003/03/26 15:39:15 WARNING rtrmgr XrlFinderTarget ] Handling
method for finder/0.1/resolve_xrl failed: XrlCmdError 102 Command failed Xrl
target does not exist. "Xrl target does not exist."
+++[ 2003/03/26 15:39:15 FATAL rtrmgr:68259 RTRMGR +144 master_conf_tree.cc
config_done ] Startup failed
200 Resolve failed
Abort (core dumped)
cabana# [ 2003/03/26 15:39:17 ERROR ospf:68264 XifFinder +329
finder_ng_client.cc reg_callback ] Failed to register client named ospfd of
class undisclosed: "211 Reply timed out"
#0 0x28233b78 in kill () from /usr/lib/libc.so.4
#1 0x28274742 in abort () from /usr/lib/libc.so.4
#2 0x8146826 in xlog_fatal (module_name=0x81662d1 "RTRMGR",
where=0xbfbe907c "+144 master_conf_tree.cc config_done",
fmt=0x8225a20 "Startup failed\n200 Resolve failed") at xlog.c:420
#3 0x808d06c in MasterConfigTree::config_done (this=0xbfbff770, status=-1,
errmsg=@0xbfbeb110) at master_conf_tree.cc:144
#4 0x80915e8 in XorpMemberCallback2B0, __default_alloc_template > const &>::dispatch (this=0x81fd3d0, a1=-1, a2=@0xbfbeb110) at
../libxorp/callback.hh:1672
#5 0x80979cd in XorpBatch::abort_transaction (this=0x818ce80,
errmsg=@0xbfbeb110) at xorp_client.cc:133
#6 0x80978dd in XorpBatch::batch_item_done (this=0x818ce80,
batch_item=0x81f3ac0, success=false, errmsg=@0xbfbeb110)
at xorp_client.cc:121
#7 0x809829a in XorpBatchXrlItem::response_callback (this=0x81f3ac0,
err=@0x818a42c, xrlargs=0x0) at xorp_client.cc:204
#8 0x809b4ac in XorpMemberCallback2B0::dispatch (this=0x81fda20,
a1=@0x818a42c, a2=0x0) at ../libxorp/callback.hh:1672
#9 0x8111e54 in XrlRouterDispatchState::dispatch (this=0x8210f60,
e=@0x818a42c, a=0x0) at xrl_router.cc:285
#10 0x810ffe2 in XrlRouter::resolve_callback (this=0xbfbff818, e=@0x818a42c,
dbe=0x0, ds=0x8210f60) at xrl_router.cc:433
#11 0x8111434 in XorpMemberCallback2B1::dispatch (this=0x8210f80,
a1=@0x818a42c, a2=0x0) at ../libxorp/callback.hh:1764
#12 0x8123ba1 in FinderNGClientQuery::query_callback (this=0x8210fa0,
e=@0xbfbf73b0, al=0x0) at finder_ng_client.cc:162
#13 0x811d810 in XorpMemberCallback2B0::dispatch (
this=0x81fda40, a1=@0xbfbf73b0, a2=0x0) at ../libxorp/callback.hh:1672
#14 0x813fc8d in XrlFinderV0p1Client::unmarshall6 (this=0xbfbf9494,
e=@0xbfbf73b0, a=0x0, cb=0xbfbf5274) at finder_xif.cc:262
#15 0x814390c in XorpMemberCallback2B1 > >::dispatch (this=0x8210fc0, a1=@0xbfbf73b0, a2=0x0)
at ../libxorp/callback.hh:1764
#16 0x811433c in FinderMessengerBase::dispatch_xrl_response (this=0x8209900,
seqno=1068, xe=@0xbfbf73b0, args=0x0)
at finder_messenger.cc:51
#17 0x80daacb in FinderTcpMessenger::read_event (this=0x8209900, errval=0,
data=0x81eef00 "Finder 0.2\nMsgType r\nSeqNo 1068\nMsgData 102 /
Xrl+target+does+not+exist.\n://24.153.152.251:2084/bgp/0.2/enable_peer-0ee99
9c951e51c2f0121d604a947", data_bytes=73) at finder_tcp_messenger.cc:69
#18 0x812850c in FinderTcpBase::read_callback (this=0x820991c, ev=DATA,
buffer=0x81eef00 "Finder 0.2\nMsgType r\nSeqNo 1068\nMsgData 102 /
Xrl+target+does+not+exist.\n://24.153.152.251:2084/bgp/0.2/enable_peer-0ee99
9c951e51c2f0121d604a947", buffer_bytes=73, offset=73) at finder_tcp.cc:167
#19 0x81299bc in XorpMemberCallback4B0::dispatch (this=0x81fda30, a1=DATA,
a2=0x81eef00 "Finder 0.2\nMsgType r\nSeqNo 1068\nMsgData 102 /
Xrl+target+does+not+exist.\n://24.153.152.251:2084/bgp/0.2/enable_peer-0ee99
9c951e51c2f0121d604a947", a3=73, a4=73) at ../libxorp/callback.hh:3098
#20 0x81491a2 in AsyncFileReader::BufferInfo::dispatch_callback
(this=0xbfbf9504, e=DATA) at asyncio.hh:183
#21 0x8147946 in AsyncFileReader::complete_transfer (this=0x820992c, err=0,
done=73) at asyncio.cc:107
#22 0x814782b in AsyncFileReader::read (this=0x820992c, fd=10, m=SEL_RD) at
asyncio.cc:88
#23 0x8148904 in XorpMemberCallback2B0::dispatch (this=0x81fda60, a1=10, a2=SEL_RD)
at ../libxorp/callback.hh:1672
#24 0x815a3c8 in SelectorList::Node::run_hooks (this=0x8203168, m=SEL_RD,
fd=10) at selector.cc:97
#25 0x8158db4 in SelectorList::select (this=0xbfbff8f0, timeout=0xbfbfb7ac)
at selector.cc:237
#26 0x814ac5a in EventLoop::run (this=0xbfbff8d8) at eventloop.cc:34
#27 0x8055e03 in main (argc=1, argv=0xbfbffba0) at main_rtrmgr.cc:179
From hodson@icir.org Thu Mar 27 16:17:05 2003
From: hodson@icir.org (Orion Hodson)
Date: Thu, 27 Mar 2003 08:17:05 -0800
Subject: [Xorp-users] ospf causes rtrmgr to crash
In-Reply-To: Your message of "Wed, 26 Mar 2003 15:57:37 CST."
<013301c2f3e2$b73bc020$1ac8a8c0@cartwright>
Message-ID: <200303271617.h2RGH5AT098580@puma.icir.org>
/-- "Brian Edwards" wrote:
| Orion,
| This is what I see now. rtrmgr still crashes, but ospfd is started and I
| see the warning message multiple times. BTW, let me know if reporting this
| type of stuff is useful or if it's a distraction.
|
Brian,
I'm guessing we have a chicken and egg situation here, but don't really have
the cycles right now. We will look into it, but it'll be a while.
- Orion