From atanu at ICSI.Berkeley.EDU  Thu May  1 07:43:16 2008
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Thu, 01 May 2008 07:43:16 -0700
Subject: [Xorp-users] SPF Calculations
In-Reply-To: Message from "Gorski, Andrew J." <agorski@mitre.org> of "Thu,
	01 May 2008 01:28:53 EDT."
	<9863411DEA890E458E57C11C5A1A18EAB8247C@IMCSRV7.MITRE.ORG> 
Message-ID: <17396.1209652996@tigger.icir.org>

Hi,

We don't keep track of the number of SPF calculations performed.

   Atanu.

>>>>> "Andrew" == Andrew J Gorski <Gorski> writes:

    Andrew>    When using OSPF in XORP, is there anyway to see how many
    Andrew> SPF calculations have been performed since the process began
    Andrew> or since the counter was reset?
    Andrew> _______________________________________________ Xorp-users
    Andrew> mailing list Xorp-users at xorp.org
    Andrew> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From tsche at mitre.org  Thu May  1 10:17:50 2008
From: tsche at mitre.org (Che, Ting-Shuo T.)
Date: Thu, 1 May 2008 13:17:50 -0400
Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent?
References: Message from "Che, Ting-Shuo T." <tsche@mitre.org>    of "Tue,
	29 Apr 2008 14:14:50 EDT."
	<9FDF44CB3E9C9943B656E85501CF36FA022BF892@IMCSRV1.MITRE.ORG>
	<86609.1209495714@tigger.icir.org> 
Message-ID: <9FDF44CB3E9C9943B656E85501CF36FA022BF957@IMCSRV1.MITRE.ORG>

Did several more tests and found 20 OSPFv3 neighbors also has problem
but not 15.

Attached is the "complete" log that uses the command line you
recommended. Looks 
like there is no more messages than I have provided, no matter
foreground or
background command, standard output or error redirection, ... 

Please let me know if I miss anything or you have other thoughts. Thank
you 
very much for the help.

Ting

-----Original Message-----
From: Che, Ting-Shuo T. 
Sent: Tuesday, April 29, 2008 3:42 PM
To: 'atanu at icsi.berkeley.edu'
Cc: xorp-users at xorp.org
Subject: RE: [Xorp-users] No more than 25 OSPFv3 neighbors fully
adjacent? 

Thanks a lot for the guidance. I will do it ASAP. Indeed the OSPFv3
process seems to "partially" exit 
and no longer functioning. What puzzled me was somehow "ps -ef" show
xorp_ospfv3 still exists...

Ting

PS. 
root at 192.168.1.2> [ 2008/04/14 14:14:34  ERROR xorp_rtrmgr:252 XRL +638
xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout
[ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed
out
[ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed
out
root at 192.168.1.2>
root at 192.168.1.2> show ospf6 neighbor | match Full | count
[ 2008/04/14 14:15:15  WARNING xorp_rtrmgr:252 XrlFinderTarget +406
../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
failed Target "ospfv3" does not exist or is not enabled.
Count: 0 lines
root at 192.168.1.2> show ospf6 neighbor
[ 2008/04/14 14:15:36  WARNING xorp_rtrmgr:252 XrlFinderTarget +406
../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
failed Target "ospfv3" does not exist or is not enabled.
ERROR: Command
"/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited
with exit status 255.
root at 192.168.1.2> exit

bash-3.00# date
Mon Apr 14 14:15:50 MEST 2008

bash-3.00# ps -ef | grep xorp
root       252   221  2 13:39 ?        00:01:01 ./xorp_rtrmgr -b
ipv6ospf.boot
root       254   252  2 13:39 ?        00:00:51 xorp_fea
root       255   252  0 13:39 ?        00:00:03 xorp_rib
root       256   252  0 13:39 ?        00:00:03 xorp_policy
root       257   252 17 13:39 ?        00:06:26 xorp_ospfv3
root     24839   221  0 14:15 ?        00:00:00 grep xorp

-----Original Message-----
From: atanu at icir.org [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh
Sent: Tuesday, April 29, 2008 3:02 PM
To: Che, Ting-Shuo T.
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully
adjacent? 

Hi,

The OSPF process seems to have exited, typically the XORP processes
will
print a message before exiting, it would be useful to see this message.

Could you run the router manager in the background and capture the
output, the following works for me with /bin/sh:
# ./xorp_rtrmgr -b ./ipv6ospf.boot > log 2>&1 &

If you are not already could you also try building from CVS so that you
have all of the fixes.

  Atanu.

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ErrorLog20Ospfv3Neighbors.txt
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080501/63341e28/attachment-0001.txt 

From atanu at ICSI.Berkeley.EDU  Thu May  1 10:39:45 2008
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Thu, 01 May 2008 10:39:45 -0700
Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent?
In-Reply-To: Message from "Che, Ting-Shuo T." <tsche@mitre.org> of "Thu,
	01 May 2008 13:17:50 EDT."
	<9FDF44CB3E9C9943B656E85501CF36FA022BF957@IMCSRV1.MITRE.ORG> 
Message-ID: <37014.1209663585@tigger.icir.org>

Hi,

I don't understand why the log file has no content very strange.

Did you try using the latest code from CVS we have fixed may things
since the last release?

      Atanu.

>>>>> "Ting-Shuo" == Ting-Shuo T Che <Che> writes:

    Ting-Shuo> Did several more tests and found 20 OSPFv3 neighbors also has problem
    Ting-Shuo> but not 15.

    Ting-Shuo> Attached is the "complete" log that uses the command line you
    Ting-Shuo> recommended. Looks 
    Ting-Shuo> like there is no more messages than I have provided, no matter
    Ting-Shuo> foreground or
    Ting-Shuo> background command, standard output or error redirection, ... 

    Ting-Shuo> Please let me know if I miss anything or you have other thoughts. Thank
    Ting-Shuo> you 
    Ting-Shuo> very much for the help.

    Ting-Shuo> Ting

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: Che, Ting-Shuo T. 
    Ting-Shuo> Sent: Tuesday, April 29, 2008 3:42 PM
    Ting-Shuo> To: 'atanu at icsi.berkeley.edu'
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: RE: [Xorp-users] No more than 25 OSPFv3 neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Thanks a lot for the guidance. I will do it ASAP. Indeed the OSPFv3
    Ting-Shuo> process seems to "partially" exit 
    Ting-Shuo> and no longer functioning. What puzzled me was somehow "ps -ef" show
    Ting-Shuo> xorp_ospfv3 still exists...

    Ting-Shuo> Ting

    Ting-Shuo> PS. 
    Ting-Shuo> root at 192.168.1.2> [ 2008/04/14 14:14:34  ERROR xorp_rtrmgr:252 XRL +638
    Ting-Shuo> xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive timeout
    Ting-Shuo> [ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
    Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed
    Ting-Shuo> out
    Ting-Shuo> [ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
    Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response 211 Reply timed
    Ting-Shuo> out
    Ting-Shuo> root at 192.168.1.2>
    Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor | match Full | count
    Ting-Shuo> [ 2008/04/14 14:15:15  WARNING xorp_rtrmgr:252 XrlFinderTarget +406
    Ting-Shuo> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
    Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> Count: 0 lines
    Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor
    Ting-Shuo> [ 2008/04/14 14:15:36  WARNING xorp_rtrmgr:252 XrlFinderTarget +406
    Ting-Shuo> ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
    Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> ERROR: Command
    Ting-Shuo> "/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited
    Ting-Shuo> with exit status 255.
    Ting-Shuo> root at 192.168.1.2> exit

    Ting-Shuo> bash-3.00# date
    Ting-Shuo> Mon Apr 14 14:15:50 MEST 2008

    Ting-Shuo> bash-3.00# ps -ef | grep xorp
    Ting-Shuo> root       252   221  2 13:39 ?        00:01:01 ./xorp_rtrmgr -b
    Ting-Shuo> ipv6ospf.boot
    Ting-Shuo> root       254   252  2 13:39 ?        00:00:51 xorp_fea
    Ting-Shuo> root       255   252  0 13:39 ?        00:00:03 xorp_rib
    Ting-Shuo> root       256   252  0 13:39 ?        00:00:03 xorp_policy
    Ting-Shuo> root       257   252 17 13:39 ?        00:06:26 xorp_ospfv3
    Ting-Shuo> root     24839   221  0 14:15 ?        00:00:00 grep xorp

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: atanu at icir.org [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh
    Ting-Shuo> Sent: Tuesday, April 29, 2008 3:02 PM
    Ting-Shuo> To: Che, Ting-Shuo T.
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Hi,

    Ting-Shuo> The OSPF process seems to have exited, typically the XORP processes
    Ting-Shuo> will
    Ting-Shuo> print a message before exiting, it would be useful to see this message.

    Ting-Shuo> Could you run the router manager in the background and capture the
    Ting-Shuo> output, the following works for me with /bin/sh:
    Ting-Shuo> # ./xorp_rtrmgr -b ./ipv6ospf.boot > log 2>&1 &

    Ting-Shuo> If you are not already could you also try building from CVS so that you
    Ting-Shuo> have all of the fixes.

    Ting-Shuo> Atanu.


From atanu at ICSI.Berkeley.EDU  Thu May  1 10:46:50 2008
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Thu, 01 May 2008 10:46:50 -0700
Subject: [Xorp-users] BGP and Policy module shutdown
In-Reply-To: Message from "Yue Li" <yueli.m@gmail.com> of "Wed,
	30 Apr 2008 19:54:48 EDT."
	<49567c360804301654w68903cb6t852f2a41e91d9cc@mail.gmail.com> 
Message-ID: <38099.1209664010@tigger.icir.org>

Hi,

Do you have a simple way for us to reproduce this problem?

   Atanu.

>>>>> "Yue" == Yue Li <yueli.m at gmail.com> writes:

    Yue> Hi, All
    Yue> I am testing bgp and policies with 30 XORP instances.
    Yue> I got the following errors from one xorp instance, bgp and policy
    Yue> modules shutdown:
    Yue> [ 2008/04/30 19:07:08  ERROR xorp_rtrmgr:9832 RTRMGR +747
    Yue> module_manager.cc done_cb ] Command "/local/xorp/bgp/xorp_bgp":
    Yue> terminated with signal 11.
    Yue> [ 2008/04/30 19:07:08  ERROR xorp_rtrmgr:9832 RTRMGR +747
    Yue> module_manager.cc done_cb ] Command "/local/xorp/policy/xorp_policy":
    Yue> terminated with signal 6.
    Yue> [ 2008/04/30 19:07:08  ERROR xorp_policy:10139 XRL +635 xrl_pf_stcp.cc
    Yue> die ] XrlPFSTCPSender died: Keepalive timeout
    Yue> [ 2008/04/30 19:07:08  ERROR xorp_policy:10139 LIBXORP +213
    Yue> buffered_asyncio.cc io_event ] read error 104
    Yue> [ 2008/04/30 19:07:08  ERROR xorp_policy:10139 XRL +782 xrl_pf_stcp.cc
    Yue> read_event ] Read failed (error = 104)
    Yue> [ 2008/04/30 19:07:08  ERROR xorp_policy:10139 XRL +635 xrl_pf_stcp.cc
    Yue> die ] XrlPFSTCPSender died: read error
    Yue> [ 2008/04/30 19:07:08 INFO xorp_rib RIB ] Received death event for
    Yue> protocol bgp shutting down -------
    Yue> OriginTable: ebgp
    Yue> EGP
    Yue> next table = Merged:(ebgp)+(ibgp)
    Yue> [ 2008/04/30 19:07:08 INFO xorp_rib RIB ] Received death event for
    Yue> protocol bgp shutting down -------
    Yue> OriginTable: ebgp
    Yue> EGP
    Yue> next table = Merged:(ebgp)+(ibgp)
    Yue> [ 2008/04/30 19:07:08 INFO xorp_rib RIB ] Received death event for
    Yue> protocol bgp shutting down -------
    Yue> OriginTable: ebgp
    Yue> EGP
    Yue> next table = Merged:(ebgp)+(ibgp)
    Yue> [ 2008/04/30 19:07:08 INFO xorp_rib RIB ] Received death event for
    Yue> protocol bgp shutting down -------
    Yue> OriginTable: ebgp
    Yue> EGP
    Yue> next table = Merged:(ebgp)+(ibgp)
    Yue> [ 2008/04/30 19:07:08  FATAL xorp_policy:10139 XifRib +53
    Yue> xorp_policy.cc main ] PolicyException: FMException from line 122 of
    Yue> filter_manager.cc: XRL policy_backend_cb() error: 210 Transport failed

    Yue> I have configured the import and export policies with about 4,000
    Yue> terms on this router, most of them are like :
    Yue> policy-statement bgp_in {
    Yue> term 0 {
    Yue> from {
    Yue> neighbor: 10.0.1.81
    Yue> }
    Yue> then {
    Yue> accept
    Yue> }
    Yue> }
    Yue> term 1 {
    Yue> from {
    Yue> neighbor: 10.0.1.62
    Yue> network4: 199.253.246.0/24
    Yue> }
    Yue> then {
    Yue> accept
    Yue> }
    Yue> ...
    Yue> term import_last {
    Yue> then {
    Yue> reject
    Yue> }
    Yue> }
    Yue> }

    Yue> policy-statement bgp_out {
    Yue> term 0 {
    Yue> from {
    Yue> protocol: "static"
    Yue> network4: 129.142.0.0/16
    Yue> }
    Yue> to {
    Yue> neighbor: 10.0.1.141
    Yue> }
    Yue> then {
    Yue> nexthop4: 10.0.1.142
    Yue> accept
    Yue> }
    Yue> }
    Yue> ...
    Yue> term 209 {
    Yue> from {
    Yue> protocol: "bgp"
    Yue> network4: 146.75.0.0/16
    Yue> }
    Yue> to {
    Yue> neighbor: 10.0.1.141
    Yue> }
    Yue> then {
    Yue> accept
    Yue> }
    Yue> }
    Yue> ...
    Yue> term export_last {
    Yue> then {
    Yue> reject
    Yue> }
    Yue> }
    Yue> }

    Yue> bgp {
    Yue> bgp-id: 10.0.1.142
    Yue> import: "bgp_in"
    Yue> export: "bgp_out"
    Yue> local-as: 1257
    Yue> traceoptions {
    Yue> flag {
    Yue> all {
    Yue> disable: true
    Yue> }
    Yue> }
    Yue> }
    Yue> peer 10.0.1.141 {
    Yue> local-ip: 10.0.1.142
    Yue> as: 286
    Yue> next-hop: 10.0.1.142
    Yue> ipv4-multicast: false
    Yue> ipv6-unicast: false
    Yue> ipv6-multicast: false
    Yue> }
    Yue> ...
    Yue> }

    Yue> Could anyone give some clues? Thanks!

    Yue> _______________________________________________
    Yue> Xorp-users mailing list
    Yue> Xorp-users at xorp.org
    Yue> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From tsche at mitre.org  Thu May  1 11:52:00 2008
From: tsche at mitre.org (Che, Ting-Shuo T.)
Date: Thu, 1 May 2008 14:52:00 -0400
Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent?
In-Reply-To: <37014.1209663585@tigger.icir.org>
References: Message from "Che, Ting-Shuo T." <tsche@mitre.org>    of "Thu,
	01 May 2008 13:17:50 EDT."
	<9FDF44CB3E9C9943B656E85501CF36FA022BF957@IMCSRV1.MITRE.ORG>
	<37014.1209663585@tigger.icir.org>
Message-ID: <9FDF44CB3E9C9943B656E85501CF36FA022BF95B@IMCSRV1.MITRE.ORG>

Did not know whether it is the latest. The RELEASE_NOTES file (dated
March 5, 2008) 
indicates "Release 1.5-WIP" and "xorp/RELEASE_NOTES, v 1.198 2008/03/06
04:58:08 
Pavlin Exp". It was released in March to address OSPFv3/BGPv4
redistribution issues.

Is http://cvsweb.xorp.org/cgi-bin/cvsweb.cgi/xorp/VERSION the place to
browse or I 
have to follow http://www.xorp.org/cvs.html to check out the latest? In
general, are
you aware of this type of scalability concerns before?

Thank you very much.

Ting 

-----Original Message-----
From: atanu at icir.org [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh
Sent: Thursday, May 01, 2008 1:40 PM
To: Che, Ting-Shuo T.
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully
adjacent? 

Hi,

I don't understand why the log file has no content very strange.

Did you try using the latest code from CVS we have fixed may things
since the last release?

      Atanu.

>>>>> "Ting-Shuo" == Ting-Shuo T Che <Che> writes:

    Ting-Shuo> Did several more tests and found 20 OSPFv3 neighbors
also has problem
    Ting-Shuo> but not 15.

    Ting-Shuo> Attached is the "complete" log that uses the command
line you
    Ting-Shuo> recommended. Looks 
    Ting-Shuo> like there is no more messages than I have provided, no
matter
    Ting-Shuo> foreground or
    Ting-Shuo> background command, standard output or error
redirection, ... 

    Ting-Shuo> Please let me know if I miss anything or you have other
thoughts. Thank
    Ting-Shuo> you 
    Ting-Shuo> very much for the help.

    Ting-Shuo> Ting

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: Che, Ting-Shuo T. 
    Ting-Shuo> Sent: Tuesday, April 29, 2008 3:42 PM
    Ting-Shuo> To: 'atanu at icsi.berkeley.edu'
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: RE: [Xorp-users] No more than 25 OSPFv3
neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Thanks a lot for the guidance. I will do it ASAP. Indeed
the OSPFv3
    Ting-Shuo> process seems to "partially" exit 
    Ting-Shuo> and no longer functioning. What puzzled me was somehow
"ps -ef" show
    Ting-Shuo> xorp_ospfv3 still exists...

    Ting-Shuo> Ting

    Ting-Shuo> PS. 
    Ting-Shuo> root at 192.168.1.2> [ 2008/04/14 14:14:34  ERROR
xorp_rtrmgr:252 XRL +638
    Ting-Shuo> xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive
timeout
    Ting-Shuo> [ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
    Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response
211 Reply timed
    Ting-Shuo> out
    Ting-Shuo> [ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
    Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response
211 Reply timed
    Ting-Shuo> out
    Ting-Shuo> root at 192.168.1.2>
    Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor | match Full |
count
    Ting-Shuo> [ 2008/04/14 14:15:15  WARNING xorp_rtrmgr:252
XrlFinderTarget +406
    Ting-Shuo> ../xrl/targets/finder_base.cc
handle_finder_0_2_resolve_xrl ] Handling
    Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError
102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> Count: 0 lines
    Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor
    Ting-Shuo> [ 2008/04/14 14:15:36  WARNING xorp_rtrmgr:252
XrlFinderTarget +406
    Ting-Shuo> ../xrl/targets/finder_base.cc
handle_finder_0_2_resolve_xrl ] Handling
    Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError
102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> ERROR: Command
    Ting-Shuo>
"/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited
    Ting-Shuo> with exit status 255.
    Ting-Shuo> root at 192.168.1.2> exit

    Ting-Shuo> bash-3.00# date
    Ting-Shuo> Mon Apr 14 14:15:50 MEST 2008

    Ting-Shuo> bash-3.00# ps -ef | grep xorp
    Ting-Shuo> root       252   221  2 13:39 ?        00:01:01
./xorp_rtrmgr -b
    Ting-Shuo> ipv6ospf.boot
    Ting-Shuo> root       254   252  2 13:39 ?        00:00:51 xorp_fea
    Ting-Shuo> root       255   252  0 13:39 ?        00:00:03 xorp_rib
    Ting-Shuo> root       256   252  0 13:39 ?        00:00:03
xorp_policy
    Ting-Shuo> root       257   252 17 13:39 ?        00:06:26
xorp_ospfv3
    Ting-Shuo> root     24839   221  0 14:15 ?        00:00:00 grep
xorp

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: atanu at icir.org [mailto:atanu at icir.org] On Behalf
Of Atanu Ghosh
    Ting-Shuo> Sent: Tuesday, April 29, 2008 3:02 PM
    Ting-Shuo> To: Che, Ting-Shuo T.
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: Re: [Xorp-users] No more than 25 OSPFv3
neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Hi,

    Ting-Shuo> The OSPF process seems to have exited, typically the
XORP processes
    Ting-Shuo> will
    Ting-Shuo> print a message before exiting, it would be useful to
see this message.

    Ting-Shuo> Could you run the router manager in the background and
capture the
    Ting-Shuo> output, the following works for me with /bin/sh:
    Ting-Shuo> # ./xorp_rtrmgr -b ./ipv6ospf.boot > log 2>&1 &

    Ting-Shuo> If you are not already could you also try building from
CVS so that you
    Ting-Shuo> have all of the fixes.

    Ting-Shuo> Atanu.



From ssohn at gmu.edu  Thu May  1 12:08:37 2008
From: ssohn at gmu.edu (Eric Sohn)
Date: Thu, 01 May 2008 15:08:37 -0400
Subject: [Xorp-users] Question on OSPF setting
Message-ID: <001b01c8abbe$c2a99a10$47fcce30$@edu>

Hello,

 

My code is not quite working great.
I hope anybody can take a look at my codes and find some bugs if there is
in.

 

My connection is quite simple.

 

Source1 - R1 -R2 - Sink1

 

Symptom is ping sink1 from source1 is impossible and each router does not
have neighbor information in ospf database.

 

At R1 of xorp configuration, 

 

protocols {

    ospf4 {

        router-id: 10.1.1.2

        area 0.0.0.0 {

            interface eth2 {

                vif eth2 {

                        address 10.1.1.2

                }

            }

            interface eth4 {

                vif eth4 {

                        address 10.1.3.3

 

                }

            }

        }

    }

}

 

 

At R2

 

protocols {

    ospf4 {

        area 0.0.0.0 {

            interface eth4 {

                vif eth4 {

                        address 10.1.1.3

                }

            }

            interface eth2 {

                vif eth2 {

                        address 10.1.2.2

                }

            }

        }

        router-id: 10.1.1.3

    }

}

 

Two scripts are for routing itself and I didn't set anything for routing
(i.e., no policy, no static).

 

Is there anything wrong in this code ?

 

Eric

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080501/f955c634/attachment.html 

From atanu at ICSI.Berkeley.EDU  Thu May  1 15:10:11 2008
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Thu, 01 May 2008 15:10:11 -0700
Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent?
In-Reply-To: Message from "Che, Ting-Shuo T." <tsche@mitre.org> of "Thu,
	01 May 2008 14:52:00 EDT."
	<9FDF44CB3E9C9943B656E85501CF36FA022BF95B@IMCSRV1.MITRE.ORG> 
Message-ID: <71888.1209679811@tigger.icir.org>

Hi,

You should go to <http://www.xorp.org/cvs.html> and check out the latest
code.

Could you try the same experiment on a regular PC running XORP so we can
try and identify what the problem is.

    Atanu.

>>>>> "Ting-Shuo" == Ting-Shuo T Che <Che> writes:

    Ting-Shuo> Did not know whether it is the latest. The RELEASE_NOTES file (dated
    Ting-Shuo> March 5, 2008) 
    Ting-Shuo> indicates "Release 1.5-WIP" and "xorp/RELEASE_NOTES, v 1.198 2008/03/06
    Ting-Shuo> 04:58:08 
    Ting-Shuo> Pavlin Exp". It was released in March to address OSPFv3/BGPv4
    Ting-Shuo> redistribution issues.

    Ting-Shuo> Is http://cvsweb.xorp.org/cgi-bin/cvsweb.cgi/xorp/VERSION the place to
    Ting-Shuo> browse or I 
    Ting-Shuo> have to follow http://www.xorp.org/cvs.html to check out the latest? In
    Ting-Shuo> general, are
    Ting-Shuo> you aware of this type of scalability concerns before?

    Ting-Shuo> Thank you very much.

    Ting-Shuo> Ting 

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: atanu at icir.org [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh
    Ting-Shuo> Sent: Thursday, May 01, 2008 1:40 PM
    Ting-Shuo> To: Che, Ting-Shuo T.
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Hi,

    Ting-Shuo> I don't understand why the log file has no content very strange.

    Ting-Shuo> Did you try using the latest code from CVS we have fixed may things
    Ting-Shuo> since the last release?

    Ting-Shuo> Atanu.

>>>>> "Ting-Shuo" == Ting-Shuo T Che <Che> writes:

    Ting-Shuo> Did several more tests and found 20 OSPFv3 neighbors
    Ting-Shuo> also has problem
    Ting-Shuo> but not 15.

    Ting-Shuo> Attached is the "complete" log that uses the command
    Ting-Shuo> line you
    Ting-Shuo> recommended. Looks 
    Ting-Shuo> like there is no more messages than I have provided, no
    Ting-Shuo> matter
    Ting-Shuo> foreground or
    Ting-Shuo> background command, standard output or error
    Ting-Shuo> redirection, ... 

    Ting-Shuo> Please let me know if I miss anything or you have other
    Ting-Shuo> thoughts. Thank
    Ting-Shuo> you 
    Ting-Shuo> very much for the help.

    Ting-Shuo> Ting

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: Che, Ting-Shuo T. 
    Ting-Shuo> Sent: Tuesday, April 29, 2008 3:42 PM
    Ting-Shuo> To: 'atanu at icsi.berkeley.edu'
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: RE: [Xorp-users] No more than 25 OSPFv3
    Ting-Shuo> neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Thanks a lot for the guidance. I will do it ASAP. Indeed
    Ting-Shuo> the OSPFv3
    Ting-Shuo> process seems to "partially" exit 
    Ting-Shuo> and no longer functioning. What puzzled me was somehow
    Ting-Shuo> "ps -ef" show
    Ting-Shuo> xorp_ospfv3 still exists...

    Ting-Shuo> Ting

    Ting-Shuo> PS. 
    Ting-Shuo> root at 192.168.1.2> [ 2008/04/14 14:14:34  ERROR
    Ting-Shuo> xorp_rtrmgr:252 XRL +638
    Ting-Shuo> xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive
    Ting-Shuo> timeout
    Ting-Shuo> [ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
    Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response
    Ting-Shuo> 211 Reply timed
    Ting-Shuo> out
    Ting-Shuo> [ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
    Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response
    Ting-Shuo> 211 Reply timed
    Ting-Shuo> out
    Ting-Shuo> root at 192.168.1.2>
    Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor | match Full |
    Ting-Shuo> count
    Ting-Shuo> [ 2008/04/14 14:15:15  WARNING xorp_rtrmgr:252
    Ting-Shuo> XrlFinderTarget +406
    Ting-Shuo> ../xrl/targets/finder_base.cc
    Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling
    Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError
    Ting-Shuo> 102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> Count: 0 lines
    Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor
    Ting-Shuo> [ 2008/04/14 14:15:36  WARNING xorp_rtrmgr:252
    Ting-Shuo> XrlFinderTarget +406
    Ting-Shuo> ../xrl/targets/finder_base.cc
    Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling
    Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError
    Ting-Shuo> 102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> ERROR: Command
    Ting-Shuo> 
    Ting-Shuo> "/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited
    Ting-Shuo> with exit status 255.
    Ting-Shuo> root at 192.168.1.2> exit

    Ting-Shuo> bash-3.00# date
    Ting-Shuo> Mon Apr 14 14:15:50 MEST 2008

    Ting-Shuo> bash-3.00# ps -ef | grep xorp
    Ting-Shuo> root       252   221  2 13:39 ?        00:01:01
    Ting-Shuo> ./xorp_rtrmgr -b
    Ting-Shuo> ipv6ospf.boot
    Ting-Shuo> root       254   252  2 13:39 ?        00:00:51 xorp_fea
    Ting-Shuo> root       255   252  0 13:39 ?        00:00:03 xorp_rib
    Ting-Shuo> root       256   252  0 13:39 ?        00:00:03
    Ting-Shuo> xorp_policy
    Ting-Shuo> root       257   252 17 13:39 ?        00:06:26
    Ting-Shuo> xorp_ospfv3
    Ting-Shuo> root     24839   221  0 14:15 ?        00:00:00 grep
    Ting-Shuo> xorp

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: atanu at icir.org [mailto:atanu at icir.org] On Behalf
    Ting-Shuo> Of Atanu Ghosh
    Ting-Shuo> Sent: Tuesday, April 29, 2008 3:02 PM
    Ting-Shuo> To: Che, Ting-Shuo T.
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: Re: [Xorp-users] No more than 25 OSPFv3
    Ting-Shuo> neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Hi,

    Ting-Shuo> The OSPF process seems to have exited, typically the
    Ting-Shuo> XORP processes
    Ting-Shuo> will
    Ting-Shuo> print a message before exiting, it would be useful to
    Ting-Shuo> see this message.

    Ting-Shuo> Could you run the router manager in the background and
    Ting-Shuo> capture the
    Ting-Shuo> output, the following works for me with /bin/sh:
    Ting-Shuo> # ./xorp_rtrmgr -b ./ipv6ospf.boot > log 2>&1 &

    Ting-Shuo> If you are not already could you also try building from
    Ting-Shuo> CVS so that you
    Ting-Shuo> have all of the fixes.

    Ting-Shuo> Atanu.



From atanu at ICSI.Berkeley.EDU  Thu May  1 15:17:16 2008
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Thu, 01 May 2008 15:17:16 -0700
Subject: [Xorp-users] Question on OSPF setting
In-Reply-To: Message from Eric Sohn <ssohn@gmu.edu> of "Thu,
	01 May 2008 15:08:37 EDT." <001b01c8abbe$c2a99a10$47fcce30$@edu> 
Message-ID: <72949.1209680236@tigger.icir.org>

Hi,

Your config files also require an interfaces block, XORP will only use
interfaces that it has been configured to use.

interfaces {
    interface eth2 {
        vif eth2 {
            address 10.1.1.2 {
                prefix-length: 16
            }
        }
    }
}


       Atanu.

>>>>> "Eric" == Eric Sohn <ssohn at gmu.edu> writes:

    Eric> Hello,


    Eric> My code is not quite working great.
    Eric> I hope anybody can take a look at my codes and find some bugs if there
    Eric> is in.


    Eric> My connection is quite simple.


    Eric> Source1 - R1 -R2 - Sink1


    Eric> Symptom is ping sink1 from source1 is impossible and each router does
    Eric> not have neighbor information in ospf database.


    Eric> At R1 of xorp configuration,


    Eric> protocols {

    Eric> ospf4 {

    Eric> router-id: 10.1.1.2

    Eric> area 0.0.0.0 {

    Eric> interface eth2 {

    Eric> vif eth2 {

    Eric> address 10.1.1.2

    Eric> }

    Eric> }

    Eric> interface eth4 {

    Eric> vif eth4 {

    Eric> address 10.1.3.3


    Eric> }

    Eric> }

    Eric> }

    Eric> }

    Eric> }



    Eric> At R2


    Eric> protocols {

    Eric> ospf4 {

    Eric> area 0.0.0.0 {

    Eric> interface eth4 {

    Eric> vif eth4 {

    Eric> address 10.1.1.3

    Eric> }

    Eric> }

    Eric> interface eth2 {

    Eric> vif eth2 {

    Eric> address 10.1.2.2

    Eric> }

    Eric> }

    Eric> }

    Eric> router-id: 10.1.1.3

    Eric> }

    Eric> }


    Eric> Two scripts are for routing itself and I didn't set anything for
    Eric> routing (i.e., no policy, no static).


    Eric> Is there anything wrong in this code ?


    Eric> Eric
    Eric> _______________________________________________
    Eric> Xorp-users mailing list
    Eric> Xorp-users at xorp.org
    Eric> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From tsche at mitre.org  Thu May  1 15:18:32 2008
From: tsche at mitre.org (Che, Ting-Shuo T.)
Date: Thu, 1 May 2008 18:18:32 -0400
Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent?
In-Reply-To: <71888.1209679811@tigger.icir.org>
References: Message from "Che, Ting-Shuo T." <tsche@mitre.org>    of "Thu,
	01 May 2008 14:52:00 EDT."
	<9FDF44CB3E9C9943B656E85501CF36FA022BF95B@IMCSRV1.MITRE.ORG>
	<71888.1209679811@tigger.icir.org>
Message-ID: <9FDF44CB3E9C9943B656E85501CF36FA022BF973@IMCSRV1.MITRE.ORG>

Tried regular Linux PC and more neighbors could be supported but still
have issue eventually. Thinking about trying older but stable XORP
build. 
Would you recommend 1.4 (2007-03-20)?

Thank you very much.

Ting

-----Original Message-----
From: atanu at icir.org [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh
Sent: Thursday, May 01, 2008 6:10 PM
To: Che, Ting-Shuo T.
Cc: xorp-users at xorp.org
Subject: Re: [Xorp-users] No more than 25 OSPFv3 neighbors fully
adjacent? 

Hi,

You should go to <http://www.xorp.org/cvs.html> and check out the
latest
code.

Could you try the same experiment on a regular PC running XORP so we
can
try and identify what the problem is.

    Atanu.

>>>>> "Ting-Shuo" == Ting-Shuo T Che <Che> writes:

    Ting-Shuo> Did not know whether it is the latest. The RELEASE_NOTES
file (dated
    Ting-Shuo> March 5, 2008) 
    Ting-Shuo> indicates "Release 1.5-WIP" and "xorp/RELEASE_NOTES, v
1.198 2008/03/06
    Ting-Shuo> 04:58:08 
    Ting-Shuo> Pavlin Exp". It was released in March to address
OSPFv3/BGPv4
    Ting-Shuo> redistribution issues.

    Ting-Shuo> Is
http://cvsweb.xorp.org/cgi-bin/cvsweb.cgi/xorp/VERSION the place to
    Ting-Shuo> browse or I 
    Ting-Shuo> have to follow http://www.xorp.org/cvs.html to check out
the latest? In
    Ting-Shuo> general, are
    Ting-Shuo> you aware of this type of scalability concerns before?

    Ting-Shuo> Thank you very much.

    Ting-Shuo> Ting 

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: atanu at icir.org [mailto:atanu at icir.org] On Behalf
Of Atanu Ghosh
    Ting-Shuo> Sent: Thursday, May 01, 2008 1:40 PM
    Ting-Shuo> To: Che, Ting-Shuo T.
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: Re: [Xorp-users] No more than 25 OSPFv3
neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Hi,

    Ting-Shuo> I don't understand why the log file has no content very
strange.

    Ting-Shuo> Did you try using the latest code from CVS we have fixed
may things
    Ting-Shuo> since the last release?

    Ting-Shuo> Atanu.

>>>>> "Ting-Shuo" == Ting-Shuo T Che <Che> writes:

    Ting-Shuo> Did several more tests and found 20 OSPFv3 neighbors
    Ting-Shuo> also has problem
    Ting-Shuo> but not 15.

    Ting-Shuo> Attached is the "complete" log that uses the command
    Ting-Shuo> line you
    Ting-Shuo> recommended. Looks 
    Ting-Shuo> like there is no more messages than I have provided, no
    Ting-Shuo> matter
    Ting-Shuo> foreground or
    Ting-Shuo> background command, standard output or error
    Ting-Shuo> redirection, ... 

    Ting-Shuo> Please let me know if I miss anything or you have other
    Ting-Shuo> thoughts. Thank
    Ting-Shuo> you 
    Ting-Shuo> very much for the help.

    Ting-Shuo> Ting

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: Che, Ting-Shuo T. 
    Ting-Shuo> Sent: Tuesday, April 29, 2008 3:42 PM
    Ting-Shuo> To: 'atanu at icsi.berkeley.edu'
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: RE: [Xorp-users] No more than 25 OSPFv3
    Ting-Shuo> neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Thanks a lot for the guidance. I will do it ASAP. Indeed
    Ting-Shuo> the OSPFv3
    Ting-Shuo> process seems to "partially" exit 
    Ting-Shuo> and no longer functioning. What puzzled me was somehow
    Ting-Shuo> "ps -ef" show
    Ting-Shuo> xorp_ospfv3 still exists...

    Ting-Shuo> Ting

    Ting-Shuo> PS. 
    Ting-Shuo> root at 192.168.1.2> [ 2008/04/14 14:14:34  ERROR
    Ting-Shuo> xorp_rtrmgr:252 XRL +638
    Ting-Shuo> xrl_pf_stcp.cc die ] XrlPFSTCPSender died: Keepalive
    Ting-Shuo> timeout
    Ting-Shuo> [ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
    Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response
    Ting-Shuo> 211 Reply timed
    Ting-Shuo> out
    Ting-Shuo> [ 2008/04/14 14:14:48  ERROR xorp_rtrmgr:252 FINDER +85
    Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response
    Ting-Shuo> 211 Reply timed
    Ting-Shuo> out
    Ting-Shuo> root at 192.168.1.2>
    Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor | match Full |
    Ting-Shuo> count
    Ting-Shuo> [ 2008/04/14 14:15:15  WARNING xorp_rtrmgr:252
    Ting-Shuo> XrlFinderTarget +406
    Ting-Shuo> ../xrl/targets/finder_base.cc
    Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling
    Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError
    Ting-Shuo> 102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> Count: 0 lines
    Ting-Shuo> root at 192.168.1.2> show ospf6 neighbor
    Ting-Shuo> [ 2008/04/14 14:15:36  WARNING xorp_rtrmgr:252
    Ting-Shuo> XrlFinderTarget +406
    Ting-Shuo> ../xrl/targets/finder_base.cc
    Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling
    Ting-Shuo> method for finder/0.2/resolve_xrl failed: XrlCmdError
    Ting-Shuo> 102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> ERROR: Command
    Ting-Shuo> 
    Ting-Shuo>
"/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours": exited
    Ting-Shuo> with exit status 255.
    Ting-Shuo> root at 192.168.1.2> exit

    Ting-Shuo> bash-3.00# date
    Ting-Shuo> Mon Apr 14 14:15:50 MEST 2008

    Ting-Shuo> bash-3.00# ps -ef | grep xorp
    Ting-Shuo> root       252   221  2 13:39 ?        00:01:01
    Ting-Shuo> ./xorp_rtrmgr -b
    Ting-Shuo> ipv6ospf.boot
    Ting-Shuo> root       254   252  2 13:39 ?        00:00:51 xorp_fea
    Ting-Shuo> root       255   252  0 13:39 ?        00:00:03 xorp_rib
    Ting-Shuo> root       256   252  0 13:39 ?        00:00:03
    Ting-Shuo> xorp_policy
    Ting-Shuo> root       257   252 17 13:39 ?        00:06:26
    Ting-Shuo> xorp_ospfv3
    Ting-Shuo> root     24839   221  0 14:15 ?        00:00:00 grep
    Ting-Shuo> xorp

    Ting-Shuo> -----Original Message-----
    Ting-Shuo> From: atanu at icir.org [mailto:atanu at icir.org] On Behalf
    Ting-Shuo> Of Atanu Ghosh
    Ting-Shuo> Sent: Tuesday, April 29, 2008 3:02 PM
    Ting-Shuo> To: Che, Ting-Shuo T.
    Ting-Shuo> Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: Re: [Xorp-users] No more than 25 OSPFv3
    Ting-Shuo> neighbors fully
    Ting-Shuo> adjacent? 

    Ting-Shuo> Hi,

    Ting-Shuo> The OSPF process seems to have exited, typically the
    Ting-Shuo> XORP processes
    Ting-Shuo> will
    Ting-Shuo> print a message before exiting, it would be useful to
    Ting-Shuo> see this message.

    Ting-Shuo> Could you run the router manager in the background and
    Ting-Shuo> capture the
    Ting-Shuo> output, the following works for me with /bin/sh:
    Ting-Shuo> # ./xorp_rtrmgr -b ./ipv6ospf.boot > log 2>&1 &

    Ting-Shuo> If you are not already could you also try building from
    Ting-Shuo> CVS so that you
    Ting-Shuo> have all of the fixes.

    Ting-Shuo> Atanu.




From atanu at ICSI.Berkeley.EDU  Thu May  1 15:24:31 2008
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Thu, 01 May 2008 15:24:31 -0700
Subject: [Xorp-users] No more than 25 OSPFv3 neighbors fully adjacent?
In-Reply-To: Message from "Che, Ting-Shuo T." <tsche@mitre.org> of "Thu,
	01 May 2008 18:18:32 EDT."
	<9FDF44CB3E9C9943B656E85501CF36FA022BF973@IMCSRV1.MITRE.ORG> 
Message-ID: <74011.1209680671@tigger.icir.org>

Hi,

I would recommend using the latest code in CVS we have fixed a number of
things since the last release.

If you still see a problem could you please send the output generated by
the router mananger.

    Atanu.

>>>>> "Ting-Shuo" == Ting-Shuo T Che <Che> writes:

    Ting-Shuo> Tried regular Linux PC and more neighbors could be
    Ting-Shuo> supported but still have issue eventually. Thinking about
    Ting-Shuo> trying older but stable XORP build.  Would you recommend
    Ting-Shuo> 1.4 (2007-03-20)?

    Ting-Shuo> Thank you very much.

    Ting-Shuo> Ting

    Ting-Shuo> -----Original Message----- From: atanu at icir.org
    Ting-Shuo> [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh Sent:
    Ting-Shuo> Thursday, May 01, 2008 6:10 PM To: Che, Ting-Shuo T.  Cc:
    Ting-Shuo> xorp-users at xorp.org Subject: Re: [Xorp-users] No more
    Ting-Shuo> than 25 OSPFv3 neighbors fully adjacent?

    Ting-Shuo> Hi,

    Ting-Shuo> You should go to <http://www.xorp.org/cvs.html> and check
    Ting-Shuo> out the latest code.

    Ting-Shuo> Could you try the same experiment on a regular PC running
    Ting-Shuo> XORP so we can try and identify what the problem is.

    Ting-Shuo>     Atanu.

>>>>> "Ting-Shuo" == Ting-Shuo T Che <Che> writes:

    Ting-Shuo> Did not know whether it is the latest. The RELEASE_NOTES
    Ting-Shuo> file (dated March 5, 2008) indicates "Release 1.5-WIP"
    Ting-Shuo> and "xorp/RELEASE_NOTES, v 1.198 2008/03/06 04:58:08
    Ting-Shuo> Pavlin Exp". It was released in March to address
    Ting-Shuo> OSPFv3/BGPv4 redistribution issues.

    Ting-Shuo> Is http://cvsweb.xorp.org/cgi-bin/cvsweb.cgi/xorp/VERSION
    Ting-Shuo> the place to browse or I have to follow
    Ting-Shuo> http://www.xorp.org/cvs.html to check out the latest? In
    Ting-Shuo> general, are you aware of this type of scalability
    Ting-Shuo> concerns before?

    Ting-Shuo> Thank you very much.

    Ting-Shuo> Ting

    Ting-Shuo> -----Original Message----- From: atanu at icir.org
    Ting-Shuo> [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh Sent:
    Ting-Shuo> Thursday, May 01, 2008 1:40 PM To: Che, Ting-Shuo T.  Cc:
    Ting-Shuo> xorp-users at xorp.org Subject: Re: [Xorp-users] No more
    Ting-Shuo> than 25 OSPFv3 neighbors fully adjacent?

    Ting-Shuo> Hi,

    Ting-Shuo> I don't understand why the log file has no content very
    Ting-Shuo> strange.

    Ting-Shuo> Did you try using the latest code from CVS we have fixed
    Ting-Shuo> may things since the last release?

    Ting-Shuo> Atanu.

>>>>> "Ting-Shuo" == Ting-Shuo T Che <Che> writes:

    Ting-Shuo> Did several more tests and found 20 OSPFv3 neighbors also
    Ting-Shuo> has problem but not 15.

    Ting-Shuo> Attached is the "complete" log that uses the command line
    Ting-Shuo> you recommended. Looks like there is no more messages
    Ting-Shuo> than I have provided, no matter foreground or background
    Ting-Shuo> command, standard output or error redirection, ...

    Ting-Shuo> Please let me know if I miss anything or you have other
    Ting-Shuo> thoughts. Thank you very much for the help.

    Ting-Shuo> Ting

    Ting-Shuo> -----Original Message----- From: Che, Ting-Shuo T.  Sent:
    Ting-Shuo> Tuesday, April 29, 2008 3:42 PM To:
    Ting-Shuo> 'atanu at icsi.berkeley.edu' Cc: xorp-users at xorp.org
    Ting-Shuo> Subject: RE: [Xorp-users] No more than 25 OSPFv3
    Ting-Shuo> neighbors fully adjacent?

    Ting-Shuo> Thanks a lot for the guidance. I will do it ASAP. Indeed
    Ting-Shuo> the OSPFv3 process seems to "partially" exit and no
    Ting-Shuo> longer functioning. What puzzled me was somehow "ps -ef"
    Ting-Shuo> show xorp_ospfv3 still exists...

    Ting-Shuo> Ting

    Ting-Shuo> PS.  root at 192.168.1.2> [ 2008/04/14 14:14:34 ERROR
    Ting-Shuo> xorp_rtrmgr:252 XRL +638 xrl_pf_stcp.cc die ]
    Ting-Shuo> XrlPFSTCPSender died: Keepalive timeout [ 2008/04/14
    Ting-Shuo> 14:14:48 ERROR xorp_rtrmgr:252 FINDER +85
    Ting-Shuo> finder_xrl_queue.hh dispatch_cb ] Sent xrl got response
    Ting-Shuo> 211 Reply timed out [ 2008/04/14 14:14:48 ERROR
    Ting-Shuo> xorp_rtrmgr:252 FINDER +85 finder_xrl_queue.hh
    Ting-Shuo> dispatch_cb ] Sent xrl got response 211 Reply timed out
    Ting-Shuo> root at 192.168.1.2> root at 192.168.1.2> show ospf6 neighbor |
    Ting-Shuo> match Full | count [ 2008/04/14 14:15:15 WARNING
    Ting-Shuo> xorp_rtrmgr:252 XrlFinderTarget +406
    Ting-Shuo> ../xrl/targets/finder_base.cc
    Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling method for
    Ting-Shuo> finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> Count: 0 lines root at 192.168.1.2> show ospf6 neighbor [
    Ting-Shuo> 2008/04/14 14:15:36 WARNING xorp_rtrmgr:252
    Ting-Shuo> XrlFinderTarget +406 ../xrl/targets/finder_base.cc
    Ting-Shuo> handle_finder_0_2_resolve_xrl ] Handling method for
    Ting-Shuo> finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
    Ting-Shuo> failed Target "ospfv3" does not exist or is not enabled.
    Ting-Shuo> ERROR: Command
    Ting-Shuo> 
    Ting-Shuo> 
    Ting-Shuo> "/opt/embedded/tools/ppc_85xx/usr/ospf/tools/print_neighbours":
    Ting-Shuo> exited with exit status 255.  root at 192.168.1.2> exit

    Ting-Shuo> bash-3.00# date Mon Apr 14 14:15:50 MEST 2008

    Ting-Shuo> bash-3.00# ps -ef | grep xorp root 252 221 2 13:39 ?
    Ting-Shuo> 00:01:01 ./xorp_rtrmgr -b ipv6ospf.boot root 254 252 2
    Ting-Shuo> 13:39 ?  00:00:51 xorp_fea root 255 252 0 13:39 ?
    Ting-Shuo> 00:00:03 xorp_rib root 256 252 0 13:39 ?  00:00:03
    Ting-Shuo> xorp_policy root 257 252 17 13:39 ?  00:06:26 xorp_ospfv3
    Ting-Shuo> root 24839 221 0 14:15 ?  00:00:00 grep xorp

    Ting-Shuo> -----Original Message----- From: atanu at icir.org
    Ting-Shuo> [mailto:atanu at icir.org] On Behalf Of Atanu Ghosh Sent:
    Ting-Shuo> Tuesday, April 29, 2008 3:02 PM To: Che, Ting-Shuo T.
    Ting-Shuo> Cc: xorp-users at xorp.org Subject: Re: [Xorp-users] No more
    Ting-Shuo> than 25 OSPFv3 neighbors fully adjacent?

    Ting-Shuo> Hi,

    Ting-Shuo> The OSPF process seems to have exited, typically the XORP
    Ting-Shuo> processes will print a message before exiting, it would
    Ting-Shuo> be useful to see this message.

    Ting-Shuo> Could you run the router manager in the background and
    Ting-Shuo> capture the output, the following works for me with
    Ting-Shuo> /bin/sh: # ./xorp_rtrmgr -b ./ipv6ospf.boot > log 2>&1 &

    Ting-Shuo> If you are not already could you also try building from
    Ting-Shuo> CVS so that you have all of the fixes.

    Ting-Shuo> Atanu.




From markryde at gmail.com  Mon May  5 00:55:52 2008
From: markryde at gmail.com (Mark Ryden)
Date: Mon, 5 May 2008 10:55:52 +0300
Subject: [Xorp-users] Error: 102 Command failed Cannot enable vif
	register_vif: no such vif (newbie)
Message-ID: <dac45060805050055i3e3f5389t3bc738e5c70eae2@mail.gmail.com>

Hello,
I am using xorp-1.4, build from sources tar file.
  I had tried to configure rtrmgr/config.boot  and start  xorp_rtrmgr
and I get the following  "102 Command failed Cannot enable vif
register_vif: no such vif" error
Here is the full log and the config.boot file ; I appreciate if
somebody can help.

./xorp_rtrmgr

./xorp_rtrmgr
[ 2008/05/05 10:26:24  INFO xorp_rtrmgr:28400 RTRMGR +239
master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4,
rib, fib2mrib, igmp, pimsm4, policy, static_routes
[ 2008/05/05 10:26:24  INFO xorp_rtrmgr:28400 RTRMGR +96
module_manager.cc execute ] Executing module: interfaces
(fea/xorp_fea)
[ 2008/05/05 10:26:24 INFO xorp_fea MFEA ] MFEA enabled
[ 2008/05/05 10:26:24 INFO xorp_fea MFEA ] CLI enabled
[ 2008/05/05 10:26:24 INFO xorp_fea MFEA ] CLI started
[ 2008/05/05 10:26:24 INFO xorp_fea MFEA ] MFEA enabled
[ 2008/05/05 10:26:24 INFO xorp_fea MFEA ] CLI enabled
[ 2008/05/05 10:26:24 INFO xorp_fea MFEA ] CLI started
[ 2008/05/05 10:26:26  INFO xorp_rtrmgr:28400 RTRMGR +96
module_manager.cc execute ] Executing module: fea (fea/xorp_fea)
[ 2008/05/05 10:26:32  INFO xorp_rtrmgr:28400 RTRMGR +96
module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea)
[ 2008/05/05 10:26:32 INFO xorp_fea MFEA ] Interface added: Vif[eth0]
pif_index: 2 vif_index: 0 addr: 192.168.0.54 subnet: 192.168.0.0/24
broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST
UNDERLYING_VIF_UP MTU: 1500
[ 2008/05/05 10:26:32 INFO xorp_fea MFEA ] MFEA started
[ 2008/05/05 10:26:33  INFO xorp_rtrmgr:28400 RTRMGR +96
module_manager.cc execute ] Executing module: rib (rib/xorp_rib)
[ 2008/05/05 10:26:35  INFO xorp_rtrmgr:28400 RTRMGR +96
module_manager.cc execute ] Executing module: fib2mrib
(fib2mrib/xorp_fib2mrib)
[ 2008/05/05 10:26:37  INFO xorp_rtrmgr:28400 RTRMGR +96
module_manager.cc execute ] Executing module: igmp
(mld6igmp/xorp_igmp)
[ 2008/05/05 10:26:37  WARNING xorp_rtrmgr:28400 XrlFinderTarget +406
../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
failed Target "IGMP" does not exist or is not enabled.
[ 2008/05/05 10:26:37 INFO xorp_igmp MLD6IGMP ] Protocol enabled
[ 2008/05/05 10:26:37 INFO xorp_igmp MLD6IGMP ] CLI enabled
[ 2008/05/05 10:26:37 INFO xorp_igmp MLD6IGMP ] CLI started
[ 2008/05/05 10:26:38 INFO xorp_igmp MLD6IGMP ] Interface added:
Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.54 subnet:
192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2008/05/05 10:26:38 INFO xorp_igmp MLD6IGMP ] Protocol started
[ 2008/05/05 10:26:39 INFO xorp_igmp MLD6IGMP ] Interface enabled:
Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.54 subnet:
192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2008/05/05 10:26:39 INFO xorp_igmp MLD6IGMP ] Interface started:
Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.54 subnet:
192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2008/05/05 10:26:39  INFO xorp_rtrmgr:28400 RTRMGR +96
module_manager.cc execute ] Executing module: pimsm4 (pim/xorp_pimsm4)
[ 2008/05/05 10:26:39  WARNING xorp_rtrmgr:28400 XrlFinderTarget +406
../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
failed Target "PIMSM_4" does not exist or is not enabled.
[ 2008/05/05 10:26:39 WARNING xorp_fea XrlMfeaTarget ] Handling method
for mfea/0.1/send_protocol_message4 failed: XrlCmdError 102 Command
failed Cannot send IGMP protocol message from 192.168.0.54 to
224.0.0.1 on vif eth0: Vif eth0 is DOWN
[ 2008/05/05 10:26:39  ERROR xorp_igmp:28404 MLD6IGMP +1519
xrl_mld6igmp_node.cc mfea_client_send_protocol_message_cb ] Cannot
send a protocol message: 102 Command failed Cannot send IGMP protocol
message from 192.168.0.54 to 224.0.0.1 on vif eth0: Vif eth0 is DOWN
[ 2008/05/05 10:26:39 INFO xorp_pimsm4 PIM ] Protocol enabled
[ 2008/05/05 10:26:39 INFO xorp_pimsm4 PIM ] CLI enabled
[ 2008/05/05 10:26:39 INFO xorp_pimsm4 PIM ] CLI started
[ 2008/05/05 10:26:40 INFO xorp_pimsm4 PIM ] Interface added:
Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.54 subnet:
192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500
[ 2008/05/05 10:26:40 INFO xorp_pimsm4 PIM ] Protocol started
[ 2008/05/05 10:26:41 INFO xorp_pimsm4 PIM ] Interface enabled:
Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.54 subnet:
192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED
[ 2008/05/05 10:26:41 INFO xorp_pimsm4 PIM ] Interface started:
Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.54 subnet:
192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST
BROADCAST UNDERLYING_VIF_UP MTU: 1500 UP IPv4 ENABLED
[ 2008/05/05 10:26:41  ERROR xorp_pimsm4:28405 PIM +797 pim_node.cc
enable_vif ] Cannot enable vif register_vif: no such vif
[ 2008/05/05 10:26:41 WARNING xorp_pimsm4 XrlPimTarget ] Handling
method for pim/0.1/enable_vif failed: XrlCmdError 102 Command failed
Cannot enable vif register_vif: no such vif
[ 2008/05/05 10:26:41  ERROR xorp_rtrmgr:28400 RTRMGR +675
master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command
failed Cannot enable vif register_vif: no such vif
[ 2008/05/05 10:26:41  ERROR xorp_rtrmgr:28400 RTRMGR +251
master_conf_tree.cc config_done ] Configuration failed: 102 Command
failed Cannot enable vif register_vif: no such vif
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +2228 task.cc
run_task ] No more tasks to run
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +171
module_manager.cc terminate ] Terminating module: fea
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +171
module_manager.cc terminate ] Terminating module: fib2mrib
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +194
module_manager.cc terminate ] Killing module: fib2mrib
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +171
module_manager.cc terminate ] Terminating module: igmp
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +194
module_manager.cc terminate ] Killing module: igmp
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +171
module_manager.cc terminate ] Terminating module: interfaces
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +171
module_manager.cc terminate ] Terminating module: mfea4
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +194
module_manager.cc terminate ] Killing module: mfea4
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +171
module_manager.cc terminate ] Terminating module: pimsm4
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +194
module_manager.cc terminate ] Killing module: pimsm4
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +171
module_manager.cc terminate ] Terminating module: rib
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +194
module_manager.cc terminate ] Killing module: rib
[ 2008/05/05 10:26:41  ERROR xorp_rtrmgr:28400 RTRMGR +747
module_manager.cc done_cb ] Command
"/src1/xorp-1.4/fib2mrib/xorp_fib2mrib": terminated with signal 15.
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +282
module_manager.cc module_exited ] Module killed during shutdown:
fib2mrib
[ 2008/05/05 10:26:41  ERROR xorp_rtrmgr:28400 RTRMGR +747
module_manager.cc done_cb ] Command "/src1/xorp-1.4/rib/xorp_rib":
terminated with signal 15.
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +282
module_manager.cc module_exited ] Module killed during shutdown: rib
[ 2008/05/05 10:26:41  ERROR xorp_rtrmgr:28400 LIBXORP +533 asyncio.cc
complete_transfer ] Write error 104
[ 2008/05/05 10:26:41  ERROR xorp_rtrmgr:28400 LIBXORP +533 asyncio.cc
complete_transfer ] Write error 104
[ 2008/05/05 10:26:41  ERROR xorp_rtrmgr:28400 RTRMGR +747
module_manager.cc done_cb ] Command "/src1/xorp-1.4/fea/xorp_fea":
terminated with signal 15.
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +282
module_manager.cc module_exited ] Module killed during shutdown: mfea4
[ 2008/05/05 10:26:41  ERROR xorp_rtrmgr:28400 RTRMGR +747
module_manager.cc done_cb ] Command "/src1/xorp-1.4/pim/xorp_pimsm4":
terminated with signal 15.
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +282
module_manager.cc module_exited ] Module killed during shutdown:
pimsm4
[ 2008/05/05 10:26:41  ERROR xorp_rtrmgr:28400 RTRMGR +747
module_manager.cc done_cb ] Command
"/src1/xorp-1.4/mld6igmp/xorp_igmp": terminated with signal 15.
[ 2008/05/05 10:26:41  INFO xorp_rtrmgr:28400 RTRMGR +282
module_manager.cc module_exited ] Module killed during shutdown: igmp


 rtrmgr/config.boot
======================
/* $XORP: xorp/rtrmgr/config.boot.sample,v 1.46 2007/03/12 10:16:05
atanu Exp $ */


interfaces {
    restore-original-config-on-shutdown: false
    interface eth0 {
	description: "data interface"
	disable: false
	/* default-system-config */
	vif eth0 {
	    disable: false
	    address 192.168.0.54 {
		prefix-length: 24
		broadcast: 192.168.0.255
		disable: false
	    }
/*
	    address 10:10:10:10:10:10:10:10 {
		prefix-length: 64
		disable: false
	    }
*/
/*
	    address fe80::1 {
		prefix-length: 64
		disable: false
	    }
*/
	}
    }

}

fea {
    unicast-forwarding4 {
	disable: false
	forwarding-entries {
	    retain-on-startup: false
	    retain-on-shutdown:	false
	}
    }
/*
    unicast-forwarding6 {
	disable: false
	forwarding-entries {
	    retain-on-startup: false
	    retain-on-shutdown:	false
	}
    }
*/

}

protocols {
    static {
	route 10.20.0.0/16 {
	    next-hop: 10.10.10.20
	    metric: 1
/*
	    qualified-next-hop 172.17.0.2 {
		metric: 10
	    }
*/
	}
	mrib-route 10.20.0.0/16 {
	    next-hop: 10.10.10.30
	    metric: 1
	}
/*
	route 20:20:20:20::/64 {
	    next-hop: 10:10:10:10:10:10:10:20
	    metric: 1
	}
	mrib-route 20:20:20:20::/64 {
	    next-hop: 10:10:10:10:10:10:10:30
	    metric: 1
	}
*/
    }
}

policy {
    /* Describe connected routes for redistribution */
    policy-statement connected {
	term export {
	    from {
		protocol: "connected"
	    }
	}
    }
}

policy {
    /* Describe static routes for redistribution */
    policy-statement static {
	term export {
	    from {
		protocol: "static"
	    }
	}
    }
}


protocols {
    igmp {
	disable: false
	interface eth0 {
	    vif eth0 {
		disable: false
		/* version: 2 */
		/* enable-ip-router-alert-option-check: false */
		/* query-interval: 125 */
		/* query-last-member-interval: 1 */
		/* query-response-interval: 10 */
		/* robust-count: 2 */
	    }
	}
	traceoptions {
	    flag all {
		disable: false
	    }
	}
    }
/*
    mld {
	disable: false
	interface eth0 {
	    vif eth0 {
		disable: false
		version: 1
		enable-ip-router-alert-option-check: false
		query-interval: 125
		query-last-member-interval: 1
		query-response-interval: 10
		robust-count: 2
	    }
	}
	traceoptions {
	    flag all {
		disable: false
	    }
	}
    }
*/
}

protocols {
    pimsm4 {
	disable: false
	interface eth0 {
	    vif eth0 {
		disable: false
		/* enable-ip-router-alert-option-check: false */
		/* dr-priority: 1 */
		/* hello-period: 30 */
		/* hello-triggered-delay: 5 */
		/* alternative-subnet 10.40.0.0/16 */
	    }
	}
	interface register_vif {
	    vif register_vif {
		/* Note: this vif should be always enabled */
		disable: false
	    }
	}

	static-rps {
	    rp 10.60.0.1 {
		group-prefix 224.0.0.0/4 {
		    /* rp-priority: 192 */
		    /* hash-mask-len: 30 */
		}
	    }
	}

	bootstrap {
	    disable: false
	    cand-bsr {
		scope-zone 224.0.0.0/4 {
		    /* is-scope-zone: false */
		    cand-bsr-by-vif-name: "eth0"
		    /* cand-bsr-by-vif-addr: 10.10.10.10 */
		    /* bsr-priority: 1 */
		    /* hash-mask-len: 30 */
		}
	    }

	    cand-rp {
		group-prefix 224.0.0.0/4 {
		    /* is-scope-zone: false */
		    cand-rp-by-vif-name: "eth0"
		    /* cand-rp-by-vif-addr: 10.10.10.10 */
		    /* rp-priority: 192 */
		    /* rp-holdtime: 150 */
		}
	    }
	}

	switch-to-spt-threshold {
	    /* approx. 1K bytes/s (10Kbps) threshold */
	    disable: false
	    interval: 100
	    bytes: 102400
	}

	traceoptions {
	    flag all {
		disable: false
	    }
	}
    }

/*
    pimsm6 {
	disable: false
	interface eth0 {
	    vif eth0 {
		disable: false
		enable-ip-router-alert-option-check: false
		dr-priority: 1
		hello-period: 30
		hello-triggered-delay: 5
		alternative-subnet 40:40:40:40::/64
	    }
	}
	interface register_vif {
	    vif register_vif {
		disable: false
	    }
	}

	static-rps {
	    rp 50:50:50:50:50:50:50:50 {
		group-prefix ff00::/8 {
		    rp-priority: 192
		    hash-mask-len: 126
		}
	    }
	}

	bootstrap {
	    disable: false
	    cand-bsr {
		scope-zone ff00::/8 {
		    is-scope-zone: false
		    cand-bsr-by-vif-name: "eth0"
		    cand-bsr-by-vif-addr: 10:10:10:10:10:10:10:10
		    bsr-priority: 1
		    hash-mask-len: 126
		}
	    }

	    cand-rp {
		group-prefix ff00::/8 {
		    is-scope-zone: false
		    cand-rp-by-vif-name: "eth0"
		    cand-rp-by-vif-addr: 10:10:10:10:10:10:10:10
		    rp-priority: 192
		    rp-holdtime: 150
		}
	    }
	}

	switch-to-spt-threshold {
	    disable: false
	    interval: 100
	    bytes: 102400
	}

	traceoptions {
	    flag all {
		disable: false
	    }
	}
    }
*/
}

/*
 * Note: fib2mrib is needed for multicast only if the unicast protocols
 * don't populate the MRIB with multicast-specific routes.
 */
protocols {
    fib2mrib {
	disable: false
    }
}



/*
 * See xorp/mibs/snmpdscripts/README on how to configure Net-SNMP in your host
 * before uncommenting the snmp section below.
 * Also check that the "bgp4_mib_1657.so" exists in the correct location.
 */

/*
protocols {
    snmp {
	mib-module bgp4_mib_1657 {
	    abs-path: "/usr/local/xorp/mibs/bgp4_mib_1657.so"
	}
    }
}
*/

Regards,
Mark Ryden


From rosenrami at gmail.com  Mon May  5 07:05:22 2008
From: rosenrami at gmail.com (Rami Rosen)
Date: Mon, 5 May 2008 17:05:22 +0300
Subject: [Xorp-users] Error: 102 Command failed Cannot enable vif
	register_vif: no such vif (newbie)
Message-ID: <ae5426fb0805050705x64948f59tce5e509f2859d6c4@mail.gmail.com>

Hi,

 It seems to me that this error is caused because  the "plumbing"
entry is missing; please try with the plumbing entry.

Regards,
Rami Rosen


From pavlin at ICSI.Berkeley.EDU  Mon May  5 08:22:32 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Mon, 05 May 2008 08:22:32 -0700
Subject: [Xorp-users] Error: 102 Command failed Cannot enable vif
	register_vif: no such vif (newbie)
In-Reply-To: <dac45060805050055i3e3f5389t3bc738e5c70eae2@mail.gmail.com> 
References: <dac45060805050055i3e3f5389t3bc738e5c70eae2@mail.gmail.com>
Message-ID: <200805051522.m45FMWiA025807@fruitcake.ICSI.Berkeley.EDU>

Mark Ryden <markryde at gmail.com> wrote:

> Hello,
> I am using xorp-1.4, build from sources tar file.
>   I had tried to configure rtrmgr/config.boot  and start  xorp_rtrmgr
> and I get the following  "102 Command failed Cannot enable vif
> register_vif: no such vif" error
> Here is the full log and the config.boot file ; I appreciate if
> somebody can help.

You need to configure the MFEA as well. E.g.:

plumbing {
    mfea4 {
        interface eth0 {
            vif eth0 {
                disable: false
            }
        }
        interface register_vif {
            vif register_vif {
                /* Note: this vif should be always enabled */
                disable: false
            }
        }
    }
}

Pavlin


From libin020989 at sohu.com  Wed May  7 03:07:50 2008
From: libin020989 at sohu.com (=?gb2312?B?wO6x8g==?=)
Date: Wed, 7 May 2008 18:07:50 +0800
Subject: [Xorp-users] can not receive multicast data packet
Message-ID: <200805071754482960252@sohu.com>

I'm using xorp to build a network,xorp connects to a multicast source and a multicast receiver,when I send UDP packets on the source,I can not receive the packets on the receiver,I can not find the reason,
Here is the xorp's state

root at netbsd> show igmp group 
IF     Group           Source          LastReported Timeout V  S    v1T    v2T
rtk0   224.3.3.20      0.0.0.0         192.168.111.100     145 3  E     0     0
root at netbsd> show pim mfc 
Group           Source          RP             
224.3.3.20      192.168.222.35  14.14.14.14    
    Incoming interface :      bce0
    Outgoing interfaces:      .O.
root at netbsd> show pim join 
Group           Source          RP              Flags
224.3.3.20      0.0.0.0         14.14.14.14     WC   
    Upstream interface (RP):   bce0
    Upstream MRIB next hop (RP): 192.168.55.1
    Upstream RPF'(*,G):        192.168.55.1
    Upstream state:            Joined 
    Join timer:                32
    Local receiver include WC: .O.
    Joins RP:                  ...
    Joins WC:                  ...
    Join state:                ...
    Prune state:               ...
    Prune pending state:       ...
    I am assert winner state:  ...
    I am assert loser state:   ...
    Assert winner WC:          ...
    Assert lost WC:            ...
    Assert tracking WC:        OO.
    Could assert WC:           .O.
    I am DR:                   .OO
    Immediate olist RP:        ...
    Immediate olist WC:        .O.
    Inherited olist SG:        .O.
    Inherited olist SG_RPT:    .O.
    PIM include WC:            .O.
root at netbsd> show igmp interface 
Interface    State    Querier         Timeout Version Groups
bce0         UP       192.168.55.1         98       3      0
rtk0         UP       192.168.111.10     None       3      1
root at netbsd> show pim interface 
Interface    State    Mode   V PIMstate Priority DRaddr          Neighbors
bce0         UP       Sparse 2 NotDR           1 192.168.55.1            1
rtk0         UP       Sparse 2 DR              1 192.168.111.10          0
register_vif UP       Sparse 2 DR              1 192.168.111.10          0




??
2008-05-07
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080507/0cbfc2ca/attachment.html 

From pavlin at ICSI.Berkeley.EDU  Wed May  7 08:36:37 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Wed, 07 May 2008 08:36:37 -0700
Subject: [Xorp-users] can not receive multicast data packet
In-Reply-To: <200805071754482960252@sohu.com> 
References: <200805071754482960252@sohu.com>
Message-ID: <200805071536.m47FabOJ028076@fruitcake.ICSI.Berkeley.EDU>

?? <libin020989 at sohu.com> wrote:

> I'm using xorp to build a network,xorp connects to a multicast source and a multicast receiver,when I send UDP packets on the source,I can not receive the packets on the receiver,I can not find the reason,
> Here is the xorp's state

The state looks fine.
Two reasons come to mind:

* Firewall entries in the kernel that prevent the multicast data
  from being forwarded.
* TTL is too small: by default the multicast data packets are
  transmitted by TTL of 1 and such packets won't be forwarded. Make
  sure that the TTL at the sender is large enough to reach the
  receivers; if a have a single router in the middle TTL=2 should be
  sufficient.

Regards,
Pavlin

> root at netbsd> show igmp group 
> IF     Group           Source          LastReported Timeout V  S    v1T    v2T
> rtk0   224.3.3.20      0.0.0.0         192.168.111.100     145 3  E     0     0
> root at netbsd> show pim mfc 
> Group           Source          RP             
> 224.3.3.20      192.168.222.35  14.14.14.14    
>     Incoming interface :      bce0
>     Outgoing interfaces:      .O.
> root at netbsd> show pim join 
> Group           Source          RP              Flags
> 224.3.3.20      0.0.0.0         14.14.14.14     WC   
>     Upstream interface (RP):   bce0
>     Upstream MRIB next hop (RP): 192.168.55.1
>     Upstream RPF'(*,G):        192.168.55.1
>     Upstream state:            Joined 
>     Join timer:                32
>     Local receiver include WC: .O.
>     Joins RP:                  ...
>     Joins WC:                  ...
>     Join state:                ...
>     Prune state:               ...
>     Prune pending state:       ...
>     I am assert winner state:  ...
>     I am assert loser state:   ...
>     Assert winner WC:          ...
>     Assert lost WC:            ...
>     Assert tracking WC:        OO.
>     Could assert WC:           .O.
>     I am DR:                   .OO
>     Immediate olist RP:        ...
>     Immediate olist WC:        .O.
>     Inherited olist SG:        .O.
>     Inherited olist SG_RPT:    .O.
>     PIM include WC:            .O.
> root at netbsd> show igmp interface 
> Interface    State    Querier         Timeout Version Groups
> bce0         UP       192.168.55.1         98       3      0
> rtk0         UP       192.168.111.10     None       3      1
> root at netbsd> show pim interface 
> Interface    State    Mode   V PIMstate Priority DRaddr          Neighbors
> bce0         UP       Sparse 2 NotDR           1 192.168.55.1            1
> rtk0         UP       Sparse 2 DR              1 192.168.111.10          0
> register_vif UP       Sparse 2 DR              1 192.168.111.10          0
> 
> 
> 
> 
> ??
> 2008-05-07
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From yueli.m at gmail.com  Fri May  9 14:03:22 2008
From: yueli.m at gmail.com (Yue Li)
Date: Fri, 9 May 2008 17:03:22 -0400
Subject: [Xorp-users] STCPRequestHandler died: life timer expired
Message-ID: <49567c360805091403p14082a41jdb91b5ae8af4fa72@mail.gmail.com>

Hi, All
I got the following errors when run policy and bgp modules. Any ideas?
I also attached my config file.
Any help will be appreciated.

[ 2008/05/09 16:50:57  ERROR xorp_fea:27671 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:50:57  ERROR xorp_fea:27671 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:50:58  ERROR xorp_fea:27671 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:02  ERROR xorp_fea:27671 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:02  ERROR xorp_rib:27672 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:04  ERROR xorp_rib:27672 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:06  ERROR xorp_fea:27671 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:06  ERROR xorp_static_routes:27674 XRL +339
xrl_pf_stcp.cc die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:08  ERROR xorp_static_routes:27674 XRL +339
xrl_pf_stcp.cc die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:08  ERROR xorp_rib:27672 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:08  ERROR xorp_fea:27671 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:08  ERROR xorp_bgp:27675 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:10  ERROR xorp_bgp:27675 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:10  ERROR xorp_policy:27673 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:12  ERROR xorp_rib:27672 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:14  ERROR xorp_bgp:27675 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:14  ERROR xorp_static_routes:27674 XRL +339
xrl_pf_stcp.cc die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:14  ERROR xorp_rib:27672 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:14  ERROR xorp_bgp:27675 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired
[ 2008/05/09 16:51:14  ERROR xorp_fea:27671 XRL +339 xrl_pf_stcp.cc
die ] STCPRequestHandler died: life timer expired


/* This file is generated for XORP Router: 10.0.0.10*/
interfaces {
   interface tun0 {
       disable: false
       vif tun0 {
          disable: false
          address 10.0.0.10 {
             prefix-length: 30
                disable: false
          }
       }
   }
   interface tun1 {
       disable: false
       vif tun1 {
          disable: false
          address 10.0.4.162 {
             prefix-length: 30
                disable: false
          }
       }
   }
}
policy {
  policy-statement bgp_in {
    term 0 {
        from {
             neighbor: 10.0.0.9
        }
        then {
             accept
        }
    }
    term 1 {
        from {
             neighbor: 10.0.4.161
        }
        then {
             accept
        }
    }
    term import_last {
        then {
             reject
        }
    }
 }
  policy-statement bgp_out {
    term 0 {
        from {
             protocol: "static"
             network4: 194.103.154.0/24
        }
        to {
             neighbor: 10.0.0.9
        }
        then {
             nexthop4: 10.0.0.10
             accept
        }
    }
    term 1 {
        from {
             protocol: "static"
             network4: 194.114.240.0/24
        }
        to {
             neighbor: 10.0.0.9
        }
        then {
             nexthop4: 10.0.0.10
             accept
        }
    }
    term 2 {
        from {
             protocol: "static"
             network4: 194.103.154.0/24
        }
        to {
             neighbor: 10.0.0.9
        }
        then {
             nexthop4: 10.0.0.10
             accept
        }
    }
    term 3 {
        from {
             protocol: "static"
             network4: 194.114.240.0/24
        }
        to {
             neighbor: 10.0.0.9
        }
        then {
             nexthop4: 10.0.0.10
             accept
        }
    }
    term 4 {
        from {
             protocol: "static"
             network4: 194.103.154.0/24
        }
        to {
             neighbor: 10.0.4.161
        }
        then {
             nexthop4: 10.0.4.162
             accept
        }
    }
    term 5 {
        from {
             protocol: "static"
             network4: 194.114.240.0/24
        }
        to {
             neighbor: 10.0.4.161
        }
        then {
             nexthop4: 10.0.4.162
             accept
        }
    }
    term 6 {
        from {
             protocol: "static"
             network4: 194.103.154.0/24
        }
        to {
             neighbor: 10.0.4.161
        }
        then {
             nexthop4: 10.0.4.162
             accept
        }
    }
    term 7 {
        from {
             protocol: "static"
             network4: 194.114.240.0/24
        }
        to {
             neighbor: 10.0.4.161
        }
        then {
             nexthop4: 10.0.4.162
             accept
        }
    }
    term export_last {
        then {
             reject
        }
    }
 }
}
protocols {
  static {
     route 194.103.154.0/24 {
          next-hop: 10.0.0.10
          metric: 1
     }
     route 194.114.240.0/24 {
          next-hop: 10.0.0.10
          metric: 1
     }
  }
   bgp {
      bgp-id: 10.0.0.10
      import: "bgp_in"
      export: "bgp_out"
      local-as: 21200
      traceoptions {
        flag {
          all {
            disable: true
          }
        }
      }
      peer 10.0.0.9 {
          local-ip: 10.0.0.10
          as: 3301
          next-hop: 10.0.0.10
          ipv4-multicast: false
          ipv6-unicast: false
          ipv6-multicast: false
      }
      peer 10.0.4.161 {
          local-ip: 10.0.4.162
          as: 8434
          next-hop: 10.0.4.162
          ipv4-multicast: false
          ipv6-unicast: false
          ipv6-multicast: false
      }
   }
}


From yueli.m at gmail.com  Sat May 10 14:22:16 2008
From: yueli.m at gmail.com (Yue Li)
Date: Sat, 10 May 2008 17:22:16 -0400
Subject: [Xorp-users] BGP module deactivated
Message-ID: <49567c360805101422q568225e6oba2b381c40f99ac8@mail.gmail.com>

The following config file makes bgp module deactivated.
No bgp packets are captured by using tcpdump.

And also, I can't enter the xorpsh, the ERROR is "Failed to register
with finder".

/* This file is generated for XORP Router: 10.0.0.10*/
interfaces {
   interface tun0 {
       disable: false
       vif tun0 {
          disable: false
          address 10.0.0.10 {
             prefix-length: 30
                disable: false
          }
       }
   }
   interface tun1 {
       disable: false
       vif tun1 {
          disable: false
          address 10.0.4.162 {
             prefix-length: 30
                disable: false
          }
       }
   }
}
policy {
  policy-statement bgp_in {
    term 0 {
        from {
             neighbor: 10.0.0.9
        }
        then {
             accept
        }
    }
    term 1 {
        from {
             neighbor: 10.0.4.161
        }
        then {
             accept
        }
    }
    term import_last {
        then {
             reject
        }
    }
 }
  policy-statement bgp_out {
    term 0 {
        from {
             protocol: "static"
             network4: 194.103.154.0/24
        }
        to {
             neighbor: 10.0.0.9
        }
        then {
             nexthop4: 10.0.0.10
             accept
        }
    }
    term 1 {
        from {
             protocol: "static"
             network4: 194.114.240.0/24
        }
        to {
             neighbor: 10.0.0.9
        }
        then {
             nexthop4: 10.0.0.10
             accept
        }
    }
    term 4 {
        from {
             protocol: "static"
             network4: 194.103.154.0/24
        }
        to {
             neighbor: 10.0.4.161
        }
        then {
             nexthop4: 10.0.4.162
             accept
        }
    }
    term 5 {
        from {
             protocol: "static"
             network4: 194.114.240.0/24
        }
        to {
             neighbor: 10.0.4.161
        }
        then {
             nexthop4: 10.0.4.162
             accept
        }
    }
    term export_last {
        then {
             reject
        }
    }
 }
}
protocols {
  static {
     route 194.103.154.0/24 {
          next-hop: 10.0.0.10
          metric: 1
     }
     route 194.114.240.0/24 {
          next-hop: 10.0.0.10
          metric: 1
     }
  }
   bgp {
      bgp-id: 10.0.0.10
      import: "bgp_in"
      export: "bgp_out"
      local-as: 21200
      traceoptions {
        flag {
          all {
            disable: true
          }
        }
      }
      peer 10.0.0.9 {
          local-ip: 10.0.0.10
          as: 3301
          next-hop: 10.0.0.10
          ipv4-multicast: false
          ipv6-unicast: false
          ipv6-multicast: false
      }
      peer 10.0.4.161 {
          local-ip: 10.0.4.162
          as: 8434
          next-hop: 10.0.4.162
          ipv4-multicast: false
          ipv6-unicast: false
          ipv6-multicast: false
      }
   }
}


From mayank.kandari at gmail.com  Sun May 11 21:15:08 2008
From: mayank.kandari at gmail.com (Mayank Kandari)
Date: Mon, 12 May 2008 09:45:08 +0530
Subject: [Xorp-users] Configuration of FEA for Click Forwarding Engine
Message-ID: <328b1be80805112115h6b7b1fd9y3468abd5b7f16567@mail.gmail.com>

Hello,
          I need the sample configuration of FEA for running click as a
forwarding engine.

-- 
regards
Mayank Kandari
Staff Scientist
C-DAC Mumbai
Juhu - 400049
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080512/c9097f36/attachment.html 

From mayank.kandari at gmail.com  Mon May 12 04:06:16 2008
From: mayank.kandari at gmail.com (Mayank Kandari)
Date: Mon, 12 May 2008 16:36:16 +0530
Subject: [Xorp-users] Error in configuring click
Message-ID: <328b1be80805120406m4f1f2cf5jf6b419f19ad3043b@mail.gmail.com>

Hello,
        I am getting the following error when trying to configure click as a
forwarding path.
        when I enter the set fea click disable false. I get the following
error

        Node "fea click enabled" is deprecated: Statement 'enabled:
true/false' is replaced with 'disable: false/true'


-- 
regards
Mayank Kandari
Staff Scientist
C-DAC Mumbai
Juhu - 400049
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080512/956e53f6/attachment.html 

From pavlin at ICSI.Berkeley.EDU  Mon May 12 10:24:06 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Mon, 12 May 2008 10:24:06 -0700
Subject: [Xorp-users] Configuration of FEA for Click Forwarding Engine
In-Reply-To: <328b1be80805112115h6b7b1fd9y3468abd5b7f16567@mail.gmail.com> 
References: <328b1be80805112115h6b7b1fd9y3468abd5b7f16567@mail.gmail.com>
Message-ID: <200805121724.m4CHO6ph029340@fruitcake.ICSI.Berkeley.EDU>

Mayank Kandari <mayank.kandari at gmail.com> wrote:

> Hello,
>           I need the sample configuration of FEA for running click as a
> forwarding engine.

If you get the latest XORP code from CVS there is an example in the
following location:

xorp/rtrmgr/config/click.boot

Alternatively, you can get it from the following URL:
http://cvsweb.xorp.org/cgi-bin/cvsweb.cgi/xorp/rtrmgr/config/click.boot

Hope that helps,
Pavlin

> -- 
> regards
> Mayank Kandari
> Staff Scientist
> C-DAC Mumbai
> Juhu - 400049
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From pavlin at ICSI.Berkeley.EDU  Mon May 12 10:26:16 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Mon, 12 May 2008 10:26:16 -0700
Subject: [Xorp-users] Error in configuring click
In-Reply-To: <328b1be80805120406m4f1f2cf5jf6b419f19ad3043b@mail.gmail.com> 
References: <328b1be80805120406m4f1f2cf5jf6b419f19ad3043b@mail.gmail.com>
Message-ID: <200805121726.m4CHQGAe029836@fruitcake.ICSI.Berkeley.EDU>

Mayank Kandari <mayank.kandari at gmail.com> wrote:

> Hello,
>         I am getting the following error when trying to configure click as a
> forwarding path.
>         when I enter the set fea click disable false. I get the following
> error
> 
>         Node "fea click enabled" is deprecated: Statement 'enabled:
> true/false' is replaced with 'disable: false/true'

It looks like you are using an older XORP configuration file.

Try using the xorp/rtrmgr/config/click.boot sample config from the
latest CVS.

Pavlin

> 
> -- 
> regards
> Mayank Kandari
> Staff Scientist
> C-DAC Mumbai
> Juhu - 400049
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From rajkumars at gmail.com  Tue May 13 04:11:58 2008
From: rajkumars at gmail.com (Rajkumar S)
Date: Tue, 13 May 2008 16:41:58 +0530
Subject: [Xorp-users] ip igmp join-group and xorp
Message-ID: <64de5c8b0805130411u329d66a5yb6e0323a3722f678@mail.gmail.com>

Hi,

I have a Cisco multicast router and am planning to replace it with
xorp. The configs of Cisco are as follows. The multicast happens over
a gre tunnel. I am confused about the "ip igmp join-group" command in
cisco. I do not see an equivalent command in xorp user manual. Also
there is no mention of RP in cisco config. How can xorp be configured
in this scenario?

ip multicast-routing
!
call rsvp-sync
!
interface Tunnel0
 ip address 22.22.22.254 255.255.255.252
 ip pim sparse-dense-mode
 ip igmp join-group 239.2.221.69
 tunnel source FastEthernet0/0
 tunnel destination 10.1.21.150
!
interface FastEthernet0/1
 ip address 10.80.10.210 255.255.255.0
 ip pim sparse-dense-mode
 duplex auto
 speed auto
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.1.21.177
ip route 10.253.19.5 255.255.255.255 FastEthernet0/0 name Tunnel0
ip route 10.253.21.148 255.255.255.252 10.1.21.177
ip http server

Full cisco config is at http://pastebin.ca/1016804 Is there any
information required from the other end of tunnel?

Any help would be much appreciated!

Thanks and regards,

raj


From pavlin at ICSI.Berkeley.EDU  Tue May 13 10:23:02 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Tue, 13 May 2008 10:23:02 -0700
Subject: [Xorp-users] ip igmp join-group and xorp
In-Reply-To: <64de5c8b0805130411u329d66a5yb6e0323a3722f678@mail.gmail.com> 
References: <64de5c8b0805130411u329d66a5yb6e0323a3722f678@mail.gmail.com>
Message-ID: <200805131723.m4DHN2i3001216@fruitcake.ICSI.Berkeley.EDU>

I believe the Cisco "ip igmp join-group" is used to have the router
join a particular multicast group.
In XORP you don't need to use this for the purpose of multicast
routing.

I am not familiar with Cisco's configuration so I can't comment on
the lack of RP in the config. It could be that the router might be
obtaining the Cand-RP info from the Bootstrap or the Auto-RP
mechanism.

In your XORP configuration you can start with the sample
rtrmgr/config/multicast4.boot file (if you have the latest code from
anon. CVS) or available from the following URL:
http://cvsweb.xorp.org/cgi-bin/cvsweb.cgi/xorp/rtrmgr/config/multicast4.boot

XORP supports two mechanisms for configuring the RPs: Bootstrap and
Static RPs. You can use the Bootstrap mechanism only if the rest of
your network is configured to use it; otherwise you need to use
static RPs in your config.

Hope that helps,
Pavlin

Rajkumar S <rajkumars at gmail.com> wrote:

> Hi,
> 
> I have a Cisco multicast router and am planning to replace it with
> xorp. The configs of Cisco are as follows. The multicast happens over
> a gre tunnel. I am confused about the "ip igmp join-group" command in
> cisco. I do not see an equivalent command in xorp user manual. Also
> there is no mention of RP in cisco config. How can xorp be configured
> in this scenario?
> 
> ip multicast-routing
> !
> call rsvp-sync
> !
> interface Tunnel0
>  ip address 22.22.22.254 255.255.255.252
>  ip pim sparse-dense-mode
>  ip igmp join-group 239.2.221.69
>  tunnel source FastEthernet0/0
>  tunnel destination 10.1.21.150
> !
> interface FastEthernet0/1
>  ip address 10.80.10.210 255.255.255.0
>  ip pim sparse-dense-mode
>  duplex auto
>  speed auto
> !
> ip classless
> ip route 0.0.0.0 0.0.0.0 10.1.21.177
> ip route 10.253.19.5 255.255.255.255 FastEthernet0/0 name Tunnel0
> ip route 10.253.21.148 255.255.255.252 10.1.21.177
> ip http server
> 
> Full cisco config is at http://pastebin.ca/1016804 Is there any
> information required from the other end of tunnel?
> 
> Any help would be much appreciated!
> 
> Thanks and regards,
> 
> raj
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From Swati.Deb at bristol.ac.uk  Tue May 13 10:24:53 2008
From: Swati.Deb at bristol.ac.uk (Swati Sinha Deb)
Date: Tue, 13 May 2008 18:24:53 +0100
Subject: [Xorp-users] Cannot start xorp_rtrmgr
Message-ID: <4C3E046AAB3F883F7296034D@[192.168.0.6]>

Hi,

I have XORP-1.4 running successfully on two servers.

I am trying to install this on another server. I have installed XORP-1.4 
successfully. The linux version is 2.4.21. But when I try to start the 
xorp_rtrmgr I am getting the following errors:

[eessd at atherton bin]$ sudo ./xorp_rtrmgr - my_config.boot
[ 2008/05/13 18:16:27  ERROR xorp_rtrmgr:13753 RTRMGR +330 main_rtrmgr.cc 
run ] rtrmgr shutting down due to an init error: Failed to open config 
file: /home/eessd/xorp/config.boot
[eessd at atherton bin]$ sudo ./xorp_rtrmgr -b my_config.boot
[ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +239 
master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, 
policy, static_routes
[ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
execute ] Executing module: interfaces (fea/xorp_fea)
[ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c 
comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol = 
0): Address family not supported by protocol
[ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c 
comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol = 
0): Address family not supported by protocol
[ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] MFEA enabled
[ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI enabled
[ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI started
[ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] MFEA enabled
[ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI enabled
[ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI started
[ 2008/05/13 18:16:44  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
execute ] Executing module: fea (fea/xorp_fea)
[ 2008/05/13 18:16:51  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
execute ] Executing module: rib (rib/xorp_rib)
[ 2008/05/13 18:16:53  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
execute ] Executing module: policy (policy/xorp_policy)
[ 2008/05/13 18:16:55  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
execute ] Executing module: static_routes (static_routes/xorp_static_routes)
[ 2008/05/13 18:16:57  INFO xorp_rtrmgr:13754 RTRMGR +2228 task.cc run_task 
] No more tasks to run

Any advice on the above issues will be highly appreciated.

Thanks in advance,
Swati




From pavlin at ICSI.Berkeley.EDU  Tue May 13 18:27:21 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Tue, 13 May 2008 18:27:21 -0700
Subject: [Xorp-users] Cannot start xorp_rtrmgr
In-Reply-To: <4C3E046AAB3F883F7296034D@[192.168.0.6]> 
References: <4C3E046AAB3F883F7296034D@[192.168.0.6]>
Message-ID: <200805140127.m4E1RLN8007103@fruitcake.ICSI.Berkeley.EDU>

Swati Sinha Deb <Swati.Deb at bristol.ac.uk> wrote:

> Hi,
> 
> I have XORP-1.4 running successfully on two servers.
> 
> I am trying to install this on another server. I have installed XORP-1.4 
> successfully. The linux version is 2.4.21. But when I try to start the 
> xorp_rtrmgr I am getting the following errors:
> 
> [eessd at atherton bin]$ sudo ./xorp_rtrmgr - my_config.boot
> [ 2008/05/13 18:16:27  ERROR xorp_rtrmgr:13753 RTRMGR +330 main_rtrmgr.cc 
> run ] rtrmgr shutting down due to an init error: Failed to open config 
> file: /home/eessd/xorp/config.boot

It looks like you fixed the above error, so I am not considering it
an issue anymore.

> [eessd at atherton bin]$ sudo ./xorp_rtrmgr -b my_config.boot
> [ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +239 
> master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, 
> policy, static_routes
> [ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
> execute ] Executing module: interfaces (fea/xorp_fea)
> [ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c 
> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol = 
> 0): Address family not supported by protocol
> [ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c 
> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol = 
> 0): Address family not supported by protocol

On Linux, domain = 10 is AF_INET6, i.e. IPv6.
It looks like that IPv6 is not enabled on that machine hence the
above error.
You have the following options to deal with this:

a) Configure your system (kernel, and/or config files) to enable
IPv6.

b) Recompile XORP with IPv6 disabled:
./configure --disable-ipv6
gmake clean
gmake

c) Do nothing.
   I could be wrong, but as long as you don't try to use
   any IPv6-specific configuration in your XORP config, the
   rest of XORP should work.

>From the above three choices I'd recommend (a). Exactly how you do
it is OS-specific.

However, if you think that IPv6 is already enabled, it could be that
the XORP ./configure script didn't discover IPv6; when running the
script look for a line like the following:

checking whether the system has IPv6 stack... yes

If it says "no", then please send file config.log that should be
generated after running ./configure

Regards,
Pavlin

> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] MFEA enabled
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI enabled
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI started
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] MFEA enabled
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI enabled
> [ 2008/05/13 18:16:42 INFO xorp_fea MFEA ] CLI started
> [ 2008/05/13 18:16:44  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
> execute ] Executing module: fea (fea/xorp_fea)
> [ 2008/05/13 18:16:51  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
> execute ] Executing module: rib (rib/xorp_rib)
> [ 2008/05/13 18:16:53  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
> execute ] Executing module: policy (policy/xorp_policy)
> [ 2008/05/13 18:16:55  INFO xorp_rtrmgr:13754 RTRMGR +96 module_manager.cc 
> execute ] Executing module: static_routes (static_routes/xorp_static_routes)
> [ 2008/05/13 18:16:57  INFO xorp_rtrmgr:13754 RTRMGR +2228 task.cc run_task 
> ] No more tasks to run
> 
> Any advice on the above issues will be highly appreciated.
> 
> Thanks in advance,
> Swati
> 
> 
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From Swati.Deb at bristol.ac.uk  Wed May 14 15:32:30 2008
From: Swati.Deb at bristol.ac.uk (Swati Sinha Deb)
Date: Wed, 14 May 2008 23:32:30 +0100
Subject: [Xorp-users] Cannot start xorp_rtrmgr
In-Reply-To: <200805140127.m4E1RLN8007103@fruitcake.ICSI.Berkeley.EDU>
References: <4C3E046AAB3F883F7296034D@[192.168.0.6]>
	<200805140127.m4E1RLN8007103@fruitcake.ICSI.Berkeley.EDU>
Message-ID: <D5BF74D487BC427CDC904B3D@[192.168.0.6]>

Hi Pavlin,

Many thanks for the reply. Apparently the server did not support the IPv6. 
Once enabled I could install the XORP-1.4 successfully. But now I am 
getting Click related errors. Please advice.

-bash-2.05b$ sudo ./xorp_rtrmgr -b my_config.boot
[ 2008/05/14 23:10:03  INFO xorp_rtrmgr:6615 RTRMGR +239 
master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, 
policy, static_routes
[ 2008/05/14 23:10:03  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: interfaces (fea/xorp_fea)
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] MFEA enabled
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI enabled
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI started
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] MFEA enabled
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI enabled
[ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI started
[ 2008/05/14 23:10:05  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: fea (fea/xorp_fea)
[ 2008/05/14 23:10:11  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: rib (rib/xorp_rib)
[ 2008/05/14 23:10:11  ERROR xorp_fea:6621 FEA +331 
fticonfig_entry_set_click.cc add_entry ] User-level Click command error: 
510 No element named '_xorp_rt6'
[ 2008/05/14 23:10:11  ERROR xorp_fea:6621 FEA +71 fti_transaction.cc 
operation_result ] FTI transaction commit failed on AddEntry6: net = 
fe80::/64 nexthop = fe80::204:23ff:fe08:f0aa ifname = eth3 vifname = eth3 
metric = 0 admin_distance = 0 xorp_route = true is_deleted = false 
is_unresolved = false is_connected_route = true
[ 2008/05/14 23:10:11 WARNING xorp_fea XrlFeaTarget ] Handling method for 
redist_transaction6/0.1/commit_transaction failed: XrlCmdError 102 Command 
failed AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:fe08:f0aa ifname 
= eth3 vifname = eth3 metric = 0 admin_distance = 0 xorp_route = true 
is_deleted = false is_unresolved = false is_connected_route = true
[ 2008/05/14 23:10:11  ERROR xorp_rib:6624 RIB +910 redist_xrl.cc 
dispatch_complete ] Failed to commit transaction: 102 Command failed 
AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:fe08:f0aa ifname = eth3 
vifname = eth3 metric = 0 admin_distance = 0 xorp_route = true is_deleted = 
false is_unresolved = false is_connected_route = true
[ 2008/05/14 23:10:13  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: policy (policy/xorp_policy)
[ 2008/05/14 23:10:15  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
execute ] Executing module: static_routes (static_routes/xorp_static_routes)
[ 2008/05/14 23:10:17  INFO xorp_rtrmgr:6615 RTRMGR +2228 task.cc run_task 
] No more tasks to run


Thanks in advance,
Swati

--On 13 May 2008 18:27 -0700 Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU> 
wrote:

> Swati Sinha Deb <Swati.Deb at bristol.ac.uk> wrote:
>
>> Hi,
>>
>> I have XORP-1.4 running successfully on two servers.
>>
>> I am trying to install this on another server. I have installed XORP-1.4
>> successfully. The linux version is 2.4.21. But when I try to start the
>> xorp_rtrmgr I am getting the following errors:
>>
>> [eessd at atherton bin]$ sudo ./xorp_rtrmgr - my_config.boot
>> [ 2008/05/13 18:16:27  ERROR xorp_rtrmgr:13753 RTRMGR +330
>> main_rtrmgr.cc  run ] rtrmgr shutting down due to an init error: Failed
>> to open config  file: /home/eessd/xorp/config.boot
>
> It looks like you fixed the above error, so I am not considering it
> an issue anymore.
>
>> [eessd at atherton bin]$ sudo ./xorp_rtrmgr -b my_config.boot
>> [ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +239
>> master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib,
>> policy, static_routes
>> [ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +96
>> module_manager.cc  execute ] Executing module: interfaces (fea/xorp_fea)
>> [ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c
>> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol =
>> 0): Address family not supported by protocol
>> [ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c
>> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol =
>> 0): Address family not supported by protocol
>
> On Linux, domain = 10 is AF_INET6, i.e. IPv6.
> It looks like that IPv6 is not enabled on that machine hence the
> above error.
> You have the following options to deal with this:
>
> a) Configure your system (kernel, and/or config files) to enable
> IPv6.
>
> b) Recompile XORP with IPv6 disabled:
> ./configure --disable-ipv6
> gmake clean
> gmake
>
> c) Do nothing.
>    I could be wrong, but as long as you don't try to use
>    any IPv6-specific configuration in your XORP config, the
>    rest of XORP should work.
>
> From the above three choices I'd recommend (a). Exactly how you do
> it is OS-specific.
>
> However, if you think that IPv6 is already enabled, it could be that
> the XORP ./configure script didn't discover IPv6; when running the
> script look for a line like the following:
>
> checking whether the system has IPv6 stack... yes
>
> If it says "no", then please send file config.log that should be
> generated after running ./configure
>
> Regards,
> Pavlin
>



From pavlin at ICSI.Berkeley.EDU  Wed May 14 17:28:31 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Wed, 14 May 2008 17:28:31 -0700
Subject: [Xorp-users] Cannot start xorp_rtrmgr
In-Reply-To: <D5BF74D487BC427CDC904B3D@[192.168.0.6]> 
References: <4C3E046AAB3F883F7296034D@[192.168.0.6]>
	<200805140127.m4E1RLN8007103@fruitcake.ICSI.Berkeley.EDU>
	<D5BF74D487BC427CDC904B3D@[192.168.0.6]>
Message-ID: <200805150028.m4F0SV8K016263@fruitcake.ICSI.Berkeley.EDU>

Swati Sinha Deb <Swati.Deb at bristol.ac.uk> wrote:

> Hi Pavlin,
> 
> Many thanks for the reply. Apparently the server did not support the IPv6. 
> Once enabled I could install the XORP-1.4 successfully. But now I am 
> getting Click related errors. Please advice.

Please send your XORP configuration and the Click version you are
using.

It appears that you are trying to use Click with IPv6.
The default Click config generator
(xorp/fea/xorp_fea_click_config_generator) has IPv6 disabled by
default. To enable it, edit that file and change "enable_ipv6 = 0"
to "enable_ipv6 = 1".

If you don't need IPv6, then I think you can just ignore those
IPv6-related error messages.

Regards,
Pavlin


> -bash-2.05b$ sudo ./xorp_rtrmgr -b my_config.boot
> [ 2008/05/14 23:10:03  INFO xorp_rtrmgr:6615 RTRMGR +239 
> master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, 
> policy, static_routes
> [ 2008/05/14 23:10:03  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
> execute ] Executing module: interfaces (fea/xorp_fea)
> [ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] MFEA enabled
> [ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI enabled
> [ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI started
> [ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] MFEA enabled
> [ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI enabled
> [ 2008/05/14 23:10:03 INFO xorp_fea MFEA ] CLI started
> [ 2008/05/14 23:10:05  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
> execute ] Executing module: fea (fea/xorp_fea)
> [ 2008/05/14 23:10:11  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
> execute ] Executing module: rib (rib/xorp_rib)
> [ 2008/05/14 23:10:11  ERROR xorp_fea:6621 FEA +331 
> fticonfig_entry_set_click.cc add_entry ] User-level Click command error: 
> 510 No element named '_xorp_rt6'
> [ 2008/05/14 23:10:11  ERROR xorp_fea:6621 FEA +71 fti_transaction.cc 
> operation_result ] FTI transaction commit failed on AddEntry6: net = 
> fe80::/64 nexthop = fe80::204:23ff:fe08:f0aa ifname = eth3 vifname = eth3 
> metric = 0 admin_distance = 0 xorp_route = true is_deleted = false 
> is_unresolved = false is_connected_route = true
> [ 2008/05/14 23:10:11 WARNING xorp_fea XrlFeaTarget ] Handling method for 
> redist_transaction6/0.1/commit_transaction failed: XrlCmdError 102 Command 
> failed AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:fe08:f0aa ifname 
> = eth3 vifname = eth3 metric = 0 admin_distance = 0 xorp_route = true 
> is_deleted = false is_unresolved = false is_connected_route = true
> [ 2008/05/14 23:10:11  ERROR xorp_rib:6624 RIB +910 redist_xrl.cc 
> dispatch_complete ] Failed to commit transaction: 102 Command failed 
> AddEntry6: net = fe80::/64 nexthop = fe80::204:23ff:fe08:f0aa ifname = eth3 
> vifname = eth3 metric = 0 admin_distance = 0 xorp_route = true is_deleted = 
> false is_unresolved = false is_connected_route = true
> [ 2008/05/14 23:10:13  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
> execute ] Executing module: policy (policy/xorp_policy)
> [ 2008/05/14 23:10:15  INFO xorp_rtrmgr:6615 RTRMGR +96 module_manager.cc 
> execute ] Executing module: static_routes (static_routes/xorp_static_routes)
> [ 2008/05/14 23:10:17  INFO xorp_rtrmgr:6615 RTRMGR +2228 task.cc run_task 
> ] No more tasks to run
> 
> 
> Thanks in advance,
> Swati
> 
> --On 13 May 2008 18:27 -0700 Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU> 
> wrote:
> 
> > Swati Sinha Deb <Swati.Deb at bristol.ac.uk> wrote:
> >
> >> Hi,
> >>
> >> I have XORP-1.4 running successfully on two servers.
> >>
> >> I am trying to install this on another server. I have installed XORP-1.4
> >> successfully. The linux version is 2.4.21. But when I try to start the
> >> xorp_rtrmgr I am getting the following errors:
> >>
> >> [eessd at atherton bin]$ sudo ./xorp_rtrmgr - my_config.boot
> >> [ 2008/05/13 18:16:27  ERROR xorp_rtrmgr:13753 RTRMGR +330
> >> main_rtrmgr.cc  run ] rtrmgr shutting down due to an init error: Failed
> >> to open config  file: /home/eessd/xorp/config.boot
> >
> > It looks like you fixed the above error, so I am not considering it
> > an issue anymore.
> >
> >> [eessd at atherton bin]$ sudo ./xorp_rtrmgr -b my_config.boot
> >> [ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +239
> >> master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib,
> >> policy, static_routes
> >> [ 2008/05/13 18:16:42  INFO xorp_rtrmgr:13754 RTRMGR +96
> >> module_manager.cc  execute ] Executing module: interfaces (fea/xorp_fea)
> >> [ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c
> >> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol =
> >> 0): Address family not supported by protocol
> >> [ 2008/05/13 18:16:42  ERROR xorp_fea:13755 LIBCOMM +114 comm_sock.c
> >> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol =
> >> 0): Address family not supported by protocol
> >
> > On Linux, domain = 10 is AF_INET6, i.e. IPv6.
> > It looks like that IPv6 is not enabled on that machine hence the
> > above error.
> > You have the following options to deal with this:
> >
> > a) Configure your system (kernel, and/or config files) to enable
> > IPv6.
> >
> > b) Recompile XORP with IPv6 disabled:
> > ./configure --disable-ipv6
> > gmake clean
> > gmake
> >
> > c) Do nothing.
> >    I could be wrong, but as long as you don't try to use
> >    any IPv6-specific configuration in your XORP config, the
> >    rest of XORP should work.
> >
> > From the above three choices I'd recommend (a). Exactly how you do
> > it is OS-specific.
> >
> > However, if you think that IPv6 is already enabled, it could be that
> > the XORP ./configure script didn't discover IPv6; when running the
> > script look for a line like the following:
> >
> > checking whether the system has IPv6 stack... yes
> >
> > If it says "no", then please send file config.log that should be
> > generated after running ./configure
> >
> > Regards,
> > Pavlin
> >
> 
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From Swati.Deb at bristol.ac.uk  Thu May 15 08:14:43 2008
From: Swati.Deb at bristol.ac.uk (Swati Sinha Deb)
Date: Thu, 15 May 2008 16:14:43 +0100
Subject: [Xorp-users] Cannot start xorp_rtrmgr
In-Reply-To: <200805150028.m4F0SV8K016263@fruitcake.ICSI.Berkeley.EDU>
References: <4C3E046AAB3F883F7296034D@[192.168.0.6]>
	<200805140127.m4E1RLN8007103@fruitcake.ICSI.Berkeley.EDU>
	<D5BF74D487BC427CDC904B3D@[192.168.0.6]>
	<200805150028.m4F0SV8K016263@fruitcake.ICSI.Berkeley.EDU>
Message-ID: <0CDF7B91FAB7F41575C637D0@[192.168.0.6]>

Hi Pavlin,

I don't need IPv6 so I can ignore those messages. I am using click-1.4.3. 
Are there any issues with older version of click and xorp-1.4?

Thanks for your help.

Regards,
Swati

--On 14 May 2008 17:28 -0700 Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU> 
wrote:

> Swati Sinha Deb <Swati.Deb at bristol.ac.uk> wrote:
>
>> Hi Pavlin,
>>
>> Many thanks for the reply. Apparently the server did not support the
>> IPv6.  Once enabled I could install the XORP-1.4 successfully. But now I
>> am  getting Click related errors. Please advice.
>
> Please send your XORP configuration and the Click version you are
> using.
>
> It appears that you are trying to use Click with IPv6.
> The default Click config generator
> (xorp/fea/xorp_fea_click_config_generator) has IPv6 disabled by
> default. To enable it, edit that file and change "enable_ipv6 = 0"
> to "enable_ipv6 = 1".
>
> If you don't need IPv6, then I think you can just ignore those
> IPv6-related error messages.
>
> Regards,
> Pavlin
>
>
>>> Xorp-users mailing list
>> Xorp-users at xorp.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users





From pavlin at ICSI.Berkeley.EDU  Thu May 15 09:27:37 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Thu, 15 May 2008 09:27:37 -0700
Subject: [Xorp-users] Cannot start xorp_rtrmgr
In-Reply-To: <0CDF7B91FAB7F41575C637D0@[192.168.0.6]> 
References: <4C3E046AAB3F883F7296034D@[192.168.0.6]>
	<200805140127.m4E1RLN8007103@fruitcake.ICSI.Berkeley.EDU>
	<D5BF74D487BC427CDC904B3D@[192.168.0.6]>
	<200805150028.m4F0SV8K016263@fruitcake.ICSI.Berkeley.EDU>
	<0CDF7B91FAB7F41575C637D0@[192.168.0.6]>
Message-ID: <200805151627.m4FGRbIk004495@fruitcake.ICSI.Berkeley.EDU>

Swati Sinha Deb <Swati.Deb at bristol.ac.uk> wrote:

> Hi Pavlin,
> 
> I don't need IPv6 so I can ignore those messages. I am using click-1.4.3. 
> Are there any issues with older version of click and xorp-1.4?

Click-1.4.3 should be OK.
Actually, there could be issues with newer versions of Click, but
this is not verified/tested.

Regards,
Pavlin

> Thanks for your help.
> 
> Regards,
> Swati
> 
> --On 14 May 2008 17:28 -0700 Pavlin Radoslavov <pavlin at ICSI.Berkeley.EDU> 
> wrote:
> 
> > Swati Sinha Deb <Swati.Deb at bristol.ac.uk> wrote:
> >
> >> Hi Pavlin,
> >>
> >> Many thanks for the reply. Apparently the server did not support the
> >> IPv6.  Once enabled I could install the XORP-1.4 successfully. But now I
> >> am  getting Click related errors. Please advice.
> >
> > Please send your XORP configuration and the Click version you are
> > using.
> >
> > It appears that you are trying to use Click with IPv6.
> > The default Click config generator
> > (xorp/fea/xorp_fea_click_config_generator) has IPv6 disabled by
> > default. To enable it, edit that file and change "enable_ipv6 = 0"
> > to "enable_ipv6 = 1".
> >
> > If you don't need IPv6, then I think you can just ignore those
> > IPv6-related error messages.
> >
> > Regards,
> > Pavlin
> >
> >
> >>> Xorp-users mailing list
> >> Xorp-users at xorp.org
> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
> 
> 
> 
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From mayank.kandari at gmail.com  Thu May 15 21:29:19 2008
From: mayank.kandari at gmail.com (Mayank Kandari)
Date: Fri, 16 May 2008 09:59:19 +0530
Subject: [Xorp-users] XORP Support for Click
Message-ID: <328b1be80805152129s7d4a69c3q19a33b89973d498@mail.gmail.com>

Which latest version of Click is supported by XORP and by which version of
XORP.

-- 
regards
Mayank Kandari
Staff Scientist
C-DAC Mumbai
Juhu - 400049
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080516/aa6f1b58/attachment.html 

From pavlin at ICSI.Berkeley.EDU  Thu May 15 22:45:46 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Thu, 15 May 2008 22:45:46 -0700
Subject: [Xorp-users] XORP Support for Click
In-Reply-To: <328b1be80805152129s7d4a69c3q19a33b89973d498@mail.gmail.com> 
References: <328b1be80805152129s7d4a69c3q19a33b89973d498@mail.gmail.com>
Message-ID: <200805160545.m4G5jkIp012685@fruitcake.ICSI.Berkeley.EDU>

Mayank Kandari <mayank.kandari at gmail.com> wrote:

> Which latest version of Click is supported by XORP and by which version of
> XORP.

Admittedly, the Click support is lacking behind.
If memory serves right, the Click support in XORP was deleveloped
for Click-1.4.3.
I think folks have been able to use it with XORP-1.4 and the latest
XORP code from CVS.

I don't know whether XORP will work with newer Click releases (1.5
and 1.6). If someone has tried it and it worked, please speak up.

Hope that helps,
Pavlin

> -- 
> regards
> Mayank Kandari
> Staff Scientist
> C-DAC Mumbai
> Juhu - 400049
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From greearb at candelatech.com  Wed May 21 14:49:57 2008
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 21 May 2008 14:49:57 -0700
Subject: [Xorp-users] How to choose a good cand-rp-by-vif-name ?
Message-ID: <48349905.1060509@candelatech.com>

I'm working on configuring Xorp with multicast support.

The bootstrap configuration wants a candidate VIF.

Supposing there are lots of interfaces, how does one decide which one to use for
the cand-rp-by-vif-name?

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From pavlin at ICSI.Berkeley.EDU  Thu May 22 09:31:40 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Thu, 22 May 2008 09:31:40 -0700
Subject: [Xorp-users] How to choose a good cand-rp-by-vif-name ?
In-Reply-To: <48349905.1060509@candelatech.com> 
References: <48349905.1060509@candelatech.com>
Message-ID: <200805221631.m4MGVetP017517@fruitcake.ICSI.Berkeley.EDU>

Ben Greear <greearb at candelatech.com> wrote:

> I'm working on configuring Xorp with multicast support.
> 
> The bootstrap configuration wants a candidate VIF.
> 
> Supposing there are lots of interfaces, how does one decide which one to use for
> the cand-rp-by-vif-name?

The primary IP address of the chosen vif must be reachable
(routable) by all other PIM-SM routers in your network.

Regards,
Pavlin


From arunpereira at gmail.com  Thu May 22 20:41:50 2008
From: arunpereira at gmail.com (Arun Pereira)
Date: Thu, 22 May 2008 23:41:50 -0400
Subject: [Xorp-users] Bgp Md5 support.
Message-ID: <2f5f91170805222041i44b6533ew2389e383068e9bc@mail.gmail.com>

While trying to configure bgp with md5, I noticed there is no way to
set the password for a peer. Is that because I am missing something or
is BGP md5 support not present in Xorp. Please let me know.
Thank you,
Arun.


From jvantuyl at engineyard.com  Thu May 22 22:39:28 2008
From: jvantuyl at engineyard.com (Jayson Vantuyl)
Date: Thu, 22 May 2008 22:39:28 -0700
Subject: [Xorp-users] Seeing Odd IGMP Behavior
Message-ID: <38DB3B23-CEAE-4B4A-9F83-678DB0307B49@engineyard.com>

So, I desperately want to get a few things working together.  It  
appears that XORP is my best chance, albeit a slightly shaky one.  I'm  
currently using Xorp 1.4 release.

I'm using I have a number of virtual guests that appear and  
disappear.  I would like a fully routed configuration with multicast.   
What I'm trying to accomplish is:

a) OSPF to distribute the local routes to the virtual machines
b) PIM-SM to get multicast routing

Seems simple right?

Well, I have a few issues that I've hit.

1) Dynamically removing an interface effectively crashes the FEA
2) I can't seem to receive IGMP Membership Reports

As for 1, I got it handled.  I just replaced a fatal error with a non- 
fatal one.  Specifically on fea/netlink_socket_utils.cc, around line  
300.  The error "Could not find interface corresponding to index".  It  
just didn't need to be fatal.  Not sure exactly what the implications  
are, but it appears that it's permissible to pass by a failure to  
lookup an interface index, so how much worse could it be when looking  
up the name, right?  :)

Number 2 is a bit more ugly.  So, I have two interfaces:  external,  
and vif2.0.  The first is, well, my uplink.  The second is the  
connection to the virtual machine.  External has the address/subnet of  
10.0.0.1/26.  Vif2.0 has 10.0.129.129/30.  The virtual machine on the  
other side of vif2.0 has 10.0.129.130/30.  Another machine on the  
external subnet has 10.0.0.2/26.

Now, when I listen to group 224.1.2.3 on 10.0.0.2, I get this happiness:

[ 2008/05/22 16:31:57 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_V2_MEMBERSHIP_REPORT from 10.0.0.2 to 224.1.2.3 on vif external
[ 2008/05/22 16:31:57 TRACE xorp_igmp MLD6IGMP ] Notify routing add  
membership for (0.0.0.0, 224.1.2.3) on vif external
[ 2008/05/22 16:31:57 TRACE xorp_pimsm4 PIM ] Add membership for  
(0.0.0.0, 224.1.2.3) on vif external

That seems nice, no?

When I stop listening, I get this:

[ 2008/05/22 16:33:45 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_V2_LEAVE_GROUP from 10.0.0.2 to 224.0.0.2 on vif external
[ 2008/05/22 16:33:45 TRACE xorp_igmp MLD6IGMP ] TX  
IGMP_MEMBERSHIP_QUERY from 10.0.0.1 to 224.1.2.3
[ 2008/05/22 16:33:45 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_MEMBERSHIP_QUERY from 10.0.0.1 to 224.1.2.3 on vif external
[ 2008/05/22 16:33:46 TRACE xorp_igmp MLD6IGMP ] TX  
IGMP_MEMBERSHIP_QUERY from 10.0.0.1 to 224.1.2.3
[ 2008/05/22 16:33:46 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_MEMBERSHIP_QUERY from 10.0.0.1 to 224.1.2.3 on vif external
[ 2008/05/22 16:33:47 TRACE xorp_igmp MLD6IGMP ] Notify routing delete  
membership for (0.0.0.0, 224.1.2.3) on vif external
[ 2008/05/22 16:33:47 TRACE xorp_pimsm4 PIM ] Delete membership for  
(0.0.0.0, 224.1.2.3) on vif external

That seems fairly expected.

When I listen to the same group on the virtual machine, I see no trace  
for a membership message.  Tcpdump verifies that it's coming it, but  
Xorp just seems to do nothing with it.  But, when I stop listening,  
for some reason Xorp seems to catch that just fine, and I see this:

[ 2008/05/22 16:37:05 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_V2_LEAVE_GROUP from 10.0.65.130 to 224.0.0.2 on vif vif2.0

Any thoughts?

-- 
Jayson Vantuyl
Systems Architect
Engine Yard
jvantuyl at engineyard.com
1 866 518 9275 ext 204
IRC (freenode): kagato

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080522/4630ed39/attachment.html 

From jvantuyl at engineyard.com  Thu May 22 22:39:28 2008
From: jvantuyl at engineyard.com (Jayson Vantuyl)
Date: Thu, 22 May 2008 22:39:28 -0700
Subject: [Xorp-users] Seeing Odd IGMP Behavior
Message-ID: <38DB3B23-CEAE-4B4A-9F83-678DB0307B49@engineyard.com>

So, I desperately want to get a few things working together.  It  
appears that XORP is my best chance, albeit a slightly shaky one.  I'm  
currently using Xorp 1.4 release.

I'm using I have a number of virtual guests that appear and  
disappear.  I would like a fully routed configuration with multicast.   
What I'm trying to accomplish is:

a) OSPF to distribute the local routes to the virtual machines
b) PIM-SM to get multicast routing

Seems simple right?

Well, I have a few issues that I've hit.

1) Dynamically removing an interface effectively crashes the FEA
2) I can't seem to receive IGMP Membership Reports

As for 1, I got it handled.  I just replaced a fatal error with a non- 
fatal one.  Specifically on fea/netlink_socket_utils.cc, around line  
300.  The error "Could not find interface corresponding to index".  It  
just didn't need to be fatal.  Not sure exactly what the implications  
are, but it appears that it's permissible to pass by a failure to  
lookup an interface index, so how much worse could it be when looking  
up the name, right?  :)

Number 2 is a bit more ugly.  So, I have two interfaces:  external,  
and vif2.0.  The first is, well, my uplink.  The second is the  
connection to the virtual machine.  External has the address/subnet of  
10.0.0.1/26.  Vif2.0 has 10.0.129.129/30.  The virtual machine on the  
other side of vif2.0 has 10.0.129.130/30.  Another machine on the  
external subnet has 10.0.0.2/26.

Now, when I listen to group 224.1.2.3 on 10.0.0.2, I get this happiness:

[ 2008/05/22 16:31:57 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_V2_MEMBERSHIP_REPORT from 10.0.0.2 to 224.1.2.3 on vif external
[ 2008/05/22 16:31:57 TRACE xorp_igmp MLD6IGMP ] Notify routing add  
membership for (0.0.0.0, 224.1.2.3) on vif external
[ 2008/05/22 16:31:57 TRACE xorp_pimsm4 PIM ] Add membership for  
(0.0.0.0, 224.1.2.3) on vif external

That seems nice, no?

When I stop listening, I get this:

[ 2008/05/22 16:33:45 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_V2_LEAVE_GROUP from 10.0.0.2 to 224.0.0.2 on vif external
[ 2008/05/22 16:33:45 TRACE xorp_igmp MLD6IGMP ] TX  
IGMP_MEMBERSHIP_QUERY from 10.0.0.1 to 224.1.2.3
[ 2008/05/22 16:33:45 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_MEMBERSHIP_QUERY from 10.0.0.1 to 224.1.2.3 on vif external
[ 2008/05/22 16:33:46 TRACE xorp_igmp MLD6IGMP ] TX  
IGMP_MEMBERSHIP_QUERY from 10.0.0.1 to 224.1.2.3
[ 2008/05/22 16:33:46 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_MEMBERSHIP_QUERY from 10.0.0.1 to 224.1.2.3 on vif external
[ 2008/05/22 16:33:47 TRACE xorp_igmp MLD6IGMP ] Notify routing delete  
membership for (0.0.0.0, 224.1.2.3) on vif external
[ 2008/05/22 16:33:47 TRACE xorp_pimsm4 PIM ] Delete membership for  
(0.0.0.0, 224.1.2.3) on vif external

That seems fairly expected.

When I listen to the same group on the virtual machine, I see no trace  
for a membership message.  Tcpdump verifies that it's coming it, but  
Xorp just seems to do nothing with it.  But, when I stop listening,  
for some reason Xorp seems to catch that just fine, and I see this:

[ 2008/05/22 16:37:05 TRACE xorp_igmp MLD6IGMP ] RX  
IGMP_V2_LEAVE_GROUP from 10.0.65.130 to 224.0.0.2 on vif vif2.0

Any thoughts?

-- 
Jayson Vantuyl
Systems Architect
Engine Yard
jvantuyl at engineyard.com
1 866 518 9275 ext 204
IRC (freenode): kagato

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080522/4630ed39/attachment-0003.html 

From pavlin at ICSI.Berkeley.EDU  Thu May 22 23:25:33 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Thu, 22 May 2008 23:25:33 -0700
Subject: [Xorp-users] Seeing Odd IGMP Behavior
In-Reply-To: <38DB3B23-CEAE-4B4A-9F83-678DB0307B49@engineyard.com> 
References: <38DB3B23-CEAE-4B4A-9F83-678DB0307B49@engineyard.com>
Message-ID: <200805230625.m4N6PXmJ008428@fruitcake.ICSI.Berkeley.EDU>

Jayson Vantuyl <jvantuyl at engineyard.com> wrote:

> So, I desperately want to get a few things working together.  It  appears that
> XORP is my best chance, albeit a slightly shaky one.  I'm  currently using
> Xorp 1.4 release.
> 
> I'm using I have a number of virtual guests that appear and  disappear.  I
> would like a fully routed configuration with multicast.   What I'm trying to
> accomplish is:
> 
> a) OSPF to distribute the local routes to the virtual machines
> b) PIM-SM to get multicast routing
> 
> Seems simple right?
> 
> Well, I have a few issues that I've hit.
> 
> 1) Dynamically removing an interface effectively crashes the FEA

There have been various bug fixes and refactoring in the FEA since
1.4. Please get the latest XORP code from anon. CVS and see whether
you still get the crash. If it still crashes, then please submit a
bug report how to reproduce the problem.

> 2) I can't seem to receive IGMP Membership Reports
> 
> As for 1, I got it handled.  I just replaced a fatal error with a non-
> fatal one.  Specifically on fea/netlink_socket_utils.cc, around line  300.
> The error "Could not find interface corresponding to index".  It  just didn't
> need to be fatal.  Not sure exactly what the implications  are, but it appears
> that it's permissible to pass by a failure to  lookup an interface index, so
> how much worse could it be when looking  up the name, right?  :)
> 
> Number 2 is a bit more ugly.  So, I have two interfaces:  external,  and
> vif2.0.  The first is, well, my uplink.  The second is the  connection to the
> virtual machine.  External has the address/subnet of  10.0.0.1/26.  Vif2.0 has
> 10.0.129.129/30.  The virtual machine on the  other side of vif2.0 has
> 10.0.129.130/30.  Another machine on the  external subnet has 10.0.0.2/26.
> 
> Now, when I listen to group 224.1.2.3 on 10.0.0.2, I get this happiness:
> 
> [ 2008/05/22 16:31:57 TRACE xorp_igmp MLD6IGMP ] RX  IGMP_V2_MEMBERSHIP_REPORT
> from 10.0.0.2 to 224.1.2.3 on vif external
> [ 2008/05/22 16:31:57 TRACE xorp_igmp MLD6IGMP ] Notify routing add
> membership for (0.0.0.0, 224.1.2.3) on vif external
> [ 2008/05/22 16:31:57 TRACE xorp_pimsm4 PIM ] Add membership for  (0.0.0.0,
> 224.1.2.3) on vif external
> 
> That seems nice, no?
> 
> When I stop listening, I get this:
> 
> [ 2008/05/22 16:33:45 TRACE xorp_igmp MLD6IGMP ] RX  IGMP_V2_LEAVE_GROUP from
> 10.0.0.2 to 224.0.0.2 on vif external
> [ 2008/05/22 16:33:45 TRACE xorp_igmp MLD6IGMP ] TX  IGMP_MEMBERSHIP_QUERY
> from 10.0.0.1 to 224.1.2.3
> [ 2008/05/22 16:33:45 TRACE xorp_igmp MLD6IGMP ] RX  IGMP_MEMBERSHIP_QUERY
> from 10.0.0.1 to 224.1.2.3 on vif external
> [ 2008/05/22 16:33:46 TRACE xorp_igmp MLD6IGMP ] TX  IGMP_MEMBERSHIP_QUERY
> from 10.0.0.1 to 224.1.2.3
> [ 2008/05/22 16:33:46 TRACE xorp_igmp MLD6IGMP ] RX  IGMP_MEMBERSHIP_QUERY
> from 10.0.0.1 to 224.1.2.3 on vif external
> [ 2008/05/22 16:33:47 TRACE xorp_igmp MLD6IGMP ] Notify routing delete
> membership for (0.0.0.0, 224.1.2.3) on vif external
> [ 2008/05/22 16:33:47 TRACE xorp_pimsm4 PIM ] Delete membership for  (0.0.0.0,
> 224.1.2.3) on vif external
> 
> That seems fairly expected.
> 
> When I listen to the same group on the virtual machine, I see no trace  for a
> membership message.  Tcpdump verifies that it's coming it, but  Xorp just
> seems to do nothing with it.  But, when I stop listening,  for some reason
> Xorp seems to catch that just fine, and I see this:
> 
> [ 2008/05/22 16:37:05 TRACE xorp_igmp MLD6IGMP ] RX  IGMP_V2_LEAVE_GROUP from
> 10.0.65.130 to 224.0.0.2 on vif vif2.0

What OS are you running and what kind of virtual machine are you
using? Also, I'd like to know what kind of (virtual?) interface are
you using to connect to the virtual machine.

My guess the reason you don't see the IGMP membership messages is
the following. The IGMP MEMBERSHIP REPORT messages are sent to the
joined multicast group. To receive them, the multicast router cannot
join all possible multicast groups on the interface, therefore it
sets the interface in the special ALLMULTI mode (i.e., receive all
multicast packets). Therefore, probably the ALLMULTI mode doesn't work
properly on the virtual interface, or there are firewall rules that
stop those messages before they are delivered to the host IP stack.

Another (less likely) reason could be if you have some equipment in
the middle that stops the IGMP membership messages.

On BSD system, if the interface is in ALLMULTI mode, "ifconfig -a"
should show it as an interface flag. I believe one of the following
commands will show it on Linux as well: "ifconfig -a" or "ip link"
or "ip addr".

BTW, the reason the XORP router receives the IGMP leave message is
because the destination address is 224.0.0.2 (the ALL-ROUTERS
multicast group), and the multicast router has explicitly joined
that group.

Finally, where did you run tcpdump? On the XORP router or the
virtual machine. If only on the virtual machine, try running it on
the XORP router as well.

Regards,
Pavlin

> Any thoughts?
> 
> -- 
> Jayson Vantuyl
> Systems Architect
> Engine Yard
> jvantuyl at engineyard.com
> 1 866 518 9275 ext 204
> IRC (freenode): kagato
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From ssohn at gmu.edu  Fri May 23 13:22:35 2008
From: ssohn at gmu.edu (Soon-Yong Sohn)
Date: Fri, 23 May 2008 16:22:35 -0400
Subject: [Xorp-users] Click version supported by xorp
Message-ID: <f5d9f88842087.4836ef4b@gmu.edu>

Hello,

I have a question about click.
I am trying to run click of version 1.6.0 with xorp.
I am not sure xorp is supporting click-1.6.0.
If not, do you have any plan to upgrade it to support the version 1.6.0 of click ?

Eric


From pavlin at ICSI.Berkeley.EDU  Fri May 23 14:17:34 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Fri, 23 May 2008 14:17:34 -0700
Subject: [Xorp-users] Click version supported by xorp
In-Reply-To: <f5d9f88842087.4836ef4b@gmu.edu> 
References: <f5d9f88842087.4836ef4b@gmu.edu>
Message-ID: <200805232117.m4NLHYHX025615@fruitcake.ICSI.Berkeley.EDU>

Soon-Yong Sohn <ssohn at gmu.edu> wrote:

> Hello,
> 
> I have a question about click.
> I am trying to run click of version 1.6.0 with xorp.
> I am not sure xorp is supporting click-1.6.0.
> If not, do you have any plan to upgrade it to support the version 1.6.0 of click ?

The Click support in XORP was deleveloped for Click-1.4.3, but
unfortunately it is lagging behind so we haven't tried a newer
version of Click.

Eventually we should get XORP working with never versions of Click
but right now it is a very low priority task.
If someone investigates the problem and fixes it, patches are
welcome.

Thanks,
Pavlin


From mayank.kandari at gmail.com  Wed May 28 05:17:58 2008
From: mayank.kandari at gmail.com (Mayank Kandari)
Date: Wed, 28 May 2008 17:47:58 +0530
Subject: [Xorp-users] Error of Clock
Message-ID: <328b1be80805280517l361405c8q5cc4652052674a01@mail.gmail.com>

while I am running  xorp getting the following error.
Can any one tell whats the problem ?

xorp_rtrmgr: clock.cc:47: virtual void SystemClock::advance_time():
Assertion `error == 0' failed.
Segmentation fault

-- 
regards
Mayank Kandari
Staff Scientist
C-DAC Mumbai
Juhu - 400049
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20080528/1a108ec3/attachment.html 

From pavlin at ICSI.Berkeley.EDU  Thu May 29 17:32:30 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Thu, 29 May 2008 17:32:30 -0700
Subject: [Xorp-users] Error of Clock
In-Reply-To: <328b1be80805280517l361405c8q5cc4652052674a01@mail.gmail.com> 
References: <328b1be80805280517l361405c8q5cc4652052674a01@mail.gmail.com>
Message-ID: <200805300032.m4U0WUFA005134@fruitcake.ICSI.Berkeley.EDU>

Mayank Kandari <mayank.kandari at gmail.com> wrote:

> while I am running  xorp getting the following error.
> Can any one tell whats the problem ?
> 
> xorp_rtrmgr: clock.cc:47: virtual void SystemClock::advance_time():
> Assertion `error == 0' failed.
> Segmentation fault

What OS are you running and is the problem reproducible?

The problematic code is inside libxorp/clock.cc:

    error = ::clock_gettime(CLOCK_MONOTONIC, &ts);
    assert(error == 0);

>From reading the FreeBSD-7.0 manual page for clock_gettime()
all of the few possible errors should never happen in our case.

If the problem can be reproduced, could you print the value of errno
and the corresponding string (e.g., by using strerror) by adding
the following line right before the assert() call:

    XLOG_ERROR("errno = %d (%s)", errno, strerror(errno));


Thanks,
Pavlin