From adam@hiddennet.net Wed Jan 5 09:13:33 2005 From: adam@hiddennet.net (Adam Greenhalgh) Date: Wed, 05 Jan 2005 09:13:33 +0000 Subject: [Xorp-users] Re: [Xorp-feedback] Question#2 In-Reply-To: <1104891897.41db4ff915fc0@webmail.unb.ca> References: <1104891897.41db4ff915fc0@webmail.unb.ca> Message-ID: <1104916413.6265.3.camel@cellini.cs.ucl.ac.uk> I am not sure whether linux actually fully supports ipv6 multicast forwarding, so I am forwarding this to the xorp-users@xorp.org list (this is the best place to post this type of question, I suggest you subscribe to xorp-hackers@xorp.org and xorp-users@xorp.org) . In general I'd suggest you use freebsd over linux for multicast work as unfortunately i think it is more mature (i could be wrong). Adam On Tue, 2005-01-04 at 22:24 -0400, Chen, Albert wrote: > Hi Adam, > Thank you for your reply. > Actually, I'd like to use the feature of "IPv6 multicast forwarding "on my PC router. > Does XORP work on FC2 with a Linux 2.6.x kernel? > I am looking forward from you. > > regards, > > Albert Chen > MCS > UNB Fredericton > > > Quoting Adam Greenhalgh : > > > Xorp 1.0 does compile and run on Fedora Core 2 with a linux 2.6.x > > kernel. Some of the features aren't supported on Linux because the linux > > kernel doesn't have all the features freebsd does. So you should be > > fine. > > > > I suggest you use the latest developement version of xorp. rather than > > the release version as things have improved at lot since xorp 1.0 , for > > more details check http://www.xorp.org/cvs.html . > > > > For future reference it is probably best if you post similar questions > > to xorp-hackers@xorp.org > > > > Adam > > > > On Mon, 2005-01-03 at 14:22 -0400, Chen, Albert wrote: > > > Dear Sir, > > > I am using Fedora Core 2 on my machine. Does your XORP 1.0 run on Linux 2.6.x? > > > thank you very much! > > > > > > regards, > > > > > > Albert Chen > > > MCS > > > UNB Fredericton > > > > > > > > > > > > _______________________________________________ > > > Xorp-feedback mailing list > > > Xorp-feedback@xorp.org > > > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-feedback > > -- > > Adam Greenhalgh > > > > From hasso@linux.ee Wed Jan 5 10:01:37 2005 From: hasso@linux.ee (Hasso Tepper) Date: Wed, 5 Jan 2005 12:01:37 +0200 Subject: [Xorp-users] Re: [Xorp-feedback] Question#2 In-Reply-To: <1104916413.6265.3.camel@cellini.cs.ucl.ac.uk> References: <1104891897.41db4ff915fc0@webmail.unb.ca> <1104916413.6265.3.camel@cellini.cs.ucl.ac.uk> Message-ID: <200501051201.38057.hasso@linux.ee> Adam Greenhalgh wrote: > I am not sure whether linux actually fully supports ipv6 multicast > forwarding, so I am forwarding this to the xorp-users@xorp.org list > (this is the best place to post this type of question, I suggest you > subscribe to xorp-hackers@xorp.org and xorp-users@xorp.org) . In general > I'd suggest you use freebsd over linux for multicast work as > unfortunately i think it is more mature (i could be wrong). Stock Linux doesn't support ipv6 multicast forwarding at all. There is some work done though - http://clarinet.u-strasbg.fr/~hoerdt/linux_ipv6_mforwarding/ -- Hasso Tepper From ren@sandmail.sandburst.com Thu Jan 6 13:33:35 2005 From: ren@sandmail.sandburst.com (Yonghong Ren) Date: Thu, 6 Jan 2005 08:33:35 -0500 Subject: [Xorp-users] "gmake check" error messages "timer expired..." etc. Message-ID: This is a multi-part message in MIME format. ------_=_NextPart_001_01C4F3F4.524FFB37 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Running "gmake check" got the following errors. What do they mean? Thanks! =20 =20 [ 2004/12/31 10:16:35 ERROR xorp_bgp:6010 XRL +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file ive timeout /12/31 10:16:35 ERROR xorp_rib:6008 XRL +329 xrl_pf_stcp.cc die ] STCPRequestHandler died: life timer expired [ 2004/12/31 10:16:35 ERROR xorp_rib:6008 XRL +329 xrl_pf_stcp.cc die ] STCPRequestHandler died: life timer expired =20 And many lines of ... =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D Timer Expiry *much* later than scheduled: behind by 407.523750 seconds =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D Timer Expiry *much* later than scheduled: behind by 406.523750 seconds =20 =20 ------_=_NextPart_001_01C4F3F4.524FFB37 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Running “gmake = check” got the following errors. What do they mean? = Thanks!

 

 

[ 2004/12/31 = 10:16:35  ERROR xorp_bgp:6010 XRL +628 = xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file

ive timeout

/12/31 = 10:16:35  = ERROR xorp_rib:6008 XRL +329 xrl_pf_stcp.cc die ] = STCPRequestHandler died: life timer = expired

[ 2004/12/31 = 10:16:35  ERROR xorp_rib:6008 XRL +329 = xrl_pf_stcp.cc die ] STCPRequestHandler died: life timer expired

 

And many lines of = …

 

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D

Timer Expiry *much* = later than scheduled: behind by 407.523750 = seconds

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D

Timer Expiry *much* = later than scheduled: behind by 406.523750 = seconds

 

 

=00 ------_=_NextPart_001_01C4F3F4.524FFB37-- From atanu@ICSI.Berkeley.EDU Thu Jan 6 19:08:12 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Thu, 06 Jan 2005 11:08:12 -0800 Subject: [Xorp-users] "gmake check" error messages "timer expired..." etc. In-Reply-To: Message from "Yonghong Ren" of "Thu, 06 Jan 2005 08:33:35 EST." Message-ID: <4629.1105038492@tigger.icir.org> Hi, The XORP IPC scheme by default runs over TCP. The first set of errors are due to TCP connections terminating. I think we send our own keepalive message on the these TCP connections. We use a timer to send and monitor the keepalive messages. The later errors are reporting that some timers have fired 406 seconds late. If the timer code misbehaved this maybe the reason the TCP connections were dropped. Is the problem repeatable, which operating system are you using? We have seen an occasional problem that on a heavily loaded FreeBSD machine an occasional call to gettimeofday will return a value 695 seconds behind real time. Atanu. >>>>> "Yonghong" == Yonghong Ren writes: Yonghong> Running "gmake check" got the following errors. What do Yonghong> they mean? Thanks! Yonghong> [ 2004/12/31 10:16:35 ERROR xorp_bgp:6010 XRL +628 Yonghong> xrl_pf_stcp.cc die ] Yonghong> XrlPFSTCPSender died: end of file ive timeout /12/31 Yonghong> 10:16:35 ERROR xorp_rib:6008 XRL +329 xrl_pf_stcp.cc die ] Yonghong> STCPRequestHandler died: life timer expired [ 2004/12/31 Yonghong> 10:16:35 ERROR xorp_rib:6008 XRL +329 xrl_pf_stcp.cc die ] Yonghong> STCPRequestHandler died: life timer expired =20 And many Yonghong> lines of ... Yonghong> Timer Expiry *much* later than Yonghong> scheduled: behind by 407.523750 seconds Yonghong> Timer Expiry *much* later than Yonghong> scheduled: behind by 406.523750 seconds From kras0021@umn.edu Mon Jan 10 23:05:18 2005 From: kras0021@umn.edu (Jeff Krasky) Date: Mon, 10 Jan 2005 17:05:18 CST Subject: [Xorp-users] Bind failed: Could not assign requested address Message-ID: <200501102305.j0AN5IZ3020204@dingo.software.umn.edu> Hi, I am trying to get Xorp running on a Linux machine that I have. When I log in as root and run ./xorp_rtrmgr I get the following: [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 RTRMGR +134 master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, bgp [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc run ] Running module: interfaces (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 16:24:01 INFO xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc run ] Running module: fea (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 16:24:07 INFO xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc run ] Running module: rib (/home/jkrasky/xorp/rib/xorp_rib) [ 2005/01/10 16:24:09 INFO xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc run ] Running module: bgp (/home/jkrasky/xorp/bgp/xorp_bgp) [ 2005/01/10 16:24:11 ERROR xorp_bgp:3414 BGP +400 socket.cc connect_socket ] Bind failed: Cannot assign requested address [ 2005/01/10 16:24:11 FATAL xorp_bgp:3414 BGP +67 socket.cc create_listener ] Bind failed: Cannot assign requested address [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +550 module_manager.cc killed ] Module abnormally killed: bgp [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +763 task.cc execute_done ] 210 Transport failed [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +1179 task.cc task_fail ] Shutting down fatally wounded process (bgp) [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +540 master_conf_tree.cc commit_pass2_done ] Commit failed: 210 Transport failed [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +146 master_conf_tree.cc config_done ] Configuration failed: 210 Transport failed [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +1372 task.cc run_task ] No more tasks to run [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 module_manager.cc terminate ] Terminating module: fea [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 module_manager.cc terminate ] Terminating module: interfaces [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 module_manager.cc terminate ] Killing module: interfaces (pid = 3412) [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 module_manager.cc terminate ] Terminating module: rib [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 module_manager.cc terminate ] Killing module: rib (pid = 3413) [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 module_manager.cc killed ] Module killed during shutdown: interfaces [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 module_manager.cc killed ] Module killed during shutdown: rib [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file Here is my config.boot file: interfaces { interface eth0 { description: "data interface" vif eth0 { address 172.16.1.150 { prefix-length: 32 broadcast: 172.16.1.150 } } } } fea { enable-unicast-forwarding4: true /* enable-unicast-forwarding6: true */ } protocols { bgp { bgp-id: 172.16.1.150 local-as: 33333 peer 172.16.1.152 { local-ip: 172.16.1.152 as: 33334 next-hop: 172.16.1.152 local-port: 179 peer-port: 179 /* holdtime: 120 */ /* enabled: true */ /* Optionally enable other AFI/SAFI combinations */ /* enable-ipv4-multicast */ /* enable-ipv6-unicast */ /* enable-ipv6-multicast */ } /* Originate IPv4 Routes */ /* network4 10.10.10.0/24 { next-hop: 10.10.10.10 unicast: true multicast: true } */ /* Originate IPv6 Routes */ /* network6 10:10:10:10::/64 { next-hop: 10:10:10:10:10:10:10:10 unicast: true multicast: true } */ } } If someone could give me a hint to point me in the right direction as to what might be wrong with bind() I would be grateful. Thanks, Jeff From atanu@ICSI.Berkeley.EDU Tue Jan 11 01:07:40 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Mon, 10 Jan 2005 17:07:40 -0800 Subject: [Xorp-users] Bind failed: Could not assign requested address In-Reply-To: Message from Jeff Krasky of "Mon, 10 Jan 2005 17:05:18 CST." <200501102305.j0AN5IZ3020204@dingo.software.umn.edu> Message-ID: <84659.1105405660@tigger.icir.org> Hi, The port (179) that BGP is attempting to bind to is privileged. The router manager needs to be run as root. It is also necessary to run as root if you want to install any routes in the kernel. Atanu. >>>>> "Jeff" == Jeff Krasky writes: Jeff> Hi, I am trying to get Xorp running on a Linux machine that I Jeff> have. When I log in as root and run ./xorp_rtrmgr I get the Jeff> following: Jeff> [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 RTRMGR +134 Jeff> master_conf_tree.cc execute ] Changed modules: interfaces, Jeff> fea, rib, bgp [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 Jeff> RTRMGR +404 module_manager.cc run ] Running module: interfaces Jeff> (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 16:24:01 INFO Jeff> xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc run ] Running Jeff> module: fea (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 Jeff> 16:24:07 INFO xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc Jeff> run ] Running module: rib (/home/jkrasky/xorp/rib/xorp_rib) [ Jeff> 2005/01/10 16:24:09 INFO xorp_rtrmgr:3411 RTRMGR +404 Jeff> module_manager.cc run ] Running module: bgp Jeff> (/home/jkrasky/xorp/bgp/xorp_bgp) [ 2005/01/10 16:24:11 ERROR Jeff> xorp_bgp:3414 BGP +400 socket.cc connect_socket ] Bind failed: Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 FATAL Jeff> xorp_bgp:3414 BGP +67 socket.cc create_listener ] Bind failed: Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 INFO Jeff> xorp_rtrmgr:3411 RTRMGR +550 module_manager.cc killed ] Module Jeff> abnormally killed: bgp [ 2005/01/10 16:24:11 ERROR Jeff> xorp_rtrmgr:3411 XRL +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender Jeff> died: end of file [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 Jeff> RTRMGR +763 task.cc execute_done ] 210 Transport failed [ Jeff> 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +1179 Jeff> task.cc task_fail ] Shutting down fatally wounded process Jeff> (bgp) [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +540 Jeff> master_conf_tree.cc commit_pass2_done ] Commit failed: 210 Jeff> Transport failed [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 Jeff> RTRMGR +146 master_conf_tree.cc config_done ] Configuration Jeff> failed: 210 Transport failed [ 2005/01/10 16:24:11 INFO Jeff> xorp_rtrmgr:3411 RTRMGR +1372 task.cc run_task ] No more tasks Jeff> to run [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 Jeff> module_manager.cc terminate ] Terminating module: fea [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 Jeff> module_manager.cc terminate ] Terminating module: interfaces [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 Jeff> module_manager.cc terminate ] Killing module: interfaces (pid Jeff> = 3412) [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR Jeff> +216 module_manager.cc terminate ] Terminating module: rib [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 Jeff> module_manager.cc terminate ] Killing module: rib (pid = 3413) Jeff> [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 Jeff> module_manager.cc killed ] Module killed during shutdown: Jeff> interfaces [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL Jeff> +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 Jeff> module_manager.cc killed ] Module killed during shutdown: rib Jeff> [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL +628 Jeff> xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file Jeff> Here is my config.boot file: Jeff> interfaces { interface eth0 { description: "data interface" Jeff> vif eth0 { address 172.16.1.150 { prefix-length: 32 broadcast: Jeff> 172.16.1.150 } } } } Jeff> fea { enable-unicast-forwarding4: true /* Jeff> enable-unicast-forwarding6: true */ } Jeff> protocols { bgp { bgp-id: 172.16.1.150 local-as: 33333 Jeff> peer 172.16.1.152 { local-ip: 172.16.1.152 as: 33334 Jeff> next-hop: 172.16.1.152 Jeff> local-port: 179 peer-port: 179 Jeff> /* holdtime: 120 */ /* enabled: true */ Jeff> /* Optionally enable other AFI/SAFI combinations */ Jeff> /* enable-ipv4-multicast */ Jeff> /* enable-ipv6-unicast */ /* enable-ipv6-multicast Jeff> */ } Jeff> /* Originate IPv4 Routes */ /* network4 10.10.10.0/24 { Jeff> next-hop: 10.10.10.10 unicast: true multicast: true } */ Jeff> /* Originate IPv6 Routes */ /* network6 10:10:10:10::/64 Jeff> { next-hop: 10:10:10:10:10:10:10:10 unicast: true multicast: Jeff> true } */ } } Jeff> If someone could give me a hint to point me in the right Jeff> direction as to what might be wrong with bind() I would be Jeff> grateful. Jeff> Thanks, Jeff> Jeff Jeff> _______________________________________________ Xorp-users Jeff> mailing list Xorp-users@xorp.org Jeff> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From berni@birkenwald.de Tue Jan 11 02:14:38 2005 From: berni@birkenwald.de (Bernhard Schmidt) Date: Tue, 11 Jan 2005 03:14:38 +0100 Subject: [Xorp-users] Compile error on FreeBSD 5.3 Message-ID: <1105409678.20978.4.camel@cholera> Hi, just reporting, this has been in for some days now. FreeBSD 5.3 STABLE, FreeBSD sources are from 03.01.05, cvs update has been done some minutes ago. I tried it the last few days and it always broke with that error. source='pa_backend_ipfw2.cc' object='pa_backend_ipfw2.lo' libtool=yes \ depfile='.deps/pa_backend_ipfw2.Plo' tmpdepfile='.deps/pa_backend_ipfw2.TPlo' \ depmode=gcc3 /bin/sh ../config/depcomp \ /bin/sh ../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -O2 -W -Wall -Wwrite-strings -Wcast-qual -Werror -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-22 -pipe -c -o pa_backend_ipfw2.lo `test -f pa_backend_ipfw2.cc || echo './'`pa_backend_ipfw2.cc g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -O2 -W -Wall -Wwrite-strings -Wcast-qual -Werror -Wpointer-arith -Wcast-align -Woverloaded-virtual -ftemplate-depth-22 -pipe -c pa_backend_ipfw2.cc -MT pa_backend_ipfw2.lo -MD -MP -MF .deps/pa_backend_ipfw2.TPlo -o pa_backend_ipfw2.o pa_backend_ipfw2.cc: In member function `int PaIpfw2Backend::read_ruleset4(int, std::map >, std::less, std::allocator > > > >&)': pa_backend_ipfw2.cc:497: warning: 'nbytes' might be used uninitialized in this function Bernhard From kras0021@umn.edu Tue Jan 11 02:31:24 2005 From: kras0021@umn.edu (Jeff Krasky) Date: Mon, 10 Jan 2005 20:31:24 CST Subject: [Xorp-users] Bind failed: Could not assign requested address Message-ID: <200501110231.j0B2VOJZ018039@challenge.software.umn.edu> I am getting the error when logged in as root when I run ./xorp_rtrmgr Jeff On 10 Jan 2005, Atanu Ghosh wrote: > Hi, > > The port (179) that BGP is attempting to bind to is privileged. The > router manager needs to be run as root. It is also necessary to run as > root if you want to install any routes in the kernel. > > Atanu. > > >>>>> "Jeff" == Jeff Krasky writes: > > Jeff> Hi, I am trying to get Xorp running on a Linux machine that I > Jeff> have. When I log in as root and run ./xorp_rtrmgr I get the > Jeff> following: > > Jeff> [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 RTRMGR +134 > Jeff> master_conf_tree.cc execute ] Changed modules: interfaces, > Jeff> fea, rib, bgp [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 > Jeff> RTRMGR +404 module_manager.cc run ] Running module: interfaces > Jeff> (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 16:24:01 INFO > Jeff> xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc run ] Running > Jeff> module: fea (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 > Jeff> 16:24:07 INFO xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc > Jeff> run ] Running module: rib (/home/jkrasky/xorp/rib/xorp_rib) [ > Jeff> 2005/01/10 16:24:09 INFO xorp_rtrmgr:3411 RTRMGR +404 > Jeff> module_manager.cc run ] Running module: bgp > Jeff> (/home/jkrasky/xorp/bgp/xorp_bgp) [ 2005/01/10 16:24:11 ERROR > Jeff> xorp_bgp:3414 BGP +400 socket.cc connect_socket ] Bind failed: > Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 FATAL > Jeff> xorp_bgp:3414 BGP +67 socket.cc create_listener ] Bind failed: > Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 INFO > Jeff> xorp_rtrmgr:3411 RTRMGR +550 module_manager.cc killed ] Module > Jeff> abnormally killed: bgp [ 2005/01/10 16:24:11 ERROR > Jeff> xorp_rtrmgr:3411 XRL +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender > Jeff> died: end of file [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 > Jeff> RTRMGR +763 task.cc execute_done ] 210 Transport failed [ > Jeff> 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +1179 > Jeff> task.cc task_fail ] Shutting down fatally wounded process > Jeff> (bgp) [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +540 > Jeff> master_conf_tree.cc commit_pass2_done ] Commit failed: 210 > Jeff> Transport failed [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 > Jeff> RTRMGR +146 master_conf_tree.cc config_done ] Configuration > Jeff> failed: 210 Transport failed [ 2005/01/10 16:24:11 INFO > Jeff> xorp_rtrmgr:3411 RTRMGR +1372 task.cc run_task ] No more tasks > Jeff> to run [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 > Jeff> module_manager.cc terminate ] Terminating module: fea [ > Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 > Jeff> module_manager.cc terminate ] Terminating module: interfaces [ > Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 > Jeff> module_manager.cc terminate ] Killing module: interfaces (pid > Jeff> = 3412) [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR > Jeff> +216 module_manager.cc terminate ] Terminating module: rib [ > Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 > Jeff> module_manager.cc terminate ] Killing module: rib (pid = 3413) > Jeff> [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 > Jeff> module_manager.cc killed ] Module killed during shutdown: > Jeff> interfaces [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL > Jeff> +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file [ > Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 > Jeff> module_manager.cc killed ] Module killed during shutdown: rib > Jeff> [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL +628 > Jeff> xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file > > Jeff> Here is my config.boot file: > > Jeff> interfaces { interface eth0 { description: "data interface" > Jeff> vif eth0 { address 172.16.1.150 { prefix-length: 32 broadcast: > Jeff> 172.16.1.150 } } } } > > Jeff> fea { enable-unicast-forwarding4: true /* > Jeff> enable-unicast-forwarding6: true */ } > > Jeff> protocols { bgp { bgp-id: 172.16.1.150 local-as: 33333 > > Jeff> peer 172.16.1.152 { local-ip: 172.16.1.152 as: 33334 > Jeff> next-hop: 172.16.1.152 > > Jeff> local-port: 179 peer-port: 179 > > Jeff> /* holdtime: 120 */ /* enabled: true */ > > Jeff> /* Optionally enable other AFI/SAFI combinations */ > Jeff> /* enable-ipv4-multicast */ > > Jeff> /* enable-ipv6-unicast */ /* enable-ipv6-multicast > Jeff> */ } > > Jeff> /* Originate IPv4 Routes */ /* network4 10.10.10.0/24 { > Jeff> next-hop: 10.10.10.10 unicast: true multicast: true } */ > > Jeff> /* Originate IPv6 Routes */ /* network6 10:10:10:10::/64 > Jeff> { next-hop: 10:10:10:10:10:10:10:10 unicast: true multicast: > Jeff> true } */ } } > > Jeff> If someone could give me a hint to point me in the right > Jeff> direction as to what might be wrong with bind() I would be > Jeff> grateful. > > Jeff> Thanks, > > > > Jeff> Jeff > > Jeff> _______________________________________________ Xorp-users > Jeff> mailing list Xorp-users@xorp.org > Jeff> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > _______________________________________________ > Xorp-users mailing list > Xorp-users@xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > From atanu@ICSI.Berkeley.EDU Tue Jan 11 03:36:08 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Mon, 10 Jan 2005 19:36:08 -0800 Subject: [Xorp-users] Bind failed: Could not assign requested address In-Reply-To: Message from Jeff Krasky of "Mon, 10 Jan 2005 20:31:24 CST." <200501110231.j0B2VOJZ018039@challenge.software.umn.edu> Message-ID: <20087.1105414568@tigger.icir.org> Hi, Is there a chance that the "local-ip" statement in the configuration file does not match any of the interface addresses on your host? Atanu. >>>>> "Jeff" == Jeff Krasky writes: Jeff> I am getting the error when logged in as root when I run Jeff> ./xorp_rtrmgr Jeff Jeff> On 10 Jan 2005, Atanu Ghosh wrote: >> Hi, >> >> The port (179) that BGP is attempting to bind to is >> privileged. The router manager needs to be run as root. It is >> also necessary to run as root if you want to install any routes >> in the kernel. >> >> Atanu. >> >> >>>>> "Jeff" == Jeff Krasky writes: >> Jeff> Hi, I am trying to get Xorp running on a Linux machine that I Jeff> have. When I log in as root and run ./xorp_rtrmgr I get the Jeff> following: >> Jeff> [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 RTRMGR +134 Jeff> master_conf_tree.cc execute ] Changed modules: interfaces, Jeff> fea, rib, bgp [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 Jeff> RTRMGR +404 module_manager.cc run ] Running module: interfaces Jeff> (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 16:24:01 INFO Jeff> xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc run ] Running Jeff> module: fea (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 Jeff> 16:24:07 INFO xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc Jeff> run ] Running module: rib (/home/jkrasky/xorp/rib/xorp_rib) [ Jeff> 2005/01/10 16:24:09 INFO xorp_rtrmgr:3411 RTRMGR +404 Jeff> module_manager.cc run ] Running module: bgp Jeff> (/home/jkrasky/xorp/bgp/xorp_bgp) [ 2005/01/10 16:24:11 ERROR Jeff> xorp_bgp:3414 BGP +400 socket.cc connect_socket ] Bind failed: Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 FATAL Jeff> xorp_bgp:3414 BGP +67 socket.cc create_listener ] Bind failed: Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 INFO Jeff> xorp_rtrmgr:3411 RTRMGR +550 module_manager.cc killed ] Module Jeff> abnormally killed: bgp [ 2005/01/10 16:24:11 ERROR Jeff> xorp_rtrmgr:3411 XRL +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender Jeff> died: end of file [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 Jeff> RTRMGR +763 task.cc execute_done ] 210 Transport failed [ Jeff> 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +1179 Jeff> task.cc task_fail ] Shutting down fatally wounded process Jeff> (bgp) [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +540 Jeff> master_conf_tree.cc commit_pass2_done ] Commit failed: 210 Jeff> Transport failed [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 Jeff> RTRMGR +146 master_conf_tree.cc config_done ] Configuration Jeff> failed: 210 Transport failed [ 2005/01/10 16:24:11 INFO Jeff> xorp_rtrmgr:3411 RTRMGR +1372 task.cc run_task ] No more tasks Jeff> to run [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 Jeff> module_manager.cc terminate ] Terminating module: fea [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 Jeff> module_manager.cc terminate ] Terminating module: interfaces [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 Jeff> module_manager.cc terminate ] Killing module: interfaces (pid Jeff> = 3412) [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR Jeff> +216 module_manager.cc terminate ] Terminating module: rib [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 Jeff> module_manager.cc terminate ] Killing module: rib (pid = 3413) Jeff> [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 Jeff> module_manager.cc killed ] Module killed during shutdown: Jeff> interfaces [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL Jeff> +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 Jeff> module_manager.cc killed ] Module killed during shutdown: rib Jeff> [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL +628 Jeff> xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file >> Jeff> Here is my config.boot file: >> Jeff> interfaces { interface eth0 { description: "data interface" Jeff> vif eth0 { address 172.16.1.150 { prefix-length: 32 broadcast: Jeff> 172.16.1.150 } } } } >> Jeff> fea { enable-unicast-forwarding4: true /* Jeff> enable-unicast-forwarding6: true */ } >> Jeff> protocols { bgp { bgp-id: 172.16.1.150 local-as: 33333 >> Jeff> peer 172.16.1.152 { local-ip: 172.16.1.152 as: 33334 next-hop: Jeff> 172.16.1.152 >> Jeff> local-port: 179 peer-port: 179 >> Jeff> /* holdtime: 120 */ /* enabled: true */ >> Jeff> /* Optionally enable other AFI/SAFI combinations */ /* Jeff> enable-ipv4-multicast */ >> Jeff> /* enable-ipv6-unicast */ /* enable-ipv6-multicast */ } >> Jeff> /* Originate IPv4 Routes */ /* network4 10.10.10.0/24 { Jeff> next-hop: 10.10.10.10 unicast: true multicast: true } */ >> Jeff> /* Originate IPv6 Routes */ /* network6 10:10:10:10::/64 { Jeff> next-hop: 10:10:10:10:10:10:10:10 unicast: true multicast: Jeff> true } */ } } >> Jeff> If someone could give me a hint to point me in the right Jeff> direction as to what might be wrong with bind() I would be Jeff> grateful. >> Jeff> Thanks, >> Jeff> Jeff >> Jeff> _______________________________________________ Xorp-users Jeff> mailing list Xorp-users@xorp.org Jeff> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> _______________________________________________ Xorp-users >> mailing list Xorp-users@xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> From atanu@ICSI.Berkeley.EDU Tue Jan 11 04:23:52 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Mon, 10 Jan 2005 20:23:52 -0800 Subject: [Xorp-users] Compile error on FreeBSD 5.3 In-Reply-To: Message from Bernhard Schmidt of "Tue, 11 Jan 2005 03:14:38 +0100." <1105409678.20978.4.camel@cholera> Message-ID: <34245.1105417432@tigger.icir.org> Thanks for reporting this. Atanu. >>>>> "Bernhard" == Bernhard Schmidt writes: Bernhard> Hi, just reporting, this has been in for some days Bernhard> now. FreeBSD 5.3 STABLE, FreeBSD sources are from Bernhard> 03.01.05, cvs update has been done some minutes ago. I Bernhard> tried it the last few days and it always broke with that Bernhard> error. Bernhard> source='pa_backend_ipfw2.cc' object='pa_backend_ipfw2.lo' Bernhard> libtool=yes \ depfile='.deps/pa_backend_ipfw2.Plo' Bernhard> tmpdepfile='.deps/pa_backend_ipfw2.TPlo' \ depmode=gcc3 Bernhard> /bin/sh ../config/depcomp \ /bin/sh ../libtool Bernhard> --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -O2 Bernhard> -W -Wall -Wwrite-strings -Wcast-qual -Werror Bernhard> -Wpointer-arith -Wcast-align -Woverloaded-virtual Bernhard> -ftemplate-depth-22 -pipe -c -o pa_backend_ipfw2.lo `test Bernhard> -f pa_backend_ipfw2.cc || echo './'`pa_backend_ipfw2.cc Bernhard> g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -O2 -W -Wall Bernhard> -Wwrite-strings -Wcast-qual -Werror -Wpointer-arith Bernhard> -Wcast-align -Woverloaded-virtual -ftemplate-depth-22 Bernhard> -pipe -c pa_backend_ipfw2.cc -MT pa_backend_ipfw2.lo -MD Bernhard> -MP -MF .deps/pa_backend_ipfw2.TPlo -o pa_backend_ipfw2.o Bernhard> pa_backend_ipfw2.cc: In member function `int Bernhard> PaIpfw2Backend::read_ruleset4(int, std::map std::vector >, Bernhard> std::less, std::allocator uint16_t, std::vector > Bernhard> > > >&)': pa_backend_ipfw2.cc:497: warning: 'nbytes' might Bernhard> be used uninitialized in this function Bernhard> Bernhard Bernhard> _______________________________________________ Xorp-users Bernhard> mailing list Xorp-users@xorp.org Bernhard> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From kras0021@UMN.EDU Tue Jan 11 20:46:01 2005 From: kras0021@UMN.EDU (Jeff Krasky) Date: Tue, 11 Jan 2005 14:46:01 CST Subject: [Xorp-users] Bind failed: Could not assign requested address Message-ID: <200501112046.j0BKk1kS014093@dingo.software.umn.edu> Yes, that was it. Thank you. Jeff On 10 Jan 2005, Atanu Ghosh wrote: > Hi, > > Is there a chance that the "local-ip" statement in the configuration > file does not match any of the interface addresses on your host? > > Atanu. > > >>>>> "Jeff" == Jeff Krasky writes: > > Jeff> I am getting the error when logged in as root when I run > Jeff> ./xorp_rtrmgr Jeff > > > Jeff> On 10 Jan 2005, Atanu Ghosh wrote: > >> Hi, > >> > >> The port (179) that BGP is attempting to bind to is > >> privileged. The router manager needs to be run as root. It is > >> also necessary to run as root if you want to install any routes > >> in the kernel. > >> > >> Atanu. > >> > >> >>>>> "Jeff" == Jeff Krasky writes: > >> > Jeff> Hi, I am trying to get Xorp running on a Linux machine that I > Jeff> have. When I log in as root and run ./xorp_rtrmgr I get the > Jeff> following: > >> > Jeff> [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 RTRMGR +134 > Jeff> master_conf_tree.cc execute ] Changed modules: interfaces, > Jeff> fea, rib, bgp [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 > Jeff> RTRMGR +404 module_manager.cc run ] Running module: interfaces > Jeff> (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 16:24:01 INFO > Jeff> xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc run ] Running > Jeff> module: fea (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 > Jeff> 16:24:07 INFO xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc > Jeff> run ] Running module: rib (/home/jkrasky/xorp/rib/xorp_rib) [ > Jeff> 2005/01/10 16:24:09 INFO xorp_rtrmgr:3411 RTRMGR +404 > Jeff> module_manager.cc run ] Running module: bgp > Jeff> (/home/jkrasky/xorp/bgp/xorp_bgp) [ 2005/01/10 16:24:11 ERROR > Jeff> xorp_bgp:3414 BGP +400 socket.cc connect_socket ] Bind failed: > Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 FATAL > Jeff> xorp_bgp:3414 BGP +67 socket.cc create_listener ] Bind failed: > Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 INFO > Jeff> xorp_rtrmgr:3411 RTRMGR +550 module_manager.cc killed ] Module > Jeff> abnormally killed: bgp [ 2005/01/10 16:24:11 ERROR > Jeff> xorp_rtrmgr:3411 XRL +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender > Jeff> died: end of file [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 > Jeff> RTRMGR +763 task.cc execute_done ] 210 Transport failed [ > Jeff> 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +1179 > Jeff> task.cc task_fail ] Shutting down fatally wounded process > Jeff> (bgp) [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +540 > Jeff> master_conf_tree.cc commit_pass2_done ] Commit failed: 210 > Jeff> Transport failed [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 > Jeff> RTRMGR +146 master_conf_tree.cc config_done ] Configuration > Jeff> failed: 210 Transport failed [ 2005/01/10 16:24:11 INFO > Jeff> xorp_rtrmgr:3411 RTRMGR +1372 task.cc run_task ] No more tasks > Jeff> to run [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 > Jeff> module_manager.cc terminate ] Terminating module: fea [ > Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 > Jeff> module_manager.cc terminate ] Terminating module: interfaces [ > Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 > Jeff> module_manager.cc terminate ] Killing module: interfaces (pid > Jeff> = 3412) [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR > Jeff> +216 module_manager.cc terminate ] Terminating module: rib [ > Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 > Jeff> module_manager.cc terminate ] Killing module: rib (pid = 3413) > Jeff> [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 > Jeff> module_manager.cc killed ] Module killed during shutdown: > Jeff> interfaces [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL > Jeff> +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file [ > Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 > Jeff> module_manager.cc killed ] Module killed during shutdown: rib > Jeff> [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL +628 > Jeff> xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file > >> > Jeff> Here is my config.boot file: > >> > Jeff> interfaces { interface eth0 { description: "data interface" > Jeff> vif eth0 { address 172.16.1.150 { prefix-length: 32 broadcast: > Jeff> 172.16.1.150 } } } } > >> > Jeff> fea { enable-unicast-forwarding4: true /* > Jeff> enable-unicast-forwarding6: true */ } > >> > Jeff> protocols { bgp { bgp-id: 172.16.1.150 local-as: 33333 > >> > Jeff> peer 172.16.1.152 { local-ip: 172.16.1.152 as: 33334 next-hop: > Jeff> 172.16.1.152 > >> > Jeff> local-port: 179 peer-port: 179 > >> > Jeff> /* holdtime: 120 */ /* enabled: true */ > >> > Jeff> /* Optionally enable other AFI/SAFI combinations */ /* > Jeff> enable-ipv4-multicast */ > >> > Jeff> /* enable-ipv6-unicast */ /* enable-ipv6-multicast */ } > >> > Jeff> /* Originate IPv4 Routes */ /* network4 10.10.10.0/24 { > Jeff> next-hop: 10.10.10.10 unicast: true multicast: true } */ > >> > Jeff> /* Originate IPv6 Routes */ /* network6 10:10:10:10::/64 { > Jeff> next-hop: 10:10:10:10:10:10:10:10 unicast: true multicast: > Jeff> true } */ } } > >> > Jeff> If someone could give me a hint to point me in the right > Jeff> direction as to what might be wrong with bind() I would be > Jeff> grateful. > >> > Jeff> Thanks, > >> > Jeff> Jeff > >> > Jeff> _______________________________________________ Xorp-users > Jeff> mailing list Xorp-users@xorp.org > Jeff> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > >> _______________________________________________ Xorp-users > >> mailing list Xorp-users@xorp.org > >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > >> > > > From jmorillo@ac.upc.edu Wed Jan 12 14:03:33 2005 From: jmorillo@ac.upc.edu (jmorillo@ac.upc.edu) Date: Wed, 12 Jan 2005 15:03:33 +0100 Subject: [Xorp-users] Problem starting XORP+User Click Message-ID: <1105538613.41e52e35cf6b3@www.ac.upc.es> Hello, I'm trying to use XORP in combination with User Level Click forwarding. When I run ./xorp_rtrmgr I get the following error message: [ 2005/01/12 14:47:07 ERROR xorp_fea:2593 LIBCOMM +499 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 13000): Connection refused [ 2005/01/12 14:47:07 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... Click is installed on /usr/local/bin. I didn't modify the xorp_fea_click_config_generator file (maybe it's necessary to do it), and my XORP configuration file is as follows: /* $XORP: xorp/rtrmgr/config.boot.sample,v 1.20 2004/12/17 06:03:18 pavlin Exp $ */ interfaces { interface eth1 { description: "data interface" enabled: true vif eth1 { enabled: true address 147.83.34.82 { prefix-length: 24 broadcast: 147.83.34.255 enabled: true } } } } fea { enable-unicast-forwarding4: true /* enable-unicast-forwarding6: true */ click { enabled: true /* * Note: If both kernel-click and user-click are enabled, then * typically kernel-click-config-generator-file and * user-click-config-generator-file should point to different * generator files. Otherwise, a single common generator * wouldn't know whether to generate configuration for kernel-level * Click or for user-level Click. */ kernel-click { enabled: false install-on-startup: false kernel-click-modules: "/path/to/proclikefs.o:/path/to/click.o" /* XXX: On FreeBSD we need only module click.ko */ /* kernel-click-modules: "/path/to/click.ko" */ mount-directory: "/click" kernel-click-config-generator-file: "/user/local/xorp/fea/xorp_fea_click_config_generator" } user-click { enabled: true command-file: "/usr/local/bin/click" /* * Note: don't add "-p " as an extra argument, because it * will conflict with the FEA's addition of the same argument. */ command-extra-arguments: "-R" command-execute-on-startup: true control-address: 127.0.0.1 control-socket-port: 13000 startup-config-file: "/dev/null" user-click-config-generator-file: "/root/XORP/xorp/fea/xorp_fea_click_config_generator" } } } protocols { static { route4 0.0.0.0/0 { nexthop: 147.83.34.2 metric: 0 } } } Maybe I'm missing anything? What means startup-config-file: "/dev/null"? Any help or suggestion will be welcome. Thanks in advance, julian From pavlin@icir.org Thu Jan 13 02:32:00 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 12 Jan 2005 18:32:00 -0800 Subject: [Xorp-users] Problem starting XORP+User Click In-Reply-To: Message from jmorillo@ac.upc.edu of "Wed, 12 Jan 2005 15:03:33 +0100." <1105538613.41e52e35cf6b3@www.ac.upc.es> Message-ID: <200501130232.j0D2W0hR015417@possum.icir.org> Julian, > I'm trying to use XORP in combination with User Level Click forwarding. > When I run ./xorp_rtrmgr I get the following error message: > > [ 2005/01/12 14:47:07 ERROR xorp_fea:2593 LIBCOMM +499 comm_sock.c > comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = > 127.0.0.1, remote_port = 13000): Connection refused > [ 2005/01/12 14:47:07 WARNING xorp_fea FEA ] Could not open user-level Click > socket: Connection refused. Trying again... > > Click is installed on /usr/local/bin. Does this message appears only 1-2 times, or does it happen a number of times? On startup, the FEA may have to wait a bit until the click process is ready and accepts connections on its control socket. In other words, if you see above messages just 1-2 times, then this is fine and you can ignore them. If however you see numerous messages as those above, and then ERROR "Could not open ..." error message (that error message should not contain the "Trying again..." text), then this is an error that needs to be tracked further. Admittably, it would be less confusing if you don't see any intermediate messages while the REA attempts to open the communication socket to Click. I will add this as a TODO entry. > Maybe I'm missing anything? What means startup-config-file: "/dev/null"? Any > help or suggestion will be welcome. On startup, the click binary expects "-f filename" as an argument to specify the startup configuration file to load. If you don't have a startup config file, then you should use an empty file. File "/dev/null" is just such empty file that can be used instead. Apparently, the click binary won't start listening for control connections if it wasn't started with the "-f filename" argument. Regards, Pavlin From atanu@ICSI.Berkeley.EDU Thu Jan 13 02:40:13 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Wed, 12 Jan 2005 18:40:13 -0800 Subject: [Xorp-users] Bind failed: Could not assign requested address In-Reply-To: Message from Jeff Krasky of "Tue, 11 Jan 2005 14:46:01 CST." <200501112046.j0BKk1kS014093@dingo.software.umn.edu> Message-ID: <24467.1105584013@tigger.icir.org> This problem has been logged as a bug. The error message should have been more useful and the BGP process shouldn't have exited. Atanu. >>>>> "Jeff" == Jeff Krasky writes: Jeff> Yes, that was it. Thank you. Jeff Jeff> On 10 Jan 2005, Atanu Ghosh wrote: >> Hi, >> >> Is there a chance that the "local-ip" statement in the >> configuration file does not match any of the interface addresses >> on your host? >> >> Atanu. >> >> >>>>> "Jeff" == Jeff Krasky writes: >> Jeff> I am getting the error when logged in as root when I run Jeff> ./xorp_rtrmgr Jeff >> Jeff> On 10 Jan 2005, Atanu Ghosh wrote: >> >> Hi, >> >> >> >> The port (179) that BGP is attempting to bind to is >> >> privileged. The router manager needs to be run as root. It is >> >> also necessary to run as root if you want to install any routes >> >> in the kernel. >> >> >> >> Atanu. >> >> >> >> >>>>> "Jeff" == Jeff Krasky writes: >> >> Jeff> Hi, I am trying to get Xorp running on a Linux machine that I Jeff> have. When I log in as root and run ./xorp_rtrmgr I get the Jeff> following: >> >> Jeff> [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 RTRMGR +134 Jeff> master_conf_tree.cc execute ] Changed modules: interfaces, Jeff> fea, rib, bgp [ 2005/01/10 16:23:59 INFO xorp_rtrmgr:3411 Jeff> RTRMGR +404 module_manager.cc run ] Running module: interfaces Jeff> (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 16:24:01 INFO Jeff> xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc run ] Running Jeff> module: fea (/home/jkrasky/xorp/fea/xorp_fea) [ 2005/01/10 Jeff> 16:24:07 INFO xorp_rtrmgr:3411 RTRMGR +404 module_manager.cc Jeff> run ] Running module: rib (/home/jkrasky/xorp/rib/xorp_rib) [ Jeff> 2005/01/10 16:24:09 INFO xorp_rtrmgr:3411 RTRMGR +404 Jeff> module_manager.cc run ] Running module: bgp Jeff> (/home/jkrasky/xorp/bgp/xorp_bgp) [ 2005/01/10 16:24:11 ERROR Jeff> xorp_bgp:3414 BGP +400 socket.cc connect_socket ] Bind failed: Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 FATAL Jeff> xorp_bgp:3414 BGP +67 socket.cc create_listener ] Bind failed: Jeff> Cannot assign requested address [ 2005/01/10 16:24:11 INFO Jeff> xorp_rtrmgr:3411 RTRMGR +550 module_manager.cc killed ] Module Jeff> abnormally killed: bgp [ 2005/01/10 16:24:11 ERROR Jeff> xorp_rtrmgr:3411 XRL +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender Jeff> died: end of file [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 Jeff> RTRMGR +763 task.cc execute_done ] 210 Transport failed [ Jeff> 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +1179 Jeff> task.cc task_fail ] Shutting down fatally wounded process Jeff> (bgp) [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 RTRMGR +540 Jeff> master_conf_tree.cc commit_pass2_done ] Commit failed: 210 Jeff> Transport failed [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 Jeff> RTRMGR +146 master_conf_tree.cc config_done ] Configuration Jeff> failed: 210 Transport failed [ 2005/01/10 16:24:11 INFO Jeff> xorp_rtrmgr:3411 RTRMGR +1372 task.cc run_task ] No more tasks Jeff> to run [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 Jeff> module_manager.cc terminate ] Terminating module: fea [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +216 Jeff> module_manager.cc terminate ] Terminating module: interfaces [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 Jeff> module_manager.cc terminate ] Killing module: interfaces (pid Jeff> = 3412) [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR Jeff> +216 module_manager.cc terminate ] Terminating module: rib [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +262 Jeff> module_manager.cc terminate ] Killing module: rib (pid = 3413) Jeff> [ 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 Jeff> module_manager.cc killed ] Module killed during shutdown: Jeff> interfaces [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL Jeff> +628 xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file [ Jeff> 2005/01/10 16:24:11 INFO xorp_rtrmgr:3411 RTRMGR +546 Jeff> module_manager.cc killed ] Module killed during shutdown: rib Jeff> [ 2005/01/10 16:24:11 ERROR xorp_rtrmgr:3411 XRL +628 Jeff> xrl_pf_stcp.cc die ] XrlPFSTCPSender died: end of file >> >> Jeff> Here is my config.boot file: >> >> Jeff> interfaces { interface eth0 { description: "data interface" Jeff> vif eth0 { address 172.16.1.150 { prefix-length: 32 broadcast: Jeff> 172.16.1.150 } } } } >> >> Jeff> fea { enable-unicast-forwarding4: true /* Jeff> enable-unicast-forwarding6: true */ } >> >> Jeff> protocols { bgp { bgp-id: 172.16.1.150 local-as: 33333 >> >> Jeff> peer 172.16.1.152 { local-ip: 172.16.1.152 as: 33334 next-hop: Jeff> 172.16.1.152 >> >> Jeff> local-port: 179 peer-port: 179 >> >> Jeff> /* holdtime: 120 */ /* enabled: true */ >> >> Jeff> /* Optionally enable other AFI/SAFI combinations */ /* Jeff> enable-ipv4-multicast */ >> >> Jeff> /* enable-ipv6-unicast */ /* enable-ipv6-multicast */ } >> >> Jeff> /* Originate IPv4 Routes */ /* network4 10.10.10.0/24 { Jeff> next-hop: 10.10.10.10 unicast: true multicast: true } */ >> >> Jeff> /* Originate IPv6 Routes */ /* network6 10:10:10:10::/64 { Jeff> next-hop: 10:10:10:10:10:10:10:10 unicast: true multicast: Jeff> true } */ } } >> >> Jeff> If someone could give me a hint to point me in the right Jeff> direction as to what might be wrong with bind() I would be Jeff> grateful. >> >> Jeff> Thanks, >> >> Jeff> Jeff >> >> Jeff> _______________________________________________ Xorp-users Jeff> mailing list Xorp-users@xorp.org Jeff> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> >> _______________________________________________ Xorp-users >> >> mailing list Xorp-users@xorp.org >> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> >> >> >> >> From kohler@CS.UCLA.EDU Thu Jan 13 04:12:42 2005 From: kohler@CS.UCLA.EDU (Eddie Kohler) Date: Wed, 12 Jan 2005 20:12:42 -0800 Subject: [Xorp-users] Problem starting XORP+User Click In-Reply-To: <200501130232.j0D2W0hR015417@possum.icir.org> References: <200501130232.j0D2W0hR015417@possum.icir.org> Message-ID: <5F2A4B5C-6519-11D9-B724-000A95A6D9BC@cs.ucla.edu> >> Maybe I'm missing anything? What means startup-config-file: >> "/dev/null"? Any >> help or suggestion will be welcome. > > On startup, the click binary expects "-f filename" as an argument to > specify the startup configuration file to load. If you don't have a > startup config file, then you should use an empty file. File > "/dev/null" is just such empty file that can be used instead. > Apparently, the click binary won't start listening for control > connections if it wasn't started with the "-f filename" argument. FYI, what's going on here is unless you supply a filename Click blocks & reads stdin. You can also say " -e '' " instead of -f /dev/null. Eddie From dondonc@asti.dost.gov.ph Fri Jan 14 14:52:00 2005 From: dondonc@asti.dost.gov.ph (Dondon Carlos) Date: Fri, 14 Jan 2005 22:52:00 +0800 Subject: [Xorp-users] a newbie's question about xorp Message-ID: <41E7DC90.4070005@asti.dost.gov.ph> Good morning, guys! I am installing the xorp for my Unidirectional Link router. I loaded the Free-BSD 4.10 in the box and I installed xorp. THe lan card I'm using has 4 interfaces and FreeBSD recognizes them as ste0, ste1,ste2 and ste3. THe ste0 interface points to the satellite link and the ste1 points to the LAN part of the network. I followed the instructions handed in to me. It includes installing net-snmp and gmake. I also created the xorp group using the command pw groupadd xorp -g 12000 I configured and installed the xorp then I made the config.boot. Here is the exact copy of the config.boot: interfaces { interface ste0 { description: "upstream interface" enabled: true default-system-config } interface ste1 { description: "downstream interface" enabled: true default-system-config } } plumbing { mfea4 { enabled: true interface ste0 { vif ste0 { enabled: true } } interface ste1 { vif ste1 { enabled: true } } interface register_vif { vif register_vif { enabled: true } } /*traceoptions { flag all { enabled: true } } */ } } protocols { igmp { enabled: true interface ste0 { vif ste0 { enabled: true } } interface ste1 { vif ste1 { enabled: true } } /*traceoptions { flag all { enabled: true } } } } protocols { pimsm4 { enabled: true interface ste0 { vif ste0 { enabled: true } } interface ste1 { vif ste1 { enabled: true } } interface register_vif { vif register_vif { enabled: true } } switch-to-spt-threshold { enabled: true interval-sec: 100 bytes: 102400 } } } protocols { fib2mrib { enabled: true } } After this I typed the command: /usr/local/xorp/bin/xorp_rtrmgr & and I received the error message, [.... ERROR xorp_rtrmgr:6354 RTRMGR +311 main_rtrmgr.cc run] rtrmgr shutting down due to init error: PARSE ERROR [Config File /usr/local/xorp/config.boot, line 2] No template found in template map; last symbol parsed was "ste0" Can anyone help me here? Thank you very much in advance. CHeers, Dondon From jmorillo@ac.upc.edu Fri Jan 14 08:44:26 2005 From: jmorillo@ac.upc.edu (=?iso-8859-1?q?Juli=E1n=20David=20=20Morillo=20Pozo?=) Date: Fri, 14 Jan 2005 09:44:26 +0100 Subject: [Xorp-users] XORP + User Click Message-ID: <200501140944.26412.jmorillo@ac.upc.edu> Hello, I have a simple XORP configuration file, that simply assigns an IP to the eth1 interface of my machine. If I run XORP with this configuration using the Linux kernel as forwarding path and then I add a default route via xorpsh, everything goes ok and I can ping any other machine. But if I do the same but enabling user-level click, I can add the default route in the same way (without any error message) but I cannot ping machines others than mine... what I'm missing? What's going wrong? Thanks in advance, -- ============================================= Julián David Morillo Pozo PhD Student - Computer Networking Group Department of Computer Architecture (DAC) Polytechnical University of Catalonia (UPC) Phone: +34-934017182 Fax: +34-934017055 URL: http://people.ac.upc.edu/jmorillo ============================================= From atanu@ICSI.Berkeley.EDU Fri Jan 14 20:03:31 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Fri, 14 Jan 2005 12:03:31 -0800 Subject: [Xorp-users] a newbie's question about xorp In-Reply-To: Message from Dondon Carlos of "Fri, 14 Jan 2005 22:52:00 +0800." <41E7DC90.4070005@asti.dost.gov.ph> Message-ID: <49855.1105733011@tigger.icir.org> Hi, I notice that in your config you open a comment "/*traceoptions {", which does not seem to get closed. Atanu. >>>>> "Dondon" == Dondon Carlos writes: Dondon> Good morning, guys! Dondon> I am installing the xorp for my Unidirectional Link router. I loaded Dondon> the Free-BSD 4.10 in the box and I installed xorp. THe lan card I'm Dondon> using has 4 interfaces and FreeBSD recognizes them as ste0, ste1,ste2 Dondon> and ste3. THe ste0 interface points to the satellite link and the ste1 Dondon> points to the LAN part of the network. I followed the instructions Dondon> handed in to me. It includes installing net-snmp and gmake. I also Dondon> created the xorp group using the command Dondon> pw groupadd xorp -g 12000 Dondon> I configured and installed the xorp then I made the config.boot. Dondon> Here is the exact copy of the config.boot: Dondon> interfaces { Dondon> interface ste0 { Dondon> description: "upstream interface" Dondon> enabled: true Dondon> default-system-config Dondon> } Dondon> interface ste1 { Dondon> description: "downstream interface" Dondon> enabled: true Dondon> default-system-config Dondon> } Dondon> } Dondon> plumbing { Dondon> mfea4 { Dondon> enabled: true Dondon> interface ste0 { Dondon> vif ste0 { Dondon> enabled: true Dondon> } Dondon> } Dondon> interface ste1 { Dondon> vif ste1 { Dondon> enabled: true Dondon> } Dondon> } Dondon> interface register_vif { Dondon> vif register_vif { Dondon> enabled: true Dondon> } Dondon> } Dondon> /*traceoptions { Dondon> flag all { Dondon> enabled: true Dondon> } Dondon> } */ Dondon> } Dondon> } Dondon> protocols { Dondon> igmp { Dondon> enabled: true Dondon> interface ste0 { Dondon> vif ste0 { Dondon> enabled: true Dondon> } Dondon> } Dondon> interface ste1 { Dondon> vif ste1 { Dondon> enabled: true Dondon> } Dondon> } Dondon> /*traceoptions { Dondon> flag all { Dondon> enabled: true Dondon> } Dondon> } Dondon> } Dondon> } Dondon> protocols { Dondon> pimsm4 { Dondon> enabled: true Dondon> interface ste0 { Dondon> vif ste0 { Dondon> enabled: true Dondon> } Dondon> } Dondon> interface ste1 { Dondon> vif ste1 { Dondon> enabled: true Dondon> } Dondon> } Dondon> interface register_vif { Dondon> vif register_vif { Dondon> enabled: true Dondon> } Dondon> } Dondon> switch-to-spt-threshold { Dondon> enabled: true Dondon> interval-sec: 100 Dondon> bytes: 102400 Dondon> } Dondon> } Dondon> } Dondon> protocols { Dondon> fib2mrib { Dondon> enabled: true Dondon> } Dondon> } Dondon> After this I typed the command: Dondon> /usr/local/xorp/bin/xorp_rtrmgr & Dondon> and I received the error message, Dondon> [.... ERROR xorp_rtrmgr:6354 RTRMGR +311 main_rtrmgr.cc run] rtrmgr Dondon> shutting down due to init error: PARSE ERROR [Config File Dondon> /usr/local/xorp/config.boot, line 2] No template found in template Dondon> map; last symbol parsed was "ste0" Dondon> Can anyone help me here? Thank you very much in advance. Dondon> CHeers, Dondon> Dondon Dondon> _______________________________________________ Dondon> Xorp-users mailing list Dondon> Xorp-users@xorp.org Dondon> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin@icir.org Fri Jan 14 21:02:29 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Fri, 14 Jan 2005 13:02:29 -0800 Subject: [Xorp-users] XORP + User Click In-Reply-To: Message from =?iso-8859-1?q?Juli=E1n=20David=20=20Morillo=20Pozo?= of "Fri, 14 Jan 2005 09:44:26 +0100." <200501140944.26412.jmorillo@ac.upc.edu> Message-ID: <200501142102.j0EL2TtA028631@possum.icir.org> > I have a simple XORP configuration file, that simply assigns an IP to the eth1 > interface of my machine. If I run XORP with this configuration using the > Linux kernel as forwarding path and then I add a default route via xorpsh, > everything goes ok and I can ping any other machine. > But if I do the same but enabling user-level click, I can add the default > route in the same way (without any error message) but I cannot ping machines > others than mine... what I'm missing? What's going wrong? I believe you see the above behavior because when you are running user-level Click, all add/delete routes from XORP go to the user-level Click only. In other words, the add/delete XORP routes are NOT added to the kernel. This was the intended design choice. Otherwise, we may end-up with mixing user-level and kernel-level forwarding, and the result may be confusing (at least). BTW, have you tried traceroute through your XORP+user-level-Click router? I guess when you try to run "ping" on your XORP+Click router, the outgoing packets from that host itself will attempt to go out of the box via the kernel IP stack, and are NOT picked-up by user-level Click. In your case you don't have a default forwarding entry in the kernel (see above), hence you cannot ping other machines. Myself I am not familiar enough with Click configurations to say whether it is possible to create user-level Click configuration that can pick-up the packets originated from the local host so they can be forwarded by user-level Click. Eddie? Thanks, Pavlin From zec@icir.org Fri Jan 14 22:13:00 2005 From: zec@icir.org (Marko Zec) Date: Fri, 14 Jan 2005 23:13:00 +0100 Subject: [Xorp-users] XORP + User Click In-Reply-To: <200501142102.j0EL2TtA028631@possum.icir.org> References: <200501142102.j0EL2TtA028631@possum.icir.org> Message-ID: <200501142313.00627.zec@icir.org> On Friday 14 January 2005 22:02, Pavlin Radoslavov wrote: ... > Myself I am not familiar enough with Click configurations to say > whether it is possible to create user-level Click configuration that > can pick-up the packets originated from the local host so they can > be forwarded by user-level Click. KernelTun() element could help in such scenarios, and should work for both receiving and sending packets from Click to the OS. Here's an example config (pretty much useless, though): rt :: LinearIPLookup( 192.168.200.200/30 2, 161.53.0.0/16 0, 10.0.0.0/8 1 ); kt :: KernelTun(10.1.2.3/24); kt -> rt; rt[0] -> Print("0") -> Discard; rt[1] -> Print("1") -> Discard; rt[2] -> Print("2") -> kt; At least on FreeBSD, this will automatically instantiate a "tun" network interface in the kernel, and any packets sent down this interface will then show up in Click. Hope this helps, Marko From pavlin@icir.org Fri Jan 14 22:45:59 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Fri, 14 Jan 2005 14:45:59 -0800 Subject: [Xorp-users] XORP + User Click In-Reply-To: Message from Marko Zec of "Fri, 14 Jan 2005 23:13:00 +0100." <200501142313.00627.zec@icir.org> Message-ID: <200501142245.j0EMjxuF029312@possum.icir.org> > On Friday 14 January 2005 22:02, Pavlin Radoslavov wrote: > ... > > Myself I am not familiar enough with Click configurations to say > > whether it is possible to create user-level Click configuration that > > can pick-up the packets originated from the local host so they can > > be forwarded by user-level Click. > > > KernelTun() element could help in such scenarios, and should work for > both receiving and sending packets from Click to the OS. Here's an > example config (pretty much useless, though): > > rt :: LinearIPLookup( > 192.168.200.200/30 2, > 161.53.0.0/16 0, > 10.0.0.0/8 1 > ); > > kt :: KernelTun(10.1.2.3/24); > > kt -> rt; > > rt[0] -> Print("0") -> Discard; > rt[1] -> Print("1") -> Discard; > rt[2] -> Print("2") -> kt; > > > At least on FreeBSD, this will automatically instantiate a "tun" network > interface in the kernel, and any packets sent down this interface will > then show up in Click. Thanks, that is useful to know it. Though, my question was slightly different. If the user uses the ping command on that host (as Julian did), then the ICMP packets originated by the ping command will be sent-down the IP stack of the OS, will be looked-up against the kernel forwarding table (and eventually throwed away if there is no matching forwarding entry). With your example above I understand that if somehow the user explicitly specifies that the outgoing ICMP ping packets are sent on the "tun" interface, then the outgoing ICMP ping packets will be forwarded properly by user-level Click. However, it doesn't seem that you can tell ping (at least the FreeBSD ping) to send the packets on a specific interface. Hence, even with the help of KernelTun, it looks like it is not possible to intercept all packets sent down to the IP stack (unless they are explicitly sent via the tun interface). If someone wants to do that, I believe the answer would be "use kernel-level Click". Thanks, Pavlin From zec@icir.org Sat Jan 15 00:19:19 2005 From: zec@icir.org (Marko Zec) Date: Sat, 15 Jan 2005 01:19:19 +0100 Subject: [Xorp-users] XORP + User Click In-Reply-To: <200501142245.j0EMjxuF029312@possum.icir.org> References: <200501142245.j0EMjxuF029312@possum.icir.org> Message-ID: <200501150119.19472.zec@icir.org> On Friday 14 January 2005 23:45, Pavlin Radoslavov wrote: > > On Friday 14 January 2005 22:02, Pavlin Radoslavov wrote: > > ... > > > > > Myself I am not familiar enough with Click configurations to say > > > whether it is possible to create user-level Click configuration > > > that can pick-up the packets originated from the local host so > > > they can be forwarded by user-level Click. > > > > KernelTun() element could help in such scenarios, and should work > > for both receiving and sending packets from Click to the OS. > > Here's an example config (pretty much useless, though): > > > > rt :: LinearIPLookup( > > 192.168.200.200/30 2, > > 161.53.0.0/16 0, > > 10.0.0.0/8 1 > > ); > > > > kt :: KernelTun(10.1.2.3/24); > > > > kt -> rt; > > > > rt[0] -> Print("0") -> Discard; > > rt[1] -> Print("1") -> Discard; > > rt[2] -> Print("2") -> kt; > > > > > > At least on FreeBSD, this will automatically instantiate a "tun" > > network interface in the kernel, and any packets sent down this > > interface will then show up in Click. > > Thanks, that is useful to know it. > Though, my question was slightly different. > > If the user uses the ping command on that host (as Julian did), > then the ICMP packets originated by the ping command will be > sent-down the IP stack of the OS, will be looked-up against the > kernel forwarding table (and eventually throwed away if there is no > matching forwarding entry). > > With your example above I understand that if somehow the user > explicitly specifies that the outgoing ICMP ping packets are sent on > the "tun" interface, then the outgoing ICMP ping packets will be > forwarded properly by user-level Click. > > However, it doesn't seem that you can tell ping (at least the > FreeBSD ping) to send the packets on a specific interface. > Hence, even with the help of KernelTun, it looks like it is not > possible to intercept all packets sent down to the IP stack (unless > they are explicitly sent via the tun interface). Agreed. Still, one could use policy-based routing, such as ipfw fwd rules, to force selected traffic to go down the "tun" device, regardles on what the kernel forwarding table has to say. Or alternatively use netgraph(4) to intercept outgoing packets at the ethernet layer and then loop them back to the host so that Click can fetch them via FromDevice(). However, those are really OS-specific hacks, rather then generic and portable solutions. > If someone wants to do that, I believe the answer would be > "use kernel-level Click". Yup, that would be the proper way. Cheers, Marko From kohler@icir.org Sat Jan 15 01:44:31 2005 From: kohler@icir.org (Eddie Kohler) Date: Fri, 14 Jan 2005 17:44:31 -0800 Subject: [Xorp-users] XORP + User Click In-Reply-To: <200501150119.19472.zec@icir.org> References: <200501142245.j0EMjxuF029312@possum.icir.org> <200501150119.19472.zec@icir.org> Message-ID: <41E8757F.2070709@icir.org> Marko is right. I'd expect that, if you wanted traffic to go through user-level Click, you'd use somehting like KernelTun, then make it the default route, clearing out all other entries. Eddie Marko Zec wrote: > On Friday 14 January 2005 23:45, Pavlin Radoslavov wrote: > >>>On Friday 14 January 2005 22:02, Pavlin Radoslavov wrote: >>>... >>> >>> >>>>Myself I am not familiar enough with Click configurations to say >>>>whether it is possible to create user-level Click configuration >>>>that can pick-up the packets originated from the local host so >>>>they can be forwarded by user-level Click. >>> >>>KernelTun() element could help in such scenarios, and should work >>>for both receiving and sending packets from Click to the OS. >>>Here's an example config (pretty much useless, though): >>> >>>rt :: LinearIPLookup( >>> 192.168.200.200/30 2, >>> 161.53.0.0/16 0, >>> 10.0.0.0/8 1 >>> ); >>> >>>kt :: KernelTun(10.1.2.3/24); >>> >>>kt -> rt; >>> >>>rt[0] -> Print("0") -> Discard; >>>rt[1] -> Print("1") -> Discard; >>>rt[2] -> Print("2") -> kt; >>> >>> >>>At least on FreeBSD, this will automatically instantiate a "tun" >>>network interface in the kernel, and any packets sent down this >>>interface will then show up in Click. >> >>Thanks, that is useful to know it. >>Though, my question was slightly different. >> >>If the user uses the ping command on that host (as Julian did), >>then the ICMP packets originated by the ping command will be >>sent-down the IP stack of the OS, will be looked-up against the >>kernel forwarding table (and eventually throwed away if there is no >>matching forwarding entry). >> >>With your example above I understand that if somehow the user >>explicitly specifies that the outgoing ICMP ping packets are sent on >>the "tun" interface, then the outgoing ICMP ping packets will be >>forwarded properly by user-level Click. >> >>However, it doesn't seem that you can tell ping (at least the >>FreeBSD ping) to send the packets on a specific interface. >>Hence, even with the help of KernelTun, it looks like it is not >>possible to intercept all packets sent down to the IP stack (unless >>they are explicitly sent via the tun interface). > > > > Agreed. Still, one could use policy-based routing, such as ipfw fwd > rules, to force selected traffic to go down the "tun" device, regardles > on what the kernel forwarding table has to say. Or alternatively use > netgraph(4) to intercept outgoing packets at the ethernet layer and > then loop them back to the host so that Click can fetch them via > FromDevice(). However, those are really OS-specific hacks, rather then > generic and portable solutions. > > > >>If someone wants to do that, I believe the answer would be >>"use kernel-level Click". > > > > Yup, that would be the proper way. > > Cheers, > > Marko > _______________________________________________ > Xorp-users mailing list > Xorp-users@xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From dondonc@asti.dost.gov.ph Sat Jan 15 02:24:13 2005 From: dondonc@asti.dost.gov.ph (Dondon Carlos) Date: Sat, 15 Jan 2005 10:24:13 +0800 Subject: [Xorp-users] a newbie's question about xorp In-Reply-To: <49855.1105733011@tigger.icir.org> References: <49855.1105733011@tigger.icir.org> Message-ID: <41E87ECD.2050400@asti.dost.gov.ph> Hi Atanu! Sorry but I forgot to put the extra '*/' in my mail. However, I checked the config in my UDLR and there is the */ to close the comment. I'm still wondering what possibly could go worng here? I still receive the same error message. Dondon Atanu Ghosh wrote: >Hi, > >I notice that in your config you open a comment "/*traceoptions {", >which does not seem to get closed. > > Atanu. > > > >>>>>>"Dondon" == Dondon Carlos writes: >>>>>> >>>>>> > > Dondon> Good morning, guys! > > Dondon> I am installing the xorp for my Unidirectional Link router. I loaded > Dondon> the Free-BSD 4.10 in the box and I installed xorp. THe lan card I'm > Dondon> using has 4 interfaces and FreeBSD recognizes them as ste0, ste1,ste2 > Dondon> and ste3. THe ste0 interface points to the satellite link and the ste1 > Dondon> points to the LAN part of the network. I followed the instructions > Dondon> handed in to me. It includes installing net-snmp and gmake. I also > Dondon> created the xorp group using the command > Dondon> pw groupadd xorp -g 12000 > Dondon> I configured and installed the xorp then I made the config.boot. > Dondon> Here is the exact copy of the config.boot: > Dondon> interfaces { > Dondon> interface ste0 { > Dondon> description: "upstream interface" > Dondon> enabled: true > Dondon> default-system-config > Dondon> } > Dondon> interface ste1 { > Dondon> description: "downstream interface" > Dondon> enabled: true > Dondon> default-system-config > Dondon> } > Dondon> } > Dondon> plumbing { > Dondon> mfea4 { > Dondon> enabled: true > Dondon> interface ste0 { > Dondon> vif ste0 { > Dondon> enabled: true > Dondon> } > Dondon> } > Dondon> interface ste1 { > Dondon> vif ste1 { > Dondon> enabled: true > Dondon> } > Dondon> } > Dondon> interface register_vif { > Dondon> vif register_vif { > Dondon> enabled: true > Dondon> } > Dondon> } > Dondon> /*traceoptions { > Dondon> flag all { > Dondon> enabled: true > Dondon> } > Dondon> } */ > Dondon> } > Dondon> } > Dondon> protocols { > Dondon> igmp { > Dondon> enabled: true > Dondon> interface ste0 { > Dondon> vif ste0 { > Dondon> enabled: true > Dondon> } > Dondon> } > Dondon> interface ste1 { > Dondon> vif ste1 { > Dondon> enabled: true > Dondon> } > Dondon> } > Dondon> /*traceoptions { > Dondon> flag all { > Dondon> enabled: true > Dondon> } > Dondon> } > Dondon> } > Dondon> } > Dondon> protocols { > Dondon> pimsm4 { > Dondon> enabled: true > Dondon> interface ste0 { > Dondon> vif ste0 { > Dondon> enabled: true > Dondon> } > Dondon> } > Dondon> interface ste1 { > Dondon> vif ste1 { > Dondon> enabled: true > Dondon> } > Dondon> } > Dondon> interface register_vif { > Dondon> vif register_vif { > Dondon> enabled: true > Dondon> } > Dondon> } > Dondon> switch-to-spt-threshold { > Dondon> enabled: true > Dondon> interval-sec: 100 > Dondon> bytes: 102400 > Dondon> } > Dondon> } > Dondon> } > Dondon> protocols { > Dondon> fib2mrib { > Dondon> enabled: true > Dondon> } > Dondon> } > > Dondon> After this I typed the command: > Dondon> /usr/local/xorp/bin/xorp_rtrmgr & > > Dondon> and I received the error message, > > Dondon> [.... ERROR xorp_rtrmgr:6354 RTRMGR +311 main_rtrmgr.cc run] rtrmgr > Dondon> shutting down due to init error: PARSE ERROR [Config File > Dondon> /usr/local/xorp/config.boot, line 2] No template found in template > Dondon> map; last symbol parsed was "ste0" > > Dondon> Can anyone help me here? Thank you very much in advance. > > Dondon> CHeers, > Dondon> Dondon > > > Dondon> _______________________________________________ > Dondon> Xorp-users mailing list > Dondon> Xorp-users@xorp.org > Dondon> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > From pavlin@icir.org Sat Jan 15 02:29:39 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Fri, 14 Jan 2005 18:29:39 -0800 Subject: [Xorp-users] a newbie's question about xorp In-Reply-To: Message from Dondon Carlos of "Sat, 15 Jan 2005 10:24:13 +0800." <41E87ECD.2050400@asti.dost.gov.ph> Message-ID: <200501150229.j0F2Td0B031114@possum.icir.org> Dondon, > Sorry but I forgot to put the extra '*/' in my mail. However, I checked > the config in my UDLR and there is the */ to close the comment. I'm > still wondering what possibly could go worng here? I still receive the > same error message. Please verify that you have */ in both places where you have /*traceoptions Also, note that you cannot have nested comments, hence please verify that too. Regards, Pavlin > > Dondon > > Atanu Ghosh wrote: > > >Hi, > > > >I notice that in your config you open a comment "/*traceoptions {", > >which does not seem to get closed. > > > > Atanu. > > > > > > > >>>>>>"Dondon" == Dondon Carlos writes: > >>>>>> > >>>>>> > > > > Dondon> Good morning, guys! > > > > Dondon> I am installing the xorp for my Unidirectional Link router. I loaded > > Dondon> the Free-BSD 4.10 in the box and I installed xorp. THe lan card I'm > > Dondon> using has 4 interfaces and FreeBSD recognizes them as ste0, ste1,ste2 > > Dondon> and ste3. THe ste0 interface points to the satellite link and the ste1 > > Dondon> points to the LAN part of the network. I followed the instructions > > Dondon> handed in to me. It includes installing net-snmp and gmake. I also > > Dondon> created the xorp group using the command > > Dondon> pw groupadd xorp -g 12000 > > Dondon> I configured and installed the xorp then I made the config.boot. > > Dondon> Here is the exact copy of the config.boot: > > Dondon> interfaces { > > Dondon> interface ste0 { > > Dondon> description: "upstream interface" > > Dondon> enabled: true > > Dondon> default-system-config > > Dondon> } > > Dondon> interface ste1 { > > Dondon> description: "downstream interface" > > Dondon> enabled: true > > Dondon> default-system-config > > Dondon> } > > Dondon> } > > Dondon> plumbing { > > Dondon> mfea4 { > > Dondon> enabled: true > > Dondon> interface ste0 { > > Dondon> vif ste0 { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > Dondon> interface ste1 { > > Dondon> vif ste1 { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > Dondon> interface register_vif { > > Dondon> vif register_vif { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > Dondon> /*traceoptions { > > Dondon> flag all { > > Dondon> enabled: true > > Dondon> } > > Dondon> } */ > > Dondon> } > > Dondon> } > > Dondon> protocols { > > Dondon> igmp { > > Dondon> enabled: true > > Dondon> interface ste0 { > > Dondon> vif ste0 { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > Dondon> interface ste1 { > > Dondon> vif ste1 { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > Dondon> /*traceoptions { > > Dondon> flag all { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > Dondon> } > > Dondon> } > > Dondon> protocols { > > Dondon> pimsm4 { > > Dondon> enabled: true > > Dondon> interface ste0 { > > Dondon> vif ste0 { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > Dondon> interface ste1 { > > Dondon> vif ste1 { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > Dondon> interface register_vif { > > Dondon> vif register_vif { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > Dondon> switch-to-spt-threshold { > > Dondon> enabled: true > > Dondon> interval-sec: 100 > > Dondon> bytes: 102400 > > Dondon> } > > Dondon> } > > Dondon> } > > Dondon> protocols { > > Dondon> fib2mrib { > > Dondon> enabled: true > > Dondon> } > > Dondon> } > > > > Dondon> After this I typed the command: > > Dondon> /usr/local/xorp/bin/xorp_rtrmgr & > > > > Dondon> and I received the error message, > > > > Dondon> [.... ERROR xorp_rtrmgr:6354 RTRMGR +311 main_rtrmgr.cc run] rtrmgr > > Dondon> shutting down due to init error: PARSE ERROR [Config File > > Dondon> /usr/local/xorp/config.boot, line 2] No template found in template > > Dondon> map; last symbol parsed was "ste0" > > > > Dondon> Can anyone help me here? Thank you very much in advance. > > > > Dondon> CHeers, > > Dondon> Dondon > > > > > > Dondon> _______________________________________________ > > Dondon> Xorp-users mailing list > > Dondon> Xorp-users@xorp.org > > Dondon> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users@xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From dondonc@asti.dost.gov.ph Sat Jan 15 03:42:23 2005 From: dondonc@asti.dost.gov.ph (Dondon Carlos) Date: Sat, 15 Jan 2005 11:42:23 +0800 Subject: [Xorp-users] a newbie's question about xorp In-Reply-To: <200501150229.j0F2Td0B031114@possum.icir.org> References: <200501150229.j0F2Td0B031114@possum.icir.org> Message-ID: <41E8911F.1010909@asti.dost.gov.ph> thanks pavlin! hmmm....what i did was just to remove the comments so i will not be bothered by them anymore. i tried to run xorp_rtrmgr again and i still received the same error message... i actually don't know where to debug the problem. cheers, Dondon Pavlin Radoslavov wrote: >Dondon, > > > >>Sorry but I forgot to put the extra '*/' in my mail. However, I checked >>the config in my UDLR and there is the */ to close the comment. I'm >>still wondering what possibly could go worng here? I still receive the >>same error message. >> >> > >Please verify that you have */ in both places where you have >/*traceoptions > >Also, note that you cannot have nested comments, hence please verify >that too. > >Regards, >Pavlin > > > >>Dondon >> >>Atanu Ghosh wrote: >> >> >> >>>Hi, >>> >>>I notice that in your config you open a comment "/*traceoptions {", >>>which does not seem to get closed. >>> >>> Atanu. >>> >>> >>> >>> >>> >>>>>>>>"Dondon" == Dondon Carlos writes: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>> Dondon> Good morning, guys! >>> >>> Dondon> I am installing the xorp for my Unidirectional Link router. I loaded >>> Dondon> the Free-BSD 4.10 in the box and I installed xorp. THe lan card I'm >>> Dondon> using has 4 interfaces and FreeBSD recognizes them as ste0, ste1,ste2 >>> Dondon> and ste3. THe ste0 interface points to the satellite link and the ste1 >>> Dondon> points to the LAN part of the network. I followed the instructions >>> Dondon> handed in to me. It includes installing net-snmp and gmake. I also >>> Dondon> created the xorp group using the command >>> Dondon> pw groupadd xorp -g 12000 >>> Dondon> I configured and installed the xorp then I made the config.boot. >>> Dondon> Here is the exact copy of the config.boot: >>> Dondon> interfaces { >>> Dondon> interface ste0 { >>> Dondon> description: "upstream interface" >>> Dondon> enabled: true >>> Dondon> default-system-config >>> Dondon> } >>> Dondon> interface ste1 { >>> Dondon> description: "downstream interface" >>> Dondon> enabled: true >>> Dondon> default-system-config >>> Dondon> } >>> Dondon> } >>> Dondon> plumbing { >>> Dondon> mfea4 { >>> Dondon> enabled: true >>> Dondon> interface ste0 { >>> Dondon> vif ste0 { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> Dondon> interface ste1 { >>> Dondon> vif ste1 { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> Dondon> interface register_vif { >>> Dondon> vif register_vif { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> Dondon> /*traceoptions { >>> Dondon> flag all { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } */ >>> Dondon> } >>> Dondon> } >>> Dondon> protocols { >>> Dondon> igmp { >>> Dondon> enabled: true >>> Dondon> interface ste0 { >>> Dondon> vif ste0 { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> Dondon> interface ste1 { >>> Dondon> vif ste1 { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> Dondon> /*traceoptions { >>> Dondon> flag all { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> Dondon> } >>> Dondon> } >>> Dondon> protocols { >>> Dondon> pimsm4 { >>> Dondon> enabled: true >>> Dondon> interface ste0 { >>> Dondon> vif ste0 { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> Dondon> interface ste1 { >>> Dondon> vif ste1 { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> Dondon> interface register_vif { >>> Dondon> vif register_vif { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> Dondon> switch-to-spt-threshold { >>> Dondon> enabled: true >>> Dondon> interval-sec: 100 >>> Dondon> bytes: 102400 >>> Dondon> } >>> Dondon> } >>> Dondon> } >>> Dondon> protocols { >>> Dondon> fib2mrib { >>> Dondon> enabled: true >>> Dondon> } >>> Dondon> } >>> >>> Dondon> After this I typed the command: >>> Dondon> /usr/local/xorp/bin/xorp_rtrmgr & >>> >>> Dondon> and I received the error message, >>> >>> Dondon> [.... ERROR xorp_rtrmgr:6354 RTRMGR +311 main_rtrmgr.cc run] rtrmgr >>> Dondon> shutting down due to init error: PARSE ERROR [Config File >>> Dondon> /usr/local/xorp/config.boot, line 2] No template found in template >>> Dondon> map; last symbol parsed was "ste0" >>> >>> Dondon> Can anyone help me here? Thank you very much in advance. >>> >>> Dondon> CHeers, >>> Dondon> Dondon >>> >>> >>> Dondon> _______________________________________________ >>> Dondon> Xorp-users mailing list >>> Dondon> Xorp-users@xorp.org >>> Dondon> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >>> >>> >>> >>> >>> >>_______________________________________________ >>Xorp-users mailing list >>Xorp-users@xorp.org >>http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> >> > > > > From pavlin@icir.org Sat Jan 15 03:57:37 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Fri, 14 Jan 2005 19:57:37 -0800 Subject: [Xorp-users] a newbie's question about xorp In-Reply-To: Message from Dondon Carlos of "Sat, 15 Jan 2005 11:42:23 +0800." <41E8911F.1010909@asti.dost.gov.ph> Message-ID: <200501150357.j0F3vbOt031913@possum.icir.org> > thanks pavlin! > > hmmm....what i did was just to remove the comments so i will not be > bothered by them anymore. i tried to run xorp_rtrmgr again and i still > received the same error message... > > i actually don't know where to debug the problem. Hmmm, are you sure you are modifying the correct config file? You may be modifying one config file, and the rtrmgr may be reading a default config file located somewhere else. Here is what I did: 1. I copied your original config file, and removed all /* and */ 2. I started the rtrmgr by explicitly specifying the config file, and by specifying verbose output: ./xorp_rtrmgr -b my_config.boot -v In my test I didn't see the error you had, so make sure that the rtrmgr is actually started with the correct config file. The first 6 lines should contain info about the boot file location, the directory with the template files, etc, so make sure this info is correct. E.g., make sure that the directory with the template files doesn't point to a location to some old files. Regards, Pavlin From M.Handley@cs.ucl.ac.uk Sat Jan 15 12:20:17 2005 From: M.Handley@cs.ucl.ac.uk (Mark Handley) Date: Sat, 15 Jan 2005 12:20:17 +0000 Subject: [Xorp-users] a newbie's question about xorp In-Reply-To: Your message of "Sat, 15 Jan 2005 10:24:13 +0800." <41E87ECD.2050400@asti.dost.gov.ph> Message-ID: <9512.1105791617@vulture.xorp.org> >Sorry but I forgot to put the extra '*/' in my mail. However, I checked >the config in my UDLR and there is the */ to close the comment. I'm >still wondering what possibly could go worng here? I still receive the >same error message. It is possible that there is no interface.tp files in the place that the rtrmgr is searching for configuration templates. If this was the case, then rtrmgr would not know about the interface keyword. If you're running out of the compilation directory, this shouldn't be a problem if you've got a full XORP checkout. If you're running from an installed directory, then we'd need to know that rtrmgr is searching the right place. You should be able to run something like this to check: vulture.xorp.org: ./xorp_rtrmgr -v -n -b config.boot [ 2005/01/15 12:18:30 TRACE xorp_rtrmgr RTRMGR ] Boot file := config.boot [ 2005/01/15 12:18:30 TRACE xorp_rtrmgr RTRMGR ] Templates directory := /home/vulture/u0/mjh/xorp/xorp/etc/templates [ 2005/01/15 12:18:30 TRACE xorp_rtrmgr RTRMGR ] Xrl targets directory := /home/vulture/u0/mjh/xorp/xorp/xrl/targets [ 2005/01/15 12:18:30 TRACE xorp_rtrmgr RTRMGR ] Execute Xrls := false .... Then check that the templates directory that is being searched does actually contain a reasonable version of interfaces.tp Cheers, Mark From dondonc@asti.dost.gov.ph Mon Jan 17 03:47:47 2005 From: dondonc@asti.dost.gov.ph (Dondon Carlos) Date: Mon, 17 Jan 2005 11:47:47 +0800 Subject: [Xorp-users] a newbie's question about xorp In-Reply-To: <9512.1105791617@vulture.xorp.org> References: <9512.1105791617@vulture.xorp.org> Message-ID: <41EB3563.1020108@asti.dost.gov.ph> Thanks guys! It was a directory problem. I checked them and I got them running this morning. Thank you very much! CHeers, Dondon Mark Handley wrote: >>Sorry but I forgot to put the extra '*/' in my mail. However, I checked >>the config in my UDLR and there is the */ to close the comment. I'm >>still wondering what possibly could go worng here? I still receive the >>same error message. >> >> > >It is possible that there is no interface.tp files in the place that >the rtrmgr is searching for configuration templates. If this was the >case, then rtrmgr would not know about the interface keyword. > >If you're running out of the compilation directory, this shouldn't be >a problem if you've got a full XORP checkout. If you're running from >an installed directory, then we'd need to know that rtrmgr is >searching the right place. > >You should be able to run something like this to check: > >vulture.xorp.org: ./xorp_rtrmgr -v -n -b config.boot >[ 2005/01/15 12:18:30 TRACE xorp_rtrmgr RTRMGR ] Boot file := config.boot >[ 2005/01/15 12:18:30 TRACE xorp_rtrmgr RTRMGR ] Templates directory := /home/vulture/u0/mjh/xorp/xorp/etc/templates >[ 2005/01/15 12:18:30 TRACE xorp_rtrmgr RTRMGR ] Xrl targets directory := /home/vulture/u0/mjh/xorp/xorp/xrl/targets >[ 2005/01/15 12:18:30 TRACE xorp_rtrmgr RTRMGR ] Execute Xrls := false >.... > >Then check that the templates directory that is being searched does >actually contain a reasonable version of interfaces.tp > >Cheers, > Mark > > > From rafael.guimaraes@ac.upc.edu Wed Jan 19 17:58:19 2005 From: rafael.guimaraes@ac.upc.edu (Rafael Paoliello Guimaraes) Date: Wed, 19 Jan 2005 18:58:19 +0100 Subject: [Xorp-users] Using kernel-level click and XORP Message-ID: <41EE9FBB.70305@ac.upc.edu> Hello, Sometime ago, somebody said here that click in the user-level mode would only route packets that are beeing forwarded by the node. This means that packets generated by the node itself go directly through the IP stack to the linux kernel forwarding table. In order to have these packets forwarded by click, there were two possibilities: using the KernelTun() element or using click in the kernel-level mode. Well, I tried the second choice and it doesn't seem to work. In the scenario below, node B has kernel-level click+XORP installed and I removed all routes from the linux forwarding table to guarantee packets are not routed through linux. In this case I can ping from A to C, but I can't ping from B to C. A - B - C Shouldn't this work? Should I explicitly configure this behavior somewhere? Cheers, -- =========================================== Rafael Paoliello Guimaraes PhD Student - Computer Networking Group Department of Computer Architecture (DAC) Polytechnic University of Catalonia (UPC) Phone: +34-934017187 Fax: +34-934017055 URL: http://people.ac.upc.es/rpaoliel =========================================== From pavlin@icir.org Wed Jan 19 23:52:00 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 19 Jan 2005 15:52:00 -0800 Subject: [Xorp-users] Using kernel-level click and XORP In-Reply-To: Message from Rafael Paoliello Guimaraes of "Wed, 19 Jan 2005 18:58:19 +0100." <41EE9FBB.70305@ac.upc.edu> Message-ID: <200501192352.j0JNq0kv059003@possum.icir.org> > Sometime ago, somebody said here that click in the user-level mode would > only route packets that are beeing forwarded by the node. This means > that packets generated by the node itself go directly through the IP > stack to the linux kernel forwarding table. In order to have these > packets forwarded by click, there were two possibilities: using the > KernelTun() element or using click in the kernel-level mode. > > Well, I tried the second choice and it doesn't seem to work. In the > scenario below, node B has kernel-level click+XORP installed and I > removed all routes from the linux forwarding table to guarantee packets > are not routed through linux. In this case I can ping from A to C, but I > can't ping from B to C. > > A - B - C > > Shouldn't this work? Should I explicitly configure this behavior somewhere? It won't work by the default Click configuration generated by XORP. I guess the reason is because the packets originated by the host are processed first by the host IP stack. Hence, if you remove all forwarding entries from your kernel, the outgoing packets won't be able to leave the IP stack. If the packet passes through the host IP stack, then you need something in the Click configuration to "pick-up" the packet and pass it through the Click IP stack. I guess what you need there is the FromHost Click element (see http://www.pdos.lcs.mit.edu/click/doc/FromHost.n.html), and at the same time you may have to add the appropriate forwarding entry (e.g., 0.0.0.0/0 in addition to the entry automatically added by FromHost) to your kernel that points to the fake interface created by FromHost. Eddie and Marko, please correct me if I am missing something. In general, dealing with this goes beyond the scope of XORP, so you have to modify the sample fea/xorp_fea_click_config_generator script for your own needs. On the other hand, if you don't really need the packets originated by the host to go through the Click configuration, then just don't delete the routes for the directly-connected subnets, and the ping from B to C should work. Regards, Pavlin From pavlin@icir.org Thu Jan 20 01:25:09 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Wed, 19 Jan 2005 17:25:09 -0800 Subject: [Xorp-users] Using kernel-level click and XORP In-Reply-To: Message from Pavlin Radoslavov of "Wed, 19 Jan 2005 15:52:00 PST." <200501192352.j0JNq0kv059003@possum.icir.org> Message-ID: <200501200125.j0K1P9Fv090184@possum.icir.org> > > Sometime ago, somebody said here that click in the user-level mode would > > only route packets that are beeing forwarded by the node. This means > > that packets generated by the node itself go directly through the IP > > stack to the linux kernel forwarding table. In order to have these > > packets forwarded by click, there were two possibilities: using the > > KernelTun() element or using click in the kernel-level mode. > > > > Well, I tried the second choice and it doesn't seem to work. In the > > scenario below, node B has kernel-level click+XORP installed and I > > removed all routes from the linux forwarding table to guarantee packets > > are not routed through linux. In this case I can ping from A to C, but I > > can't ping from B to C. > > > > A - B - C > > > > Shouldn't this work? Should I explicitly configure this behavior somewhere? > > It won't work by the default Click configuration generated by XORP. > I guess the reason is because the packets originated by the host > are processed first by the host IP stack. > Hence, if you remove all forwarding entries from your > kernel, the outgoing packets won't be able to leave the IP stack. > > If the packet passes through the host IP stack, then you need > something in the Click configuration to "pick-up" the packet and > pass it through the Click IP stack. > I guess what you need there is the FromHost Click element > (see http://www.pdos.lcs.mit.edu/click/doc/FromHost.n.html), and at > the same time you may have to add the appropriate forwarding entry > (e.g., 0.0.0.0/0 in addition to the entry automatically added by > FromHost) to your kernel that points to the fake interface created > by FromHost. > Eddie and Marko, please correct me if I am missing something. > > In general, dealing with this goes beyond the scope of XORP, > so you have to modify the sample fea/xorp_fea_click_config_generator > script for your own needs. > > On the other hand, if you don't really need the packets originated > by the host to go through the Click configuration, then just don't > delete the routes for the directly-connected subnets, and the ping > from B to C should work. While on the subject. As you may noticed already, if Click is enabled, all XORP routes are added to Click (only). If you want those routes to be added to the system kernel as well, now there is a new configuration switch: .... click { .... duplicate-routes-to-kernel: false .... } Its default value is false (i.e., the routes will not be added to the system kernel). Regards, Pavlin From videoip videoip Fri Jan 21 17:20:57 2005 From: videoip videoip (videoip videoip) Date: Fri, 21 Jan 2005 15:20:57 -0200 Subject: [Xorp-users] Newbie: trouble getting XORP started Message-ID: <5947ea5305012109204f197eeb@mail.gmail.com> Hi, I´m trying to run XORP under Mandrake Linux and I get the following errors and warnings: [ 2005/01/21 04:40:15 ERROR xorp_fea:2568 FEA +565 fticonfig.cc unicast_forward ing_enabled6 ] Cannot open file /proc/sys/net/ipv6/conf/all/forwarding for readi ng: No such file or directory [ 2005/01/21 04:40:15 FATAL xorp_fea:2568 FEA +77 fticonfig.cc FtiConfig ] Cann [ 2005/01/21 04:40:16 WARNING xorp_rtrmgr:2567 XrlFinderTarget +406 finder_base I´ve read the configuration manual but it didn´t help me too much. If there´s anyone out there kind enough to give a look at my config.boot, I would really appreciate it. Thanks a lot. --------------------------------------------------------------------------------------------------- /* CONFIG.BOOT */ interfaces { interface eth0 { description: "Salida a red 0" enabled: true default-system-config } interface eth1 { description: "Salida a red 1" enabled: true default-system-config } } plumbing { mfea4 { enabled: true interface eth0 { vif eth0 { enabled: true } } interface eth1 { vif eth1 { enabled: true } } interface register_vif { vif register_vif { enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { igmp { enabled: true interface eth0 { vif eth0 { enabled: true } } interface eth1 { vif eth1 { enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { pimsm4 { enabled: true interface eth0 { vif eth0 { enabled: true } } interface eth1 { vif eth1 { enabled: true } } interface register_vif { vif register_vif { enabled: true } } static-rps { rp 192.168.0.3 { group-prefix 224.0.0.0/4 { } } } bootstrap { enabled: true cand-bsr { scope-zone 224.0.0.0/4 { cand-bsr-by-vif-name: "eth0" bsr-priority: 1 hash-mask-len: 30 } } cand-rp { group-prefix 224.0.0.0/4 { cand-rp-by-vif-name: "eth0" rp-priority: 192 rp-holdtime: 150 } } } switch-to-spt-threshold { enabled: true interval-sec: 100 bytes: 102400 } traceoptions { flag all { enabled: true } } } } protocols { fib2mrib { enabled: true } } From jmorillo@ac.upc.edu Fri Jan 21 18:42:04 2005 From: jmorillo@ac.upc.edu (=?iso-8859-1?q?Juli=E1n=20David=20=20Morillo=20Pozo?=) Date: Fri, 21 Jan 2005 19:42:04 +0100 Subject: [Xorp-users] Newbie: trouble getting XORP started In-Reply-To: <5947ea5305012109204f197eeb@mail.gmail.com> References: <5947ea5305012109204f197eeb@mail.gmail.com> Message-ID: <200501211942.04763.jmorillo@ac.upc.edu> Hi, I think that what is happening is that XORP is trying to access /proc/sys/net/ipv6/conf/all/forwarding file for reading and you need root priviliges for doing it. I hope this would help you. El Viernes, 21 de Enero de 2005 18:20, videoip videoip escribió: > Hi, I´m trying to run XORP under Mandrake Linux and I get the > following errors and warnings: > > [ 2005/01/21 04:40:15 ERROR xorp_fea:2568 FEA +565 fticonfig.cc > unicast_forward ing_enabled6 ] Cannot open file > /proc/sys/net/ipv6/conf/all/forwarding for readi ng: No such file or > directory > [ 2005/01/21 04:40:15 FATAL xorp_fea:2568 FEA +77 fticonfig.cc FtiConfig ] > Cann [ 2005/01/21 04:40:16 WARNING xorp_rtrmgr:2567 XrlFinderTarget +406 > finder_base > > I´ve read the configuration manual but it didn´t help me too much. > If there´s anyone out there kind enough to give a look at my > config.boot, I would really appreciate it. Thanks a lot. > > --------------------------------------------------------------------------- >------------------------ > > /* CONFIG.BOOT */ > > interfaces { > interface eth0 { > description: "Salida a red 0" > enabled: true > default-system-config > } > interface eth1 { > description: "Salida a red 1" > enabled: true > default-system-config > } > } > > plumbing { > mfea4 { > enabled: true > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth1 { > vif eth1 { > enabled: true > } > } > interface register_vif { > vif register_vif { > enabled: true > } > } > traceoptions { > flag all { > enabled: true > } > } > } > } > > protocols { > igmp { > enabled: true > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth1 { > vif eth1 { > enabled: true > } > } > traceoptions { > flag all { > enabled: true > } > } > } > } > > protocols { > pimsm4 { > enabled: true > interface eth0 { > vif eth0 { > enabled: true > } > } > interface eth1 { > vif eth1 { > enabled: true > } > } > interface register_vif { > vif register_vif { > enabled: true > } > } > static-rps { > rp 192.168.0.3 { > group-prefix 224.0.0.0/4 { > } > } > } > > bootstrap { > enabled: true > cand-bsr { > scope-zone 224.0.0.0/4 { > cand-bsr-by-vif-name: "eth0" > bsr-priority: 1 > hash-mask-len: 30 > } > } > > cand-rp { > group-prefix 224.0.0.0/4 { > cand-rp-by-vif-name: "eth0" > rp-priority: 192 > rp-holdtime: 150 > } > } > } > > switch-to-spt-threshold { > enabled: true > interval-sec: 100 > bytes: 102400 > } > > traceoptions { > flag all { > enabled: true > } > } > } > } > > > protocols { > fib2mrib { > enabled: true > } > } > > _______________________________________________ > Xorp-users mailing list > Xorp-users@xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- ============================================= Julián David Morillo Pozo PhD Student - Computer Networking Group Department of Computer Architecture (DAC) Polytechnical University of Catalonia (UPC) Phone: +34-934017182 Fax: +34-934017055 URL: http://people.ac.upc.edu/jmorillo ============================================= From rafael.guimaraes@ac.upc.edu Fri Jan 21 19:06:08 2005 From: rafael.guimaraes@ac.upc.edu (Rafael Paoliello Guimaraes) Date: Fri, 21 Jan 2005 20:06:08 +0100 Subject: [Xorp-users] Click configuration generator on XORP Message-ID: <41F152A0.30409@ac.upc.edu> Hello, I was taking a look at the configuration file generated by XORP to be used in Click and there is a point that I didn't really understand. Whenever an interface receives an ARP Reply, makes n+1 copies of it (through the Tee element) and send one copy for each of the n interfaces (in fact to their ARPQuerier element) and 1 copy to the host (in the case that click is running in user-level, this last ARP reply is discarded). Why does an ARP reply need to be sent to the ARPQuerier of other interfaces? Is there any case where a packet may be waiting an ARP reply to be sent through an interface and this ARP reply comes from another interface? Am I missing something? Best regards, -- =========================================== Rafael Paoliello Guimaraes PhD Student - Computer Networking Group Department of Computer Architecture (DAC) Polytechnic University of Catalonia (UPC) Phone: +34-934017187 Fax: +34-934017055 URL: http://people.ac.upc.es/rpaoliel =========================================== From bms@spc.org Fri Jan 21 21:28:25 2005 From: bms@spc.org (Bruce M Simpson) Date: Fri, 21 Jan 2005 21:28:25 +0000 Subject: [Xorp-users] Click configuration generator on XORP In-Reply-To: <41F152A0.30409@ac.upc.edu> References: <41F152A0.30409@ac.upc.edu> Message-ID: <20050121212825.GG64596@dhcp120.icir.org> On Fri, Jan 21, 2005 at 08:06:08PM +0100, Rafael Paoliello Guimaraes wrote: > Why does an ARP reply need to be sent to the ARPQuerier of other > interfaces? Is there any case where a packet may be waiting an ARP reply > to be sent through an interface and this ARP reply comes from another > interface? Am I missing something? I'm not familiar with what Click does, but the most likely scenario I can think of is Proxy ARP, however the behaviour you describe is also possible. BMS From pavlin@icir.org Sat Jan 22 11:29:37 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Sat, 22 Jan 2005 03:29:37 -0800 Subject: [Xorp-users] Click configuration generator on XORP In-Reply-To: Message from Rafael Paoliello Guimaraes of "Fri, 21 Jan 2005 20:06:08 +0100." <41F152A0.30409@ac.upc.edu> Message-ID: <200501221129.j0MBTbwb000419@possum.icir.org> > I was taking a look at the configuration file generated by XORP to be > used in Click and there is a point that I didn't really understand. > > Whenever an interface receives an ARP Reply, makes n+1 copies of it > (through the Tee element) and send one copy for each of the n interfaces > (in fact to their ARPQuerier element) and 1 copy to the host (in the > case that click is running in user-level, this last ARP reply is > discarded). > > Why does an ARP reply need to be sent to the ARPQuerier of other > interfaces? Is there any case where a packet may be waiting an ARP reply > to be sent through an interface and this ARP reply comes from another > interface? Am I missing something? Rafael, FYI, the Click config generated by XORP is based on the config generated by the click/conf/make-ip-conf.pl script (from the Click distribution). Sorry, I don't know why that Click config looks the way it is, but you may try to ask on the Click mailing list. Regards, Pavlin From pavlin@icir.org Sat Jan 22 11:48:55 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Sat, 22 Jan 2005 03:48:55 -0800 Subject: [Xorp-users] Newbie: trouble getting XORP started In-Reply-To: Message from =?iso-8859-1?q?Juli=E1n=20David=20=20Morillo=20Pozo?= of "Fri, 21 Jan 2005 19:42:04 +0100." <200501211942.04763.jmorillo@ac.upc.edu> Message-ID: <200501221148.j0MBmtwc000681@possum.icir.org> > I think that what is happening is that XORP is trying to access > /proc/sys/net/ipv6/conf/all/forwarding file for reading and you need root > priviliges for doing it. If that file is on the system, by default (at least on RedHat) you don't need root permission to read it. I guess what happens is that the "./configure" check has decided that the system has IPv6 enabled (the check is basically a simple program that tries to create "socket(AF_INET6, SOCK_STREAM, 0)"), hence the XORP code is compiled with "#define HAVE_IPV6 1". Assuming that the compiled XORP binaries are run on the same system, somehow that system doesn't have file /proc/sys/net/ipv6/conf/all/forwarding. Hence, please try to find why that file is not there. E.g., do you have any other files under /proc/sys/net/ipv6? Regards, Pavlin > > I hope this would help you. > > El Viernes, 21 de Enero de 2005 18:20, videoip videoip escribió: > > Hi, I´m trying to run XORP under Mandrake Linux and I get the > > following errors and warnings: > > > > [ 2005/01/21 04:40:15 ERROR xorp_fea:2568 FEA +565 fticonfig.cc > > unicast_forward ing_enabled6 ] Cannot open file > > /proc/sys/net/ipv6/conf/all/forwarding for readi ng: No such file or > > directory > > [ 2005/01/21 04:40:15 FATAL xorp_fea:2568 FEA +77 fticonfig.cc FtiConfig ] > > Cann [ 2005/01/21 04:40:16 WARNING xorp_rtrmgr:2567 XrlFinderTarget +406 > > finder_base From videoip videoip Sat Jan 22 22:58:46 2005 From: videoip videoip (videoip videoip) Date: Sat, 22 Jan 2005 19:58:46 -0300 Subject: [Xorp-users] Newbie: trouble getting XORP started Message-ID: <5947ea5305012214582cc62819@mail.gmail.com> My problem is that I have two machines with Mandrake 10 installed, in the one I want to run xorp I can't compile the code due to lack of free space in the harddisk, so I compiled the code in the other machine then made a RPM, and installed that RPM in the first machine, because of the thing you've told me it appears that the machine I want to run xorp doesn't have support for ipv6, but the one I compiled the code has, because I'm working with ipv4 and don't need ipv6 at all, my question is how do I compile xorp without ipv6 support?? Thanks in advance, Guillermo. ----- Original Message ----- From: "Pavlin Radoslavov" To: "Julián David Morillo Pozo" Cc: "videoip videoip" ; Sent: Saturday, January 22, 2005 9:48 AM Subject: Re: [Xorp-users] Newbie: trouble getting XORP started >> I think that what is happening is that XORP is trying to access >> /proc/sys/net/ipv6/conf/all/forwarding file for reading and you need root >> priviliges for doing it. > > If that file is on the system, by default (at least on RedHat) you > don't need root permission to read it. > > I guess what happens is that the "./configure" check has decided > that the system has IPv6 enabled (the check is basically a simple > program that tries to create "socket(AF_INET6, SOCK_STREAM, 0)"), > hence the XORP code is compiled with "#define HAVE_IPV6 1". > Assuming that the compiled XORP binaries are run on the same system, > somehow that system doesn't have file > /proc/sys/net/ipv6/conf/all/forwarding. > > Hence, please try to find why that file is not there. E.g., do you > have any other files under /proc/sys/net/ipv6? > > Regards, > Pavlin > >> >> I hope this would help you. >> >> El Viernes, 21 de Enero de 2005 18:20, videoip videoip escribió: >> > Hi, I´m trying to run XORP under Mandrake Linux and I get the >> > following errors and warnings: >> > >> > [ 2005/01/21 04:40:15 ERROR xorp_fea:2568 FEA +565 fticonfig.cc >> > unicast_forward ing_enabled6 ] Cannot open file >> > /proc/sys/net/ipv6/conf/all/forwarding for readi ng: No such file or >> > directory >> > [ 2005/01/21 04:40:15 FATAL xorp_fea:2568 FEA +77 fticonfig.cc >> > FtiConfig ] >> > Cann [ 2005/01/21 04:40:16 WARNING xorp_rtrmgr:2567 XrlFinderTarget >> > +406 >> > finder_base > From pavlin@icir.org Sat Jan 22 23:02:17 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Sat, 22 Jan 2005 15:02:17 -0800 Subject: [Xorp-users] Newbie: trouble getting XORP started In-Reply-To: Message from videoip videoip of "Sat, 22 Jan 2005 19:58:46 -0300." <5947ea5305012214582cc62819@mail.gmail.com> Message-ID: <200501222302.j0MN2HKe001369@possum.icir.org> > My problem is that I have two machines with Mandrake 10 installed, in > the one I want to run xorp I can't compile the code due to lack of > free space in the harddisk, so I compiled the code in the other > machine then made a RPM, and installed that RPM in the first machine, > because of the thing you've told me it appears that the machine I want > to run xorp doesn't have support for ipv6, but the one I compiled the > code has, because I'm working with ipv4 and don't need ipv6 at all, my > question is how do I compile xorp without ipv6 support?? ./configure --disable-ipv6 gmake Regards, Pavlin From videoip@gmail.com Mon Jan 24 14:58:27 2005 From: videoip@gmail.com (VideoIP) Date: Mon, 24 Jan 2005 12:58:27 -0200 Subject: [Xorp-users] Cannot enable vif eth0: no such vif Message-ID: <000e01c50225$2b8d8e70$6f01a8c0@pcflo> This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C50214.65C4B980 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable We were finally able to recompile xorp without IPv6 support. Now we have = another problem. The program is reporting it cannot enable vif eth0, = even though it previously seemed to be using that interface=B4s IP = correctly: [ 2005/01/24 02:10:42 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.3 to 224.0.0.2 on vif eth0 Afterwards I receive the error: [ 2005/01/24 02:11:06 ERROR xorp_pimsm4:2156 PIM +692 pim_node.cc = enable_vif ] Cannot enable vif eth0: no such vif If you have any idea about what I might be getting wrong please let me = know. Here=B4s the complete error log, just in case: -------------------------------------------------------------------------= ------- [ 2005/01/24 02:10:00 INFO xorp_rtrmgr:2140 RTRMGR +134 = master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea4, = rib, fib2mrib, igmp, pimsm4 [ 2005/01/24 02:10:00 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run ] Running module: interfaces = (/usr/local/xorp/fea/xorp_fea) [ 2005/01/24 02:10:02 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:03 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:05 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:07 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:09 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run ] Running module: fea = (/usr/local/xorp/fea/xorp_fea) [ 2005/01/24 02:10:13 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run ] Running module: mfea4 = (/usr/local/xorp/fea/xorp_fea) [ 2005/01/24 02:10:13 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: = >finder://MFEA_4/mfea/0.1/start_mfea< [ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] New vif: Vif[eth0] pif_index: = 2 vif_index: 0 addr: 192.168.0.3 subnet: 192.168.0.0/24 broadcast: = 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] New vif: Vif[eth1] pif_index: = 3 vif_index: 1 addr: 192.168.2.3 subnet: 192.168.2.0/24 broadcast: = 192.168.3.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP [ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] Enabled vif: eth0 [ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] Started vif: eth0 [ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] New vif: Vif[register_vif] = pif_index: 2 vif_index: 2 addr: 192.168.0.3 subnet: 192.168.0.3/32 = broadcast: 192.168.0.3 peer: 0.0.0.0 Flags: PIM_REGISTER = UNDERLYING_VIF_UP [ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] Enabled vif: eth1 [ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] Started vif: eth1 [ 2005/01/24 02:10:17 INFO xorp_fea MFEA ] Enabled vif: register_vif [ 2005/01/24 02:10:17 INFO xorp_fea MFEA ] Started vif: register_vif [ 2005/01/24 02:10:18 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run ] Running module: rib = (/usr/local/xorp/rib/xorp_rib) [ 2005/01/24 02:10:20 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target = "rib" does not exist or is not enabled. [ 2005/01/24 02:10:21 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:22 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:23 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run ] Running module: fib2mrib = (/usr/local/xorp/fib2mrib/xorp_fib2mrib) [ 2005/01/24 02:10:31 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run ] Running module: igmp = (/usr/local/xorp/mld6igmp/xorp_igmp) [ 2005/01/24 02:10:31 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = 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. [ 2005/01/24 02:10:32 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = 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. [ 2005/01/24 02:10:33 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:34 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:35 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: = >finder://IGMP/mld6igmp/0.1/start_mld6igmp< [ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth0] = pif_index: 0 vif_index: 0 Flags: [ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Added new address to vif = eth0: addr: 192.168.0.3 subnet: 192.168.0.0/24 broadcast: 192.168.0.255 = peer: 0.0.0.0 [ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Vif flags changed: = Vif[eth0] pif_index: 0 vif_index: 0 addr: 192.168.0.3 subnet: = 192.168.0.0/24 broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST = BROADCAST UNDERLYING_VIF_UP [ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth1] = pif_index: 0 vif_index: 1 Flags: [ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Added new address to vif = eth1: addr: 192.168.2.3 subnet: 192.168.2.0/24 broadcast: 192.168.3.255 = peer: 0.0.0.0 [ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Vif flags changed: = Vif[eth1] pif_index: 0 vif_index: 1 addr: 192.168.2.3 subnet: = 192.168.2.0/24 broadcast: 192.168.3.255 peer: 0.0.0.0 Flags: MULTICAST = BROADCAST UNDERLYING_VIF_UP [ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] New vif: = Vif[register_vif] pif_index: 0 vif_index: 2 Flags: [ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Added new address to vif = register_vif: addr: 192.168.0.3 subnet: 192.168.0.3/32 broadcast: = 192.168.0.3 peer: 0.0.0.0 [ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Vif flags changed: = Vif[register_vif] pif_index: 0 vif_index: 2 addr: 192.168.0.3 subnet: = 192.168.0.3/32 broadcast: 192.168.0.3 peer: 0.0.0.0 Flags: PIM_REGISTER = UNDERLYING_VIF_UP [ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth0 [ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth0] = pif_index: 0 vif_index: 0 addr: 192.168.0.3 subnet: 192.168.0.0/24 = broadcast: 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST = UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/01/24 02:10:37 TRACE xorp_igmp MLD6IGMP ] TX = IGMP_MEMBERSHIP_QUERY from 192.168.0.3 to 224.0.0.1 [ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] Started vif: eth0 [ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth1 [ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth1] = pif_index: 0 vif_index: 1 addr: 192.168.2.3 subnet: 192.168.2.0/24 = broadcast: 192.168.3.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST = UNDERLYING_VIF_UP UP IPv4 ENABLED [ 2005/01/24 02:10:37 TRACE xorp_igmp MLD6IGMP ] TX = IGMP_MEMBERSHIP_QUERY from 192.168.2.3 to 224.0.0.1 [ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] Started vif: eth1 [ 2005/01/24 02:10:37 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run ] Running module: pimsm4 = (/usr/local/xorp/pim/xorp_pimsm4) [ 2005/01/24 02:10:37 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target = "PIMSM_4" does not exist or is not enabled. [ 2005/01/24 02:10:38 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_MEMBERSHIP_QUERY from 192.168.0.3 to 224.0.0.1 on vif eth0 [ 2005/01/24 02:10:39 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target = "PIMSM_4" does not exist or is not enabled. [ 2005/01/24 02:10:39 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.3 to 224.0.0.2 on vif eth0 [ 2005/01/24 02:10:40 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:40 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.3 to 224.0.0.2 on vif eth0 [ 2005/01/24 02:10:40 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT from 192.168.2.3 to 224.0.0.2 on vif eth1 [ 2005/01/24 02:10:41 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:42 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:42 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.3 to 224.0.0.2 on vif eth0 [ 2005/01/24 02:10:51 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT from 192.168.2.3 to 224.0.0.2 on vif eth1 [ 2005/01/24 02:10:51 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT from 192.168.2.3 to 224.0.0.2 on vif eth1 [ 2005/01/24 02:10:52 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:54 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:55 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:56 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:10:58 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:11:00 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:11:02 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:11:03 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406 = finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for = finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not enabled. [ 2005/01/24 02:11:05 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL: = >finder://PIMSM_4/pim/0.1/start_pim< [ 2005/01/24 02:11:06 ERROR xorp_pimsm4:2156 PIM +692 pim_node.cc = enable_vif ] Cannot enable vif eth0: no such vif [ 2005/01/24 02:11:06 WARNING xorp_pimsm4 XrlPimTarget ] Handling method = for pim/0.1/enable_vif failed: XrlCmdError 102 Command failed Cannot = enable vif eth0: no such vif [ 2005/01/24 02:11:06 ERROR xorp_rtrmgr:2140 RTRMGR +533 = master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command = failed Cannot enable vif eth0: no such vif [ 2005/01/24 02:11:06 ERROR xorp_rtrmgr:2140 RTRMGR +146 = master_conf_tree.cc config_done ] Configuration failed: 102 Command = failed Cannot enable vif eth0: no such vif [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +1366 task.cc = run_task ] No more tasks to run [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc terminate ] Terminating module: fea [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc terminate ] Terminating module: fib2mrib [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc terminate ] Killing module: fib2mrib (pid =3D 2154) [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc killed ] Module killed during shutdown: fib2mrib [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc terminate ] Terminating module: igmp [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc terminate ] Killing module: igmp (pid =3D 2155) [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc killed ] Module killed during shutdown: igmp [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc terminate ] Terminating module: interfaces [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc terminate ] Terminating module: mfea4 [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc terminate ] Killing module: mfea4 (pid =3D 2141) [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc killed ] Module killed during shutdown: mfea4 [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc terminate ] Terminating module: pimsm4 [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc terminate ] Killing module: pimsm4 (pid =3D 2156) [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc terminate ] Terminating module: rib [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc terminate ] Killing module: rib (pid =3D 2151) [ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc killed ] Module killed during shutdown: rib [ 2005/01/24 02:11:08 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc killed ] Module killed during shutdown: pimsm4 ------=_NextPart_000_000B_01C50214.65C4B980 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
We were finally able to recompile = xorp without=20 IPv6 support. Now we have another problem. The program is reporting it = cannot=20 enable vif eth0, even though it previously seemed to be using that = interface=B4s=20 IP correctly:
 

[ 2005/01/24 02:10:42 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT=20 from 192.168.0.3 to 224.0.0.2 on vif eth0

Afterwards I receive the error:

[ 2005/01/24 02:11:06 ERROR xorp_pimsm4:2156 PIM +692=20 pim_node.cc enable_vif ] Cannot enable vif eth0: no such=20 vif

 
If you have any idea about what I might = be getting=20 wrong please let me know.
 
 
Here=B4s the complete error = log, just in=20 case:

[ 2005/01/24 02:10:00 INFO xorp_rtrmgr:2140 RTRMGR +134 = master_conf_tree.cc=20 execute ] Changed modules: interfaces, fea, mfea4, rib, fib2mrib, igmp,=20 pimsm4

[ 2005/01/24 02:10:00 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run=20 ] Running module: interfaces (/usr/local/xorp/fea/xorp_fea)

[ 2005/01/24 02:10:02 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:03 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:05 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:07 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:09 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run=20 ] Running module: fea (/usr/local/xorp/fea/xorp_fea)

[ 2005/01/24 02:10:13 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run=20 ] Running module: mfea4 (/usr/local/xorp/fea/xorp_fea)

[ 2005/01/24 02:10:13 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL:=20 >finder://MFEA_4/mfea/0.1/start_mfea<

[ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] New vif: Vif[eth0] = pif_index: 2=20 vif_index: 0 addr: 192.168.0.3 subnet: 192.168.0.0/24 broadcast: = 192.168.0.255=20 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP

[ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] New vif: Vif[eth1] = pif_index: 3=20 vif_index: 1 addr: 192.168.2.3 subnet: 192.168.2.0/24 broadcast: = 192.168.3.255=20 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP

[ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] Enabled vif: eth0

[ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] Started vif: eth0

[ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] New vif: Vif[register_vif] = pif_index: 2 vif_index: 2 addr: 192.168.0.3 subnet: 192.168.0.3/32 = broadcast:=20 192.168.0.3 peer: 0.0.0.0 Flags: PIM_REGISTER UNDERLYING_VIF_UP

[ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] Enabled vif: eth1

[ 2005/01/24 02:10:16 INFO xorp_fea MFEA ] Started vif: eth1

[ 2005/01/24 02:10:17 INFO xorp_fea MFEA ] Enabled vif: = register_vif

[ 2005/01/24 02:10:17 INFO xorp_fea MFEA ] Started vif: = register_vif

[ 2005/01/24 02:10:18 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run=20 ] Running module: rib (/usr/local/xorp/rib/xorp_rib)

[ 2005/01/24 02:10:20 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target = "rib" does=20 not exist or is not enabled.

[ 2005/01/24 02:10:21 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:22 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:23 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run=20 ] Running module: fib2mrib (/usr/local/xorp/fib2mrib/xorp_fib2mrib)

[ 2005/01/24 02:10:31 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run=20 ] Running module: igmp (/usr/local/xorp/mld6igmp/xorp_igmp)

[ 2005/01/24 02:10:31 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target = "IGMP" does=20 not exist or is not enabled.

[ 2005/01/24 02:10:32 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target = "IGMP" does=20 not exist or is not enabled.

[ 2005/01/24 02:10:33 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:34 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:35 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL:=20 >finder://IGMP/mld6igmp/0.1/start_mld6igmp<

[ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth0] = pif_index:=20 0 vif_index: 0 Flags:

[ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Added new address to = vif=20 eth0: addr: 192.168.0.3 subnet: 192.168.0.0/24 broadcast: 192.168.0.255 = peer:=20 0.0.0.0

[ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Vif flags changed: = Vif[eth0]=20 pif_index: 0 vif_index: 0 addr: 192.168.0.3 subnet: 192.168.0.0/24 = broadcast:=20 192.168.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST = UNDERLYING_VIF_UP

[ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] New vif: Vif[eth1] = pif_index:=20 0 vif_index: 1 Flags:

[ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Added new address to = vif=20 eth1: addr: 192.168.2.3 subnet: 192.168.2.0/24 broadcast: 192.168.3.255 = peer:=20 0.0.0.0

[ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Vif flags changed: = Vif[eth1]=20 pif_index: 0 vif_index: 1 addr: 192.168.2.3 subnet: 192.168.2.0/24 = broadcast:=20 192.168.3.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST = UNDERLYING_VIF_UP

[ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] New vif: = Vif[register_vif]=20 pif_index: 0 vif_index: 2 Flags:

[ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Added new address to = vif=20 register_vif: addr: 192.168.0.3 subnet: 192.168.0.3/32 broadcast: = 192.168.0.3=20 peer: 0.0.0.0

[ 2005/01/24 02:10:36 INFO xorp_igmp MLD6IGMP ] Vif flags changed:=20 Vif[register_vif] pif_index: 0 vif_index: 2 addr: 192.168.0.3 subnet:=20 192.168.0.3/32 broadcast: 192.168.0.3 peer: 0.0.0.0 Flags: PIM_REGISTER=20 UNDERLYING_VIF_UP

[ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth0

[ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth0] = pif_index:=20 0 vif_index: 0 addr: 192.168.0.3 subnet: 192.168.0.0/24 broadcast: = 192.168.0.255=20 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 = ENABLED

[ 2005/01/24 02:10:37 TRACE xorp_igmp MLD6IGMP ] TX = IGMP_MEMBERSHIP_QUERY=20 from 192.168.0.3 to 224.0.0.1

[ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] Started vif: eth0

[ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] Enabled vif: eth1

[ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] STARTING Vif[eth1] = pif_index:=20 0 vif_index: 1 addr: 192.168.2.3 subnet: 192.168.2.0/24 broadcast: = 192.168.3.255=20 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP UP IPv4 = ENABLED

[ 2005/01/24 02:10:37 TRACE xorp_igmp MLD6IGMP ] TX = IGMP_MEMBERSHIP_QUERY=20 from 192.168.2.3 to 224.0.0.1

[ 2005/01/24 02:10:37 INFO xorp_igmp MLD6IGMP ] Started vif: eth1

[ 2005/01/24 02:10:37 INFO xorp_rtrmgr:2140 RTRMGR +356 = module_manager.cc run=20 ] Running module: pimsm4 (/usr/local/xorp/pim/xorp_pimsm4)

[ 2005/01/24 02:10:37 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target = "PIMSM_4"=20 does not exist or is not enabled.

[ 2005/01/24 02:10:38 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_MEMBERSHIP_QUERY=20 from 192.168.0.3 to 224.0.0.1 on vif eth0

[ 2005/01/24 02:10:39 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target = "PIMSM_4"=20 does not exist or is not enabled.

[ 2005/01/24 02:10:39 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT=20 from 192.168.0.3 to 224.0.0.2 on vif eth0

[ 2005/01/24 02:10:40 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:40 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT=20 from 192.168.0.3 to 224.0.0.2 on vif eth0

[ 2005/01/24 02:10:40 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT=20 from 192.168.2.3 to 224.0.0.2 on vif eth1

[ 2005/01/24 02:10:41 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:42 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:42 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT=20 from 192.168.0.3 to 224.0.0.2 on vif eth0

[ 2005/01/24 02:10:51 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT=20 from 192.168.2.3 to 224.0.0.2 on vif eth1

[ 2005/01/24 02:10:51 TRACE xorp_igmp MLD6IGMP ] RX = IGMP_V2_MEMBERSHIP_REPORT=20 from 192.168.2.3 to 224.0.0.2 on vif eth1

[ 2005/01/24 02:10:52 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:54 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:55 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:56 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:10:58 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:11:00 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:11:02 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:11:03 WARNING xorp_rtrmgr:2140 XrlFinderTarget +406=20 finder_base.cc handle_finder_0_2_resolve_xrl ] Handling method for=20 finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target = is not=20 enabled.

[ 2005/01/24 02:11:05 TRACE xorp_rtrmgr RTRMGR ] Startup with XRL:=20 >finder://PIMSM_4/pim/0.1/start_pim<

[ 2005/01/24 02:11:06 ERROR xorp_pimsm4:2156 PIM +692 pim_node.cc = enable_vif=20 ] Cannot enable vif eth0: no such vif

[ 2005/01/24 02:11:06 WARNING xorp_pimsm4 XrlPimTarget ] Handling = method for=20 pim/0.1/enable_vif failed: XrlCmdError 102 Command failed Cannot enable = vif=20 eth0: no such vif

[ 2005/01/24 02:11:06 ERROR xorp_rtrmgr:2140 RTRMGR +533 = master_conf_tree.cc=20 commit_pass2_done ] Commit failed: 102 Command failed Cannot enable vif = eth0: no=20 such vif

[ 2005/01/24 02:11:06 ERROR xorp_rtrmgr:2140 RTRMGR +146 = master_conf_tree.cc=20 config_done ] Configuration failed: 102 Command failed Cannot enable vif = eth0:=20 no such vif

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +1366 task.cc = run_task ]=20 No more tasks to run

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc=20 terminate ] Terminating module: fea

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc=20 terminate ] Terminating module: fib2mrib

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc=20 terminate ] Killing module: fib2mrib (pid =3D 2154)

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc=20 killed ] Module killed during shutdown: fib2mrib

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc=20 terminate ] Terminating module: igmp

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc=20 terminate ] Killing module: igmp (pid =3D 2155)

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc=20 killed ] Module killed during shutdown: igmp

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc=20 terminate ] Terminating module: interfaces

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc=20 terminate ] Terminating module: mfea4

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc=20 terminate ] Killing module: mfea4 (pid =3D 2141)

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc=20 killed ] Module killed during shutdown: mfea4

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc=20 terminate ] Terminating module: pimsm4

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc=20 terminate ] Killing module: pimsm4 (pid =3D 2156)

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +166 = module_manager.cc=20 terminate ] Terminating module: rib

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +213 = module_manager.cc=20 terminate ] Killing module: rib (pid =3D 2151)

[ 2005/01/24 02:11:07 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc=20 killed ] Module killed during shutdown: rib

[ 2005/01/24 02:11:08 INFO xorp_rtrmgr:2140 RTRMGR +498 = module_manager.cc=20 killed ] Module killed during shutdown: pimsm4

 
 
------=_NextPart_000_000B_01C50214.65C4B980-- From kohler@CS.UCLA.EDU Mon Jan 24 21:06:05 2005 From: kohler@CS.UCLA.EDU (Eddie Kohler) Date: Mon, 24 Jan 2005 13:06:05 -0800 Subject: [Xorp-users] Click configuration generator on XORP In-Reply-To: <41F152A0.30409@ac.upc.edu> References: <41F152A0.30409@ac.upc.edu> Message-ID: Hi Rafael, I think you're right, that this is not necessary, but it's the way we've written Click IP configurations since we wrote Click. (Which is like more than 5 years ago. Shit, time flies.) ARP replies received on interface X could be sent only to the ARPQuerier for interface X, and the host. The current design makes sense if an ARP reply might arrive on an interface different from the interface that sent the request. However, the current design isn't exactly a bug: it behaves correctly. Eddie On Jan 21, 2005, at 11:06 AM, Rafael Paoliello Guimaraes wrote: > Hello, > > I was taking a look at the configuration file generated by XORP to be > used in Click and there is a point that I didn't really understand. > > Whenever an interface receives an ARP Reply, makes n+1 copies of it > (through the Tee element) and send one copy for each of the n > interfaces (in fact to their ARPQuerier element) and 1 copy to the > host (in the case that click is running in user-level, this last ARP > reply is discarded). > > Why does an ARP reply need to be sent to the ARPQuerier of other > interfaces? Is there any case where a packet may be waiting an ARP > reply to be sent through an interface and this ARP reply comes from > another interface? Am I missing something? > > Best regards, > > -- > > =========================================== > Rafael Paoliello Guimaraes > PhD Student - Computer Networking Group > Department of Computer Architecture (DAC) > Polytechnic University of Catalonia (UPC) > Phone: +34-934017187 Fax: +34-934017055 > URL: http://people.ac.upc.es/rpaoliel > =========================================== > _______________________________________________ > Xorp-users mailing list > Xorp-users@xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin@icir.org Tue Jan 25 00:54:43 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 24 Jan 2005 16:54:43 -0800 Subject: [Xorp-users] Cannot enable vif eth0: no such vif In-Reply-To: Message from "VideoIP" of "Mon, 24 Jan 2005 12:58:27 -0200." <000e01c50225$2b8d8e70$6f01a8c0@pcflo> Message-ID: <200501250054.j0P0shox046342@possum.icir.org> > We were finally able to recompile xorp without IPv6 support. Now we have = > another problem. The program is reporting it cannot enable vif eth0, = > even though it previously seemed to be using that interface=B4s IP = > correctly: > > [ 2005/01/24 02:10:42 TRACE xorp_igmp MLD6IGMP ] RX = > IGMP_V2_MEMBERSHIP_REPORT from 192.168.0.3 to 224.0.0.2 on vif eth0 > > Afterwards I receive the error: > > [ 2005/01/24 02:11:06 ERROR xorp_pimsm4:2156 PIM +692 pim_node.cc = > enable_vif ] Cannot enable vif eth0: no such vif > > > If you have any idea about what I might be getting wrong please let me = > know. > What XORP version do you use? I think I've found and fixed the problem, so please get the lastest code from the CVS repository and let me know if it works for you. Thanks, Pavlin From pavlin@icir.org Tue Jan 25 01:58:54 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 24 Jan 2005 17:58:54 -0800 Subject: [Xorp-users] Newbie: trouble getting XORP started In-Reply-To: Message from Pavlin Radoslavov of "Sat, 22 Jan 2005 15:02:17 PST." <200501222302.j0MN2HKe001369@possum.icir.org> Message-ID: <200501250158.j0P1ws9q067364@possum.icir.org> > > My problem is that I have two machines with Mandrake 10 installed, in > > the one I want to run xorp I can't compile the code due to lack of > > free space in the harddisk, so I compiled the code in the other > > machine then made a RPM, and installed that RPM in the first machine, > > because of the thing you've told me it appears that the machine I want > > to run xorp doesn't have support for ipv6, but the one I compiled the > > code has, because I'm working with ipv4 and don't need ipv6 at all, my > > question is how do I compile xorp without ipv6 support?? > > ./configure --disable-ipv6 > gmake FYI, the original problem you had (XORP binary compiled on IPv6-capable machine would coredump on machine that doesn't have IPv6) has been fixed long time ago in the CVS repository, but this was after the 1.0 release. Regards, Pavlin From rafael.guimaraes@ac.upc.edu Tue Jan 25 14:34:08 2005 From: rafael.guimaraes@ac.upc.edu (Rafael Paoliello Guimaraes) Date: Tue, 25 Jan 2005 15:34:08 +0100 Subject: [Xorp-users] Click configuration generator on XORP In-Reply-To: References: <41F152A0.30409@ac.upc.edu> Message-ID: <41F658E0.8020006@ac.upc.edu> Hi Eddie, I know that this is not a bug, for me it was just redundant. I was just trying to understand why it was done this way, maybe I was missing something. In fact, I thought that maybe this should be interesting in the case that we had more than one interface connected to the same subnet. But this was the only case I could think of where this configuration may be more efficient. Anyway, thank you for your time... Cheers, =========================================== Rafael Paoliello Guimaraes PhD Student - Computer Networking Group Department of Computer Architecture (DAC) Polytechnic University of Catalonia (UPC) Phone: +34-934017187 Fax: +34-934017055 URL: http://people.ac.upc.es/rpaoliel =========================================== Eddie Kohler wrote: > Hi Rafael, > > I think you're right, that this is not necessary, but it's the way we've > written Click IP configurations since we wrote Click. (Which is like > more than 5 years ago. Shit, time flies.) ARP replies received on > interface X could be sent only to the ARPQuerier for interface X, and > the host. > > The current design makes sense if an ARP reply might arrive on an > interface different from the interface that sent the request. > > However, the current design isn't exactly a bug: it behaves correctly. > > Eddie > > > On Jan 21, 2005, at 11:06 AM, Rafael Paoliello Guimaraes wrote: > >> Hello, >> >> I was taking a look at the configuration file generated by XORP to be >> used in Click and there is a point that I didn't really understand. >> >> Whenever an interface receives an ARP Reply, makes n+1 copies of it >> (through the Tee element) and send one copy for each of the n >> interfaces (in fact to their ARPQuerier element) and 1 copy to the >> host (in the case that click is running in user-level, this last ARP >> reply is discarded). >> >> Why does an ARP reply need to be sent to the ARPQuerier of other >> interfaces? Is there any case where a packet may be waiting an ARP >> reply to be sent through an interface and this ARP reply comes from >> another interface? Am I missing something? >> >> Best regards, >> >> -- >> >> =========================================== >> Rafael Paoliello Guimaraes >> PhD Student - Computer Networking Group >> Department of Computer Architecture (DAC) >> Polytechnic University of Catalonia (UPC) >> Phone: +34-934017187 Fax: +34-934017055 >> URL: http://people.ac.upc.es/rpaoliel >> =========================================== >> _______________________________________________ >> Xorp-users mailing list >> Xorp-users@xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > _______________________________________________ > Xorp-users mailing list > Xorp-users@xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > From kras0021@umn.edu Tue Jan 25 20:58:21 2005 From: kras0021@umn.edu (Jeff Krasky) Date: Tue, 25 Jan 2005 14:58:21 CST Subject: [Xorp-users] writing callbacks Message-ID: <200501252058.j0PKwLBn003654@firefox.software.umn.edu> Hi, I am creating my own process and it will use XRL to give some commands to BGP. For example, I created an XrlBgpV0p2Client object and I will call send_originate_route4() on this object. My problem is how to create the last parameter, OriginateRoute4CB. It is my understanding that I need to write my own callback method. Is this correct? If so, how do I make it of that type? Thanks, Jeff From pavlin@icir.org Tue Jan 25 23:30:50 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Tue, 25 Jan 2005 15:30:50 -0800 Subject: [Xorp-users] writing callbacks In-Reply-To: Message from Jeff Krasky of "Tue, 25 Jan 2005 14:58:21 CST." <200501252058.j0PKwLBn003654@firefox.software.umn.edu> Message-ID: <200501252330.j0PNUoAO006278@possum.icir.org> > I am creating my own process and it will use XRL to give some commands to > BGP. For example, I created an XrlBgpV0p2Client object and I will call > send_originate_route4() on this object. > > My problem is how to create the last parameter, OriginateRoute4CB. It is > my understanding that I need to write my own callback method. Is this > correct? If so, how do I make it of that type? Jeff, Yes, you have to write your own callback method. Please have a look in the xorp/docs/xorpdev_101/ document (it is not in the 1.0 distribution, so you would have to fetch it from the CVS repository). Section 4.1 describes in details how to generate the stub code for the caller, what the type of the callback should be, etc. Regards, Pavlin P.S. In your particular case, the type of the callback should be a method that has "const XrlError&" as an argument and returns "void". Example: void MyClass::bgp_client_send_originate_route4_cb(const XrlError& xrl_error) { ... } ... MyClass::send_route() { ... bool success = _bgp_client.send_originate_route4( target_name, nlri, next_hop, unicast, multicast, callback(this, &MyClass::bgp_client_send_originate_route4_cb)); ... } From pavlin@icir.org Wed Jan 26 00:10:18 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Tue, 25 Jan 2005 16:10:18 -0800 Subject: [Xorp-users] XORP entry added to the OpenBSD ports tree Message-ID: <200501260010.j0Q0AIUj006625@possum.icir.org> FYI. Pavlin ------- Forwarded Message Date: Wed, 26 Jan 2005 00:33:32 +0100 From: Christian Weisgerber To: Pavlin Radoslavov Subject: Re: xorp port (WIP) FYI, I've imported a port of xorp-1.0 into the OpenBSD ports tree. - -- Christian "naddy" Weisgerber naddy@mips.inka.de ------- End of Forwarded Message From fjvilanova@inf.ufrgs.br Thu Jan 27 19:38:30 2005 From: fjvilanova@inf.ufrgs.br (fjvilanova@inf.ufrgs.br) Date: Thu, 27 Jan 2005 17:38:30 -0200 Subject: [Xorp-users] SNMP and liveCD Message-ID: <1106854710.41f94336d08d1@webmail.inf.ufrgs.br> Anyone knows how to configure Net-SNMP using XORP liveCD? thanks, Felipe Jung Vilanova ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From andy@wormspace.net Fri Jan 28 03:59:41 2005 From: andy@wormspace.net (andy@wormspace.net) Date: Thu, 27 Jan 2005 19:59:41 -0800 (PST) Subject: [Xorp-users] Filtering capabilities Message-ID: <50360.12.146.232.2.1106884781.spork@webmail.wormspace.net> Hi, I'm really new to routers so please forgive me if this question is stupid. Is this software capable of filtering functions such as other routers? That is, by setting up the router to accept specific traffic...will the traffic that is not specified be dropped by the router? Again, sorry if this question might be a bit elementary. I am trying to learn about this as I am trying to explore an open source routing solution for a project I'm working. Thanks in advance for any responses received. -Andy ------------------------------------------------ "The road ahead is ALWAYS under construction." -Author Unknown From atanu@ICSI.Berkeley.EDU Fri Jan 28 04:07:22 2005 From: atanu@ICSI.Berkeley.EDU (Atanu Ghosh) Date: Thu, 27 Jan 2005 20:07:22 -0800 Subject: [Xorp-users] SNMP and liveCD In-Reply-To: Message from fjvilanova@inf.ufrgs.br of "Thu, 27 Jan 2005 17:38:30 -0200." <1106854710.41f94336d08d1@webmail.inf.ufrgs.br> Message-ID: <5025.1106885242@tigger.icir.org> Hi, I don't think that the liveCD was built with SNMP support. If you want to use SNMP you will need to build XORP yourself from the CVS repository. There is a README in the mibs directory that explains what you need to do. Currently only BGP supports SNMP. We haven't tried using SNMP for a while, so it wouldn't be surprise if there are problems. Atanu. >>>>> "fjvilanova" == fjvilanova writes: fjvilanova> Anyone knows how to configure Net-SNMP using XORP liveCD? fjvilanova> thanks, fjvilanova> Felipe Jung Vilanova fjvilanova> ---------------------------------------------------------------- fjvilanova> This message was sent using IMP, the Internet Messaging Program. fjvilanova> _______________________________________________ fjvilanova> Xorp-users mailing list fjvilanova> Xorp-users@xorp.org fjvilanova> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From dave.price@aber.ac.uk Fri Jan 28 12:37:05 2005 From: dave.price@aber.ac.uk (Dave Price) Date: Fri, 28 Jan 2005 12:37:05 +0000 Subject: [Xorp-users] XORP on Solaris?? Message-ID: <162.1106915825@aber.ac.uk> Dear All, We are currently considering replacing our current "home built" router with a new box. Our current router, built many years ago, uses a Pentium 300 (ish) and a multi-interface 100 Mbps ethernet to link four networks. It currently runs an old Solaris for Intel OS. It only currently handles unicast routing. One possibility being considered is basically a faster version of same, but basing it on a sun branded rack mount server with AMD processors. What OS though? We could just use Solaris and its inbuilt IP routing as we do now and we get some firewalling. Another thought is XORP run on something? It would be nice if it did multicast routing for us too. Any thoughts folks? Has anyone ported XORP to Solaris? Thanks for any thoughts you may have to offer. Dave Price From videoip@gmail.com Mon Jan 31 22:09:28 2005 From: videoip@gmail.com (VideoIP) Date: Mon, 31 Jan 2005 20:09:28 -0200 Subject: [Xorp-users] Cannot enable vif eth0: no such vif References: <200501271347.j0RDlwaw075728@possum.icir.org> Message-ID: <001d01c507e1$8cd14c50$6f01a8c0@pcflo> This is a multi-part message in MIME format. ------=_NextPart_000_001A_01C507D0.C4D93B50 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit Hi Pavlin, I´ve followed your advice and downloaded the latest version from the CVS and compiled it directly on the Linux I want to route with. I´ve set up the config.boot file and started xorp_rtrmgr without errors. I´m streaming a video with VLC to 231.1.1.1 but it´s not reaching the other side of the router, where I have another VLC trying to read that address. Would you mind taking a look at my config.boot and telling me if you think it´s fine? As usual, thanks a lot. ----- Original Message ----- From: "Pavlin Radoslavov" To: "VideoIP" Cc: "Pavlin Radoslavov" Sent: Thursday, January 27, 2005 11:47 AM Subject: Re: [Xorp-users] Cannot enable vif eth0: no such vif >> This is getting weirder every minute, there=B4s actually NO config.log = >> or config.status in the xorp directory or even in the whole PC for that = >> matter. The problem is that configure doesn=B4t even start, the only = >> message I receive is the one I already told you about. I enclose a = >> screen capture. We are using Mandrake Linux 10.0 Official. > > If ./configure failed, then it is no surprise there are no > config.log and config.status, because they are auto-generated by > ./configure. > > One potential problem that comes to mind is to verify that > /bin/sh is valid. E.g., is it there; if it is a symbolic link, does > it point to a valid file, etc? > > If /bin/sh is valid, then can you try the following: > sh ./configure > > If nothing useful comes out of it, then try > strace ./configure > > Also, did you by any chance use any Microsoft Windows related stuff? > For example: > * did you edit or load ./configure in Windows environment > * was ./configure saved on a Windows file system > * Did you use any Windows tools such as winzip to copy the files > around? > > The reason I ask about Windows, is because after some web search I > found that other people have had similar problems. For example, see > http://www.spinics.net/lists/ac/msg01035.html > > Hmmm, when I look into the gif file you sent me, why some text files > like README and RELEASE_NOTES have the executable flag set? They > don't have the executable flag set in the CVS repository. Is it > because of some additional manipulation of the whole tree? > > Thanks, > Pavlin ------=_NextPart_000_001A_01C507D0.C4D93B50 Content-Type: application/octet-stream; name="config.boot" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="config.boot" /* $XORP: xorp/rtrmgr/config.boot.sample,v 1.16 2004/06/21 18:06:05 = hodson Exp $ */ interfaces { interface eth0 { description: "Salida a red 0" enabled: true default-system-config } interface eth1 { description: "Salida a red 1" enabled: true default-system-config } } plumbing { mfea4 { enabled: true interface eth0 { vif eth0 { enabled: true } } interface eth1 { vif eth1 { enabled: true } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { igmp { enabled: true interface eth0 { vif eth0 { enabled: true } } interface eth1 { vif eth1 { enabled: true } } traceoptions { flag all { enabled: true } } } } protocols { pimsm4 { enabled: true interface eth0 { vif eth0 { enabled: true /* dr-priority: 1 */ /* alternative-subnet 10.40.0.0/16 */ } } interface eth1 { vif eth1 { enabled: true /* dr-priority: 1 */ /* alternative-subnet 10.40.0.0/16 */ } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ enabled: true } } static-rps { rp 192.168.0.3 { group-prefix 224.0.0.0/4 { /* rp-priority: 192 */ /* hash-mask-len: 30 */ } } } bootstrap { enabled: true cand-bsr { scope-zone 224.0.0.0/4 { /* is-scope-zone: false */ cand-bsr-by-vif-name: "eth0" bsr-priority: 1 hash-mask-len: 30=20 } } cand-rp { group-prefix 224.0.0.0/4 { /* is-scope-zone: false */ cand-rp-by-vif-name: "eth0" rp-priority: 192 rp-holdtime: 150=20 } } } switch-to-spt-threshold { /* approx. 1K bytes/s (10Kbps) threshold */ enabled: true interval-sec: 100 bytes: 102400 } traceoptions { flag all { enabled: true } } } } /* * Note: fib2mrib is needed for multicast only if the unicast protocols * don't populate the MRIB with multicast-specific routes. */ protocols { fib2mrib { enabled: true } } /* * See xorp/mibs/snmpdscripts/README on how to configure Net-SNMP in = your host * before uncommenting the snmp section below. * Also check that the "bgp4_mib_1657.so" exists in the correct = location. */ /* *protocols { * snmp { * mib-module bgp4_mib_1657 { * abs-path: "/usr/local/xorp/mibs/bgp4_mib_1657.so" * } * } *} */ ------=_NextPart_000_001A_01C507D0.C4D93B50-- From pavlin@icir.org Mon Jan 31 22:22:30 2005 From: pavlin@icir.org (Pavlin Radoslavov) Date: Mon, 31 Jan 2005 14:22:30 -0800 Subject: [Xorp-users] Cannot enable vif eth0: no such vif In-Reply-To: Message from "VideoIP" of "Mon, 31 Jan 2005 20:09:28 -0200." <001d01c507e1$8cd14c50$6f01a8c0@pcflo> Message-ID: <200501312222.j0VMMUv0015226@possum.icir.org> > Hi Pavlin, I´ve followed your advice and downloaded the latest version from > the CVS and compiled it directly on the Linux I want to route with. > I´ve set up the config.boot file and started xorp_rtrmgr without errors. I´m > streaming a video with VLC to 231.1.1.1 but it´s not reaching the other side > of the router, where I have another VLC trying to read that address. > Would you mind taking a look at my config.boot and telling me if you think > it´s fine? You may want to add the following to your config file: fea { enable-unicast-forwarding4: true /* enable-unicast-forwarding6: true */ } If it still doesn't work, then please send me the following: - cat /proc/net/ip_mr_vif cat /proc/net/ip_mr_cache (while XORP is running) - The output of the following xorpsh CLI commands: show pim rps show pim join - your log file Regards, Pavlin