From pavlin at icir.org  Mon Oct  1 10:12:54 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Mon, 01 Oct 2007 10:12:54 -0700
Subject: [Xorp-users] CLI spin fix (hack)
In-Reply-To: Message from Ben Greear <greearb@candelatech.com> 
	of "Sun, 30 Sep 2007 11:22:57 PDT." <46FFE981.90106@candelatech.com> 
Message-ID: <200710011712.l91HCsKT046430@possum.icir.org>

Ben Greear <greearb at candelatech.com> wrote:

> Pavlin Radoslavov wrote:
> > Ben Greear <greearb at candelatech.com> wrote:
> >
> >   
> >> It seems that if you pipe multiple commands into the CLI, it will busy
> >> spin waiting for the previous command to complete.  Since 'commit'
> >> can take multiple seconds when adding an interface, this eats a lot
> >> of CPU.
> >>     
> >
> > Could you clarify what you mean by piping multiple commands into the
> > CLI. Is it when you use multiple "-c <cmd>" arguments after applying
> > your second patch.
> >   
> 
> Yes, or when you do xorpsh < cmd_file.txt
> where cmd_file.txt has several lines in it, like:
> 
> configure
> remove interface foo
> commit
> ...
> exit
> exit

Could you send me the exact initial config.boot and the cmd_file.txt
configuration files you are using in your testing, so we can have a
calibration point.

Thanks,
Pavlin


From greearb at candelatech.com  Mon Oct  1 10:59:40 2007
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 01 Oct 2007 10:59:40 -0700
Subject: [Xorp-users] CLI spin fix (hack)
In-Reply-To: <200710011712.l91HCsKT046430@possum.icir.org>
References: <200710011712.l91HCsKT046430@possum.icir.org>
Message-ID: <4701358C.1050200@candelatech.com>

Pavlin Radoslavov wrote:
> Ben Greear <greearb at candelatech.com> wrote:
> 
>> Pavlin Radoslavov wrote:
>>> Ben Greear <greearb at candelatech.com> wrote:
>>>
>>>   
>>>> It seems that if you pipe multiple commands into the CLI, it will busy
>>>> spin waiting for the previous command to complete.  Since 'commit'
>>>> can take multiple seconds when adding an interface, this eats a lot
>>>> of CPU.
>>>>     
>>> Could you clarify what you mean by piping multiple commands into the
>>> CLI. Is it when you use multiple "-c <cmd>" arguments after applying
>>> your second patch.
>>>   
>> Yes, or when you do xorpsh < cmd_file.txt
>> where cmd_file.txt has several lines in it, like:
>>
>> configure
>> remove interface foo
>> commit
>> ...
>> exit
>> exit
> 
> Could you send me the exact initial config.boot and the cmd_file.txt
> configuration files you are using in your testing, so we can have a
> calibration point.

Here are the commands I'm sending to xorpsh.  The numbers on the left
are millisecond timestamps, so this delete takes about 11 seconds!

The 3 router config files are attached, the 'vr: xxxx' cooresponds
to the number in the routing config files.


After starting with the attached config files, I remove the interface
from one VR:

1191260992793:  Card.cc 5684: Writing XORP cli commands to vr: 20002 cmds -:
configure
delete interfaces interface rddVR44
commit
delete protocols ospf4 area 0.0.0.0 interface rddVR44
commit
exit
exit
:-
1191261003885:  Card.cc 5690: Done with xorp-cli, rv: 0


And then add it to another:
1191261004057:  Card.cc 5684: Writing XORP cli commands to vr: 20001 cmds -:
configure
set interfaces interface rddVR44 vif rddVR44 address 10.4.0.7 prefix-length 24
commit
set protocols ospf4 area 0.0.0.0 interface rddVR44 vif rddVR44 address 10.4.0.7 interface-cost 1
commit
exit
exit
:-
1191261017077:  Card.cc 5690: Done with xorp-cli, rv: 0

After this is complete, XORP seems to be configured correctly,
but the OSPF peers remain in ExStart and Init states (depending
on which xorp you are querying.)

There is some other magic with routing rules to allow all of this to work on a single
machine, but you could probably reproduce this with 3 machines and some
vlan interfaces or similar...

If you want access to a system with my control software on it, I can
provide one on our DMZ.

Thanks,
Ben



> 
> Thanks,
> Pavlin


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

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xorp-vr10001.conf
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071001/5e9fc82a/attachment.ksh 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xorp-vr10002.conf
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071001/5e9fc82a/attachment-0001.ksh 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xorp-vr10008.conf
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071001/5e9fc82a/attachment-0002.ksh 

From pavlin at icir.org  Mon Oct  1 11:31:59 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Mon, 01 Oct 2007 11:31:59 -0700
Subject: [Xorp-users] VLAN support in XORP
In-Reply-To: Message from Mykola Dzham <i@levsha.org.ua> of "Mon,
	01 Oct 2007 00:29:37 +0300." <20070930212937.GF30765@expo.ukrweb.net> 
Message-ID: <200710011831.l91IVxah048882@possum.icir.org>

Mykola Dzham <i at levsha.org.ua> wrote:

>  Pavlin Radoslavov wrote:
> > 
> > In term of VLAN naming, the situation is the following.
> > In FreeBSD (and I believe in other BSDs as well, but I haven't
> > double-checked it yet), the vlan name has to be "vlan%d". However,
> > the integer after "vlan" doesn't need to match the VLAN ID. E.g.,
> > vlan10 could have VLAN ID of, say, 20.
> > 
> > In Linux the naming scheme can be programmed in advance using
> > ioctl(SET_VLAN_NAME_TYPE_CMD). The choices are names like:
> >  (a) vlan0005
> >  (b) eth1.0005
> >  (c) vlan5
> >  (d) eth0.5
> 
> FreeBSD can use naming scheme like <interface>.<tag> :
> 
> # ifconfig bfe0.10 create
> # ifconfig bfe0.10
> bfe0.10: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         ether 00:17:a4:db:e1:78
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active
>         vlan: 10 parent interface: bfe0
> # 
> 
> Support of such syntax commited 3 years ago
> 
> This scheme hawe some problems in FreeBSD : you cannot write in rc.conf
> line like ifconfig_bfe0.10="inet ..." - dots is not allowed in variable
> names; ng_ether cannot name ether node, attached to this interface, as
> bfe0.10 - dots is use in netgraph as delimiters in path
> 
> But this scheme also has some advantages: you can create several
> interfaces with same vlan id (on different parent interfaces), syntax
> is cisco-like ;)
> 
> Is it possible to implement in xorp both naming schemes: vlan%d and
> ifname.%d ?

Thank you for the info.
After a second round of changes, currently XORP allows the vlan name
to be (re)named to any string the user might like as long as the
underlying system supports that. To the best of my knowledge, vlan
renaming is supported in Linux, FreeBSD and DragonFlyBSD, but not in
NetBSD and OpenBSD.

Regards,
Pavlin


From xorp at scj-arlt.de  Tue Oct  2 13:32:06 2007
From: xorp at scj-arlt.de (Juergen Arlt)
Date: Tue, 2 Oct 2007 22:32:06 +0200
Subject: [Xorp-users] Possibility to generate about 20000 with XORP ?
Message-ID: <001d01c80533$4d62a300$3301a8c0@jarlt>

Hi,

I would like to distribute about 20,000 routers with XORP to an attached BGP
peer to simulate a part of the internet load. Do I need to configure all the
networks to advertise as static routes in XORP and redistribute it into BGP
or is there any better solution for this?

Thanks
Juergen

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

From pavlin at icir.org  Tue Oct  2 17:15:55 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Tue, 02 Oct 2007 17:15:55 -0700
Subject: [Xorp-users] Patch for making it harder to crash rib when
	removing interfaces.
In-Reply-To: Message from Pavlin Radoslavov <pavlin@icir.org> of "Fri,
	28 Sep 2007 14:00:59 PDT."
	<200709282100.l8SL0xab003545@possum.icir.org> 
Message-ID: <200710030015.l930FtMW004916@possum.icir.org>

> I just implemented the reference counting for the vif entries inside
> the RIB.
> I believe the reference counting needs to be done only inside the
> RouteEntry constructor and destructor which reduces significantly
> the amount of changes.
> 
> I will send you the patch in a private email to reduce the
> unnecessary traffic on the list.
> Please test it and let me know whether it fixes the problem.

For the record, Ben tested the patch (thanks Ben!) and it seems to
fix the problem (on the RIB side), so now the patch is committed to
CVS.

Pavlin


From pavlin at icir.org  Tue Oct  2 22:04:58 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Tue, 02 Oct 2007 22:04:58 -0700
Subject: [Xorp-users] CLI spin fix (hack)
In-Reply-To: Message from Ben Greear <greearb@candelatech.com> 
	of "Mon, 01 Oct 2007 10:59:40 PDT." <4701358C.1050200@candelatech.com> 
Message-ID: <200710030504.l9354wfo007155@possum.icir.org>

A non-text attachment was scrubbed...
Name: cli.patch
Type: text/x-c++
Size: 1420 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071002/fca0a821/attachment.bin 

From hantongs at gmail.com  Tue Oct  2 23:30:18 2007
From: hantongs at gmail.com (Hansi)
Date: Wed, 3 Oct 2007 14:30:18 +0800
Subject: [Xorp-users] STDOUT messages from XORP
Message-ID: <2f9e317b0710022330u47aa5958lb90ffc65080f37f0@mail.gmail.com>

Hello All,

I have successfully established OSPFv2 adjacencies on two XORP-installed
machines. Thank you for everyone's help. Both machines are installed with
different OS.

Box 1:

OS: Linux Ubuntu Fiesty Fawn 7.04
XORP: code from cvs

Box 2:

OS: FreeBSD AMD64 6.2
XORP: code from 1.4 stable.

Though everything appears to be working well. I can't help but notice some
messages generated from STDOUT when deleting ospfv2 protocols:

For BOX1: xorp from cvs

[ 2007/10/03 14:14:10  INFO xorp_rtrmgr:20965 RTRMGR +1019 task.cc shutdown
] Shutting down module: ospf4
[ 2007/10/03 14:14:10  INFO xorp_rtrmgr:20965 RTRMGR +275 module_manager.cc
module_exited ] Module normal exit: ospf4
[ 2007/10/03 14:14:11  WARNING xorp_rtrmgr:20965 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 "ospfv2" does not exist or is not enabled.
[ 2007/10/03 14:14:12  INFO xorp_rtrmgr:20965 RTRMGR +1019 task.cc shutdown
] Shutting down module: policy
[ 2007/10/03 14:14:12  INFO xorp_rtrmgr:20965 RTRMGR +275 module_manager.cc
module_exited ] Module normal exit: policy
[ 2007/10/03 14:14:12  INFO xorp_rtrmgr:20965 XRL +391 xrl_router.cc
send_resolved ] Sender died (protocol = "stcp", address = "127.0.0.1:36368")
[ 2007/10/03 14:14:12  ERROR xorp_rtrmgr:20965 LIBXORP +213
buffered_asyncio.cc io_event ] read error 111
[ 2007/10/03 14:14:12  ERROR xorp_rtrmgr:20965 XRL +785 xrl_pf_stcp.cc
read_event ] Read failed (error = 111)
[ 2007/10/03 14:14:12  ERROR xorp_rtrmgr:20965 XRL +638 xrl_pf_stcp.cc die ]
XrlPFSTCPSender died: read error
[ 2007/10/03 14:14:13  INFO xorp_rtrmgr:20965 RTRMGR +2228 task.cc run_task
] No more tasks to run


FOR BOX2: xorp 1.4 stable

[ 2007/10/03 06:18:03  INFO xorp_rtrmgr:1189 RTRMGR +1019 task.cc shutdown ]
Shutting down module: ospf4
[ 2007/10/03 06:18:03  INFO xorp_rtrmgr:1189 RTRMGR +275 module_manager.cc
module_exited ] Module normal exit: ospf4
[ 2007/10/03 06:18:04  WARNING xorp_rtrmgr:1189 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 "ospfv2" does not exist or is not enabled.
[ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 RTRMGR +1019 task.cc shutdown ]
Shutting down module: policy
[ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 XRL +391 xrl_router.cc
send_resolved ] Sender died (protocol = "stcp", address = "127.0.0.1:55705")
[ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 LIBCOMM +735 comm_sock.c
comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr =
127.0.0.1, remote_port = 55705): Connection refused
[ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 XRL +55 xrl_pf_factory.cc
create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError
from line 582 of xrl_pf_stcp.cc: Could not connect to 127.0.0.1:55705
[ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 XRL +402 xrl_router.cc
send_resolved ] Could not create XrlPFSender for protocol = "stcp" address =
"127.0.0.1:55705"
[ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 RTRMGR +275 module_manager.cc
module_exited ] Module normal exit: policy
[ 2007/10/03 06:18:05  WARNING xorp_rtrmgr:1189 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 "policy" does not exist or is not enabled.
[ 2007/10/03 06:18:06  INFO xorp_rtrmgr:1189 RTRMGR +2228 task.cc run_task ]
No more tasks to run

Are those STDOUT messages generated normal in nature? specifically these
ones:

2007/10/03 06:18:04  WARNING xorp_rtrmgr:1189 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 "ospfv2" does not exist or is not enabled.
[ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 RTRMGR +1019 task.cc shutdown ]
Shutting down module: policy
[ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 XRL +391 xrl_router.cc
send_resolved ] Sender died (protocol = "stcp", address = "127.0.0.1:55705")
[ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 LIBCOMM +735 comm_sock.c
comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr =
127.0.0.1, remote_port = 55705): Connection refused
[ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 XRL +55 xrl_pf_factory.cc
create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError
from line 582 of xrl_pf_stcp.cc: Could not connect to 127.0.0.1:55705
[ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 XRL +402 xrl_router.cc
send_resolved ] Could not create XrlPFSender for protocol = "stcp" address =
"127.0.0.1:55705"

Hoping for a favorable response.

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071003/82dfcf50/attachment.html 

From atanu at ICSI.Berkeley.EDU  Wed Oct  3 11:50:58 2007
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Wed, 03 Oct 2007 11:50:58 -0700
Subject: [Xorp-users] Possibility to generate about 20000 with XORP ?
In-Reply-To: Message from "Juergen Arlt" <xorp@scj-arlt.de> of "Tue,
	02 Oct 2007 22:32:06 +0200." <001d01c80533$4d62a300$3301a8c0@jarlt> 
Message-ID: <27641.1191437458@tigger.icir.org>

Hi,

What we do in our internal testing is to introduce a saved mtrd file.

Take a look at bgp/harness/test_peering2.sh (function test1), this test
uses the file icsi1.mrtd which is in the CVS repository, I think it
contains around 17K routes. 

There is program bgp/harness/harness.py that can be used to create BGP
sessions and introduce the routes contained in mrtd format files. This
program can also be used to collect routes in mrtd format. Note that
before running this program the programs xorp_finder, coord and
test_peer (with the argument "-s peer1") must be running.

	  Atanu.

>>>>> "Juergen" == Juergen Arlt <xorp at scj-arlt.de> writes:

    Juergen>    Hi,

    Juergen>    I would like to distribute about 20,000 routers with
    Juergen> XORP to an attached BGP peer to simulate a part of the
    Juergen> internet load. Do I need to configure all the networks to
    Juergen> advertise as static routes in XORP and redistribute it into
    Juergen> BGP or is there any better solution for this?

    Juergen>    Thanks

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


From pavlin at icir.org  Wed Oct  3 12:14:20 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Wed, 03 Oct 2007 12:14:20 -0700
Subject: [Xorp-users] STDOUT messages from XORP
In-Reply-To: Message from Hansi <hantongs@gmail.com> of "Wed,
	03 Oct 2007 14:30:18 +0800."
	<2f9e317b0710022330u47aa5958lb90ffc65080f37f0@mail.gmail.com> 
Message-ID: <200710031914.l93JEKwQ020838@possum.icir.org>

Hansi <hantongs at gmail.com> wrote:

> Hello All,
> 
> I have successfully established OSPFv2 adjacencies on two XORP-installed
> machines. Thank you for everyone's help. Both machines are installed with
> different OS.
> 
> Box 1:
> 
> OS: Linux Ubuntu Fiesty Fawn 7.04
> XORP: code from cvs
> 
> Box 2:
> 
> OS: FreeBSD AMD64 6.2
> XORP: code from 1.4 stable.
> 
> Though everything appears to be working well. I can't help but notice some
> messages generated from STDOUT when deleting ospfv2 protocols:

Those are transient warnings/errors that happen during startup or
shutdown which can be ignored. Ideally they shouldn't be there, but
for the time being we need to live with them :(

Regards,
Pavlin

> For BOX1: xorp from cvs
> 
> [ 2007/10/03 14:14:10  INFO xorp_rtrmgr:20965 RTRMGR +1019 task.cc shutdown
> ] Shutting down module: ospf4
> [ 2007/10/03 14:14:10  INFO xorp_rtrmgr:20965 RTRMGR +275 module_manager.cc
> module_exited ] Module normal exit: ospf4
> [ 2007/10/03 14:14:11  WARNING xorp_rtrmgr:20965 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 "ospfv2" does not exist or is not enabled.
> [ 2007/10/03 14:14:12  INFO xorp_rtrmgr:20965 RTRMGR +1019 task.cc shutdown
> ] Shutting down module: policy
> [ 2007/10/03 14:14:12  INFO xorp_rtrmgr:20965 RTRMGR +275 module_manager.cc
> module_exited ] Module normal exit: policy
> [ 2007/10/03 14:14:12  INFO xorp_rtrmgr:20965 XRL +391 xrl_router.cc
> send_resolved ] Sender died (protocol = "stcp", address = "127.0.0.1:36368")
> [ 2007/10/03 14:14:12  ERROR xorp_rtrmgr:20965 LIBXORP +213
> buffered_asyncio.cc io_event ] read error 111
> [ 2007/10/03 14:14:12  ERROR xorp_rtrmgr:20965 XRL +785 xrl_pf_stcp.cc
> read_event ] Read failed (error = 111)
> [ 2007/10/03 14:14:12  ERROR xorp_rtrmgr:20965 XRL +638 xrl_pf_stcp.cc die ]
> XrlPFSTCPSender died: read error
> [ 2007/10/03 14:14:13  INFO xorp_rtrmgr:20965 RTRMGR +2228 task.cc run_task
> ] No more tasks to run
> 
> 
> FOR BOX2: xorp 1.4 stable
> 
> [ 2007/10/03 06:18:03  INFO xorp_rtrmgr:1189 RTRMGR +1019 task.cc shutdown ]
> Shutting down module: ospf4
> [ 2007/10/03 06:18:03  INFO xorp_rtrmgr:1189 RTRMGR +275 module_manager.cc
> module_exited ] Module normal exit: ospf4
> [ 2007/10/03 06:18:04  WARNING xorp_rtrmgr:1189 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 "ospfv2" does not exist or is not enabled.
> [ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 RTRMGR +1019 task.cc shutdown ]
> Shutting down module: policy
> [ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 XRL +391 xrl_router.cc
> send_resolved ] Sender died (protocol = "stcp", address = "127.0.0.1:55705")
> [ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 LIBCOMM +735 comm_sock.c
> comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr =
> 127.0.0.1, remote_port = 55705): Connection refused
> [ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 XRL +55 xrl_pf_factory.cc
> create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError
> from line 582 of xrl_pf_stcp.cc: Could not connect to 127.0.0.1:55705
> [ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 XRL +402 xrl_router.cc
> send_resolved ] Could not create XrlPFSender for protocol = "stcp" address =
> "127.0.0.1:55705"
> [ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 RTRMGR +275 module_manager.cc
> module_exited ] Module normal exit: policy
> [ 2007/10/03 06:18:05  WARNING xorp_rtrmgr:1189 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 "policy" does not exist or is not enabled.
> [ 2007/10/03 06:18:06  INFO xorp_rtrmgr:1189 RTRMGR +2228 task.cc run_task ]
> No more tasks to run
> 
> Are those STDOUT messages generated normal in nature? specifically these
> ones:
> 
> 2007/10/03 06:18:04  WARNING xorp_rtrmgr:1189 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 "ospfv2" does not exist or is not enabled.
> [ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 RTRMGR +1019 task.cc shutdown ]
> Shutting down module: policy
> [ 2007/10/03 06:18:05  INFO xorp_rtrmgr:1189 XRL +391 xrl_router.cc
> send_resolved ] Sender died (protocol = "stcp", address = "127.0.0.1:55705")
> [ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 LIBCOMM +735 comm_sock.c
> comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr =
> 127.0.0.1, remote_port = 55705): Connection refused
> [ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 XRL +55 xrl_pf_factory.cc
> create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError
> from line 582 of xrl_pf_stcp.cc: Could not connect to 127.0.0.1:55705
> [ 2007/10/03 06:18:05  ERROR xorp_rtrmgr:1189 XRL +402 xrl_router.cc
> send_resolved ] Could not create XrlPFSender for protocol = "stcp" address =
> "127.0.0.1:55705"
> 
> Hoping for a favorable response.
> 
> Thank you.
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From atanu at ICSI.Berkeley.EDU  Wed Oct  3 14:39:31 2007
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Wed, 03 Oct 2007 14:39:31 -0700
Subject: [Xorp-users] adding/removing interfaces with xorp-cli
In-Reply-To: Message from Ben Greear <greearb@candelatech.com> 
	of "Thu, 20 Sep 2007 11:58:01 PDT." <46F2C2B9.6020401@candelatech.com> 
Message-ID: <69088.1191447571@tigger.icir.org>

Hi,

I have just checked in a fix that allows OSPF to be configured with
interface/vif/addresses that don't exist in the interfaces block.

Your example should work now.

     Atanu.

>>>>> "Ben" == Ben Greear <greearb at candelatech.com> writes:

    Ben> I tried these commands:

    Ben> delete interfaces interface rddVR44 vif rddVR44 address 10.4.0.1
    Ben> delete protocols ospf4 area 0.0.0.0 interface rddVR44 vif rddVR44 address 10.4.0.1
    Ben> set protocols ospf4 area 0.0.0.0 interface rddVR44 vif rddVR44 address 10.4.0.10
    Ben> set interfaces interface rddVR44 vif rddVR44 address 10.4.0.10 prefix-length 24
    Ben> commit

    Ben> I get this error on commit:

    Ben> root at lanforge-33-46# commit Commit Failed
    Ben> 102 Command failed BadPeer from line 479 of peer_manager.cc: Unable to get prefix length for rddVR44/rddVR44/10.4.0.10[edit]

    Ben> I also tried this:
    Ben> delete interfaces interface rddVR44 vif rddVR44 address 10.4.0.1
    Ben> delete protocols ospf4 area 0.0.0.0 interface rddVR44 vif rddVR44 address 10.4.0.1
    Ben> commit

    Ben> This failed with:
    Ben> root at lanforge-33-46# commit
    Ben> Commit Failed
    Ben> 102 Command failed Failed executing: "RemoveAddr4: rddVR44 rddVR44 10.4.0.1"[edit]

    Ben> And, I tried removing just the ospf portion:
    Ben> root at lanforge-33-46> configure Entering configuration mode.
    Ben> There are no other users in configuration mode.
    Ben> [edit]
    Ben> root at lanforge-33-46# delete protocols ospf4 area 0.0.0.0 interface rddVR44 vif rddVR44 address 10.4.0.1
    Ben> Deleting:
    Ben> 10.4.0.1 {
    Ben> }

    Ben> OK
    Ben> [edit]
    Ben> root at lanforge-33-46# commit
    Ben> Commit Failed
    Ben> 102 Command failed BadPeer from line 392 of peer_manager.cc: No mapping for rddVR44/rddVR44 exists[edit]


    Ben> I tried just changing the interface info:

    Ben> root at lanforge-33-46> configure Entering configuration mode.
    Ben> There are no other users in configuration mode.
    Ben> [edit]
    Ben> root at lanforge-33-46# delete interfaces interface rddVR44 vif rddVR44 address 10.4.0.1
    Ben> Deleting:
    Ben> 10.4.0.1 {
    Ben> prefix-length: 24
    Ben> }

    Ben> OK
    Ben> [edit]
    Ben> root at lanforge-33-46# set interfaces interface rddVR44 vif rddVR44 address 10.4.0.10 prefix-length 24
    Ben> [edit]
    Ben> root at lanforge-33-46# commit
    Ben> Commit Failed
    Ben> 102 Command failed Failed executing: "RemoveAddr4: rddVR44 rddVR44 10.4.0.1"[edit]
    Ben> root at lanforge-33-46#


    Ben> Any ideas?

    Ben> Thanks,
    Ben> Ben

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

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


From greearb at candelatech.com  Wed Oct  3 14:43:34 2007
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 03 Oct 2007 14:43:34 -0700
Subject: [Xorp-users] adding/removing interfaces with xorp-cli
In-Reply-To: <69088.1191447571@tigger.icir.org>
References: <69088.1191447571@tigger.icir.org>
Message-ID: <47040D06.2080801@candelatech.com>

Atanu Ghosh wrote:
> Hi,
> 
> I have just checked in a fix that allows OSPF to be configured with
> interface/vif/addresses that don't exist in the interfaces block.

Thanks, I will try that out in a few minutes and let you
know how it goes.

Ben

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


From greearb at candelatech.com  Wed Oct  3 15:56:02 2007
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 03 Oct 2007 15:56:02 -0700
Subject: [Xorp-users] CLI spin fix (hack)
In-Reply-To: <200710030504.l9354wfo007155@possum.icir.org>
References: <200710030504.l9354wfo007155@possum.icir.org>
Message-ID: <47041E02.8060406@candelatech.com>

Pavlin Radoslavov wrote:
>> Here are the commands I'm sending to xorpsh.  The numbers on the left
>> are millisecond timestamps, so this delete takes about 11 seconds!
> 
> I think I found the problem.
> Please apply the following patch to the xorp/cli directory and let
> me know whether it fixes the problem for you.

This appears to fix the problem, thanks!

Ben

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


From greearb at candelatech.com  Wed Oct  3 15:58:54 2007
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 03 Oct 2007 15:58:54 -0700
Subject: [Xorp-users] adding/removing interfaces with xorp-cli
In-Reply-To: <69088.1191447571@tigger.icir.org>
References: <69088.1191447571@tigger.icir.org>
Message-ID: <47041EAE.1090509@candelatech.com>

Atanu Ghosh wrote:
> Hi,
> 
> I have just checked in a fix that allows OSPF to be configured with
> interface/vif/addresses that don't exist in the interfaces block.
> 
> Your example should work now.

I was able to remove the intermediate commits from my
commands, and the commit still works fine.  So,
that part does seem to be fixed.

I still have the problem I reported yesterday where
the one ospf doesn't seem to realize the remote ospf
instance has changed when I logically move the interface
to a new remote xorp...

Thanks,
Ben

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


From atanu at ICSI.Berkeley.EDU  Wed Oct  3 16:11:34 2007
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Wed, 03 Oct 2007 16:11:34 -0700
Subject: [Xorp-users] adding/removing interfaces with xorp-cli
In-Reply-To: Message from Ben Greear <greearb@candelatech.com> 
	of "Wed, 03 Oct 2007 15:58:54 PDT." <47041EAE.1090509@candelatech.com> 
Message-ID: <92319.1191453094@tigger.icir.org>

>>>>> "Ben" == Ben Greear <greearb at candelatech.com> writes:

    Ben> Atanu Ghosh wrote:

    >> Hi,
    >> I have just checked in a fix that allows OSPF to be configured with
    >> interface/vif/addresses that don't exist in the interfaces block.
    >> Your example should work now.

    Ben> I was able to remove the intermediate commits from my
    Ben> commands, and the commit still works fine.  So,
    Ben> that part does seem to be fixed.

Good.

    Ben> I still have the problem I reported yesterday where
    Ben> the one ospf doesn't seem to realize the remote ospf
    Ben> instance has changed when I logically move the interface
    Ben> to a new remote xorp...

After you have moved the links could you send the output of "show
interfaces" from both ends of a "broken" link?

    Atanu.


From pavlin at icir.org  Wed Oct  3 16:14:39 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Wed, 03 Oct 2007 16:14:39 -0700
Subject: [Xorp-users] CLI spin fix (hack)
In-Reply-To: Message from Ben Greear <greearb@candelatech.com> 
	of "Wed, 03 Oct 2007 15:56:02 PDT." <47041E02.8060406@candelatech.com> 
Message-ID: <200710032314.l93NEdaE032549@possum.icir.org>

Ben Greear <greearb at candelatech.com> wrote:

> Pavlin Radoslavov wrote:
> >> Here are the commands I'm sending to xorpsh.  The numbers on the left
> >> are millisecond timestamps, so this delete takes about 11 seconds!
> > 
> > I think I found the problem.
> > Please apply the following patch to the xorp/cli directory and let
> > me know whether it fixes the problem for you.
> 
> This appears to fix the problem, thanks!

Patch committed.

Thanks!
Pavlin

> Ben
> 
> -- 
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From greearb at candelatech.com  Wed Oct  3 16:24:14 2007
From: greearb at candelatech.com (Ben Greear)
Date: Wed, 03 Oct 2007 16:24:14 -0700
Subject: [Xorp-users] adding/removing interfaces with xorp-cli
In-Reply-To: <92319.1191453094@tigger.icir.org>
References: <92319.1191453094@tigger.icir.org>
Message-ID: <4704249E.5000908@candelatech.com>

Atanu Ghosh wrote:
>>>>>> "Ben" == Ben Greear <greearb at candelatech.com> writes:
> 
>     Ben> Atanu Ghosh wrote:
> 
>     >> Hi,
>     >> I have just checked in a fix that allows OSPF to be configured with
>     >> interface/vif/addresses that don't exist in the interfaces block.
>     >> Your example should work now.
> 
>     Ben> I was able to remove the intermediate commits from my
>     Ben> commands, and the commit still works fine.  So,
>     Ben> that part does seem to be fixed.
> 
> Good.
> 
>     Ben> I still have the problem I reported yesterday where
>     Ben> the one ospf doesn't seem to realize the remote ospf
>     Ben> instance has changed when I logically move the interface
>     Ben> to a new remote xorp...
> 
> After you have moved the links could you send the output of "show
> interfaces" from both ends of a "broken" link?

Router-8 is the one that did not have config change to it (but had
it's connection to router 2 moved to router 1.)  It appears to think
it is still connected to router 2.

Since this is all sort of virtual on a single machine, it's possible it
*is* somehow talking to router 2, but router-2 certainly doesn't seem
to know about it.


[root at lanforge-33-46 lanforge]# export XORP_FINDER_SERVER_PORT=20008; xorpsh
Welcome to XORP on lanforge-33-46
root at lanforge-33-46> show ospf4 neighbor
   Address         Interface             State      ID              Pri  Dead
10.4.0.7         rddVR45/rddVR45        Full      127.1.0.2        128    36
root at lanforge-33-46> show interfaces
my_discard/my_discard: Flags:<ENABLED> mtu 0
         physical index 0
rddVR45/rddVR45: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
         inet 10.4.0.2 subnet 10.4.0.0/24 broadcast 10.4.0.255
         physical index 154
         ether 0:89:d6:d6:9a:42
rddVR5/rddVR5: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
         inet 10.1.0.1 subnet 10.1.0.0/24 broadcast 10.1.0.255
         physical index 99
         ether 0:16:94:2e:4a:1f
root at lanforge-33-46> quit
[root at lanforge-33-46 lanforge]# export XORP_FINDER_SERVER_PORT=20001; xorpsh
Welcome to XORP on lanforge-33-46
root at lanforge-33-46> show ospf4 neighbor
   Address         Interface             State      ID              Pri  Dead
10.0.0.1         rddVR1/rddVR1          Full      127.1.0.2        128    35
10.4.0.2         rddVR44/rddVR44        Init      127.1.0.8        128    36
root at lanforge-33-46> show interfaces
my_discard/my_discard: Flags:<ENABLED> mtu 0
         physical index 0
rddVR1/rddVR1: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
         inet 10.0.0.2 subnet 10.0.0.0/24 broadcast 10.0.0.255
         physical index 95
         ether 0:ec:14:a9:b8:b7
rddVR44/rddVR44: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
         inet 10.4.0.7 subnet 10.4.0.0/24 broadcast 10.4.0.255
         physical index 156
         ether 0:4d:6:d3:45:21
root at lanforge-33-46> quit


Thanks,
Ben


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


From atanu at ICSI.Berkeley.EDU  Thu Oct  4 11:55:49 2007
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Thu, 04 Oct 2007 11:55:49 -0700
Subject: [Xorp-users] adding/removing interfaces with xorp-cli
In-Reply-To: Message from Ben Greear <greearb@candelatech.com> 
	of "Wed, 03 Oct 2007 16:24:14 PDT." <4704249E.5000908@candelatech.com> 
Message-ID: <85647.1191524149@tigger.icir.org>

>>>>> "Ben" == Ben Greear <greearb at candelatech.com> writes:

    Ben> I still have the problem I reported yesterday where
    Ben> the one ospf doesn't seem to realize the remote ospf
    Ben> instance has changed when I logically move the interface
    Ben> to a new remote xorp...

    Atanu> After you have moved the links could you send the output of "show
    Atanu> interfaces" from both ends of a "broken" link?

    Ben> Router-8 is the one that did not have config change to it (but had
    Ben> it's connection to router 2 moved to router 1.)  It appears to think
    Ben> it is still connected to router 2.

    Ben> Since this is all sort of virtual on a single machine, it's
    Ben> possible it *is* somehow talking to router 2, but router-2
    Ben> certainly doesn't seem to know about it.

    Ben> [root at lanforge-33-46 lanforge]# export XORP_FINDER_SERVER_PORT=20008; xorpsh
    Ben> Welcome to XORP on lanforge-33-46
    Ben> root at lanforge-33-46> show ospf4 neighbor
    Ben> Address         Interface             State      ID              Pri  Dead
    Ben> 10.4.0.7         rddVR45/rddVR45        Full      127.1.0.2        128    36
    Ben> root at lanforge-33-46> show interfaces
    Ben> my_discard/my_discard: Flags:<ENABLED> mtu 0
    Ben> physical index 0
    Ben> rddVR45/rddVR45: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
    Ben> inet 10.4.0.2 subnet 10.4.0.0/24 broadcast 10.4.0.255
    Ben> physical index 154
    Ben> ether 0:89:d6:d6:9a:42
    Ben> rddVR5/rddVR5: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
    Ben> inet 10.1.0.1 subnet 10.1.0.0/24 broadcast 10.1.0.255
    Ben> physical index 99
    Ben> ether 0:16:94:2e:4a:1f
    Ben> root at lanforge-33-46> quit
    Ben> [root at lanforge-33-46 lanforge]# export XORP_FINDER_SERVER_PORT=20001; xorpsh
    Ben> Welcome to XORP on lanforge-33-46
    Ben> root at lanforge-33-46> show ospf4 neighbor
    Ben> Address         Interface             State      ID              Pri  Dead
    Ben> 10.0.0.1         rddVR1/rddVR1          Full      127.1.0.2        128    35
    Ben> 10.4.0.2         rddVR44/rddVR44        Init      127.1.0.8        128    36
    Ben> root at lanforge-33-46> show interfaces
    Ben> my_discard/my_discard: Flags:<ENABLED> mtu 0
    Ben> physical index 0
    Ben> rddVR1/rddVR1: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
    Ben> inet 10.0.0.2 subnet 10.0.0.0/24 broadcast 10.0.0.255
    Ben> physical index 95
    Ben> ether 0:ec:14:a9:b8:b7
    Ben> rddVR44/rddVR44: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
    Ben> inet 10.4.0.7 subnet 10.4.0.0/24 broadcast 10.4.0.255
    Ben> physical index 156
    Ben> ether 0:4d:6:d3:45:21
    Ben> root at lanforge-33-46> quit

The default configuration for OSPF has a router dead interval
(router-dead-interval) of 40 seconds. Only after 40 seconds has elapsed
during which time no hello or other messages have been received by a
router will the state of a neighbour change. The last field in the "show
ospf4 neighbour" is the router dead interval counting down. The state
remaining for 40 seconds after a link change should be expected. After
40 seconds the state should go to down. If you were moving physical
cables around then the disconnecting of the cable from the interface
would be detected by the FEA and OSPF would be informed, in which case
the state would move immediately to down.

>From what you say it seems that no new adjacencies are formed after
moving a link. I would enable tracing in OSPF and/or use tcpdump to see
if hello messages are being exchanged.

    Atanu.


From greearb at candelatech.com  Thu Oct  4 22:26:19 2007
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 04 Oct 2007 22:26:19 -0700
Subject: [Xorp-users] Virtual routers & interface migration is working!
Message-ID: <4705CAFB.6030806@candelatech.com>

Hello!

For the record, with Atanu's latest fixes to OSPF, I am now able to
get link migration between the Xorp virtual routers working as planned.

In particular:  I was running 3 virtual routers with OSPF, and then I 
moved one
link from one router to another.  The OSPF daemons noticed almost 
immediately (1-2
seconds it seems) and renegotiated the state machine.  The new routes 
were in place
within about 10 seconds.

We will be doing testing with larger numbers of routers and interfaces in
the coming weeks, so you've not heard the last from me, but I do
want to let the developers know I'm very appreciative of their quick bug
fixes!

My remaining Xorp wish-list includes:
*  Make xorpsh faster.  It takes multiple seconds to add or delete an 
interface & commit the
    changes.  I think this should take less than 1 second.  I've been 
testing on a slow machine,
    so maybe faster hardware will help here as well.

*  Add bpf filtering so that fea receives only packets for it's own 
interfaces.  (Yes, I know this
    will require proof of performance gains before it's allowed into the 
official code.)

*  Figure out how to build with shared libraries to decrease executable 
size (maybe it works now, not sure.)

*  Long term:  Maybe find/implement a faster mesh routing protocol.  
OSPF is nice,
    but there may be options better suited for highly dynamic networks 
like mobile
    wireless nodes...

Thanks,
Ben

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



From mayank.kandari at gmail.com  Mon Oct  8 02:11:56 2007
From: mayank.kandari at gmail.com (Mayank Kandari)
Date: Mon, 8 Oct 2007 14:41:56 +0530
Subject: [Xorp-users] RIP not announcing the route
Message-ID: <328b1be80710080211k2a0cf05fvdbd955ff916440b3@mail.gmail.com>

Hello

         I have confired the rip on xorp , but  I am not able to anounce
network from my machine.

            protocols {
        rip {
            interface eth0 {
                vif eth0 {
                    address 172.16.0.9 {
                    }
                }
            }
            export: "connected"
        }
    }
    policy {
        policy-statement connected {
            term export {
                from {
                    protocol: "connected"
                }
            }
        }
    }
    interfaces {
        interface eth0 {
            vif eth0 {
                address 10.16.0.1 {
                    prefix-length: 8
                }
                address 10.16.0.2 {
                    prefix-length: 8
                }
            }
            default-system-config {
            }
        }
    }

This is  configuration of my xorp router. Can any one help me in solving the
problem.

regards
Mayank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071008/6fc09bc5/attachment.html 

From zec at icir.org  Mon Oct  8 02:57:06 2007
From: zec at icir.org (Marko Zec)
Date: Mon, 8 Oct 2007 11:57:06 +0200
Subject: [Xorp-users] RIP not announcing the route
In-Reply-To: <328b1be80710080211k2a0cf05fvdbd955ff916440b3@mail.gmail.com>
References: <328b1be80710080211k2a0cf05fvdbd955ff916440b3@mail.gmail.com>
Message-ID: <200710081157.07265.zec@icir.org>

On Monday 08 October 2007 11:11:56 Mayank Kandari wrote:
> Hello
>
>          I have confired the rip on xorp , but  I am not able to
> anounce network from my machine.
>
>             protocols {
>         rip {
>             interface eth0 {
>                 vif eth0 {
>                     address 172.16.0.9 {
>                     }
>                 }
>             }
>             export: "connected"
>         }
>     }
>     policy {
>         policy-statement connected {
>             term export {
>                 from {
>                     protocol: "connected"
>                 }
>             }
>         }
>     }
>     interfaces {
>         interface eth0 {
>             vif eth0 {
>                 address 10.16.0.1 {
>                     prefix-length: 8
>                 }
>                 address 10.16.0.2 {
>                     prefix-length: 8
>                 }
>             }
>             default-system-config {
>             }
>         }
>     }
>
> This is  configuration of my xorp router. Can any one help me in
> solving the problem.

Addresses you configured on interfaces and in the rip section do not 
match: in rip you reference 172.16.0.9, whereas on eth0 you have 
configured 10.16.0.1 (and 10.16.0.2 as well with an overlapping prefix 
length, which is a combination which probably won't work on may 
operating systems).

Marko


From pavlin at icir.org  Mon Oct  8 14:40:28 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Mon, 08 Oct 2007 14:40:28 -0700
Subject: [Xorp-users] RIP not announcing the route
In-Reply-To: Message from Marko Zec <zec@icir.org> 
	of "Mon, 08 Oct 2007 11:57:06 +0200." <200710081157.07265.zec@icir.org> 
Message-ID: <200710082140.l98LeSEs018827@possum.icir.org>

Marko Zec <zec at icir.org> wrote:

> On Monday 08 October 2007 11:11:56 Mayank Kandari wrote:
> > Hello
> >
> >          I have confired the rip on xorp , but  I am not able to
> > anounce network from my machine.
> >
> >             protocols {
> >         rip {
> >             interface eth0 {
> >                 vif eth0 {
> >                     address 172.16.0.9 {
> >                     }
> >                 }
> >             }
> >             export: "connected"
> >         }
> >     }
> >     policy {
> >         policy-statement connected {
> >             term export {
> >                 from {
> >                     protocol: "connected"
> >                 }
> >             }
> >         }
> >     }
> >     interfaces {
> >         interface eth0 {
> >             vif eth0 {
> >                 address 10.16.0.1 {
> >                     prefix-length: 8
> >                 }
> >                 address 10.16.0.2 {
> >                     prefix-length: 8
> >                 }
> >             }
> >             default-system-config {
> >             }
> >         }
> >     }
> >
> > This is  configuration of my xorp router. Can any one help me in
> > solving the problem.
> 
> Addresses you configured on interfaces and in the rip section do not 
> match: in rip you reference 172.16.0.9, whereas on eth0 you have 
> configured 10.16.0.1 (and 10.16.0.2 as well with an overlapping prefix 
> length, which is a combination which probably won't work on may 
> operating systems).

In addition, you shouldn't be mixing the inplicit address
configuration "default-system-config" with the explicit
"vif/address" configuration. You need to delete either the
"default-system-config" statement, or the whole "vif eth0" section.

Regards,
Pavlin


From rajendraprasad at ceeyes.com  Tue Oct  9 00:09:52 2007
From: rajendraprasad at ceeyes.com (Rajendra)
Date: Tue, 9 Oct 2007 12:39:52 +0530
Subject: [Xorp-users] process to be followed to run OSPF on Host----reg.
Message-ID: <200710090720.l997KsWm015562@pork.ICSI.Berkeley.EDU>

 
Hi all,
 
  I tried to run OSPF v2 and v3 on my host, but not succeded.
 
 Can any one send me the  step by step procedure to be followed to Run OSPF.
 
 
 Thanks
 
Somineni
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071009/467ff20b/attachment.html 

From ror.sanjeev at gmail.com  Tue Oct  9 06:34:56 2007
From: ror.sanjeev at gmail.com (sanjeev kumar)
Date: Tue, 9 Oct 2007 19:04:56 +0530
Subject: [Xorp-users] Unable to configure RIP on XORP??
Message-ID: <477942240710090634m10ecec1dxa0c754f7c30fbc7e@mail.gmail.com>

Ignoring non-text/plain MIME parts

- Unprocessed:
      Please go through the following configuration:
      PC1(with XORP)  eth0 : 172.16.10.8 255.255.0.0
      eth0:0(Virtual Interface):192.168.0.1 255.255.255.0
    PC2(with
      XORP)  eth0 : 172.16.10.9 255.255.0.0
      eth0:0(Virtual Interface):10.0.0.1 255.255.255.0
         Virtual
      Interface(eth0:0)------PC1----
   ----------------------PC2-----------------Virtual
      Interface(eth0:0)
              (192.168.0.1)            (172.16.0.8)          (172.16.0.9)
      (10.0.0.1)
      This is my PC confguration:
           rip {
                  interface eth0
   - Ignored:
                  interface "eth0:0"
              }
          }
          policy {
              policy-statement connected {
                  term export {

- Ignored:
- Show quoted text -
                      from {
                          protocol: "connected"
                      }
                  }
              }
          }
          interfaces {
              restore-original-config-on-shutdown: false
              interface eth0 {
                  disable: false
                  discard: false
                  description: ""
                  vif eth0 {
                      disable: false
                  }
                  default-system-config {
                  }
              }
          }

      Same configuration on the second PC.Please guide me how to enable
   RIP(step
      by step if possible).How to advertise the different networks in
   RIP(XORP)..I
      had worked on Cisco router ,now trying to configure XORP.

      Thanks & Regards,
      Sanjeev


   --
   Efforts may fail,But don't Fail to make efforts.
   ---------
   Sanjeev Kumar
   Project Engineer
   CDAC(Formerly NCST)
   Juhu,Mumbai-400049

- Done.



---------- Forwarded message ----------
From: "sanjeev kumar" <ror.sanjeev at gmail.com>
To: xorp-users-request at xorp.org
Date: Tue, 9 Oct 2007 18:57:37 +0530
Subject: Unable to configure RIP on XORP??
 I am new to XORP.I was unable to configure RIP at XORP
   Please go through the following configuration:
   PC1(with XORP)  eth0 : 172.16.10.8 255.255.0.0
   eth0:0(Virtual Interface): 192.168.0.1 255.255.255.0

 PC2(with
   XORP)  eth0 : 172.16.10.9 255.255.0.0
   eth0:0(Virtual Interface):10.0.0.1 255.255.255.0
      Virtual
   Interface(eth0:0)------PC1----
----------------------PC2-----------------Virtual
   Interface(eth0:0)
           ( 192.168.0.1)            (172.16.0.8)          ( 172.16.0.9)
   (10.0.0.1)
   This is my PC confguration:
        rip {
               interface eth0

- Ignored:
               interface "eth0:0"
           }
       }
       policy {
           policy-statement connected {
               term export {
                   from {
                       protocol: "connected"
                   }
               }
           }
       }
       interfaces {
           restore-original-config-on-shutdown: false
           interface eth0 {
               disable: false
               discard: false
               description: ""
               vif eth0 {
                   disable: false
               }
               default-system-config {
               }
           }
       }

   Same configuration on the second PC.Please guide me how to enable
RIP(step
   by step if possible).How to advertise the different networks in
RIP(XORP)..I
   had worked on Cisco router ,now trying to configure XORP.

   Thanks & Regards,
   Sanjeev


-- 
Efforts may fail,But don't Fail to make efforts.
---------
Sanjeev Kumar
Project Engineer
CDAC(Formerly NCST)
Juhu,Mumbai-400049
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071009/7b6c5612/attachment.html 

From zec at icir.org  Tue Oct  9 08:09:11 2007
From: zec at icir.org (Marko Zec)
Date: Tue, 9 Oct 2007 17:09:11 +0200
Subject: [Xorp-users] Unable to configure RIP on XORP??
In-Reply-To: <477942240710090634m10ecec1dxa0c754f7c30fbc7e@mail.gmail.com>
References: <477942240710090634m10ecec1dxa0c754f7c30fbc7e@mail.gmail.com>
Message-ID: <200710091709.11603.zec@icir.org>

On Tuesday 09 October 2007 15:34:56 sanjeev kumar wrote:
> Ignoring non-text/plain MIME parts
>
> - Unprocessed:
>       Please go through the following configuration:
>       PC1(with XORP)  eth0 : 172.16.10.8 255.255.0.0
>       eth0:0(Virtual Interface):192.168.0.1 255.255.255.0
>     PC2(with
>       XORP)  eth0 : 172.16.10.9 255.255.0.0
>       eth0:0(Virtual Interface):10.0.0.1 255.255.255.0
>          Virtual
>       Interface(eth0:0)------PC1----
>    ----------------------PC2-----------------Virtual
>       Interface(eth0:0)
>               (192.168.0.1)            (172.16.0.8)         
> (172.16.0.9) (10.0.0.1)
>       This is my PC confguration:
>            rip {
>                   interface eth0
>    - Ignored:
>                   interface "eth0:0"
>               }
>           }
>           policy {
>               policy-statement connected {
>                   term export {
>
> - Ignored:
> - Show quoted text -
>                       from {
>                           protocol: "connected"
>                       }
>                   }
>               }
>           }
>           interfaces {
>               restore-original-config-on-shutdown: false
>               interface eth0 {
>                   disable: false
>                   discard: false
>                   description: ""
>                   vif eth0 {
>                       disable: false
>                   }
>                   default-system-config {
>                   }
>               }
>           }
>
>       Same configuration on the second PC.Please guide me how to
> enable RIP(step
>       by step if possible).How to advertise the different networks in
>    RIP(XORP)..I
>       had worked on Cisco router ,now trying to configure XORP.
>
>       Thanks & Regards,
>       Sanjeev
>
>
>    --
>    Efforts may fail,But don't Fail to make efforts.
>    ---------
>    Sanjeev Kumar
>    Project Engineer
>    CDAC(Formerly NCST)
>    Juhu,Mumbai-400049
>
> - Done.
>
>
>
> ---------- Forwarded message ----------
> From: "sanjeev kumar" <ror.sanjeev at gmail.com>
> To: xorp-users-request at xorp.org
> Date: Tue, 9 Oct 2007 18:57:37 +0530
> Subject: Unable to configure RIP on XORP??
>  I am new to XORP.I was unable to configure RIP at XORP
>    Please go through the following configuration:
>    PC1(with XORP)  eth0 : 172.16.10.8 255.255.0.0
>    eth0:0(Virtual Interface): 192.168.0.1 255.255.255.0
>
>  PC2(with
>    XORP)  eth0 : 172.16.10.9 255.255.0.0
>    eth0:0(Virtual Interface):10.0.0.1 255.255.255.0
>       Virtual
>    Interface(eth0:0)------PC1----
> ----------------------PC2-----------------Virtual
>    Interface(eth0:0)
>            ( 192.168.0.1)            (172.16.0.8)          (
> 172.16.0.9) (10.0.0.1)
>    This is my PC confguration:
>         rip {
>                interface eth0
>
> - Ignored:
>                interface "eth0:0"
>            }
>        }
>        policy {
>            policy-statement connected {
>                term export {
>                    from {
>                        protocol: "connected"
>                    }
>                }
>            }
>        }
>        interfaces {
>            restore-original-config-on-shutdown: false
>            interface eth0 {
>                disable: false
>                discard: false
>                description: ""
>                vif eth0 {
>                    disable: false
>                }
>                default-system-config {
>                }
>            }
>        }
>
>    Same configuration on the second PC.Please guide me how to enable
> RIP(step
>    by step if possible).How to advertise the different networks in
> RIP(XORP)..I
>    had worked on Cisco router ,now trying to configure XORP.
>
>    Thanks & Regards,
>    Sanjeev

Hi Sanjeev,

it would help if you could post in plain ASCII (not as a MIME 
attachment) complete XORP configurations for both nodes - from garbled 
text as above it is quite difficult to deduct the actual issues you 
might be facing.

Note that in rip config section you have to reference each 
if/vif/address on which you wish to have RIP enabled, as documented in 
section 7 of XORP's user manual.

Marko


From atanu at ICSI.Berkeley.EDU  Tue Oct  9 10:04:02 2007
From: atanu at ICSI.Berkeley.EDU (Atanu Ghosh)
Date: Tue, 09 Oct 2007 10:04:02 -0700
Subject: [Xorp-users] process to be followed to run OSPF on Host----reg.
In-Reply-To: Message from "Rajendra" <rajendraprasad@ceeyes.com> of "Tue,
	09 Oct 2007 12:39:52 +0530."
	<200710090720.l997KsWm015562@pork.ICSI.Berkeley.EDU> 
Message-ID: <30814.1191949442@tigger.icir.org>

Hi,

You will find example configurations on:
<http://www.xorp.org/getting_started.html>

	Atanu.

>>>>> "Rajendra" == Rajendra  <rajendraprasad at ceeyes.com> writes:

    Rajendra>    Hi all,



    Rajendra>      I tried to run OSPF v2 and v3 on my host, but not
    Rajendra> succeded.



    Rajendra>     Can any one send me the step by step procedure to be
    Rajendra> followed to Run OSPF.





    Rajendra>     Thanks



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


From ror.sanjeev at gmail.com  Wed Oct 10 21:08:08 2007
From: ror.sanjeev at gmail.com (sanjeev kumar)
Date: Thu, 11 Oct 2007 09:38:08 +0530
Subject: [Xorp-users] Unable to configure RIP at XORP:
Message-ID: <477942240710102108m6f0cd857q54c893ab41cc9aac@mail.gmail.com>

Dear all,

  Please suggest me full steps how to configure RIP on XORP.

 The scenario is I had installed XORP on two machines.I had created virtual
Interfaces e.g. a logical interface,eth0:0 with different networks than the
serial connection of both of the XORP router.When i configured the static
route,they are able to communicate .But how to advertise the Networks in
RIP.

              Like there are two interfaces on both(xorp) machines,one is
eth0 and other is eth0:0(Logical interface).And eth0 & eth0:0 have different
networks on both.But when i enable RIP,they are not able to communicate
however they are communicating with static route.

  Please guide me full steps,how to advertise Networks in RIP .I had tried
all the commands.

Thanks & regards,
Sanjeev
-- 
Efforts may fail,But don't Fail to make efforts.
---------
Sanjeev Kumar
Project Engineer
CDAC(Formerly NCST)
Juhu,Mumbai-400049
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071011/d9a303f6/attachment.html 

From rajendraprasad at ceeyes.com  Wed Oct 10 22:34:26 2007
From: rajendraprasad at ceeyes.com (Rajendra)
Date: Thu, 11 Oct 2007 11:04:26 +0530
Subject: [Xorp-users] what changes we have to done to  "config.boot" file
Message-ID: <200710110545.l9B5jT18008431@pork.ICSI.Berkeley.EDU>

HI all,
 
 can any one suggest me , What changes i have to made to "config.boot"
file, so that i can able to run OSPF on my system.
 
i taken "config.boot.sample " file as a reference from Root manager and
created "config.boot" file and placed in root manager directory, and then i 
 
executed the following .
 
             " ./xorp_rtrmgr -b config.boot "
 
then i am getting the following Errors :
 
    1). Group "xorp" does not exist on this system.
 
   2). Error connecting socket (family = 2, remote_addr = 127.0.0.1,
remote_port = 13000): Connection refused
 
  3). Commit failed: 102 Command failed Could not open user-level Click
socket: Connection refused 
 
  4).  Command "/home/RajKumar/xorp-1.4/fea/xorp_fea": terminated with
signal 15.
 
  
 
 Thanks
 
  Somineni



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

From pavlin at icir.org  Wed Oct 10 22:59:43 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Wed, 10 Oct 2007 22:59:43 -0700
Subject: [Xorp-users] what changes we have to done to "config.boot" file
In-Reply-To: Message from "Rajendra" <rajendraprasad@ceeyes.com> of "Thu,
	11 Oct 2007 11:04:26 +0530."
	<200710110545.l9B5jT18008431@pork.ICSI.Berkeley.EDU> 
Message-ID: <200710110559.l9B5xhHg086653@possum.icir.org>

See Adam's reply this morning to one of your colleagues:

http://mailman.icsi.berkeley.edu/pipermail/xorp-hackers/2007-October/001218.html

Pavlin

Rajendra <rajendraprasad at ceeyes.com> wrote:

> HI all,
>  
>  can any one suggest me , What changes i have to made to "config.boot"
> file, so that i can able to run OSPF on my system.
>  
> i taken "config.boot.sample " file as a reference from Root manager and
> created "config.boot" file and placed in root manager directory, and then i 
>  
> executed the following .
>  
>              " ./xorp_rtrmgr -b config.boot "
>  
> then i am getting the following Errors :
>  
>     1). Group "xorp" does not exist on this system.
>  
>    2). Error connecting socket (family = 2, remote_addr = 127.0.0.1,
> remote_port = 13000): Connection refused
>  
>   3). Commit failed: 102 Command failed Could not open user-level Click
> socket: Connection refused 
>  
>   4).  Command "/home/RajKumar/xorp-1.4/fea/xorp_fea": terminated with
> signal 15.
>  
>   
>  
>  Thanks
>  
>   Somineni
> 
> 
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From mayank.kandari at gmail.com  Wed Oct 10 23:09:47 2007
From: mayank.kandari at gmail.com (Mayank Kandari)
Date: Thu, 11 Oct 2007 11:39:47 +0530
Subject: [Xorp-users] Problem in RIP
Message-ID: <328b1be80710102309k9c8d5e4g4ec02f6e18ba93e0@mail.gmail.com>

Hello ,
            I am not able to accept RIP packet on my XORP router from my
neighbour XORP router.  following is the configuration of my router


    protocols {
        rip {
            interface eth0 {
                vif eth0 {
                    address 172.16.0.8 {
                    }
                }
            }
            export: "connected"
        }
        static {
            route 192.168.0.0/24 {
                next-hop: 172.16.0.4
            }
        }
    }
    policy {
        policy-statement static {
            term export {
                from {
                    protocol: "static"
                }
            }
        }
    }
    interfaces {
        interface eth0 {
            vif eth0 {
                address 172.16.0.8 {
                    prefix-length: 16
                }
            }
        }
    }

My router is sending RIP packet but not receiving. Following is the rip
statistics of rip interface :

mayank at cmj-isea-08.cdacmumbai.in> show rip statistics eth0 eth0 172.16.0.8

* RIP on eth0 eth0 172.16.0.8
  Status: enabled

  Counter                                        Value
  --------------------------------                  ----------------
  Requests Sent                                 88
  Updates Sent                                   87
  Triggered Updates Sent                     0
  Non-RIP Updates Sent                      0
  Total Packets Received                     0
  Request Packets Received                0
  Update Packets Received                  0
  Bad Packets Received                       0
  Authentication Failures                       0
  Bad Routes Received                        0
  Non-RIP Requests Received              0

when I take the tcpdump on my network interface , I am getting the rip
packet of neighbor router .

What is the problem with my configuration ?

regards
Mayank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071011/b4c6ba03/attachment.html 

From pavlin at icir.org  Wed Oct 10 23:50:06 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Wed, 10 Oct 2007 23:50:06 -0700
Subject: [Xorp-users] Problem in RIP
In-Reply-To: Message from "Mayank Kandari" <mayank.kandari@gmail.com> of "Thu,
	11 Oct 2007 11:39:47 +0530."
	<328b1be80710102309k9c8d5e4g4ec02f6e18ba93e0@mail.gmail.com> 
Message-ID: <200710110650.l9B6o6m0087047@possum.icir.org>

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

> Hello ,
>             I am not able to accept RIP packet on my XORP router from my
> neighbour XORP router.  following is the configuration of my router

This might not be related to the receiving of the RIP packets, but
inside the rip section you are exporting "connected" policy, while
that policy itself doesn't exist.
Did you mean to export "connected" or "static"?

Actually, I am surprised that XORP actually accepted this
configuration: I believe it will balk if the referenced policy
doesn't exist.
Hence, please confirm that you are running the latest XORP release
1.4 or the latest code from CVS, and that XORP indeed accepted this
configuration.

About the problem with receiving the RIP packets, please confirm
that the neighbor RIP router's interface belongs to the
172.16.0.0/16 subnet.
Also, it will be helpful if you copy and paste any log messages
(during startup and while both XORP instances were running) that
might be related to the problem you are seeing.

Thanks,
Pavlin

> 
>     protocols {
>         rip {
>             interface eth0 {
>                 vif eth0 {
>                     address 172.16.0.8 {
>                     }
>                 }
>             }
>             export: "connected"
>         }
>         static {
>             route 192.168.0.0/24 {
>                 next-hop: 172.16.0.4
>             }
>         }
>     }
>     policy {
>         policy-statement static {
>             term export {
>                 from {
>                     protocol: "static"
>                 }
>             }
>         }
>     }
>     interfaces {
>         interface eth0 {
>             vif eth0 {
>                 address 172.16.0.8 {
>                     prefix-length: 16
>                 }
>             }
>         }
>     }
> 
> My router is sending RIP packet but not receiving. Following is the rip
> statistics of rip interface :
> 
> mayank at cmj-isea-08.cdacmumbai.in> show rip statistics eth0 eth0 172.16.0.8
> 
> * RIP on eth0 eth0 172.16.0.8
>   Status: enabled
> 
>   Counter                                        Value
>   --------------------------------                  ----------------
>   Requests Sent                                 88
>   Updates Sent                                   87
>   Triggered Updates Sent                     0
>   Non-RIP Updates Sent                      0
>   Total Packets Received                     0
>   Request Packets Received                0
>   Update Packets Received                  0
>   Bad Packets Received                       0
>   Authentication Failures                       0
>   Bad Routes Received                        0
>   Non-RIP Requests Received              0
> 
> when I take the tcpdump on my network interface , I am getting the rip
> packet of neighbor router .
> 
> What is the problem with my configuration ?
> 
> regards
> Mayank
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From pavlin at icir.org  Wed Oct 10 23:56:46 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Wed, 10 Oct 2007 23:56:46 -0700
Subject: [Xorp-users] Unable to configure RIP at XORP:
In-Reply-To: Message from "sanjeev kumar" <ror.sanjeev@gmail.com> of "Thu,
	11 Oct 2007 09:38:08 +0530."
	<477942240710102108m6f0cd857q54c893ab41cc9aac@mail.gmail.com> 
Message-ID: <200710110656.l9B6ukBW087189@possum.icir.org>

sanjeev kumar <ror.sanjeev at gmail.com> wrote:

> Dear all,
> 
>   Please suggest me full steps how to configure RIP on XORP.

The "Getting Started" Web page contains basic information how to
configure RIP:

http://www.xorp.org/getting_started.html

The User Manual contains more details.

In your case you need to export the "connected" routes. The "Getting
Started" page has an example how to do that.

If this doesn't help, please post your exact configurations (on both
machines).

Regards,
Pavlin

>  The scenario is I had installed XORP on two machines.I had created virtual
> Interfaces e.g. a logical interface,eth0:0 with different networks than the
> serial connection of both of the XORP router.When i configured the static
> route,they are able to communicate .But how to advertise the Networks in
> RIP.
> 
>               Like there are two interfaces on both(xorp) machines,one is
> eth0 and other is eth0:0(Logical interface).And eth0 & eth0:0 have different
> networks on both.But when i enable RIP,they are not able to communicate
> however they are communicating with static route.
> 
>   Please guide me full steps,how to advertise Networks in RIP .I had tried
> all the commands.
> 
> Thanks & regards,
> Sanjeev
> -- 
> Efforts may fail,But don't Fail to make efforts.
> ---------
> Sanjeev Kumar
> Project Engineer
> CDAC(Formerly NCST)
> Juhu,Mumbai-400049
> _______________________________________________
> 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 Oct 11 01:41:05 2007
From: mayank.kandari at gmail.com (Mayank Kandari)
Date: Thu, 11 Oct 2007 14:11:05 +0530
Subject: [Xorp-users] RIP sending route but not receiving
Message-ID: <328b1be80710110141w4bc28872t62429249ed71881c@mail.gmail.com>

Hello , this is the configuration of my router

mayank at cmj-isea-08.cdacmumbai.in# show
    protocols {
        rip {
            interface eth0 {
                vif eth0 {
                    address 172.16.0.8 {
                    }
                }
            }
            export: "static"
        }
        static {
            route 40.0.0.0/8 {
                next-hop: 172.16.0.100
            }
        }
    }
    policy {
        policy-statement connected {
            term export {
                from {
                    protocol: "connected"
                    network4: 10.0.0.0/8
                }
                to {
                    nexthop4: 172.16.0.4..172.16.0.4
                }
                then {
                    accept {
                    }
                }
            }
        }
        policy-statement static {
            term export {
                from {
                    protocol: "static"
                }
            }
        }
    }
    interfaces {
        interface eth0 {
            vif eth0 {
                address 172.16.0.8 {
                    prefix-length: 16
                }
                address 10.0.0.1 {
                    prefix-length: 8
                }
            }
        }
    }

I am able to send  route from my machine and another xorp machine in my
network (172.16.0.0/16) is receiving the routes from my xorp router.
I am not receiving any route and even not able to view peers :( . Any one
can help me.

regards
Mayank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071011/a3bb6b61/attachment.html 

From pavlin at icir.org  Thu Oct 11 13:22:02 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 11 Oct 2007 13:22:02 -0700
Subject: [Xorp-users] RIP sending route but not receiving
In-Reply-To: Message from "Mayank Kandari" <mayank.kandari@gmail.com> of "Thu,
	11 Oct 2007 14:11:05 +0530."
	<328b1be80710110141w4bc28872t62429249ed71881c@mail.gmail.com> 
Message-ID: <200710112022.l9BKM2hW096929@possum.icir.org>

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

> Hello , this is the configuration of my router
> 
> mayank at cmj-isea-08.cdacmumbai.in# show
>     protocols {
>         rip {
>             interface eth0 {
>                 vif eth0 {
>                     address 172.16.0.8 {
>                     }
>                 }
>             }
>             export: "static"
>         }
>         static {
>             route 40.0.0.0/8 {
>                 next-hop: 172.16.0.100
>             }
>         }
>     }
>     policy {
>         policy-statement connected {
>             term export {
>                 from {
>                     protocol: "connected"
>                     network4: 10.0.0.0/8
>                 }
>                 to {
>                     nexthop4: 172.16.0.4..172.16.0.4
>                 }
>                 then {
>                     accept {
>                     }
>                 }
>             }
>         }
>         policy-statement static {
>             term export {
>                 from {
>                     protocol: "static"
>                 }
>             }
>         }
>     }
>     interfaces {
>         interface eth0 {
>             vif eth0 {
>                 address 172.16.0.8 {
>                     prefix-length: 16
>                 }
>                 address 10.0.0.1 {
>                     prefix-length: 8
>                 }
>             }
>         }
>     }
> 
> I am able to send  route from my machine and another xorp machine in my
> network (172.16.0.0/16) is receiving the routes from my xorp router.
> I am not receiving any route and even not able to view peers :( . Any one
> can help me.

Please send the configuration of the other XORP router as well.

Pavlin

P.S. For practical reasons, please send the configuration as a reply
in this thread instead of starting a new one so it is easier to
follow the subject.


From mayank.kandari at gmail.com  Thu Oct 11 21:36:12 2007
From: mayank.kandari at gmail.com (Mayank Kandari)
Date: Fri, 12 Oct 2007 10:06:12 +0530
Subject: [Xorp-users] RIP sending route but not receiving
In-Reply-To: <200710112022.l9BKM2hW096929@possum.icir.org>
References: <mayank.kandari@gmail.com>
	<328b1be80710110141w4bc28872t62429249ed71881c@mail.gmail.com>
	<200710112022.l9BKM2hW096929@possum.icir.org>
Message-ID: <328b1be80710112136v3e50c4b8uc1f3f20bad57c36f@mail.gmail.com>

This is the   configuration of another router
 protocols {
        rip {
            interface eth0 {
                vif eth0 {
                    address 172.16.0.4 {
                    }
                }
            }
            export: "connected"
        }
    }
    policy {
        policy-statement connected {
            term export {
                from {
                    protocol: "connected"
                    network4: 192.168.0.0/16
                }
                to {
                    nexthop4: 172.16.0.9..172.16.0.9
                }
                then {
                    accept {
                    }
                }
            }
        }
    }
    interfaces {
        interface eth0 {
            vif eth0 {
                address 172.16.0.4 {
                    prefix-length: 16
                }
            }
        }
    }




On 10/12/07, Pavlin Radoslavov <pavlin at icir.org> wrote:
>
> Mayank Kandari <mayank.kandari at gmail.com> wrote:
>
> > Hello , this is the configuration of my router
> >
> > mayank at cmj-isea-08.cdacmumbai.in# show
> >     protocols {
> >         rip {
> >             interface eth0 {
> >                 vif eth0 {
> >                     address 172.16.0.8 {
> >                     }
> >                 }
> >             }
> >             export: "static"
> >         }
> >         static {
> >             route 40.0.0.0/8 {
> >                 next-hop: 172.16.0.100
> >             }
> >         }
> >     }
> >     policy {
> >         policy-statement connected {
> >             term export {
> >                 from {
> >                     protocol: "connected"
> >                     network4: 10.0.0.0/8
> >                 }
> >                 to {
> >                     nexthop4: 172.16.0.4..172.16.0.4
> >                 }
> >                 then {
> >                     accept {
> >                     }
> >                 }
> >             }
> >         }
> >         policy-statement static {
> >             term export {
> >                 from {
> >                     protocol: "static"
> >                 }
> >             }
> >         }
> >     }
> >     interfaces {
> >         interface eth0 {
> >             vif eth0 {
> >                 address 172.16.0.8 {
> >                     prefix-length: 16
> >                 }
> >                 address 10.0.0.1 {
> >                     prefix-length: 8
> >                 }
> >             }
> >         }
> >     }
> >
> > I am able to send  route from my machine and another xorp machine in my
> > network (172.16.0.0/16) is receiving the routes from my xorp router.
> > I am not receiving any route and even not able to view peers :( . Any
> one
> > can help me.
>
> Please send the configuration of the other XORP router as well.
>
> Pavlin
>
> P.S. For practical reasons, please send the configuration as a reply
> in this thread instead of starting a new one so it is easier to
> follow the subject.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071012/7520a371/attachment.html 

From pavlin at icir.org  Thu Oct 11 23:07:00 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 11 Oct 2007 23:07:00 -0700
Subject: [Xorp-users] RIP sending route but not receiving
In-Reply-To: Message from "Mayank Kandari" <mayank.kandari@gmail.com> of "Fri,
	12 Oct 2007 10:06:12 +0530."
	<328b1be80710112136v3e50c4b8uc1f3f20bad57c36f@mail.gmail.com> 
Message-ID: <200710120607.l9C670U0002040@possum.icir.org>

I am not sure what exactly you want to achieve with the particular
"connected" policy you are exporting, so for a started I'd recommend
to use simpler setup. E.g.:

policy {
    policy-statement connected {
        term export {
            from {
                protocol: "connected"
            }
        }
    }
}


Also, if this is going to be a router you should enable unicast
forwarding:

fea {
    unicast-forwarding4 {
        disable: false
    }
}

See below for more recommendations for the other rouuter's
configuration.

> This is the   configuration of another router
>  protocols {
>         rip {
>             interface eth0 {
>                 vif eth0 {
>                     address 172.16.0.4 {
>                     }
>                 }
>             }
>             export: "connected"
>         }
>     }
>     policy {
>         policy-statement connected {
>             term export {
>                 from {
>                     protocol: "connected"
>                     network4: 192.168.0.0/16
>                 }
>                 to {
>                     nexthop4: 172.16.0.9..172.16.0.9
>                 }
>                 then {
>                     accept {
>                     }
>                 }
>             }
>         }
>     }
>     interfaces {
>         interface eth0 {
>             vif eth0 {
>                 address 172.16.0.4 {
>                     prefix-length: 16
>                 }
>             }
>         }
>     }
> 
> 
> 
> 
> On 10/12/07, Pavlin Radoslavov <pavlin at icir.org> wrote:
> >
> > Mayank Kandari <mayank.kandari at gmail.com> wrote:
> >
> > > Hello , this is the configuration of my router

Again, as in the previous case, you should start with simple setup
and you need to enable unicast forwarding:

fea {
    unicast-forwarding4 {
        disable: false
    }
}

policy {
    policy-statement connected {
        term export {
            from {
                protocol: "connected"
            }
        }
    }
}

Then, inside the "rip" section you should export "connected" instead
of "static".

Finally, configure just one address in the "interfaces" section.
The second address shouldn't hurt, but then again if you are
debugging a problem remove everything that is not needed.

When investingating the missing packets, please make sure you are
running tcpdump on the receiving host (i.e., the host that doesn't
receive the RIP packets).
If you still have the problem, then enable XRL tracing on the
receiving host and try to find whether the FEA received the RIP
packets and sent them to the RIP process. To enable XRL tracing you
need to set the XRLTRACE environmental variable to anything and then
start XORP. E.g.,

setenv XRLTRACE yes
xorp_rtrmgr -b rip.boot

You should be looking for XRLs like recv_event from the FEA to RIP.
If there are too many XRLs, then run "script" before starting XORP
so you can save the terminal output to a file (for later
processing).

Regards,
Pavlin


> > > mayank at cmj-isea-08.cdacmumbai.in# show
> > >     protocols {
> > >         rip {
> > >             interface eth0 {
> > >                 vif eth0 {
> > >                     address 172.16.0.8 {
> > >                     }
> > >                 }
> > >             }
> > >             export: "static"
> > >         }
> > >         static {
> > >             route 40.0.0.0/8 {
> > >                 next-hop: 172.16.0.100
> > >             }
> > >         }
> > >     }
> > >     policy {
> > >         policy-statement connected {
> > >             term export {
> > >                 from {
> > >                     protocol: "connected"
> > >                     network4: 10.0.0.0/8
> > >                 }
> > >                 to {
> > >                     nexthop4: 172.16.0.4..172.16.0.4
> > >                 }
> > >                 then {
> > >                     accept {
> > >                     }
> > >                 }
> > >             }
> > >         }
> > >         policy-statement static {
> > >             term export {
> > >                 from {
> > >                     protocol: "static"
> > >                 }
> > >             }
> > >         }
> > >     }
> > >     interfaces {
> > >         interface eth0 {
> > >             vif eth0 {
> > >                 address 172.16.0.8 {
> > >                     prefix-length: 16
> > >                 }
> > >                 address 10.0.0.1 {
> > >                     prefix-length: 8
> > >                 }
> > >             }
> > >         }
> > >     }
> > >
> > > I am able to send  route from my machine and another xorp machine in my
> > > network (172.16.0.0/16) is receiving the routes from my xorp router.
> > > I am not receiving any route and even not able to view peers :( . Any
> > one
> > > can help me.
> >
> > Please send the configuration of the other XORP router as well.
> >
> > Pavlin
> >
> > P.S. For practical reasons, please send the configuration as a reply
> > in this thread instead of starting a new one so it is easier to
> > follow the subject.
> >
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From zhj.zhao at gmail.com  Fri Oct 12 06:59:09 2007
From: zhj.zhao at gmail.com (jerry zhao)
Date: Fri, 12 Oct 2007 15:59:09 +0200
Subject: [Xorp-users] buffer state of router and source code of router
	software
Message-ID: <b9f77bff0710120659g1231b1c2q4d3438ee77009f37@mail.gmail.com>

Hello,
First I am sorry for this unprofessional question. The question is: *Does
any router vendor provide source code of their router software?*  I want to
get some information about the buffer state of router. Now I am doing
something about video streaming.  Sometimes there is congestion because of
buffer overflow of router. So I want to know the buffer state of router so
that I can control the sever how many date it should send. Does anyone know
whether there is a router vendor that provides source code of router
software or router product that can send the buffer state to the server? Any
advice is appreciated. Thanks
Best regards.
Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071012/9ed53e8d/attachment.html 

From a.greenhalgh at cs.ucl.ac.uk  Fri Oct 12 07:15:37 2007
From: a.greenhalgh at cs.ucl.ac.uk (Adam Greenhalgh)
Date: Fri, 12 Oct 2007 15:15:37 +0100
Subject: [Xorp-users] buffer state of router and source code of router
	software
In-Reply-To: <b9f77bff0710120659g1231b1c2q4d3438ee77009f37@mail.gmail.com>
References: <b9f77bff0710120659g1231b1c2q4d3438ee77009f37@mail.gmail.com>
Message-ID: <4769af410710120715l24a28531p68a01ff8f7cd83c2@mail.gmail.com>

Jerry,

Only those routers based on open source provide source code for their
routers, but unless you belong to the correct government agency the
source code is all closed.

You should be able to get the source code of (google will help you here)

xorp (vyatta)
quagga (was zebra and hence maybe zeb os)
gated (oldish code now)

Adam

On 12/10/2007, jerry zhao <zhj.zhao at gmail.com> wrote:
> Hello,
> First I am sorry for this unprofessional question. The question is: Does any
> router vendor provide source code of their router software?  I want to get
> some information about the buffer state of router. Now I am doing something
> about video streaming.  Sometimes there is congestion because of buffer
> overflow of router. So I want to know the buffer state of router so that I
> can control the sever how many date it should send. Does anyone know whether
> there is a router vendor that provides source code of router software or
> router product that can send the buffer state to the server? Any advice is
> appreciated. Thanks
> Best regards.
> Jerry
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>


From zhj.zhao at gmail.com  Fri Oct 12 08:17:28 2007
From: zhj.zhao at gmail.com (jerry zhao)
Date: Fri, 12 Oct 2007 17:17:28 +0200
Subject: [Xorp-users] can router send information to end system?
Message-ID: <b9f77bff0710120817y406f31b1w180a5eb867c653fc@mail.gmail.com>

Hello, all
I am a newie with router software. I hope that someone could help me.
It is supposed that there exists the following scenario:

           server<- - - ->router<- - - - ->client

Can the router send some information (e.g. its buffer state) to the server?
Any advice is appreciated. Thanks.
Best regards
Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071012/18b0b1da/attachment.html 

From greearb at candelatech.com  Mon Oct 15 16:48:28 2007
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 15 Oct 2007 16:48:28 -0700
Subject: [Xorp-users] subnet routes & xorp
Message-ID: <4713FC4C.1070908@candelatech.com>

Does xorp do the equivalent of 'ifconfig down ethx; ifconfig up ethx' when
you add and/or delete an interface & vif?

A subnet route is disappearing from and interface that I removed
from one xorp instance and added to another, and if it's bouncing the
interface, that could explain why...

Thanks,
Ben

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


From pavlin at icir.org  Mon Oct 15 17:05:22 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Mon, 15 Oct 2007 17:05:22 -0700
Subject: [Xorp-users] subnet routes & xorp
In-Reply-To: Message from Ben Greear <greearb@candelatech.com> 
	of "Mon, 15 Oct 2007 16:48:28 PDT." <4713FC4C.1070908@candelatech.com> 
Message-ID: <200710160005.l9G05MrM055637@possum.icir.org>

Ben Greear <greearb at candelatech.com> wrote:

> Does xorp do the equivalent of 'ifconfig down ethx; ifconfig up ethx' when
> you add and/or delete an interface & vif?
> 
> A subnet route is disappearing from and interface that I removed
> from one xorp instance and added to another, and if it's bouncing the
> interface, that could explain why...

The "down/up" operations should happen only in certain situations
when are really needed. E.g., setting the MTU or the MAC address are
two examples that come to mind: the interface must be in DOWN state
otherwise the setting will fail.

The Linux "ip monitor" in a separate xterm will tell you whether the
"down/up" operations actually happen in your case.

Regards,
Pavlin


From greearb at candelatech.com  Mon Oct 15 17:41:22 2007
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 15 Oct 2007 17:41:22 -0700
Subject: [Xorp-users] subnet routes & xorp
In-Reply-To: <200710160005.l9G05MrM055637@possum.icir.org>
References: <200710160005.l9G05MrM055637@possum.icir.org>
Message-ID: <471408B2.5020802@candelatech.com>

Pavlin Radoslavov wrote:
> Ben Greear <greearb at candelatech.com> wrote:
> 
>> Does xorp do the equivalent of 'ifconfig down ethx; ifconfig up ethx' when
>> you add and/or delete an interface & vif?
>>
>> A subnet route is disappearing from and interface that I removed
>> from one xorp instance and added to another, and if it's bouncing the
>> interface, that could explain why...
> 
> The "down/up" operations should happen only in certain situations
> when are really needed. E.g., setting the MTU or the MAC address are
> two examples that come to mind: the interface must be in DOWN state
> otherwise the setting will fail.
> 
> The Linux "ip monitor" in a separate xterm will tell you whether the
> "down/up" operations actually happen in your case.

It looks like Xorp is removing it, but I could be wrong.

I'm not changing MAC or MTU.

My comments inline with # prefix

# Start of my script's commands
Deleted 10:     from all to 10.0.0.2 iif rddVR44 lookup local
Deleted 10:     from all to 10.4.0.7 iif rddVR44 lookup local
Deleted 10:     from all to 10.4.0.7 iif rddVR1 lookup local
Deleted 20:     from all iif rddVR44 lookup 10001
Deleted 30:     from 10.4.0.7 lookup 10001
10:     from all to 10.4.0.7 iif rddVR44 lookup local
10:     from all to 10.0.0.1 iif rddVR44 lookup local
10:     from all to 10.2.0.1 iif rddVR44 lookup local
10:     from all to 10.3.0.1 iif rddVR44 lookup local
10:     from all to 10.4.0.7 iif rddVR0 lookup local
10:     from all to 10.4.0.7 iif rddVR3 lookup local
10:     from all to 10.4.0.7 iif br2 lookup local
20:     from all iif rddVR44 lookup 10002
30:     from 10.4.0.7 lookup 10002
10.4.0.0/24 via 10.4.0.7 dev rddVR44  table 10002

# my script should be done at this point and now calling into
# xorpsh  Looks like the routes go away here, maybe because
# Xorp is removing the IP address when I delete the interface
# through xorpsh?

Deleted 71: rddVR44    inet 10.4.0.7/24 brd 10.4.0.255 scope global rddVR44
Deleted 10.4.0.0/24 dev rddVR44  proto kernel  scope link  src 10.4.0.7
Deleted broadcast 10.4.0.255 dev rddVR44  table local  proto kernel  scope link  src 10.4.0.7
Deleted broadcast 10.4.0.0 dev rddVR44  table local  proto kernel  scope link  src 10.4.0.7
Deleted local 10.4.0.7 dev rddVR44  table local  proto kernel  scope host  src 10.4.0.7

# Specifically, here's the ones in my special routing table
Deleted 10.1.0.0/24 via 10.0.0.2 dev rddVR0  table 10002  proto xorp  metric 3 notify
Deleted 10.4.0.0/24 via 10.0.0.2 dev rddVR0  table 10002  proto xorp  metric 2 notify

# Now it seems Xorp is re-adding them, but it doesn't know how to deal with
# my special table, so in the end, my routes are not quite right...

71: rddVR44    inet 10.4.0.7/24 brd 10.4.0.255 scope global rddVR44
local 10.4.0.7 dev rddVR44  table local  proto kernel  scope host  src 10.4.0.7
broadcast 10.4.0.255 dev rddVR44  table local  proto kernel  scope link  src 10.4.0.7
10.4.0.0/24 dev rddVR44  proto kernel  scope link  src 10.4.0.7
broadcast 10.4.0.0 dev rddVR44  table local  proto kernel  scope link  src 10.4.0.7


Thanks,
Ben


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


From pavlin at icir.org  Mon Oct 15 18:06:24 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Mon, 15 Oct 2007 18:06:24 -0700
Subject: [Xorp-users] subnet routes & xorp
In-Reply-To: Message from Ben Greear <greearb@candelatech.com> 
	of "Mon, 15 Oct 2007 17:41:22 PDT." <471408B2.5020802@candelatech.com> 
Message-ID: <200710160106.l9G16OJw056323@possum.icir.org>

> >> Does xorp do the equivalent of 'ifconfig down ethx; ifconfig up ethx' when
> >> you add and/or delete an interface & vif?
> >>
> >> A subnet route is disappearing from and interface that I removed
> >> from one xorp instance and added to another, and if it's bouncing the
> >> interface, that could explain why...

On second reading I realized this is what might be happening.
If an interface is removed, then a protocol that uses that interface
might attempt to withdraw all routes pointing toward that interface.
I think this is the case for Static for example, and I guess this
might be the case for OSPF as well.

You should enable XRLTRACE to see what XRLs are exchanged when the
interface is deleted inside the XORP configuration. This will tell
you whether the route deletion is originated by XORP (and by which
module).

In addition, "ip monitor" will tell you what events actually happen
inside the kernel.

If the above is not sufficient to find the problem, XLOG_INFO() at
the bottom of the FEA inside the Linux plugins will tell you what
exactly happens between the FEA and the kernel.

Regards,
Pavlin


> > The "down/up" operations should happen only in certain situations
> > when are really needed. E.g., setting the MTU or the MAC address are
> > two examples that come to mind: the interface must be in DOWN state
> > otherwise the setting will fail.
> > 
> > The Linux "ip monitor" in a separate xterm will tell you whether the
> > "down/up" operations actually happen in your case.
> 
> It looks like Xorp is removing it, but I could be wrong.
> 
> I'm not changing MAC or MTU.
> 
> My comments inline with # prefix
> 
> # Start of my script's commands
> Deleted 10:     from all to 10.0.0.2 iif rddVR44 lookup local
> Deleted 10:     from all to 10.4.0.7 iif rddVR44 lookup local
> Deleted 10:     from all to 10.4.0.7 iif rddVR1 lookup local
> Deleted 20:     from all iif rddVR44 lookup 10001
> Deleted 30:     from 10.4.0.7 lookup 10001
> 10:     from all to 10.4.0.7 iif rddVR44 lookup local
> 10:     from all to 10.0.0.1 iif rddVR44 lookup local
> 10:     from all to 10.2.0.1 iif rddVR44 lookup local
> 10:     from all to 10.3.0.1 iif rddVR44 lookup local
> 10:     from all to 10.4.0.7 iif rddVR0 lookup local
> 10:     from all to 10.4.0.7 iif rddVR3 lookup local
> 10:     from all to 10.4.0.7 iif br2 lookup local
> 20:     from all iif rddVR44 lookup 10002
> 30:     from 10.4.0.7 lookup 10002
> 10.4.0.0/24 via 10.4.0.7 dev rddVR44  table 10002
> 
> # my script should be done at this point and now calling into
> # xorpsh  Looks like the routes go away here, maybe because
> # Xorp is removing the IP address when I delete the interface
> # through xorpsh?
> 
> Deleted 71: rddVR44    inet 10.4.0.7/24 brd 10.4.0.255 scope global rddVR44
> Deleted 10.4.0.0/24 dev rddVR44  proto kernel  scope link  src 10.4.0.7
> Deleted broadcast 10.4.0.255 dev rddVR44  table local  proto kernel  scope link  src 10.4.0.7
> Deleted broadcast 10.4.0.0 dev rddVR44  table local  proto kernel  scope link  src 10.4.0.7
> Deleted local 10.4.0.7 dev rddVR44  table local  proto kernel  scope host  src 10.4.0.7
> 
> # Specifically, here's the ones in my special routing table
> Deleted 10.1.0.0/24 via 10.0.0.2 dev rddVR0  table 10002  proto xorp  metric 3 notify
> Deleted 10.4.0.0/24 via 10.0.0.2 dev rddVR0  table 10002  proto xorp  metric 2 notify
> 
> # Now it seems Xorp is re-adding them, but it doesn't know how to deal with
> # my special table, so in the end, my routes are not quite right...
> 
> 71: rddVR44    inet 10.4.0.7/24 brd 10.4.0.255 scope global rddVR44
> local 10.4.0.7 dev rddVR44  table local  proto kernel  scope host  src 10.4.0.7
> broadcast 10.4.0.255 dev rddVR44  table local  proto kernel  scope link  src 10.4.0.7
> 10.4.0.0/24 dev rddVR44  proto kernel  scope link  src 10.4.0.7
> broadcast 10.4.0.0 dev rddVR44  table local  proto kernel  scope link  src 10.4.0.7
> 
> 
> Thanks,
> Ben
> 
> 
> -- 
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From greearb at candelatech.com  Mon Oct 15 18:07:13 2007
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 15 Oct 2007 18:07:13 -0700
Subject: [Xorp-users] subnet routes & xorp
In-Reply-To: <471408B2.5020802@candelatech.com>
References: <200710160005.l9G05MrM055637@possum.icir.org>
	<471408B2.5020802@candelatech.com>
Message-ID: <47140EC1.9020308@candelatech.com>

Ben Greear wrote:
> Pavlin Radoslavov wrote:
>> Ben Greear <greearb at candelatech.com> wrote:
>>
>>> Does xorp do the equivalent of 'ifconfig down ethx; ifconfig up ethx' when
>>> you add and/or delete an interface & vif?
>>>
>>> A subnet route is disappearing from and interface that I removed
>>> from one xorp instance and added to another, and if it's bouncing the
>>> interface, that could explain why...
>> The "down/up" operations should happen only in certain situations
>> when are really needed. E.g., setting the MTU or the MAC address are
>> two examples that come to mind: the interface must be in DOWN state
>> otherwise the setting will fail.
>>
>> The Linux "ip monitor" in a separate xterm will tell you whether the
>> "down/up" operations actually happen in your case.
> 
> It looks like Xorp is removing it, but I could be wrong.

Just FYI:  This may be perfectly proper behaviour from Xorp.
(ie, remove IP on an interface that is being deleted).

Either way, I seem to have a work-around by re-adding the route
manually after I do the xorpsh commands.

Thanks,
Ben


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


From mayank.kandari at gmail.com  Mon Oct 15 21:30:41 2007
From: mayank.kandari at gmail.com (Mayank Kandari)
Date: Tue, 16 Oct 2007 10:00:41 +0530
Subject: [Xorp-users] XORP as a distributed router
Message-ID: <328b1be80710152130h49aef554u665d9c093b77ff07@mail.gmail.com>

Is it possible to run XORP as a distributed router e.g . Forwarding engine
in one machine and routing protocol in another machine.
If yes then what changes  need to made ?


regards
Mayank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071016/07423e16/attachment.html 

From pavlin at icir.org  Tue Oct 16 18:08:31 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Tue, 16 Oct 2007 18:08:31 -0700
Subject: [Xorp-users] XORP as a distributed router
In-Reply-To: Message from "Mayank Kandari" <mayank.kandari@gmail.com> of "Tue,
	16 Oct 2007 10:00:41 +0530."
	<328b1be80710152130h49aef554u665d9c093b77ff07@mail.gmail.com> 
Message-ID: <200710170108.l9H18VuM089148@possum.icir.org>

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

> Is it possible to run XORP as a distributed router e.g . Forwarding engine
> in one machine and routing protocol in another machine.
> If yes then what changes  need to made ?

Yes, it is possible, but not "out-of-the-box" (yet).
In a nutshell, you might need to perform some simple edits to some
of the rtrmgr templates and you might need to start some of the
processes by hand.

Below is a copy from an old email with instructions how to start a
remote StaticRoutes process.

You can use a similar mechanism to start the xorp_fea process
remotely. The difference would be that you need to fool the rtrmgr
so it doesn't start the FEA locally.

As an alternative to editing some of the etc/templates/*.tp template
files you could replace the xorp_fea binary with, say, a script with
the same name that sleeps forever.

Note that it has been a while since I've tried this, so let me know
if something doesn't work.

I guess other folks on the list might have done something similar
and they might have more automated solutions.


Hope that helps,
Pavlin

================================================================
I played a bit and I was able to run a remote static_routes
process. Here is the procedure I used (note that the rtrmgr IP
address is 10.2.0.1; the IP address of the host that will run
static_routes is 10.2.0.2):

1. First edit etc/templates/static_routes.tp and replace line:
%modinfo:    path            "static_routes/xorp_static_routes";

with

%modinfo:    path            "fea/xorp_fea";

This is to fool the rtrmgr so it doesn't attempt to run the
xorp_static_routes binary. Using fea/xorp_fea instead is a harmless
hack; altenatively, you can just remove the above line.

If you want to run other programs remotely (e.g., rip/ripng), then
edit the corresponding template file instead (e.g. rip.tp or
ripng.tp).

2. On the rtrmgr side setup the finder server and client addresses
   as usual:
setenv XORP_FINDER_SERVER_ADDRESS 10.2.0.1
setenv XORP_FINDER_CLIENT_ADDRESS 10.2.0.1

3. On the remote static_routes side setup the finder server and
   client addresses as usual:
setenv XORP_FINDER_SERVER_ADDRESS 10.2.0.1
setenv XORP_FINDER_CLIENT_ADDRESS 10.2.0.2

4. Run the rtrmgr and enable connections from host 10.2.0.2:

./xorp_rtrmgr -b static.boot -a 10.2.0.2

5. Once the rtrmgr is started, at some moment you will see periodic
messages (once a second) like:

[ 2005/06/20 13:39:23  WARNING xorp_rtrmgr:66898 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 "static_routes" does not exist or is not
enabled.

That is normal. At that time you can start the xorp_static_routes on
the remote machine, and soon after that the above messages should
stop.

6. Soon after that you should see the usual "No more tasks to run"
   message in the rtrmgr log output, and at that time the router
   should be up and running.

7. Note that if you want to start xorpsh on the rtrmgr host, you
   still must setup the finder sender and client addresses:
setenv XORP_FINDER_SERVER_ADDRESS 10.2.0.1
setenv XORP_FINDER_CLIENT_ADDRESS 10.2.0.1

8. If you stop/kill (Ctrl-C) the rtrmgr, then it will gracefully
   shutdown the remote xorp_static_routes process.

9. Note that if you really need to start the xorp_static_routes
   process before starting the rtrmgr, you could do so, but then you
   have 10 seconds to start the rtrmgr (otherwise the
   xorp_static_routes process will quit).

10. If for whatever reason you cannot edit the
    etc/templates/static_routes.tp template file, then you can try
    to replace static_routes/xorp_static_routes binary with some
    dummy program (and again ignore the periodic error messages as
    in step 5), but I haven't tried this myself so off the top of my
    head I don't know whether you may run into some hidden issues.
================================================================
To automate the starting of the remote xorp_static_routes process,
you can use a script that does ssh to the remote host and runs the
process there. For example:

#!/bin/sh
# 
ssh static_routes_host env XORP_FINDER_SERVER_ADDRESS=rtrmgr_host_addr XORP_FINDER_CLIENT_ADDRESS=static_routes_host /usr/local/xorp/static_routes/xorp_static_routes

Then you don't need to edit the etc/templates/static_routes.tp
template file.

Obviously, you must have configured ssh such that when the rtrmgr
runs the script it doesn't require a password (e.g., by adding the
public keys to the authorized keys on the static_routes_host, etc).
================================================================


From hantongs at gmail.com  Wed Oct 17 04:06:13 2007
From: hantongs at gmail.com (Hansi)
Date: Wed, 17 Oct 2007 19:06:13 +0800
Subject: [Xorp-users] XORP IPv6
Message-ID: <2f9e317b0710170406i21c88c4fsa7d2c022da20bdf1@mail.gmail.com>

Hello All,

Currently, I'm on the process of exploring XORP using IPv6. Though I'm quite
familiar with IPv6, I really don't have much knowledge on setting up an IPv6
network specifically in the scenario of running dynamic routing protocols
using XORP. For IPv4, I had two XORP boxen and one client behind each XORP
machine. Connectivity is confirmed once the end clients can ping to one
another by using dynamic protocols in each XORP router to establish network
discovery. Would this setup still suffice in an IPv6 scenario? Would someone
be kind enough to guide/show me the setup of a simple IPv6 topology so that
I can explore further?

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071017/d751d0be/attachment.html 

From pavlin at icir.org  Thu Oct 18 17:24:13 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Thu, 18 Oct 2007 17:24:13 -0700
Subject: [Xorp-users] XORP IPv6
In-Reply-To: Message from Hansi <hantongs@gmail.com> of "Wed,
	17 Oct 2007 19:06:13 +0800."
	<2f9e317b0710170406i21c88c4fsa7d2c022da20bdf1@mail.gmail.com> 
Message-ID: <200710190024.l9J0ODJG013811@possum.icir.org>

> Currently, I'm on the process of exploring XORP using IPv6. Though I'm quite
> familiar with IPv6, I really don't have much knowledge on setting up an IPv6
> network specifically in the scenario of running dynamic routing protocols
> using XORP. For IPv4, I had two XORP boxen and one client behind each XORP
> machine. Connectivity is confirmed once the end clients can ping to one
> another by using dynamic protocols in each XORP router to establish network
> discovery. Would this setup still suffice in an IPv6 scenario? Would someone
> be kind enough to guide/show me the setup of a simple IPv6 topology so that
> I can explore further?

Off the top of my head, there is nothing drastically different from
IPv4 when configuring XORP for IPv6.
Some protocols/modules (e.g., FEA, BGP, StaticRoutes) capture both
IPv4 and IPv6 within a single instance/process.
Other protocols (e.g., RIP/RIPng, OSPFv2/OSPFv3, IGMP/MLD, PIM-SM)
require configuring a separate instance for IPv6.

In most cases the configuration is very similar between IPv4 and
IPv6. The XORP User Manual should capture both configurations.

One thing you should be aware is the usage of the IPv6-specific
link-local (unicast) addresses.
Some of the routing protocols need to use the link-local address of
each interface. Typically, this address is automatically assigned by
the kernel when the interface is configured.
However, currently XORP (the FEA to be specific) doesn't take into
account this address (this should be fixed in the
future). Therefore, in your IPv6 interface address configuration you
need to compensate for that by either explicitly configuring the
IPv6 link-local address (it should match the address from the
kernel) or simply by using the "default-system-config" configuration
statement.

In any case, after you run ./configure, make sure that HAVE_IPV6 is
defined in the auto-generated config.h. If it is not, then either
your system doesn't have IPv6 (not very likely on modern OS-es), or
there was something IPv6-specific in the build environment that was
missing. If the latter, please let us know so we can investigate.

Hope that helps,
Pavlin


From JayasriS at aaesys.com  Mon Oct 15 16:27:51 2007
From: JayasriS at aaesys.com (Jayasri Sangu)
Date: Mon, 15 Oct 2007 16:27:51 -0700
Subject: [Xorp-users] xorp on windows XP
Message-ID: <EC227A7B5AEA1B48A88C2C6F4FC027310296FB@aae-exch.aaesys.com>

Hello,

               I am new to xorp. We are trying to install xorp on
windows xp.  Does the windows XP is supported ? if yes, How can I
compile xorp on windows xp?

Thanks
Jayasri Sangu

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

From pavlin at icir.org  Fri Oct 19 16:35:11 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Fri, 19 Oct 2007 16:35:11 -0700
Subject: [Xorp-users] xorp on windows XP
In-Reply-To: Message from "Jayasri Sangu" <JayasriS@aaesys.com> of "Mon,
	15 Oct 2007 16:27:51 PDT."
	<EC227A7B5AEA1B48A88C2C6F4FC027310296FB@aae-exch.aaesys.com> 
Message-ID: <200710192335.l9JNZB6Q010423@possum.icir.org>

>                I am new to xorp. We are trying to install xorp on
> windows xp.  Does the windows XP is supported ? if yes, How can I
> compile xorp on windows xp?

XORP is supported only on Windows Server 2003 (among the Windows
platforms), and I doubt it will work on Windows XP.

Bruce Simpson (who did the Windows port) can give you a better
answer re. the technical issues and whether it _might_ work on other
Windows platforms.

Regards,
Pavlin


From reach_dinesh at hotmail.com  Wed Oct 24 23:59:23 2007
From: reach_dinesh at hotmail.com (dinesh kumar)
Date: Thu, 25 Oct 2007 14:59:23 +0800
Subject: [Xorp-users] Compilation Error
Message-ID: <BLU104-W45DC4A93D6AA929324FF39F0950@phx.gbl>


Dear XORP users,

I am getting the following error while I am compiling XORP :

root:~/Desktop/xorp/XORP Code/xorp-1.4# ./configure
bash: ./configure: Permission denied

and I am compiling from the following directory:

/root/Desktop/xorp/XORP Code/xorp- 1.4#

I have logged in as root only. Don't know why "permission denied" error is coming. Please give your suggestions.

Thanks,
Dinesh
_________________________________________________________________
Edit your photos like a pro with Photo Gallery.
http://www.get.live.com/wl/all


From kristian at spritelink.net  Thu Oct 25 13:39:25 2007
From: kristian at spritelink.net (Kristian Larsson)
Date: Thu, 25 Oct 2007 22:39:25 +0200
Subject: [Xorp-users] Compilation Error
In-Reply-To: <BLU104-W45DC4A93D6AA929324FF39F0950@phx.gbl>
References: <BLU104-W45DC4A93D6AA929324FF39F0950@phx.gbl>
Message-ID: <20071025203925.GA22077@spritelink.se>

On Thu, Oct 25, 2007 at 02:59:23PM +0800, dinesh kumar wrote:
> 
> Dear XORP users,
> 
> I am getting the following error while I am compiling XORP :
> 
> root:~/Desktop/xorp/XORP Code/xorp-1.4# ./configure
> bash: ./configure: Permission denied
> 
> and I am compiling from the following directory:
> 
> /root/Desktop/xorp/XORP Code/xorp- 1.4#
> 
> I have logged in as root only. Don't know why "permission denied" error is coming. Please give your suggestions.

It would seem that the execute bit on your
configure script isn't set for some reason.
Could you try to do a `chmod u+x configure` and
then try executing the script just as you tried or
perhaps an extended directory listing (`ls -la
configure`).

  -K

-- 
Kristian Larsson                                        KLL-RIPE
Network Engineer & Peering Coordinator      SpriteLink [AS39525]
+46 704 910401			              kll at spritelink.net


From reach_dinesh at hotmail.com  Fri Oct 26 00:29:32 2007
From: reach_dinesh at hotmail.com (Dinesh Kumar)
Date: Fri, 26 Oct 2007 15:29:32 +0800
Subject: [Xorp-users] Compilation Error
In-Reply-To: <20071025203925.GA22077@spritelink.se>
References: <BLU104-W45DC4A93D6AA929324FF39F0950@phx.gbl>
	<20071025203925.GA22077@spritelink.se>
Message-ID: <BLU104-W42E32A5183D24037277E67F0960@phx.gbl>


Thanks so much Kristian. You were right! I was able to execute after using chmod!

But I have a new error now :(

root:~/Desktop/xorp/XORP Code/xorp-1.4# ./configure
bash: ./configure: /bin/sh^M: bad interpreter: No such file or directory

I have got g++/gcc version 4.1

root:~/Desktop/xorp/XORP Code/xorp-1.4# g++ -v
Using built-in specs.
Target: i586-suse-linux
Configured with: .....
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)

I have checked the 'BUILD_NOTES' file.  But there is no known error with gcc v. 4.1. 

Have I missed something?


Thanks,
Dinesh
----------------------------------------> Date: Thu, 25 Oct 2007 22:39:25 +0200> From: kristian at spritelink.net> To: reach_dinesh at hotmail.com> CC: xorp-users at xorp.org> Subject: Re: [Xorp-users] Compilation Error>> On Thu, Oct 25, 2007 at 02:59:23PM +0800, dinesh kumar wrote:>>>> Dear XORP users,>>>> I am getting the following error while I am compiling XORP :>>>> root:~/Desktop/xorp/XORP Code/xorp-1.4# ./configure>> bash: ./configure: Permission denied>>>> and I am compiling from the following directory:>>>> /root/Desktop/xorp/XORP Code/xorp- 1.4#>>>> I have logged in as root only. Don't know why "permission denied" error is coming. Please give your suggestions.>> It would seem that the execute bit on your> configure script isn't set for some reason.> Could you try to do a `chmod u+x configure` and> then try executing the script just as you tried or> perhaps an extended directory listing (`ls -la> configure`).>> -K>> --> Kristian Larsson KLL-RIPE> Network Engineer & Peering C!
 oordinator SpriteLink [AS39525]> +46 704 910401 kll at spritelink.net

_________________________________________________________________
Edit your photos like a pro with Photo Gallery.
http://www.get.live.com/wl/all


From pavlin at icir.org  Fri Oct 26 21:49:38 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Fri, 26 Oct 2007 21:49:38 -0700
Subject: [Xorp-users] Compilation Error
In-Reply-To: Message from Dinesh Kumar <reach_dinesh@hotmail.com> of "Fri,
	26 Oct 2007 15:29:32 +0800."
	<BLU104-W42E32A5183D24037277E67F0960@phx.gbl> 
Message-ID: <200710270449.l9R4ncHM016431@possum.icir.org>

It looks like your system doesn't have /bin/sh .
Please install it and try again.

Regards,
Pavlin

Dinesh Kumar <reach_dinesh at hotmail.com> wrote:

> 
> Thanks so much Kristian. You were right! I was able to execute after using chmod!
> 
> But I have a new error now :(
> 
> root:~/Desktop/xorp/XORP Code/xorp-1.4# ./configure
> bash: ./configure: /bin/sh^M: bad interpreter: No such file or directory
> 
> I have got g++/gcc version 4.1
> 
> root:~/Desktop/xorp/XORP Code/xorp-1.4# g++ -v
> Using built-in specs.
> Target: i586-suse-linux
> Configured with: .....
> Thread model: posix
> gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)
> 
> I have checked the 'BUILD_NOTES' file.  But there is no known error with gcc v. 4.1. 
> 
> Have I missed something?
> 
> 
> Thanks,
> Dinesh
> ----------------------------------------> Date: Thu, 25 Oct 2007 22:39:25 +0200> From: kristian at spritelink.net> To: reach_dinesh at hotmail.com> CC: xorp-users at xorp.org> Subject: Re: [Xorp-users] Compilation Error>> On Thu, Oct 25, 2007 at 02:59:23PM +0800, dinesh kumar wrote:>>>> Dear XORP users,>>>> I am getting the following error while I am compiling XORP :>>>> root:~/Desktop/xorp/XORP Code/xorp-1.4# ./configure>> bash: ./configure: Permission denied>>>> and I am compiling from the following directory:>>>> /root/Desktop/xorp/XORP Code/xorp- 1.4#>>>> I have logged in as root only. Don't know why "permission denied" error is coming. Please give your suggestions.>> It would seem that the execute bit on your> configure script isn't set for some reason.> Could you try to do a `chmod u+x configure` and> then try executing the script just as you tried or> perhaps an extended directory listing (`ls -la> configure`).>> -K>> --> Kristian Larsson KLL-RIPE> Network Engineer & Peering!
  C!
>  oordinator SpriteLink [AS39525]> +46 704 910401 kll at spritelink.net
> 
> _________________________________________________________________
> Edit your photos like a pro with Photo Gallery.
> http://www.get.live.com/wl/all
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From reach_dinesh at hotmail.com  Sat Oct 27 01:40:01 2007
From: reach_dinesh at hotmail.com (Dinesh Kumar)
Date: Sat, 27 Oct 2007 16:40:01 +0800
Subject: [Xorp-users] Compilation Error
In-Reply-To: <200710270449.l9R4ncHM016431@possum.icir.org>
References: Message from Dinesh Kumar <reach_dinesh@hotmail.com>    of 
	<200710270449.l9R4ncHM016431@possum.icir.org>
Message-ID: <BLU104-W3F5F13EE912D70FFDF2E8F0970@phx.gbl>


Thanks Pavlin. But I do have /bin/sh, except that it is a link to bash.

#ls -l /bin/sh
lrwxrwxrwx 1 root root 4 Aug  2 15:36 /bin/sh -> bash

Is this ok? or should install /bin/sh.

Thanks,
Dinesh
----------------------------------------> To: reach_dinesh at hotmail.com> CC: xorp-users at xorp.org> Subject: Re: [Xorp-users] Compilation Error> Date: Fri, 26 Oct 2007 21:49:38 -0700> From: pavlin at icir.org>> It looks like your system doesn't have /bin/sh .> Please install it and try again.>> Regards,> Pavlin>> Dinesh Kumar  wrote:>>>>> Thanks so much Kristian. You were right! I was able to execute after using chmod!>>>> But I have a new error now :(>>>> root:~/Desktop/xorp/XORP Code/xorp-1.4# ./configure>> bash: ./configure: /bin/sh^M: bad interpreter: No such file or directory>>>> I have got g++/gcc version 4.1>>>> root:~/Desktop/xorp/XORP Code/xorp-1.4# g++ -v>> Using built-in specs.>> Target: i586-suse-linux>> Configured with: .....>> Thread model: posix>> gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)>>>> I have checked the 'BUILD_NOTES' file. But there is no known error with gcc v. 4.1.>>>> Have I missed something?>>>>>> Thanks,>> Dinesh>> ---------------------------!
 -------------> Date: Thu, 25 Oct 2007 22:39:25 +0200> From: kristian at spritelink.net> To: reach_dinesh at hotmail.com> CC: xorp-users at xorp.org> Subject: Re: [Xorp-users] Compilation Error>> On Thu, Oct 25, 2007 at 02:59:23PM +0800, dinesh kumar wrote:>>>> Dear XORP users,>>>> I am getting the following error while I am compiling XORP :>>>> root:~/Desktop/xorp/XORP Code/xorp-1.4# ./configure>> bash: ./configure: Permission denied>>>> and I am compiling from the following directory:>>>> /root/Desktop/xorp/XORP Code/xorp- 1.4#>>>> I have logged in as root only. Don't know why "permission denied" error is coming. Please give your suggestions.>> It would seem that the execute bit on your> configure script isn't set for some reason.> Could you try to do a `chmod u+x configure` and> then try executing the script just as you tried or> perhaps an extended directory listing (`ls -la> configure`).>> -K>> --> Kristian Larsson KLL-RIPE> Network Engineer & Peering!> C!>> oordinator SpriteLin!
 k [AS39525]> +46 704 910401 kll at spritelink.net>>>> ___________________
______________________________________________>> Edit your photos like a pro with Photo Gallery.>> http://www.get.live.com/wl/all>>>> _______________________________________________>> Xorp-users mailing list>> Xorp-users at xorp.org>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users

_________________________________________________________________
Edit your photos like a pro with Photo Gallery.
http://www.get.live.com/wl/all


From pavlin at icir.org  Sat Oct 27 01:55:59 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Sat, 27 Oct 2007 01:55:59 -0700
Subject: [Xorp-users] Compilation Error
In-Reply-To: Message from Dinesh Kumar <reach_dinesh@hotmail.com> of "Sat,
	27 Oct 2007 16:40:01 +0800."
	<BLU104-W3F5F13EE912D70FFDF2E8F0970@phx.gbl> 
Message-ID: <200710270855.l9R8txEd018319@possum.icir.org>

> Thanks Pavlin. But I do have /bin/sh, except that it is a link to bash.
> 
> #ls -l /bin/sh
> lrwxrwxrwx 1 root root 4 Aug  2 15:36 /bin/sh -> bash
> 
> Is this ok? or should install /bin/sh.

BTW, did you use Windows to dowload and/or uncompress the XORP
tarball?

A quick search revealed the following URL where someone had exactly
same problem (different software though) that was caused by
corrupted package after using Windows to uncompress it:

http://www.zabbix.com/forum/archive/index.php/t-837.html
[see the third comment from the bottom]

If you did something similar, please use UNIX box to download and
uncompress/untar again the XORP tarball.

Regards,
Pavlin


From reach_dinesh at hotmail.com  Sat Oct 27 02:40:13 2007
From: reach_dinesh at hotmail.com (Dinesh Kumar)
Date: Sat, 27 Oct 2007 17:40:13 +0800
Subject: [Xorp-users] Compilation Error
In-Reply-To: <200710270855.l9R8txEd018319@possum.icir.org>
References: Message from Dinesh Kumar <reach_dinesh@hotmail.com>    of 
	<200710270855.l9R8txEd018319@possum.icir.org>
Message-ID: <BLU104-W58151C747564579CC73375F0970@phx.gbl>


Dear Pavlin,

Thank you  for your time. As you had pointed out, I had uncompressed the XORP code in windows and copied it into linux. 

Now that I downloaded it again in Linux, the compiling is going smooth (atleast till now ;) ).

I look forward to work on XORP and thank everyone for their assistance.

Kind Regards,
Dinesh
----------------------------------------> To: reach_dinesh at hotmail.com> CC: xorp-users at xorp.org> Subject: Re: [Xorp-users] Compilation Error> Date: Sat, 27 Oct 2007 01:55:59 -0700> From: pavlin at icir.org>>> Thanks Pavlin. But I do have /bin/sh, except that it is a link to bash.>>>> #ls -l /bin/sh>> lrwxrwxrwx 1 root root 4 Aug 2 15:36 /bin/sh -> bash>>>> Is this ok? or should install /bin/sh.>> BTW, did you use Windows to dowload and/or uncompress the XORP> tarball?>> A quick search revealed the following URL where someone had exactly> same problem (different software though) that was caused by> corrupted package after using Windows to uncompress it:>> http://www.zabbix.com/forum/archive/index.php/t-837.html> [see the third comment from the bottom]>> If you did something similar, please use UNIX box to download and> uncompress/untar again the XORP tarball.>> Regards,> Pavlin

_________________________________________________________________
Get your free suite of Windows Live services!
http://www.get.live.com/wl/all


From victor at ambra.ro  Mon Oct 29 12:04:13 2007
From: victor at ambra.ro (Victor Sterpu)
Date: Mon, 29 Oct 2007 21:04:13 +0200
Subject: [Xorp-users] xorp snd igmp
Message-ID: <47262EAD.5080000@ambra.ro>

I compiled xorp 1.4 on a kernel 2.6.20.

When I try to start xorp_rtrmgr I receive the following message:
[ 2007/11/30 00:03:59  INFO xorp_rtrmgr:20308 RTRMGR +239 
master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, igmp
[ 2007/11/30 00:03:59  INFO xorp_rtrmgr:20308 RTRMGR +96 
module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea)
[ 2007/11/30 00:03:59  ERROR xorp_fea:20309 LIBCOMM +114 comm_sock.c 
comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol = 
0): Address family not supported by protocol
[ 2007/11/30 00:03:59  ERROR xorp_fea:20309 LIBCOMM +114 comm_sock.c 
comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol = 
0): Address family not supported by protocol
[ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] MFEA enabled
[ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] CLI enabled
[ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] CLI started
[ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] MFEA enabled
[ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] CLI enabled
[ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] CLI started
[ 2007/11/30 00:04:01  INFO xorp_rtrmgr:20308 RTRMGR +96 
module_manager.cc execute ] Executing module: fea (fea/xorp_fea)
[ 2007/11/30 00:04:05  INFO xorp_rtrmgr:20308 RTRMGR +96 
module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea)
[ 2007/11/30 00:04:05 INFO xorp_fea MFEA ] MFEA started
[ 2007/11/30 00:04:06  INFO xorp_rtrmgr:20308 RTRMGR +96 
module_manager.cc execute ] Executing module: igmp (mld6igmp/xorp_igmp)
[ 2007/11/30 00:04:06  WARNING xorp_rtrmgr:20308 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.
[ 2007/11/30 00:04:06 INFO xorp_igmp MLD6IGMP ] Protocol enabled
[ 2007/11/30 00:04:06 INFO xorp_igmp MLD6IGMP ] CLI enabled
[ 2007/11/30 00:04:06 INFO xorp_igmp MLD6IGMP ] CLI started
[ 2007/11/30 00:04:07 INFO xorp_igmp MLD6IGMP ] Protocol started
[ 2007/11/30 00:04:08  ERROR xorp_igmp:20314 MLD6IGMP +671 
mld6igmp_node.cc enable_vif ] Cannot enable vif eth1: no such vif
[ 2007/11/30 00:04:08 WARNING xorp_igmp XrlMld6igmpTarget ] Handling 
method for mld6igmp/0.1/enable_vif failed: XrlCmdError 102 Command 
failed Cannot enable vif eth1: no such vif
[ 2007/11/30 00:04:08  ERROR xorp_rtrmgr:20308 RTRMGR +675 
master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command 
failed Cannot enable vif eth1: no such vif
[ 2007/11/30 00:04:08  ERROR xorp_rtrmgr:20308 RTRMGR +251 
master_conf_tree.cc config_done ] Configuration failed: 102 Command 
failed Cannot enable vif eth1: no such vif
[ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +2228 task.cc 
run_task ] No more tasks to run
[ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +171 
module_manager.cc terminate ] Terminating module: fea
[ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +171 
module_manager.cc terminate ] Terminating module: igmp
[ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +194 
module_manager.cc terminate ] Killing module: igmp
[ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +171 
module_manager.cc terminate ] Terminating module: interfaces
[ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +171 
module_manager.cc terminate ] Terminating module: mfea4
[ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +194 
module_manager.cc terminate ] Killing module: mfea4
[ 2007/11/30 00:04:08  ERROR xorp_rtrmgr:20308 RTRMGR +747 
module_manager.cc done_cb ] Command "/usr/local/xorp/fea/xorp_fea": 
terminated with signal 15.
[ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +282 
module_manager.cc module_exited ] Module killed during shutdown: mfea4
[ 2007/11/30 00:04:08  ERROR xorp_rtrmgr:20308 RTRMGR +747 
module_manager.cc done_cb ] Command 
"/usr/local/xorp/mld6igmp/xorp_igmp": terminated with signal 15.
[ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +282 
module_manager.cc module_exited ] Module killed during shutdown: igmp

I use the following config.boot:
protocols {
    igmp {
        disable: false
        interface eth1 {
            vif eth1 {
                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
            }
        }
    }
}

What is wrong with my configuration?
Thank you.


From pavlin at icir.org  Mon Oct 29 14:53:52 2007
From: pavlin at icir.org (Pavlin Radoslavov)
Date: Mon, 29 Oct 2007 14:53:52 -0700
Subject: [Xorp-users] xorp snd igmp
In-Reply-To: Message from Victor Sterpu <victor@ambra.ro> 
	of "Mon, 29 Oct 2007 21:04:13 +0200." <47262EAD.5080000@ambra.ro> 
Message-ID: <200710292153.l9TLrqjL047945@possum.icir.org>

Victor Sterpu <victor at ambra.ro> wrote:

> I compiled xorp 1.4 on a kernel 2.6.20.
> 
> When I try to start xorp_rtrmgr I receive the following message:
> [ 2007/11/30 00:03:59  INFO xorp_rtrmgr:20308 RTRMGR +239 
> master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, igmp
> [ 2007/11/30 00:03:59  INFO xorp_rtrmgr:20308 RTRMGR +96 
> module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea)
> [ 2007/11/30 00:03:59  ERROR xorp_fea:20309 LIBCOMM +114 comm_sock.c 
> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol = 
> 0): Address family not supported by protocol
> [ 2007/11/30 00:03:59  ERROR xorp_fea:20309 LIBCOMM +114 comm_sock.c 
> comm_sock_open ] Error opening socket (domain = 10, type = 2, protocol = 
> 0): Address family not supported by protocol

It appears that your kernel doesn't have IPv6 support enabled.
If you don't (want to) enable IPv6 in your kernel, then you could
explicitly disable it in XORP:

gmake clean
./configure --disable-ipv6
gmake

In your configuration below you haven't configured "interfaces" and
"mfea4".

See the following URL for a sample IPv4 multicast configuration:

http://xorpc.icir.org/cgi-bin/cvsweb.cgi/xorp/rtrmgr/config/multicast4.boot?rev=1.1&content-type=text/x-cvsweb-markup

Also, note that just running IGMP (without PIM-SM) won't give you
any useful functionality (from user's perspective).
If you need multicast routing, You need to run PIM-SM as well.

Regards,
Pavlin

> [ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] MFEA enabled
> [ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] CLI enabled
> [ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] CLI started
> [ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] MFEA enabled
> [ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] CLI enabled
> [ 2007/11/30 00:03:59 INFO xorp_fea MFEA ] CLI started
> [ 2007/11/30 00:04:01  INFO xorp_rtrmgr:20308 RTRMGR +96 
> module_manager.cc execute ] Executing module: fea (fea/xorp_fea)
> [ 2007/11/30 00:04:05  INFO xorp_rtrmgr:20308 RTRMGR +96 
> module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea)
> [ 2007/11/30 00:04:05 INFO xorp_fea MFEA ] MFEA started
> [ 2007/11/30 00:04:06  INFO xorp_rtrmgr:20308 RTRMGR +96 
> module_manager.cc execute ] Executing module: igmp (mld6igmp/xorp_igmp)
> [ 2007/11/30 00:04:06  WARNING xorp_rtrmgr:20308 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.
> [ 2007/11/30 00:04:06 INFO xorp_igmp MLD6IGMP ] Protocol enabled
> [ 2007/11/30 00:04:06 INFO xorp_igmp MLD6IGMP ] CLI enabled
> [ 2007/11/30 00:04:06 INFO xorp_igmp MLD6IGMP ] CLI started
> [ 2007/11/30 00:04:07 INFO xorp_igmp MLD6IGMP ] Protocol started
> [ 2007/11/30 00:04:08  ERROR xorp_igmp:20314 MLD6IGMP +671 
> mld6igmp_node.cc enable_vif ] Cannot enable vif eth1: no such vif
> [ 2007/11/30 00:04:08 WARNING xorp_igmp XrlMld6igmpTarget ] Handling 
> method for mld6igmp/0.1/enable_vif failed: XrlCmdError 102 Command 
> failed Cannot enable vif eth1: no such vif
> [ 2007/11/30 00:04:08  ERROR xorp_rtrmgr:20308 RTRMGR +675 
> master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command 
> failed Cannot enable vif eth1: no such vif
> [ 2007/11/30 00:04:08  ERROR xorp_rtrmgr:20308 RTRMGR +251 
> master_conf_tree.cc config_done ] Configuration failed: 102 Command 
> failed Cannot enable vif eth1: no such vif
> [ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +2228 task.cc 
> run_task ] No more tasks to run
> [ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +171 
> module_manager.cc terminate ] Terminating module: fea
> [ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +171 
> module_manager.cc terminate ] Terminating module: igmp
> [ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +194 
> module_manager.cc terminate ] Killing module: igmp
> [ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +171 
> module_manager.cc terminate ] Terminating module: interfaces
> [ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +171 
> module_manager.cc terminate ] Terminating module: mfea4
> [ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +194 
> module_manager.cc terminate ] Killing module: mfea4
> [ 2007/11/30 00:04:08  ERROR xorp_rtrmgr:20308 RTRMGR +747 
> module_manager.cc done_cb ] Command "/usr/local/xorp/fea/xorp_fea": 
> terminated with signal 15.
> [ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +282 
> module_manager.cc module_exited ] Module killed during shutdown: mfea4
> [ 2007/11/30 00:04:08  ERROR xorp_rtrmgr:20308 RTRMGR +747 
> module_manager.cc done_cb ] Command 
> "/usr/local/xorp/mld6igmp/xorp_igmp": terminated with signal 15.
> [ 2007/11/30 00:04:08  INFO xorp_rtrmgr:20308 RTRMGR +282 
> module_manager.cc module_exited ] Module killed during shutdown: igmp
> 
> I use the following config.boot:
> protocols {
>     igmp {
>         disable: false
>         interface eth1 {
>             vif eth1 {
>                 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
>             }
>         }
>     }
> }
> 
> What is wrong with my configuration?
> Thank you.
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From daniel.paquet at gmail.com  Tue Oct 30 12:01:03 2007
From: daniel.paquet at gmail.com (Daniel Paquet)
Date: Tue, 30 Oct 2007 15:01:03 -0400
Subject: [Xorp-users] New to this multcast - Can this work with xorp?
Message-ID: <9a1a10a40710301201x5fb2b768l7cb95cac0bf9180c@mail.gmail.com>

Hello!

  I am a fresh newbie in multicast routing! Woho! hehe

  So here is the thing.

  I have a linux box that I want it to route multicast trafic from a gre tunnel.


  The linux box has only 1 network interface. The multicast trafic
gets in from the tunnel interface and needs to get out to