From karl at sipxx.com Thu Oct 1 08:46:28 2009 From: karl at sipxx.com (XORP at sipxx.com) Date: Thu, 01 Oct 2009 11:46:28 -0400 Subject: [Xorp-users] HAVE_IPV6_MULTICAST never defined in XORP-1.7 on LINUX In-Reply-To: <4ABD59FD.1010201@candelatech.com> References: <4ABBCCEF.8030608@sipxx.com> <4ABBD9A5.2010906@incunabulum.net> <4ABBE930.4000104@sipxx.com> <4ABBF1CD.3030908@incunabulum.net> <4ABCFC5A.5000707@sipxx.com> <4ABD0866.40306@incunabulum.net> <4ABD2239.3040500@sipxx.com> <4ABD4910.6020207@incunabulum.net> <4ABD5503.8040704@sipxx.com> <4ABD59FD.1010201@candelatech.com> Message-ID: <4AC4CED4.7040706@sipxx.com> This patch works fine. No problems under Linux and FreeBSD, afaics. Thank you. Can this please be committed? Ben Greear wrote: > To change back to the original topic: Here is a patch that lets xorp > compile > IPV6 multicast logic on Linux, at least. I haven't tested functionality. > > * Properly detect RFC3542 support on Linux. (it probably exists, > certainly does on F11) > * Check for HAVE_IPV6_MULTICAST > * Allow HAVE_IPV6_MULTICAST_ROUTING on Linux. > > > PS. In case anyone ever wants to know, the scons test files are > located in > obj/[platform]/.sconf_temp > > Had to run strace to figure out where it was hiding these things :P > > Thanks, > Ben > From abee_peraye at hotmail.com Thu Oct 1 23:23:37 2009 From: abee_peraye at hotmail.com (abee peraye) Date: Fri, 2 Oct 2009 13:23:37 +0700 Subject: [Xorp-users] multicast using xorp In-Reply-To: References: <47E179216C509646865919E8F4F4F85B0102C397@pluto.sapura.com> <4AC383AB.5020108@incunabulum.net> Message-ID: Yes, one of my problem while experiment in multicast was TTL setting on VLC. Maybe TTL on VLC Server have to define value for 255. 'Coz once I've ever used value of TTL 128 for passing 3 routers, but stream still can't reach client. Or maybe you forgot to configure unicast routing? I used OSPF from Quagga for unicast routing in my experiment.I already success using XORP for multicast. Hehee, thank you Mr. Bruce for your help. Thx-Abee > Date: Wed, 30 Sep 2009 17:31:08 +0100 > From: phillip.blenkinsopp at logica.com > To: xorp-users at xorp.org > Subject: Re: [Xorp-users] multicast using xorp > > Have you checked that the TTL of the traffic is sufficient? > > I've been frustrated by this when using VLC in the past because it was set to 1 causing all my traffic to be dropped and the TTL setting is quite well hidden in the UI. > > -----Original Message----- > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Bruce Simpson > Sent: 30 September 2009 17:14 > To: Fazlina Zuria Mohd Anuar > Cc: xorp-users at xorp.org > Subject: Re: [Xorp-users] multicast using xorp > > Hi, > > Thanks for your question about XORP multicast support. > > > Fazlina Zuria Mohd Anuar wrote: > > > > I would like to ask some advice about configuring multicast network > > using xorp. > > > > I would like to multicast video streaming using vlc player between 2 > > xorp router. > > > > ... > > > > Both router using same setting & the multicast doesn?t working?please > > advice..TQ!!! > > > > > Your configuration looks OK off the top of my head. > > Have you checked that IP multicast forwarding cache entries are being > pushed to the Linux kernel? The place to look is /proc/net//ip_mr_cache/. > > Unfortunately I can't be of further help on this issue at the moment, > hopefully others on the list can help out. > > thanks, > BMS > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > Please help Logica to respect the environment by not printing this email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei, die Umwelt zu sch?tzen. / Por favor ajude a Logica a respeitar o ambiente nao imprimindo este correio electronico. > > > > This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. > _________________________________________________________________ NEW! Get Windows Live FREE. http://www.get.live.com/wl/all -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091002/cffe675f/attachment.html From fazlina at sapura.com.my Fri Oct 2 00:01:11 2009 From: fazlina at sapura.com.my (Fazlina Zuria Mohd Anuar) Date: Fri, 2 Oct 2009 15:01:11 +0800 Subject: [Xorp-users] multicast using xorp References: <47E179216C509646865919E8F4F4F85B0102C397@pluto.sapura.com><4AC383AB.5020108@incunabulum.net> Message-ID: <47E179216C509646865919E8F4F4F85B0102C6CF@pluto.sapura.com> Hi all!!! Thank you so much!!! Actually my configuration on Xorp is just fine? The problem is vlc player. The TTL value have to be more than 1. And changing the value using GUI doesn?t affect the command, so I use command line to run the vlc which is: Server: vlc ?vvv c:\{source file} :file-caching=300 ?sout udp:239.240.0.2:1234 ?ttl 12 Client: Vlc udp://{server unicast IP}@239.240.0.2:1234 And its works!!!!! Thank you very much all!!! From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of abee peraye Sent: 02 Oktober 2009 14:24 PM To: xorp-users at xorp.org Subject: Re: [Xorp-users] multicast using xorp Yes, one of my problem while experiment in multicast was TTL setting on VLC. Maybe TTL on VLC Server have to define value for 255. 'Coz once I've ever used value of TTL 128 for passing 3 routers, but stream still can't reach client. Or maybe you forgot to configure unicast routing? I used OSPF from Quagga for unicast routing in my experiment. I already success using XORP for multicast. Hehee, thank you Mr. Bruce for your help. Thx -Abee > Date: Wed, 30 Sep 2009 17:31:08 +0100 > From: phillip.blenkinsopp at logica.com > To: xorp-users at xorp.org > Subject: Re: [Xorp-users] multicast using xorp > > Have you checked that the TTL of the traffic is sufficient? > > I've been frustrated by this when using VLC in the past because it was set to 1 causing all my traffic to be dropped and the TTL setting is quite well hidden in the UI. > > -----Original Message----- > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Bruce Simpson > Sent: 30 September 2009 17:14 > To: Fazlina Zuria Mohd Anuar > Cc: xorp-users at xorp.org > Subject: Re: [Xorp-users] multicast using xorp > > Hi, > > Thanks for your question about XORP multicast support. > > > Fazlina Zuria Mohd Anuar wrote: > > > > I would like to ask some advice about configuring multicast network > > using xorp. > > > > I would like to multicast video streaming using vlc player between 2 > > xorp router. > > > > ... > > > > Both router using same setting & the multicast doesn?t working?please > > advice..TQ!!! > > > > > Your configuration looks OK off the top of my head. > > Have you checked that IP multicast forwarding cache entries are being > pushed to the Linux kernel? The place to look is /proc/net//ip_mr_cache/. > > Unfortunately I can't be of further help on this issue at the moment, > hopefully others on the list can help out. > > thanks, > BMS > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > Please help Logica to respect the environment by not printing this email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei, die Umwelt zu sch?tzen. / Por favor ajude a Logica a respeitar o ambiente nao imprimindo este correio electronico. > > > > This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. > _____ Make the most of what you can do on your PC and the Web, just the way you want. Windows Live No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.409 / Virus Database: 270.14.2/2408 - Release Date: 10/01/09 18:23:00 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091002/28defaa9/attachment-0001.html From bms at incunabulum.net Fri Oct 2 04:30:02 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 02 Oct 2009 12:30:02 +0100 Subject: [Xorp-users] HAVE_IPV6_MULTICAST never defined in XORP-1.7 on LINUX In-Reply-To: <4ABD59FD.1010201@candelatech.com> References: <4ABBCCEF.8030608@sipxx.com> <4ABBD9A5.2010906@incunabulum.net> <4ABBE930.4000104@sipxx.com> <4ABBF1CD.3030908@incunabulum.net> <4ABCFC5A.5000707@sipxx.com> <4ABD0866.40306@incunabulum.net> <4ABD2239.3040500@sipxx.com> <4ABD4910.6020207@incunabulum.net> <4ABD5503.8040704@sipxx.com> <4ABD59FD.1010201@candelatech.com> Message-ID: <4AC5E43A.20809@incunabulum.net> Committed (with fixups), thanks! From bms at incunabulum.net Fri Oct 2 04:53:30 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Fri, 02 Oct 2009 12:53:30 +0100 Subject: [Xorp-users] [PATCH]: prepend project libs search path instead of appending list In-Reply-To: <4ABE5797.40408@sipxx.com> References: <4ABE5797.40408@sipxx.com> Message-ID: <4AC5E9BA.5090909@incunabulum.net> Committed, thanks! From bms at incunabulum.net Tue Oct 6 06:31:35 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Tue, 06 Oct 2009 14:31:35 +0100 Subject: [Xorp-users] Away 7th Oct - 21st Oct Message-ID: <4ACB46B7.90707@incunabulum.net> Hi all, I'll be away on a trip in Scotland from 7th Oct - 21st Oct, getting a well needed rest, so will only have sporadic access to email during that time, and will be unavailable for support requests. I'll endeavour to respond to email in detail when I get back. A 1.7-RC for the community code beginning late November is a possibility, this is depending on how much of the XRL replacement work can be finished by then. thanks, BMS From greearb at candelatech.com Tue Oct 6 09:39:47 2009 From: greearb at candelatech.com (Ben Greear) Date: Tue, 06 Oct 2009 09:39:47 -0700 Subject: [Xorp-users] Away 7th Oct - 21st Oct In-Reply-To: <4ACB46B7.90707@incunabulum.net> References: <4ACB46B7.90707@incunabulum.net> Message-ID: <4ACB72D3.40300@candelatech.com> On 10/06/2009 06:31 AM, Bruce Simpson wrote: > Hi all, > > I'll be away on a trip in Scotland from 7th Oct - 21st Oct, getting > a well needed rest, so will only have sporadic access to email during > that time, and will be unavailable for support requests. I'll endeavour > to respond to email in detail when I get back. > A 1.7-RC for the community code beginning late November is a > possibility, this is depending on how much of the XRL replacement work > can be finished by then. Enjoy, and please ignore all my emails during that time :) Ben > > thanks, > BMS > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com From david at utopia.cable.nu Wed Oct 7 00:21:07 2009 From: david at utopia.cable.nu (David Balnaves) Date: Wed, 07 Oct 2009 18:21:07 +1100 Subject: [Xorp-users] questions about IPv6 get_link_local_address Message-ID: <1254900067.22816.18615.camel@eurocorp> Hi, I think last time I asked about this I was told that in recent version of XORP, ospfv3 should set the link local address automatically and shouldn't see the error: [ 2009/10/06 02:43:51 WARNING xorp_ospfv3:14690 OSPF +462 peer_manager.cc enabled ] link-local address must be configured on eth0/eth0 In linux I see: 2: eth0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether 00:16:3e:55:1c:62 brd ff:ff:ff:ff:ff:ff inet 192.168.1.123/25 brd 192.168.1.127 scope global eth0 inet6 fe80::216:3eff:fe55:1c62/64 scope link valid_lft forever preferred_lft forever I'm using the following test config: protocols { ospf6 0 { router-id: 192.168.1.123 ip-router-alert: false area 0.0.0.1 { area-type: "normal" interface eth0 { link-type: "broadcast" vif eth0 { priority: 128 hello-interval: 9 router-dead-interval: 45 interface-cost: 1 retransmit-interval: 5 transit-delay: 1 passive: false disable: false } } } } } interfaces { restore-original-config-on-shutdown: false interface eth0 { description: "" disable: false discard: false unreachable: false management: false vif eth0 { disable: false address 192.168.1.123 { prefix-length: 25 disable: false } address 2002:7bf3:179f:0:216:3eff:fe55:1c62 { prefix-length: 64 disable: false } } } } I've downloaded and built XORP 1.6 and I still seem to have the same problem. Sure, I can set the link-local address but this is undesirable for a few reasons and I figure its best done automatically. Am I right in understanding that xorp should grab the link-local address fe80::216:3eff:fe55:1c62 from linux via ifconfig/netlink/etc during startup? I've had a look through xrl_io.cc, and it appears that the following is responsible for getting the link local address for OSPFv3: template <> bool XrlIO::get_link_local_address(const string& interface, const string& vif, IPv6& address) { debug_msg("Interface %s Vif %s\n", interface.c_str(), vif.c_str()); const IfMgrVifAtom* fv = ifmgr_iftree().find_vif(interface, vif); if (fv == NULL) return false; IfMgrVifAtom::IPv6Map::const_iterator i; for (i = fv->ipv6addrs().begin(); i != fv->ipv6addrs().end(); i++) { if (i->second.addr().is_linklocal_unicast()) { address = i->second.addr(); return true; } } return false; } Am I right in understanding that ifmgr_iftree().find_vif(interface, vif) is getting the interfaces from the RIB, and then in turn looking at each address on the interface? Is anything from underlying linux interface configuration inherited by the RIB? Does this come back to the need for xorp to listen to RA? I'm not sure which part of the documentation to find this information. Any help/corrections appreciated. David Balnaves From karl at sipxx.com Wed Oct 7 09:27:12 2009 From: karl at sipxx.com (XORP at sipxx.com) Date: Wed, 07 Oct 2009 12:27:12 -0400 Subject: [Xorp-users] questions about IPv6 get_link_local_address In-Reply-To: <1254900067.22816.18615.camel@eurocorp> References: <1254900067.22816.18615.camel@eurocorp> Message-ID: <4ACCC160.8020308@sipxx.com> The only way I have been able to accomplish this (in 1.6 and 1.7) is by using the explicit default-system-config parameter in the interfaces { interface ...} definition. David Balnaves wrote: > Hi, > > I think last time I asked about this I was told that in recent version > of XORP, ospfv3 should set the link local address automatically and > shouldn't see the error: > [ 2009/10/06 02:43:51 WARNING xorp_ospfv3:14690 OSPF +462 > peer_manager.cc enabled ] link-local address must be configured on > eth0/eth0 > > In linux I see: > 2: eth0: mtu 1500 qdisc pfifo_fast > state UNKNOWN qlen 1000 > link/ether 00:16:3e:55:1c:62 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.123/25 brd 192.168.1.127 scope global eth0 > inet6 fe80::216:3eff:fe55:1c62/64 scope link > valid_lft forever preferred_lft forever > > I'm using the following test config: > protocols { > ospf6 0 { > router-id: 192.168.1.123 > ip-router-alert: false > area 0.0.0.1 { > area-type: "normal" > interface eth0 { > link-type: "broadcast" > vif eth0 { > priority: 128 > hello-interval: 9 > router-dead-interval: 45 > interface-cost: 1 > retransmit-interval: 5 > transit-delay: 1 > passive: false > disable: false > } > } > } > } > } > interfaces { > restore-original-config-on-shutdown: false > interface eth0 { > description: "" > disable: false > discard: false > unreachable: false > management: false > vif eth0 { > disable: false > address 192.168.1.123 { > prefix-length: 25 > disable: false > } > address 2002:7bf3:179f:0:216:3eff:fe55:1c62 { > prefix-length: 64 > disable: false > } > } > } > } > > > I've downloaded and built XORP 1.6 and I still seem to have the same > problem. Sure, I can set the link-local address but this is undesirable > for a few reasons and I figure its best done automatically. Am I right > in understanding that xorp should grab the link-local address > fe80::216:3eff:fe55:1c62 from linux via ifconfig/netlink/etc during > startup? > > I've had a look through xrl_io.cc, and it appears that the following is > responsible for getting the link local address for OSPFv3: > template <> > bool > XrlIO::get_link_local_address(const string& interface, const > string& vif, > IPv6& address) > { > debug_msg("Interface %s Vif %s\n", interface.c_str(), vif.c_str()); > > const IfMgrVifAtom* fv = ifmgr_iftree().find_vif(interface, vif); > if (fv == NULL) > return false; > > IfMgrVifAtom::IPv6Map::const_iterator i; > for (i = fv->ipv6addrs().begin(); i != fv->ipv6addrs().end(); i++) { > if (i->second.addr().is_linklocal_unicast()) { > address = i->second.addr(); > return true; > } > } > > return false; > } > > Am I right in understanding that ifmgr_iftree().find_vif(interface, vif) > is getting the interfaces from the RIB, and then in turn looking at each > address on the interface? Is anything from underlying linux interface > configuration inherited by the RIB? Does this come back to the need for > xorp to listen to RA? I'm not sure which part of the documentation to > find this information. Any help/corrections appreciated. > > David Balnaves > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > From greearb at candelatech.com Wed Oct 7 09:57:41 2009 From: greearb at candelatech.com (Ben Greear) Date: Wed, 07 Oct 2009 09:57:41 -0700 Subject: [Xorp-users] questions about IPv6 get_link_local_address In-Reply-To: <4ACCC160.8020308@sipxx.com> References: <1254900067.22816.18615.camel@eurocorp> <4ACCC160.8020308@sipxx.com> Message-ID: <4ACCC885.2090705@candelatech.com> On 10/07/2009 09:27 AM, XORP at sipxx.com wrote: > The only way I have been able to accomplish this (in 1.6 and 1.7) is by > using the explicit > default-system-config > parameter in the interfaces { interface ...} definition. > > > David Balnaves wrote: >> Hi, >> >> I think last time I asked about this I was told that in recent version >> of XORP, ospfv3 should set the link local address automatically and >> shouldn't see the error: >> [ 2009/10/06 02:43:51 WARNING xorp_ospfv3:14690 OSPF +462 >> peer_manager.cc enabled ] link-local address must be configured on >> eth0/eth0 I'll put this on my list of things to look at, but my list is long! Seems like we could probe this information easily enough if the user doesn't specify it, however... Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From karl at sipxx.com Wed Oct 7 18:10:07 2009 From: karl at sipxx.com (XORP at sipxx.com) Date: Wed, 07 Oct 2009 21:10:07 -0400 Subject: [Xorp-users] questions about IPv6 get_link_local_address In-Reply-To: <4ACCC885.2090705@candelatech.com> References: <1254900067.22816.18615.camel@eurocorp> <4ACCC160.8020308@sipxx.com> <4ACCC885.2090705@candelatech.com> Message-ID: <4ACD3BEF.6000507@sipxx.com> I am not so sure it really should do this totally automatically just because OSPFv3 requires a particular kind of address. So may other modules and this can become very non-transparent if each module just goes about acquiring its own parameters. This what the 'default-system-config' parameter really seems to be good for. What I would like to suggest however, is to provide additional qualifiers to this parameter so one can differentiate what kind of system configuration gets imported. so for example: .... default-system-config { address-link-local-ipv6: true address-link-local-ipv4: false address-ipv4: false address-ipv6: true } Ben Greear wrote: > On 10/07/2009 09:27 AM, XORP at sipxx.com wrote: >> The only way I have been able to accomplish this (in 1.6 and 1.7) is by >> using the explicit >> default-system-config >> parameter in the interfaces { interface ...} definition. >> >> >> David Balnaves wrote: >>> Hi, >>> >>> I think last time I asked about this I was told that in recent version >>> of XORP, ospfv3 should set the link local address automatically and >>> shouldn't see the error: >>> [ 2009/10/06 02:43:51 WARNING xorp_ospfv3:14690 OSPF +462 >>> peer_manager.cc enabled ] link-local address must be configured on >>> eth0/eth0 > > I'll put this on my list of things to look at, but my list is > long! Seems like we could probe this information easily enough > if the user doesn't specify it, however... > > Ben > From greearb at candelatech.com Wed Oct 7 20:03:39 2009 From: greearb at candelatech.com (Ben Greear) Date: Wed, 07 Oct 2009 20:03:39 -0700 Subject: [Xorp-users] questions about IPv6 get_link_local_address In-Reply-To: <4ACD3BEF.6000507@sipxx.com> References: <1254900067.22816.18615.camel@eurocorp> <4ACCC160.8020308@sipxx.com> <4ACCC885.2090705@candelatech.com> <4ACD3BEF.6000507@sipxx.com> Message-ID: <4ACD568B.8010604@candelatech.com> XORP at sipxx.com wrote: > I am not so sure it really should do this totally automatically just > because OSPFv3 requires a particular kind of address. So may other > modules and this can become very non-transparent if each module just > goes about acquiring its own parameters. > This what the 'default-system-config' parameter really seems to be good for. > What I would like to suggest however, is to provide additional > qualifiers to this parameter so one can differentiate what kind of > system configuration gets imported. > so for example: > .... > default-system-config { > address-link-local-ipv6: true > address-link-local-ipv4: false > address-ipv4: false > address-ipv6: true > } > How about we just probe for anything not specified by the user? We can do the probe in fea so all of the modules can get the same information. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From philip_romanov at yahoo.com Thu Oct 8 10:03:29 2009 From: philip_romanov at yahoo.com (Philip Romanov) Date: Thu, 8 Oct 2009 10:03:29 -0700 (PDT) Subject: [Xorp-users] XORP IGMPv2 <-> XORP IGMPv3 Message-ID: <598290.50482.qm@web52310.mail.re2.yahoo.com> Hello, I'm researching how XORP IGMP implementation behaves when it comes to v3/v2/v1 co-existence on the same network. I have IGMPv3 RFC3376 in front of me: 7.3. Multicast Router Behavior 7.3.1. In the Presence of Older Version Queriers IGMPv3 routers may be placed on a network where at least one router on the network has not yet been upgraded to IGMPv3. The following requirements apply: o If any older versions of IGMP are present on routers, the querier MUST use the lowest version of IGMP present on the network. This must be administratively assured; routers that desire to be compatible with IGMPv1 and IGMPv2 MUST have a configuration option to act in IGMPv1 or IGMPv2 compatibility modes. When in IGMPv1 mode, routers MUST send Periodic Queries with a Max Resp Code of 0 and truncated at the Group Address field (i.e., 8 bytes long), and MUST ignore Leave Group messages. They SHOULD also warn about receiving an IGMPv2 or IGMPv3 query, although such warnings MUST be rate-limited. When in IGMPv2 mode, routers MUST send Periodic Queries truncated at the Group Address field (i.e., 8 bytes long), and SHOULD also warn about receiving an IGMPv3 query (such warnings MUST be rate-limited). They also MUST fill in the Max Resp Time in the Max Resp Code field, i.e., the exponential algorithm described in section 4.1.1 is not used. o If a router is not explicitly configured to use IGMPv1 or IGMPv2 and hears an IGMPv1 Query or IGMPv2 General Query, it SHOULD log a warning. These warnings MUST be rate-limited. I placed two XORP routers on two PCs (connection is point-to-point), with relevant part of IGMP configuration being: XORP-1: igmp { interface eth1 { vif eth1 { disable: false version: 3 } } traceoptions { flag all { disable: false } } } XORP-2: igmp { interface eth1 { vif eth1 { disable: false version: 2 } } traceoptions { flag all { disable: false } } } I'm watching for IGMP protocol exchanges from one of the PCs with wireshark. I see that XORP-1 continues to send IGMPv3 queries while XORP-2 continues to send IGMPv2 queries. Furthermore, XORP-1 replies itself to queries using v3 and XORP-2 using v2 so I have a great mix of V2 and V3 request/response traffic on my network. It does not appear that XORP-1 downshifted into IGMPv2 compatibility mode. Question, I guess, would be if XORP supports downshifting into lower version IGMP compatibility modes as per RFC? Any configuration file options that I missed? I can provide pcap capture if needed. Regards, Philip Romanov From karl at sipxx.com Thu Oct 8 16:00:09 2009 From: karl at sipxx.com (XORP at sipxx.com) Date: Thu, 08 Oct 2009 19:00:09 -0400 Subject: [Xorp-users] questions about IPv6 get_link_local_address In-Reply-To: <4ACD568B.8010604@candelatech.com> References: <1254900067.22816.18615.camel@eurocorp> <4ACCC160.8020308@sipxx.com> <4ACCC885.2090705@candelatech.com> <4ACD3BEF.6000507@sipxx.com> <4ACD568B.8010604@candelatech.com> Message-ID: <4ACE6EF9.4060803@sipxx.com> That's a reasonable scenario, I suppose. If users need to specify a parameter, they can, and if they use the default-system-config in addition, they get the rest from default. There were some other issues with this parameter from my experimentation. If I have an interface in the configuration file that uses 'default-system-config' and nothing else, it works as expected. But then, if I remove the directive from xorpsh->configure and replace it with an address specification and commit the change, the address does not get configured, I had to save the configuration in a file and restart rtrmgr in order for it to get configured accordingly. This was for an IPv4 address. Ben Greear wrote: > XORP at sipxx.com wrote: >> I am not so sure it really should do this totally automatically just >> because OSPFv3 requires a particular kind of address. So may other >> modules and this can become very non-transparent if each module just >> goes about acquiring its own parameters. >> This what the 'default-system-config' parameter really seems to be >> good for. >> What I would like to suggest however, is to provide additional >> qualifiers to this parameter so one can differentiate what kind of >> system configuration gets imported. >> so for example: >> .... >> default-system-config { >> address-link-local-ipv6: true >> address-link-local-ipv4: false >> address-ipv4: false >> address-ipv6: true >> } >> > How about we just probe for anything not specified by the user? We > can do the probe > in fea so all of the modules can get the same information. > > Thanks, > Ben > From jorn_rikkers at hotmail.com Fri Oct 9 02:30:15 2009 From: jorn_rikkers at hotmail.com (Jorn Rikkers) Date: Fri, 9 Oct 2009 09:30:15 +0000 Subject: [Xorp-users] Can't enable MFEA Message-ID: Hi, Can someone help me to enable multicast forwarding in XORP. I'm using the CORE emulation tool on FreeBSD. Everything works fine but when I enable multicast forwarding I get an "Operation not supported" on setsockopt(MRT_INIT, 1), see log below. I appreciate your help. Kind regards, Jorn [ 2009/10/09 11:10:07 INFO xorp_fea MFEA ] MFEA enabled [ 2009/10/09 11:10:07 INFO xorp_fea MFEA ] CLI enabled [ 2009/10/09 11:10:07 INFO xorp_fea MFEA ] CLI started [ 2009/10/09 11:10:07 INFO xorp_fea MFEA ] MFEA enabled [ 2009/10/09 11:10:07 INFO xorp_fea MFEA ] CLI enabled [ 2009/10/09 11:10:07 INFO xorp_fea MFEA ] CLI started [ 2009/10/09 11:10:08 INFO xorp_fea MFEA ] MFEA enabled [ 2009/10/09 11:10:08 INFO xorp_fea MFEA ] CLI enabled [ 2009/10/09 11:10:08 INFO xorp_fea MFEA ] CLI started [ 2009/10/09 11:10:08 INFO xorp_fea MFEA ] MFEA enabled [ 2009/10/09 11:10:08 INFO xorp_fea MFEA ] CLI enabled [ 2009/10/09 11:10:08 INFO xorp_fea MFEA ] CLI started [ 2009/10/09 11:10:08 INFO xorp_rtrmgr:2390 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/10/09 11:10:09 INFO xorp_rtrmgr:2396 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/10/09 11:10:12 INFO xorp_rtrmgr:2390 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/10/09 11:10:13 INFO xorp_rtrmgr:2396 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/10/09 11:10:16 INFO xorp_rtrmgr:2390 RTRMGR +101 module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea) [ 2009/10/09 11:10:16 INFO xorp_fea MFEA ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.0.0.1 subnet: 10.0.0.0/24 broadcast: 10.0.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/10/09 11:10:16 INFO xorp_fea MFEA ] Interface added: Vif[eth1] pif_index: 3 vif_index: 1 addr: 10.0.1.2 subnet: 10.0.1.0/24 broadcast: 10.0.1.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/10/09 11:10:16 ERROR xorp_fea:2405 MFEA +709 mfea_mrouter.cc start_mrt ] setsockopt(MRT_INIT, 1) failed: Operation not supported [ 2009/10/09 11:10:16 INFO xorp_fea MFEA ] MFEA started [ 2009/10/09 11:10:16 INFO xorp_fea MFEA ] Interface enabled Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.0.0.1 subnet: 10.0.0.0/24 broadcast: 10.0.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/10/09 11:10:16 ERROR xorp_fea:2405 MFEA +1113 mfea_mrouter.cc add_multicast_vif ] setsockopt(MRT_ADD_VIF, vif eth0) failed: Operation not supported [ 2009/10/09 11:10:16 ERROR xorp_fea:2405 MFEA +1191 mfea_node.cc start_vif ] Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2009/10/09 11:10:16 WARNING xorp_fea XrlMfeaTarget ] Handling method for mfea/0.1/start_vif failed: XrlCmdError 102 Command failed Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2009/10/09 11:10:16 ERROR xorp_rtrmgr:2390 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2009/10/09 11:10:16 ERROR xorp_rtrmgr:2390 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2009/10/09 11:10:16 INFO xorp_rtrmgr:2390 RTRMGR +2233 task.cc run_task ] No more tasks to run [ 2009/10/09 11:10:16 INFO xorp_rtrmgr:2390 RTRMGR +176 module_manager.cc terminate ] Terminating module: fea [ 2009/10/09 11:10:16 INFO xorp_rtrmgr:2390 RTRMGR +176 module_manager.cc terminate ] Terminating module: firewall [ 2009/10/09 11:10:16 INFO xorp_rtrmgr:2390 RTRMGR +176 module_manager.cc terminate ] Terminating module: interfaces [ 2009/10/09 11:10:16 INFO xorp_rtrmgr:2390 RTRMGR +176 module_manager.cc terminate ] Terminating module: mfea4 [ 2009/10/09 11:10:16 INFO xorp_rtrmgr:2390 RTRMGR +199 module_manager.cc terminate ] Killing module: mfea4 [ 2009/10/09 11:10:16 ERROR xorp_rtrmgr:2390 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/fea/xorp_fea": terminated with signal 15. [ 2009/10/09 11:10:16 INFO xorp_rtrmgr:2390 RTRMGR +287 module_manager.cc module_exited ] Module killed during shutdown: mfea4 [ 2009/10/09 11:10:17 INFO xorp_rtrmgr:2396 RTRMGR +101 module_manager.cc execute ] Executing module: mfea4 (fea/xorp_fea) [ 2009/10/09 11:10:17 INFO xorp_fea MFEA ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.0.0.2 subnet: 10.0.0.0/24 broadcast: 10.0.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/10/09 11:10:17 INFO xorp_fea MFEA ] Interface added: Vif[eth1] pif_index: 3 vif_index: 1 addr: 10.0.2.1 subnet: 10.0.2.0/24 broadcast: 10.0.2.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2009/10/09 11:10:17 ERROR xorp_fea:2414 MFEA +709 mfea_mrouter.cc start_mrt ] setsockopt(MRT_INIT, 1) failed: Operation not supported [ 2009/10/09 11:10:17 INFO xorp_fea MFEA ] MFEA started [ 2009/10/09 11:10:17 INFO xorp_fea MFEA ] Interface enabled Vif[eth0] pif_index: 2 vif_index: 0 addr: 10.0.0.2 subnet: 10.0.0.0/24 broadcast: 10.0.0.255 peer: 0.0.0.0 Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv4 ENABLED [ 2009/10/09 11:10:17 ERROR xorp_fea:2414 MFEA +1113 mfea_mrouter.cc add_multicast_vif ] setsockopt(MRT_ADD_VIF, vif eth0) failed: Operation not supported [ 2009/10/09 11:10:17 ERROR xorp_fea:2414 MFEA +1191 mfea_node.cc start_vif ] Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2009/10/09 11:10:17 WARNING xorp_fea XrlMfeaTarget ] Handling method for mfea/0.1/start_vif failed: XrlCmdError 102 Command failed Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2009/10/09 11:10:17 ERROR xorp_rtrmgr:2396 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2009/10/09 11:10:17 ERROR xorp_rtrmgr:2396 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2009/10/09 11:10:17 INFO xorp_rtrmgr:2396 RTRMGR +2233 task.cc run_task ] No more tasks to run [ 2009/10/09 11:10:17 INFO xorp_rtrmgr:2396 RTRMGR +176 module_manager.cc terminate ] Terminating module: fea [ 2009/10/09 11:10:17 INFO xorp_rtrmgr:2396 RTRMGR +176 module_manager.cc terminate ] Terminating module: firewall [ 2009/10/09 11:10:17 INFO xorp_rtrmgr:2396 RTRMGR +176 module_manager.cc terminate ] Terminating module: interfaces [ 2009/10/09 11:10:17 INFO xorp_rtrmgr:2396 RTRMGR +176 module_manager.cc terminate ] Terminating module: mfea4 [ 2009/10/09 11:10:17 INFO xorp_rtrmgr:2396 RTRMGR +199 module_manager.cc terminate ] Killing module: mfea4 [ 2009/10/09 11:10:17 ERROR xorp_rtrmgr:2396 RTRMGR +754 module_manager.cc done_cb ] Command "/usr/local/xorp/fea/xorp_fea": terminated with signal 15. [ 2009/10/09 11:10:17 INFO xorp_rtrmgr:2396 RTRMGR +287 module_manager.cc module_exited ] Module killed during shutdown: mfea4 _________________________________________________________________ Nieuw: onbeperkte opslagruimte in Windows Live Hotmail http://mail.live.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091009/39608856/attachment.html From david at utopia.cable.nu Fri Oct 9 03:35:30 2009 From: david at utopia.cable.nu (David Balnaves) Date: Fri, 9 Oct 2009 21:35:30 +1100 Subject: [Xorp-users] questions about IPv6 get_link_local_address In-Reply-To: <4ACE6EF9.4060803@sipxx.com> References: <1254900067.22816.18615.camel@eurocorp> <4ACCC160.8020308@sipxx.com><4ACCC885.2090705@candelatech.com> <4ACD3BEF.6000507@sipxx.com><4ACD568B.8010604@candelatech.com> <4ACE6EF9.4060803@sipxx.com> Message-ID: <3B338C3B6BE34E4685F174C66132DD03@gamma> Hi, Just a quick thanks as I found "default-system-config" addressed my issue with setting the link-local address. All the IPv6 implementations(linux, cisco, windows) I've seen sets a link-local address automatically on the interface when the interface is brought up. I think considering this should always be available, having XORP OSPFv3 probe for the link local address makes sense. Its also the behaviour of the "other" OSPFv3 implementation for linux. I've also noticed that since setting "default-system-config", the IPv6 address assigned to the interface via RA has disappeared. This may simply be because linux IPv6 forwarding has been enabled with XORP OSPFv3 becoming active. I don't recall this happening when I manually set the link-local address within XORP(and I dont know how it should deal with this). From what I remember, the RFC states that a "router" (ie: host with ipv6 forwarding enabled) should not use addresses provided by RA. David Balnaves ----- Original Message ----- From: "XORP at sipxx.com" To: Sent: Friday, October 09, 2009 10:00 AM Subject: Re: [Xorp-users] questions about IPv6 get_link_local_address > That's a reasonable scenario, I suppose. If users need to specify a > parameter, they can, and if they use the default-system-config in > addition, they get the rest from default. > > There were some other issues with this parameter from my experimentation. > If I have an interface in the configuration file that uses > 'default-system-config' and nothing else, it works as expected. > But then, if I remove the directive from xorpsh->configure and replace > it with an address specification and commit the change, the address does > not get configured, I had to save the configuration in a file and > restart rtrmgr in order for it to get configured accordingly. This was > for an IPv4 address. > > > Ben Greear wrote: >> XORP at sipxx.com wrote: >>> I am not so sure it really should do this totally automatically just >>> because OSPFv3 requires a particular kind of address. So may other >>> modules and this can become very non-transparent if each module just >>> goes about acquiring its own parameters. >>> This what the 'default-system-config' parameter really seems to be >>> good for. >>> What I would like to suggest however, is to provide additional >>> qualifiers to this parameter so one can differentiate what kind of >>> system configuration gets imported. >>> so for example: >>> .... >>> default-system-config { >>> address-link-local-ipv6: true >>> address-link-local-ipv4: false >>> address-ipv4: false >>> address-ipv6: true >>> } >>> >> How about we just probe for anything not specified by the user? We >> can do the probe >> in fea so all of the modules can get the same information. >> >> Thanks, >> Ben >> > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > From karl at sipxx.com Fri Oct 9 08:45:12 2009 From: karl at sipxx.com (XORP at sipxx.com) Date: Fri, 09 Oct 2009 11:45:12 -0400 Subject: [Xorp-users] questions about IPv6 get_link_local_address In-Reply-To: <3B338C3B6BE34E4685F174C66132DD03@gamma> References: <1254900067.22816.18615.camel@eurocorp> <4ACCC160.8020308@sipxx.com><4ACCC885.2090705@candelatech.com> <4ACD3BEF.6000507@sipxx.com><4ACD568B.8010604@candelatech.com> <4ACE6EF9.4060803@sipxx.com> <3B338C3B6BE34E4685F174C66132DD03@gamma> Message-ID: <4ACF5A88.60903@sipxx.com> Yes, routers must disregard RA messages. That said, I have found that an xorp router doesn't always do that. If the router has two interfaces on a link that gets RAs from another router, and only one of them is in the ospf6 configuration, the RA received on the second port will still cause a default route to be set, despite the fact that both interfaces are configured in the interfaces section and fea-unicast-forwarding is set. For some reason in this case, the forwarding flag for the interface doesn't get set but the 'all' flag is set. I think this is a bug, because I would have to enable another routing protocol on the port (I presume) to disable the RA. Placing the interface in the interfaces section and having fea->unicast-forwarding6 set should prevent the acceptance of the RA on all interfaces, IMHO. I believe if I manually set the forwarding flag on the second interface, RAs are ignored. This testing was done on a Centos 5.3 virtual machine. And, yes, all IPv6 stacks allocate the link-local address automatically, since it's a required feature for the IPv6 stack to operate fully. Regarding the automatic recognition, I can imagine cases were an operator may want to assign an address and not use the default provided. David Balnaves wrote: > Hi, > > Just a quick thanks as I found "default-system-config" addressed my issue > with setting the link-local address. > > All the IPv6 implementations(linux, cisco, windows) I've seen sets a > link-local address automatically on the interface when the interface is > brought up. I think considering this should always be available, having > XORP OSPFv3 probe for the link local address makes sense. Its also the > behaviour of the "other" OSPFv3 implementation for linux. > > I've also noticed that since setting "default-system-config", the IPv6 > address assigned to the interface via RA has disappeared. This may simply > be because linux IPv6 forwarding has been enabled with XORP OSPFv3 becoming > active. I don't recall this happening when I manually set the link-local > address within XORP(and I dont know how it should deal with this). From > what I remember, the RFC states that a "router" (ie: host with ipv6 > forwarding enabled) should not use addresses provided by RA. > > David Balnaves > > ----- Original Message ----- > From: "XORP at sipxx.com" > To: > Sent: Friday, October 09, 2009 10:00 AM > Subject: Re: [Xorp-users] questions about IPv6 get_link_local_address > > > >> That's a reasonable scenario, I suppose. If users need to specify a >> parameter, they can, and if they use the default-system-config in >> addition, they get the rest from default. >> >> There were some other issues with this parameter from my experimentation. >> If I have an interface in the configuration file that uses >> 'default-system-config' and nothing else, it works as expected. >> But then, if I remove the directive from xorpsh->configure and replace >> it with an address specification and commit the change, the address does >> not get configured, I had to save the configuration in a file and >> restart rtrmgr in order for it to get configured accordingly. This was >> for an IPv4 address. >> >> >> Ben Greear wrote: >> >>> XORP at sipxx.com wrote: >>> >>>> I am not so sure it really should do this totally automatically just >>>> because OSPFv3 requires a particular kind of address. So may other >>>> modules and this can become very non-transparent if each module just >>>> goes about acquiring its own parameters. >>>> This what the 'default-system-config' parameter really seems to be >>>> good for. >>>> What I would like to suggest however, is to provide additional >>>> qualifiers to this parameter so one can differentiate what kind of >>>> system configuration gets imported. >>>> so for example: >>>> .... >>>> default-system-config { >>>> address-link-local-ipv6: true >>>> address-link-local-ipv4: false >>>> address-ipv4: false >>>> address-ipv6: true >>>> } >>>> >>>> >>> How about we just probe for anything not specified by the user? We >>> can do the probe >>> in fea so all of the modules can get the same information. >>> >>> Thanks, >>> Ben >>> >>> >> _______________________________________________ >> Xorp-users mailing list >> Xorp-users at xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >> >> > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > From jet at gala.net Fri Oct 9 09:00:09 2009 From: jet at gala.net (Andriy Beregovenko) Date: Fri, 9 Oct 2009 19:00:09 +0300 Subject: [Xorp-users] Interface routing Message-ID: <44ba60c50910090900q71bc98a8o21d5ad6890692236@mail.gmail.com> Hello. I have some issue with understanding how to configure xorp-1.6 Default route do not want to apply. Here is configuration: jet at test_vz# show interfaces interface venet0 vif venet0 { address 172.20.0.202 { prefix-length: 32 } } [edit] jet at test_vz# show protocols static route 0.0.0.0/0 { next-hop: 192.0.2.1 } interface-route 192.0.2.1/32 { next-hop-interface: "venet0" next-hop-vif: "venet0" } [edit] jet at test_vz# exit jet at test_vz> show route table ipv4 unicast final 172.20.0.202/32 [connected(0)/0] > via venet0/venet0 192.0.2.1/32 [static(1)/1] > to 172.20.0.202 via venet0/venet0 jet at test_vz> This is almost all configuration... Please help me with my issue, coz i can not understand what is wrong in conf.... From fazlina at sapura.com.my Sun Oct 11 20:16:21 2009 From: fazlina at sapura.com.my (Fazlina Zuria Mohd Anuar) Date: Mon, 12 Oct 2009 11:16:21 +0800 Subject: [Xorp-users] start-up xorp in ubuntu OS Message-ID: <000301ca4aea$5f4599c0$1dd0cd40$@com.my> Hello! I would to ask is there anyone know how to auto start-up xorp automatically after boot up the Ubuntu OS? For now, I just start the xorp using command line. Thanks. Faz -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091012/8aa78427/attachment.html From luca.belforte at student.uclouvain.be Mon Oct 12 00:43:42 2009 From: luca.belforte at student.uclouvain.be (Luca Belforte) Date: Mon, 12 Oct 2009 09:43:42 +0200 Subject: [Xorp-users] Xorp + Click userlevel error connecting to Socket Message-ID: <4AD2DE2E.4030505@student.uclouvain.be> Hello, I'm trying to launch XORP 1.6 with click (1.6 or 1.4.3) but i have the following errors, and the process don't start. with click 1.6: [ 2009/10/10 00:50:14 INFO xorp_rtrmgr:2534 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea [ 2009/10/10 00:50:14 INFO xorp_rtrmgr:2534 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2009/10/10 00:50:15 INFO xorp_fea MFEA ] MFEA enabled [ 2009/10/10 00:50:15 INFO xorp_fea MFEA ] CLI enabled [ 2009/10/10 00:50:15 INFO xorp_fea MFEA ] CLI started [ 2009/10/10 00:50:15 INFO xorp_fea MFEA ] MFEA enabled [ 2009/10/10 00:50:15 INFO xorp_fea MFEA ] CLI enabled [ 2009/10/10 00:50:15 INFO xorp_fea MFEA ] CLI started [ 2009/10/10 00:50:16 INFO xorp_rtrmgr:2534 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/10/10 00:50:20 INFO xorp_rtrmgr:2534 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/10/10 00:50:24 ERROR xorp_fea:2535 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 13000): Connection refused [ 2009/10/10 00:50:24 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... [ 2009/10/10 00:50:24 ERROR xorp_fea:2535 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 13000): Connection refused [ 2009/10/10 00:50:24 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... [ 2009/10/10 00:50:24 ERROR xorp_fea:2535 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 13000): Connection refused [ 2009/10/10 00:50:24 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... [ 2009/10/10 00:50:25 ERROR xorp_fea:2535 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 13000): Connection refused [ 2009/10/10 00:50:25 WARNING xorp_fea XrlFeaTarget ] Handling method for fea_click/0.1/start_click failed: XrlCmdError 102 Command failed Could not open user-level Click socket: Connection refused [ 2009/10/10 00:50:25 ERROR xorp_rtrmgr:2534 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Could not open user-level Click socket: Connection refused [ 2009/10/10 00:50:25 ERROR xorp_rtrmgr:2534 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Could not open user-level Click socket: Connection refused [ 2009/10/10 00:50:25 INFO xorp_rtrmgr:2534 RTRMGR +2233 task.cc run_task ] No more tasks to run [ 2009/10/10 00:50:25 INFO xorp_rtrmgr:2534 RTRMGR +176 module_manager.cc terminate ] Terminating module: fea [ 2009/10/10 00:50:25 INFO xorp_rtrmgr:2534 RTRMGR +176 module_manager.cc terminate ] Terminating module: firewall [ 2009/10/10 00:50:25 INFO xorp_rtrmgr:2534 RTRMGR +176 module_manager.cc terminate ] Terminating module: interfaces [ 2009/10/10 00:50:25 INFO xorp_rtrmgr:2534 RTRMGR +199 module_manager.cc terminate ] Killing module: interfaces [ 2009/10/10 00:50:25 ERROR xorp_rtrmgr:2534 RTRMGR +754 module_manager.cc done_cb ] Command "/home/belfo/xorp/fea/xorp_fea": terminated with signal 15. [ 2009/10/10 00:50:25 INFO xorp_rtrmgr:2534 RTRMGR +287 module_manager.cc module_exited ] Module killed during shutdown: interfaces with click 1.4.3 [ 2009/10/10 00:52:14 INFO xorp_rtrmgr:2551 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, firewall, fea [ 2009/10/10 00:52:14 INFO xorp_rtrmgr:2551 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2009/10/10 00:52:15 INFO xorp_fea MFEA ] MFEA enabled [ 2009/10/10 00:52:15 INFO xorp_fea MFEA ] CLI enabled [ 2009/10/10 00:52:15 INFO xorp_fea MFEA ] CLI started [ 2009/10/10 00:52:15 INFO xorp_fea MFEA ] MFEA enabled [ 2009/10/10 00:52:15 INFO xorp_fea MFEA ] CLI enabled [ 2009/10/10 00:52:15 INFO xorp_fea MFEA ] CLI started [ 2009/10/10 00:52:16 INFO xorp_rtrmgr:2551 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2009/10/10 00:52:20 INFO xorp_rtrmgr:2551 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2009/10/10 00:52:24 ERROR xorp_fea:2552 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 13000): Connection refused [ 2009/10/10 00:52:24 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... [ 2009/10/10 00:52:24 ERROR xorp_fea:2552 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 13000): Connection refused [ 2009/10/10 00:52:24 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... [ 2009/10/10 00:52:24 ERROR xorp_fea:2552 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 13000): Connection refused [ 2009/10/10 00:52:24 WARNING xorp_fea FEA ] Could not open user-level Click socket: Connection refused. Trying again... [ 2009/10/10 00:52:25 ERROR xorp_fea:2552 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 13000): Connection refused [ 2009/10/10 00:52:25 WARNING xorp_fea XrlFeaTarget ] Handling method for fea_click/0.1/start_click failed: XrlCmdError 102 Command failed Could not open user-level Click socket: Connection refused [ 2009/10/10 00:52:25 ERROR xorp_rtrmgr:2551 RTRMGR +691 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Could not open user-level Click socket: Connection refused [ 2009/10/10 00:52:25 ERROR xorp_rtrmgr:2551 RTRMGR +261 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Could not open user-level Click socket: Connection refused [ 2009/10/10 00:52:25 INFO xorp_rtrmgr:2551 RTRMGR +2233 task.cc run_task ] No more tasks to run [ 2009/10/10 00:52:25 INFO xorp_rtrmgr:2551 RTRMGR +176 module_manager.cc terminate ] Terminating module: fea [ 2009/10/10 00:52:25 INFO xorp_rtrmgr:2551 RTRMGR +176 module_manager.cc terminate ] Terminating module: firewall [ 2009/10/10 00:52:25 INFO xorp_rtrmgr:2551 RTRMGR +176 module_manager.cc terminate ] Terminating module: interfaces [ 2009/10/10 00:52:25 INFO xorp_rtrmgr:2551 RTRMGR +199 module_manager.cc terminate ] Killing module: interfaces [ 2009/10/10 00:52:25 ERROR xorp_rtrmgr:2551 RTRMGR +754 module_manager.cc done_cb ] Command "/home/belfo/xorp/fea/xorp_fea": terminated with signal 15. [ 2009/10/10 00:52:25 INFO xorp_rtrmgr:2551 RTRMGR +287 module_manager.cc module_exited ] Module killed during shutdown: interfaces i use a really simple xorp config script, the default one, were i modified only click path informations. here it is: /* $XORP: xorp/rtrmgr/config/click.boot,v 1.1 2007/08/29 06:49:43 pavlin Exp $ */ interfaces { interface eth2 { vif eth2 { address 10.10.10.10 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false } click { /* * The Click forwarding path. * http://www.read.cs.ucla.edu/click/ */ disable: false /* * Set duplicate-routes-to-kernel to true if the XORP routes * added to Click should be added to the system kernel as well. */ duplicate-routes-to-kernel: false /* * 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 * generators. Otherwise, a single common generator * wouldn't know whether to generate configuration for kernel-level * Click or for user-level Click. */ kernel-click { disable: true install-on-startup: true 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: "/usr/local/xorp/fea/xorp_fea_click_config_generator" } user-click { disable: false command-file: "/home/belfo/click/userlevel/click" /* * Note: don't add "-p " as an extra argument, because it * will be in 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: "/dell/null" user-click-config-generator-file: "/home/belfo/xorp/fea/xorp_fea_click_config_generator" } } } what I'm missing? I'm using ubuntu-server 9.04 in virtual box thanks Luca _______________________________________________ click mailing list click at amsterdam.lcs.mit.edu https://amsterdam.lcs.mit.edu/mailman/listinfo/click From jet at gala.net Mon Oct 12 04:13:42 2009 From: jet at gala.net (Andriy Beregovenko) Date: Mon, 12 Oct 2009 14:13:42 +0300 Subject: [Xorp-users] Basic BGP configuration Message-ID: <44ba60c50910120413u1add5a53o43e302b0d989d209@mail.gmail.com> Hello. I install & configure xorp-1.6 (under debian squeeze). > show bgp routes summary Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ------ ------- ---- ------- * 77.x.x.0/21 10.7.10.7 89.x.x.x 65307 i * 89.x.x.0/20 10.7.10.7 89.x.x.x 65307 i * 193.x.x.0/22 10.7.10.7 89.x.x.x 65307 i * 195.x.x.0/23 10.7.10.7 89.x.x.x 65307 i As you can see, i received routes from remote peer and it is valid. But as you can see it is not best. some detail: > show bgp routes detail 77.x.x.0/21 From peer: 89.x.x.x Route: Not Used Origin: IGP AS Path: 65307 Nexthop: 10.7.10.7 ................. Why this route is "Not Used" status ? Configuration very simple, with minimal parameters. From jorn_rikkers at hotmail.com Tue Oct 13 04:34:32 2009 From: jorn_rikkers at hotmail.com (Jorn Rikkers) Date: Tue, 13 Oct 2009 11:34:32 +0000 Subject: [Xorp-users] Can't enable MFEA In-Reply-To: References: Message-ID: >Hi, >Can someone help me to enable multicast forwarding in XORP. I'm using the CORE emulation tool on FreeBSD. Everything works fine but when I enable multicast forwarding I get an "Operation not supported" on setsockopt(MRT_INIT, 1), see log below. according to: http://mailman.icsi.berkeley.edu/pipermail/xorp-announce/2005.txt PIM-SM: - If the kernel does not support PIM-SM, or if PIM-SM is not enabled in the kernel, then running PIM-SM will fail with the following error message: [ 2004/06/12 10:26:41 ERROR xorp_fea:444 MFEA +529 mfea_mrouter.cc start_mrt ] setsockopt(MRT_INIT, 1) failed: Operation not supported >I appreciate your help. >Kind regards, >Jorn _________________________________________________________________ Windows werkt zelfs voor je studie http://www.windows.nl/Theme.aspx?id=2 From naresh_raga at yahoo.co.in Wed Oct 14 04:46:33 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Wed, 14 Oct 2009 17:16:33 +0530 (IST) Subject: [Xorp-users] Problem with scons build in xorp 1.7-WIP Message-ID: <122752.60734.qm@web94808.mail.in2.yahoo.com> Hi bruce and jtc, After long time I am again working on this.As you said i have crosscompiled openssl 0.9.8,it has generated libcrypto.a and libssl.a in lib folder.Also it has openssl header files in include folder. I have copied them in /opt/local/??? folder,the path in which xorp is searching for libraries and include files.But even then it is resulting in errors as below: /opt/crosstool/arm-linux/gcc-3.3.4-glibc-2.3.2/bin/arm-linux-g++ -o obj/i686-pc-linux-gnu/libxipc/call_xrl -Wl,-rpath=/home/student/Desktop/xorp1.7/install/lib obj/i686-pc-linux-gnu/libxipc/call_xrl.o -L/usr/sfw/lib -L/opt/local/lib -L/usr/local/lib -Lobj/i686-pc-linux-gnu/libxipc -Llibxipc -Lobj/i686-pc-linux-gnu/libcomm -Llibcomm -Lobj/i686-pc-linux-gnu/libxorp -Llibxorp -lrt -lresolv -lcrypto -ldl -lfinder -lxipc -lcomm -lxorp obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x34): In function `hmac_md5': libxipc/hmac_md5.c:63: undefined reference to `MD5_Init' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x48):libxipc/hmac_md5.c:64: undefined reference to `MD5_Update' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x5c):libxipc/hmac_md5.c:65: undefined reference to `MD5_Final' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x158):libxipc/hmac_md5.c:96: undefined reference to `MD5_Init' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x170):libxipc/hmac_md5.c:97: undefined reference to `MD5_Update' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x184):libxipc/hmac_md5.c:98: undefined reference to `MD5_Update' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x194):libxipc/hmac_md5.c:99: undefined reference to `MD5_Final' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x1a0):libxipc/hmac_md5.c:103: undefined reference to `MD5_Init' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x1b8):libxipc/hmac_md5.c:104: undefined reference to `MD5_Update' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x1cc):libxipc/hmac_md5.c:105: undefined reference to `MD5_Update' obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x1dc):libxipc/hmac_md5.c:106: undefined reference to `MD5_Final' collect2: ld returned 1 exit status scons: *** [obj/i686-pc-linux-gnu/libxipc/call_xrl] Error 1 scons: building terminated because of errors. Previously with gnu build system while configuring itself it had option like ./configure --host=${CROSS_ARCH} --with-openssl=${CROSS_ROOT_ARCH}/usr/local/ssl to build with openssl .But now what I have done? is ,I have copied total ${CROSS_ROOT_ARCH}/usr/local/ssl folder contents which had openssl header files in include folder and libcrypto.a and libssl.a in lib folder into /opt/local/???? folder (the path it is searching for libraries and header files as prompted by xorp). Is the above approach is right.Is /opt/local is the correct folder from where xorp fetches libraries.What's wrong in the above approach.Could you please suggest me. Regards, Naresh. Try the new Yahoo! India Homepage. Click here. http://in.yahoo.com/trynew -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091014/19b30c9f/attachment.html From jtc at acorntoolworks.com Wed Oct 14 07:05:15 2009 From: jtc at acorntoolworks.com (J.T. Conklin) Date: Wed, 14 Oct 2009 07:05:15 -0700 Subject: [Xorp-users] Problem with scons build in xorp 1.7-WIP In-Reply-To: <122752.60734.qm@web94808.mail.in2.yahoo.com> (naresh raga's message of "Wed, 14 Oct 2009 17:16:33 +0530 (IST)") References: <122752.60734.qm@web94808.mail.in2.yahoo.com> Message-ID: <87eip6vzok.fsf@orac.acorntoolworks.com> naresh raga writes: > After long time I am again working on this.As you said i have > crosscompiled openssl 0.9.8,it has generated libcrypto.a and > libssl.a in lib folder.Also it has openssl header files in include > folder. I have copied them in /opt/local/??? folder,the path in > which xorp is searching for libraries and include files.But even > then it is resulting in errors as below: > > /opt/crosstool/arm-linux/gcc-3.3.4-glibc-2.3.2/bin/arm-linux-g++ -o obj/i686-pc-linux-gnu/libxipc/call_xrl -Wl,-rpath=/home/student/Desktop/xorp1.7/install/lib obj/i686-pc-linux-gnu/libxipc/call_xrl.o -L/usr/sfw/lib -L/opt/local/lib -L/usr/local/lib -Lobj/i686-pc-linux-gnu/libxipc -Llibxipc -Lobj/i686-pc-linux-gnu/libcomm -Llibcomm -Lobj/i686-pc-linux-gnu/libxorp -Llibxorp -lrt -lresolv -lcrypto -ldl -lfinder -lxipc -lcomm -lxorp > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x34): In function `hmac_md5': > libxipc/hmac_md5.c:63: undefined reference to `MD5_Init' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x48):libxipc/hmac_md5.c:64: undefined reference to `MD5_Update' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x5c):libxipc/hmac_md5.c:65: undefined reference to `MD5_Final' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x158):libxipc/hmac_md5.c:96: undefined reference to `MD5_Init' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x170):libxipc/hmac_md5.c:97: undefined reference to `MD5_Update' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x184):libxipc/hmac_md5.c:98: undefined reference to `MD5_Update' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x194):libxipc/hmac_md5.c:99: undefined reference to `MD5_Final' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x1a0):libxipc/hmac_md5.c:103: undefined reference to `MD5_Init' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x1b8):libxipc/hmac_md5.c:104: undefined reference to `MD5_Update' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x1cc):libxipc/hmac_md5.c:105: undefined reference to `MD5_Update' > obj/i686-pc-linux-gnu/libxipc/libxipc.a(hmac_md5.o)(.text+0x1dc):libxipc/hmac_md5.c:106: undefined reference to `MD5_Final' > collect2: ld returned 1 exit status > scons: *** [obj/i686-pc-linux-gnu/libxipc/call_xrl] Error 1 > scons: building terminated because of errors. Hi Naresh, I suspect the problem is the location of the -lcrypto in the link line. The GNU linker is a single pass linker, so when it process static library archives, it only adds objects if there is a pending unresolved reference. In this case, -lxipc (libxipc.a) has the unresolved reference, but it is after -lcrypto. Can you manually run the above command line, moving -lcrypto last? If this completes your build, I'll see what needs to be done to reorder the libraries. Don't give up hope, you're real close... --jtc -- J.T. Conklin From naresh_raga at yahoo.co.in Wed Oct 14 09:03:27 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Wed, 14 Oct 2009 21:33:27 +0530 (IST) Subject: [Xorp-users] Problem with scons build in xorp 1.7-WIP In-Reply-To: <87eip6vzok.fsf@orac.acorntoolworks.com> Message-ID: <105932.68400.qm@web94807.mail.in2.yahoo.com> Hi Naresh, I suspect the problem is the location of the -lcrypto in the link line.? The GNU linker is a single pass linker, so when it process static library archives, it only adds objects if there is a pending unresolved reference. In this case, -lxipc (libxipc.a) has the unresolved reference, but it is after -lcrypto. Can you manually run the above command line, moving -lcrypto last? If this completes your build, I'll see what needs to be done to reorder the libraries. Don't give up hope, you're real close... ? ? --jtc -- J.T. Conklin Hi jtc, What you said was right.I have moved -lcrypto last and have run the command line manually,it has not resulted in any error.It has successfully created the executable call_xrl.So,please jtc reorder the libraries. Thanks, Naresh. Add whatever you love to the Yahoo! India homepage. Try now! http://in.yahoo.com/trynew -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091014/c9dbd63d/attachment.html From luca.belforte at student.uclouvain.be Thu Oct 15 03:04:53 2009 From: luca.belforte at student.uclouvain.be (Luca Belforte) Date: Thu, 15 Oct 2009 12:04:53 +0200 Subject: [Xorp-users] Loopback address Message-ID: <4AD6F3C5.9070500@student.uclouvain.be> I'm trying to set up a loopback address on my routers, used instead of the address of an interface, in case a link will not work. But i can't find how do it, i modified the lo address, but the address is not "forwarder" to other routers, so i can't ping it. in cisco we can do like this: interface Loopback0 description "*** Loopback ***" no ip address ipv4 address 10.0.1.1/32 ipv4 ospf area 0 exit How i can set up the same in Xorp? Thanks Luca From jtc at acorntoolworks.com Fri Oct 16 07:25:05 2009 From: jtc at acorntoolworks.com (J.T. Conklin) Date: Fri, 16 Oct 2009 07:25:05 -0700 Subject: [Xorp-users] Problem with scons build in xorp 1.7-WIP In-Reply-To: <105932.68400.qm@web94807.mail.in2.yahoo.com> (naresh raga's message of "Wed, 14 Oct 2009 21:33:27 +0530 (IST)") References: <105932.68400.qm@web94807.mail.in2.yahoo.com> Message-ID: <87eip3tnzy.fsf@orac.acorntoolworks.com> naresh raga writes: > What you said was right.I have moved -lcrypto last and have run the > command line manually,it has not resulted in any error.It has > successfully created the executable call_xrl.So,please jtc reorder > the libraries. Hi Naresh, I'll see what I can do this weekend. Fixing this should not be difficult. --jtc -- J.T. Conklin From naresh_raga at yahoo.co.in Fri Oct 16 10:12:00 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Fri, 16 Oct 2009 22:42:00 +0530 (IST) Subject: [Xorp-users] Problem with scons build in xorp 1.7-WIP In-Reply-To: <87eip3tnzy.fsf@orac.acorntoolworks.com> Message-ID: <442457.89499.qm@web94816.mail.in2.yahoo.com> Hi Naresh, I'll see what I can do this weekend.? Fixing this should not be difficult. ? ? --jtc -- J.T. Conklin Hi J.T.C, I am eagerly waiting for your reply.I think after fixing this up my job would be easy to cross-compile xorp.I am also currently working on TS-7800-ARM 9 based which had 500Mhz processor,128MB RAM,2.6 debian.I'l let you know the problems while porting xorp onto this kit meanwhile. Regards, Naresh. Now, send attachments up to 25MB with Yahoo! India Mail. Learn how. http://in.overview.mail.yahoo.com/photos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091016/78575cbd/attachment.html From naresh_raga at yahoo.co.in Sun Oct 18 06:11:23 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Sun, 18 Oct 2009 18:41:23 +0530 (IST) Subject: [Xorp-users] Error while building xorp-1.6 :g++-4.3: Internal error: Killed (program cc1plus) In-Reply-To: <87eip3tnzy.fsf@orac.acorntoolworks.com> Message-ID: <897110.49383.qm@web94809.mail.in2.yahoo.com> Hi , I am trying to build xorp-1.6 on TS-7800.The board is ARM based and had 500MHz processor and 128MB RAM.The default OS is debian with 2.6 kernel on it.While I am building xorp-1.6 on the board using gcc-4.3 and g++-4.3,it? got resulted in the below error: make[2]: Entering directory `/mnt/pen/xorp-1.6/xrl' Making all in interfaces make[3]: Entering directory `/mnt/pen/xorp-1.6/xrl/interfaces' /bin/sh ../../libtool --tag=CXX?? --mode=compile g++-4.3 -DHAVE_CONFIG_H -I. -Ic ?g++-4.3 -DHAVE_CONFIG_H -I. -I../.. -I../.. -g -Werror -W -Wall -Wwrite-stringo {standard input}: Assembler messages: {standard input}:173730: Warning: end of file not at end of a line; newline insd {standard input}:174186: Error: expected comma after name `_Z8callbackIv16XrlPie g++-4.3: Internal error: Killed (program cc1plus) Please submit a full bug report. What does this error indicate?What should I do to remove this error? Thanks, Naresh. Now, send attachments up to 25MB with Yahoo! India Mail. Learn how. http://in.overview.mail.yahoo.com/photos -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091018/0f3dc830/attachment.html From bms at incunabulum.net Mon Oct 19 08:40:48 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 19 Oct 2009 16:40:48 +0100 Subject: [Xorp-users] XORP IGMPv2 <-> XORP IGMPv3 In-Reply-To: <598290.50482.qm@web52310.mail.re2.yahoo.com> References: <598290.50482.qm@web52310.mail.re2.yahoo.com> Message-ID: <4ADC8880.8000508@incunabulum.net> Philip Romanov wrote: > Question, I guess, would be if XORP supports downshifting into lower version IGMP compatibility modes as per RFC? Any configuration file options that I missed? > I believe that it does, but I didn't write it. Pavlin Radoslavov wrote most of PIM and IGMP in XORP, he is not currently active on the project. I know that it can be tied down to specific versions of IGMP, however, the Older Querier Present behaviour isn't something I've exercised. If it doesn't, this is probably something which needs to be looked at as a spec compliance issue, and the best time/place to do that is as part of a 1.7-RC. If you come up with a patch in the meantime, even better. If you could raise a Trac ticket about this issue on Sourceforge, then someone can look into the issue as time permits. regards, BMS From bms at incunabulum.net Mon Oct 19 08:42:42 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 19 Oct 2009 16:42:42 +0100 Subject: [Xorp-users] Can't enable MFEA In-Reply-To: References: Message-ID: <4ADC88F2.6070304@incunabulum.net> Jorn Rikkers wrote: > Hi, > > Can someone help me to enable multicast forwarding in XORP. I'm using > the CORE emulation tool on FreeBSD. Everything works fine but when I > enable multicast forwarding I get an "Operation not supported" on > setsockopt(MRT_INIT, 1), see log below. Do you have 'options MROUTING' (if statically compiling the multicast forwarding code) in your kernel configuration, or do you have the 'ip_mroute.ko' kernel module loaded? Please verify with: 'kldstat -v | grep mroute'. thanks, BMS From bms at incunabulum.net Mon Oct 19 08:45:12 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 19 Oct 2009 16:45:12 +0100 Subject: [Xorp-users] Error while building xorp-1.6 :g++-4.3: Internal error: Killed (program cc1plus) In-Reply-To: <897110.49383.qm@web94809.mail.in2.yahoo.com> References: <897110.49383.qm@web94809.mail.in2.yahoo.com> Message-ID: <4ADC8988.1070603@incunabulum.net> naresh raga wrote: > Hi , > I am trying to build xorp-1.6 on TS-7800.The board is ARM based and > had 500MHz processor and 128MB RAM.The default OS is debian with 2.6 > kernel on it.While I am building xorp-1.6 on the board using gcc-4.3 > and g++-4.3,it got resulted in the below error: > ... Unfortunately the source file which triggered this error seems to be missing from your log output. I don't use GCC 4.3 (apart from occasional casual tests), however, it may be worthwhile looking at the GCC bug database for this version of the G++ compiler, and that may be the best place to start investigating your issue. thanks, BMS From bms at incunabulum.net Mon Oct 19 08:47:13 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 19 Oct 2009 16:47:13 +0100 Subject: [Xorp-users] start-up xorp in ubuntu OS In-Reply-To: <000301ca4aea$5f4599c0$1dd0cd40$@com.my> References: <000301ca4aea$5f4599c0$1dd0cd40$@com.my> Message-ID: <4ADC8A01.8030905@incunabulum.net> Fazlina Zuria Mohd Anuar wrote: > > Hello! > > I would to ask is there anyone know how to auto start-up xorp > automatically after boot up the Ubuntu OS? > > For now, I just start the xorp using command line. > There is a Debian package for XORP, which Ubuntu is able to deploy and use. This isn't supported by XORP, Inc. or the XORP developers themselves, however. I believe this package may have the appropriate RC glue for automated system startup, so you may wish to look into this and see if it works for you. This hasn't, however, been updated to use the current SVN sources, so you may wish to contact the maintainer of this package directly. thanks, BMS From bms at incunabulum.net Mon Oct 19 08:48:46 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 19 Oct 2009 16:48:46 +0100 Subject: [Xorp-users] Can't enable MFEA In-Reply-To: References: Message-ID: <4ADC8A5E.7020006@incunabulum.net> Jorn Rikkers wrote: > ... > PIM-SM: > - If the kernel does not support PIM-SM, or if PIM-SM is not enabled in the kernel, then running PIM-SM will fail with the following error message: > [ 2004/06/12 10:26:41 ERROR xorp_fea:444 MFEA +529 mfea_mrouter.cc start_mrt ] setsockopt(MRT_INIT, 1) failed: Operation not supported > The appropriate PIM hooks should be enabled automatically in FreeBSD kernel compiles since at least FreeBSD 4.6, however, MROUTING itself may not be enabled. A failure with MRT_INIT usually suggests that the kernel was compiled without multicast forwarding support, or it was not loaded as a kernel module; please refer to my other reply. thanks, BMS From bms at incunabulum.net Mon Oct 19 08:50:10 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 19 Oct 2009 16:50:10 +0100 Subject: [Xorp-users] Interface routing In-Reply-To: <44ba60c50910090900q71bc98a8o21d5ad6890692236@mail.gmail.com> References: <44ba60c50910090900q71bc98a8o21d5ad6890692236@mail.gmail.com> Message-ID: <4ADC8AB2.7020209@incunabulum.net> Andriy Beregovenko wrote: > jet at test_vz# show protocols static > route 0.0.0.0/0 { > next-hop: 192.0.2.1 > } > interface-route 192.0.2.1/32 { > next-hop-interface: "venet0" > next-hop-vif: "venet0" > } > This would cause recursive next-hop resolution, which isn't supported by the RIB. Perhaps your default route should also be an interface route? thanks, BMS From bms at incunabulum.net Mon Oct 19 08:56:10 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Mon, 19 Oct 2009 16:56:10 +0100 Subject: [Xorp-users] Loopback address In-Reply-To: <4AD6F3C5.9070500@student.uclouvain.be> References: <4AD6F3C5.9070500@student.uclouvain.be> Message-ID: <4ADC8C1A.302@incunabulum.net> Luca Belforte wrote: > I'm trying to set up a loopback address on my routers, used instead of > the address of an interface, in case a link will not work. > But i can't find how do it, i modified the lo address, but the address > is not "forwarder" to other routers, so i can't ping it. > > in cisco we can do like this: > > interface Loopback0 > description "*** Loopback ***" > no ip address > ipv4 address 10.0.1.1/32 > ipv4 ospf area 0 > exit > > > How i can set up the same in Xorp? > I believe you'll need to configure the 'lo' interface manually within the XORP configuration. The FEA has a certain amount of support for software interfaces; the 'discard' interface, for example, is a purely software mechanism, which isn't implemented consistently across all forwarding platforms. For the Linux case, you'll probably need to set up an IPv4 alias on lo in the interfaces {} block. For BSDs, the same may work, but you might wish to 'clone' a separate loX instance during system startup (something XORP can't do for you directly). I can't think of any reason off the top of my head why it should not be possible to redistribute routes which reference that interface by address, unless the protocol(s) involved are trying to omit local addresses for whatever reason. thanks, BMS From naresh_raga at yahoo.co.in Thu Oct 22 05:44:55 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Thu, 22 Oct 2009 18:14:55 +0530 (IST) Subject: [Xorp-users] Error while building xorp-1.6 :g++-4.3: Internal error: Killed (program cc1plus) In-Reply-To: <4ADC8988.1070603@incunabulum.net> Message-ID: <378365.92708.qm@web94815.mail.in2.yahoo.com> Hi Bruce, I have searched for this error in net.It is indicative of less RAM.G++ ran out of RAM memory while building the executable. I have worked on 128MB RAM and on 500MHz arm based machine.To get rid of this,I have used the lower version g++-3.3 and xorp-1.4.Even in this case also while generating executables for next_hop_resolver.cc, plumbing.cc in bgp and area_router.cc ,peer.cc in ospf,I got the same error from g++-3.3.So,I have removed bgp and ospf protocols and built? xorp-1.4.xorp_rtrmgr working fine..but i think bgp is compulsory for routing the packets out of the domain.I can manage without ospf but bgp is needed. I have a question here:are these protocols bgp and ospf memory intensive. I am thinking a solution for bgp to get built into xorp-1.4.I will use cross-compiler and build this module separately in my x86 machine.I will add this module into xorp-1.4 and then i will separately build rtrmgr once again to add bgp configured into it. Is the above way a right approach?Or is there any solution to get bgp into already built xorp-1.4?Or is there any alternatives to bgp protocol that is available in xorp platform(I am unable to find one, please help me.) Regards, Naresh. Connect more, do more and share more with Yahoo! India Mail. Learn more. http://in.overview.mail.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091022/a567dda6/attachment.html From greearb at candelatech.com Thu Oct 22 06:21:51 2009 From: greearb at candelatech.com (Ben Greear) Date: Thu, 22 Oct 2009 06:21:51 -0700 Subject: [Xorp-users] Error while building xorp-1.6 :g++-4.3: Internal error: Killed (program cc1plus) In-Reply-To: <378365.92708.qm@web94815.mail.in2.yahoo.com> References: <378365.92708.qm@web94815.mail.in2.yahoo.com> Message-ID: <4AE05C6F.3070505@candelatech.com> naresh raga wrote: > Hi Bruce, > I have searched for this error in net.It is indicative of less RAM.G++ > ran out of RAM memory while building the executable. > I have worked on 128MB RAM and on 500MHz arm based machine.To get rid > of this,I have used the lower version g++-3.3 and xorp-1.4.Even in > this case also while generating executables for next_hop_resolver.cc, > plumbing.cc in bgp and area_router.cc ,peer.cc in ospf,I got the same > error from g++-3.3.So,I have removed bgp and ospf protocols and built > xorp-1.4.xorp_rtrmgr working fine..but i think bgp is compulsory for > routing the packets out of the domain.I can manage without ospf but > bgp is needed. > I have a question here:are these protocols bgp and ospf memory intensive. > Can you just add swap to the system? It won't be fast, but maybe it would at least compile? I think recent kernels can even swap over network file systems... Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From naresh_raga at yahoo.co.in Fri Oct 23 02:31:26 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Fri, 23 Oct 2009 15:01:26 +0530 (IST) Subject: [Xorp-users] Error while building xorp-1.6 :g++-4.3: Internal error: Killed (program cc1plus) In-Reply-To: <4AE05C6F.3070505@candelatech.com> Message-ID: <944229.69431.qm@web94808.mail.in2.yahoo.com> Thanks Ben I have thought of this,but not tried in this direction. I will try to work on this direction also. Regards, Ben. Add whatever you love to the Yahoo! India homepage. Try now! http://in.yahoo.com/trynew -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091023/1548a679/attachment.html From naresh_raga at yahoo.co.in Sat Oct 24 04:06:37 2009 From: naresh_raga at yahoo.co.in (naresh raga) Date: Sat, 24 Oct 2009 16:36:37 +0530 (IST) Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr Message-ID: <406045.23702.qm@web94806.mail.in2.yahoo.com> hi Bruce and JTC, Thanks for your help regarding this error.I had done some experimentation to definitely say that this error is due to less RAM or processor speed.I would like to share with you. I had built xorp-1.4 on 500MHz,128MB RAM arm9 based board, having 2.6.21 kernel and debian sarge OS, but not with all protocols configured.I had to leave bgp and ospf which resulted in g++-3.3-Internal error:Killed( program cc1plus).Final xorp_rtrmgr is running fine on the board.I took this xorp-1.4 (built) onto 200MHz,64MB RAM arm9 based board,having 2.4.26 kernel and debian sarge OS.I tried to execute ./xorp_rtrmgr on this board.But it resulted in XrlRouter Failed.No Finder? error. Now I can say that the error is because of less RAM or processor speed.I don't think the error is due to kernel.I just want to inform this to you people who helped me lot. Make a note of this error in bugzilla,please. Regards, Naresh. Add whatever you love to the Yahoo! India homepage. Try now! http://in.yahoo.com/trynew -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091024/980b6103/attachment.html From dirk.schulz at kinzesberg.de Sat Oct 24 08:54:21 2009 From: dirk.schulz at kinzesberg.de (Dirk H. Schulz) Date: Sat, 24 Oct 2009 17:54:21 +0200 Subject: [Xorp-users] Two Router Managers crashing simultaneously Message-ID: <4AE3232D.1070700@kinzesberg.de> I am running Xorp on two servers (Xorp 1.4.1). Both xorp routers are connected to two upstream routers, talking OSPF, nothing else. After more than 1,5 years of trouble free use both router managers crashed simultaneously. Upstream claims not to have worked on their routers. Now I want to find out what exactly happened, if possible. Is there some known bug in 1.4.1 that can make both router managers crash at the same time? Or could it have been sime kind of DOS attack? Any hint or help would be greatly appreciated. Dirk From greearb at candelatech.com Sat Oct 24 16:44:06 2009 From: greearb at candelatech.com (Ben Greear) Date: Sat, 24 Oct 2009 16:44:06 -0700 Subject: [Xorp-users] Two Router Managers crashing simultaneously In-Reply-To: <4AE3232D.1070700@kinzesberg.de> References: <4AE3232D.1070700@kinzesberg.de> Message-ID: <4AE39146.8020404@candelatech.com> Dirk H. Schulz wrote: > I am running Xorp on two servers (Xorp 1.4.1). Both xorp routers are > connected to two upstream routers, talking OSPF, nothing else. > > After more than 1,5 years of trouble free use both router managers > crashed simultaneously. Upstream claims not to have worked on their > routers. > > Now I want to find out what exactly happened, if possible. > > Is there some known bug in 1.4.1 that can make both router managers > crash at the same time? Or could it have been sime kind of DOS attack? > > Any hint or help would be greatly appreciated. > Check for core files..if they exist, run gdb on them and send us the backtrace. Also, send us the last bit of the xorp logs..if it was an assert, useful information may be present there. Either way, the answer is likely to upgrade to the 1.6 code branch. Thanks, Ben > Dirk > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > -- Ben Greear Candela Technologies Inc http://www.candelatech.com From bms at incunabulum.net Sun Oct 25 08:04:41 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Sun, 25 Oct 2009 15:04:41 +0000 Subject: [Xorp-users] Two Router Managers crashing simultaneously In-Reply-To: <4AE3232D.1070700@kinzesberg.de> References: <4AE3232D.1070700@kinzesberg.de> Message-ID: <4AE46909.4000502@incunabulum.net> Dirk H. Schulz wrote: > Is there some known bug in 1.4.1 that can make both router managers > crash at the same time? Or could it have been sime kind of DOS attack? > As Ben pointed out, without some backtraces, it's difficult to go on. From memory, there were a (very few) stability and security fixes during the 1.4->1.5 XORP releases, so it's quite possible that you ran into one of the issues which were fixed at that time. Some general comments: * One great feature to have around would be an automated tool for backtrace collection, etc. A patch for this has been on my 'wish list' for a while. * Otherwise, it's probably best to make sure you have GDB installed somewhere to catch analysis from crashed XORP processes. If you can preserve the core file, you can do this offline from the production systems themselves. Collection's another matter -- it's a good use of NFS or even removable flash media. cheers, BMS From bms at incunabulum.net Sun Oct 25 08:08:05 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Sun, 25 Oct 2009 15:08:05 +0000 Subject: [Xorp-users] Error:XrlRouter Failed.No Finder?while running ./xorp_rtrmgr In-Reply-To: <406045.23702.qm@web94806.mail.in2.yahoo.com> References: <406045.23702.qm@web94806.mail.in2.yahoo.com> Message-ID: <4AE469D5.5050506@incunabulum.net> naresh raga wrote: > hi Bruce and JTC, > Thanks for your help regarding this error.I had done some > experimentation to definitely say that this error is due to less RAM > or processor speed.I would like to share with you. > > I had built xorp-1.4 on 500MHz,128MB RAM arm9 based board, having > 2.6.21 kernel and debian sarge OS, but not with all protocols > configured.I had to leave bgp and ospf which resulted in > g++-3.3-Internal error:Killed( program cc1plus).Final xorp_rtrmgr is > running fine on the board.I took this xorp-1.4 (built) onto > 200MHz,64MB RAM arm9 based board,having 2.4.26 kernel and debian sarge > OS.I tried to execute ./xorp_rtrmgr on this board.But it resulted in > XrlRouter Failed.No Finder? error. > It sounds like you probably ran into a resource limit of some kind. The XORP memory footprint has probably gone down a good deal since 1.4, thanks mostly to JT's work at XORP, Inc.; and also down to catching some heap stuff in that spin. It might be worthwhile trying again with the latest code in SVN. cheers, BMS From greearb at candelatech.com Sun Oct 25 09:59:08 2009 From: greearb at candelatech.com (Ben Greear) Date: Sun, 25 Oct 2009 09:59:08 -0700 Subject: [Xorp-users] Two Router Managers crashing simultaneously In-Reply-To: <4AE46909.4000502@incunabulum.net> References: <4AE3232D.1070700@kinzesberg.de> <4AE46909.4000502@incunabulum.net> Message-ID: <4AE483DC.3050608@candelatech.com> Bruce Simpson wrote: > Dirk H. Schulz wrote: > >> Is there some known bug in 1.4.1 that can make both router managers >> crash at the same time? Or could it have been sime kind of DOS attack? >> >> > > As Ben pointed out, without some backtraces, it's difficult to go on. > From memory, there were a (very few) stability and security fixes > during the 1.4->1.5 XORP releases, so it's quite possible that you ran > into one of the issues which were fixed at that time. > > Some general comments: > * One great feature to have around would be an automated tool for > backtrace collection, etc. A patch for this has been on my 'wish list' > for a while. > If you start xorp with a script, and then check for cores when rtrmgr stops for any reason, and if gdb exists, you can get backtraces automatically. I use something similar for my product, but since xorp has lots of processes, you'd have to do some magic with 'file' to figure out which binary created the core. if [ -f $base_dir/core ] then echo "*******************CRASH*********************" >> $log_dir/CRASH_INFO_$fc.txt echo -n "DATE: " >> $log_dir/CRASH_INFO_$fc.txt date >> $log_dir/CRASH_INFO_$fc.txt echo bt > /tmp/gdb_input echo quit >> /tmp/gdb_input gdb \$BTSERVER $base_dir/core < /tmp/gdb_input >> $log_dir/CRASH_INFO_$fc.txt mv -f $base_dir/core $base_dir/core_$fc.old fi Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From dirk.schulz at kinzesberg.de Mon Oct 26 06:16:36 2009 From: dirk.schulz at kinzesberg.de (Dirk H. Schulz) Date: Mon, 26 Oct 2009 14:16:36 +0100 Subject: [Xorp-users] Two Router Managers crashing simultaneously In-Reply-To: <4AE46909.4000502@incunabulum.net> References: <4AE3232D.1070700@kinzesberg.de> <4AE46909.4000502@incunabulum.net> Message-ID: <4AE5A134.7080605@kinzesberg.de> Thanks, Ben and Bruce, for your answers. Unfortunately there is no core files on the router servers, so finding out what happened is likely to be unsuccessful. I will update to 1.6, then. Dirk Bruce Simpson schrieb: > Dirk H. Schulz wrote: >> Is there some known bug in 1.4.1 that can make both router managers >> crash at the same time? Or could it have been sime kind of DOS attack? >> > > As Ben pointed out, without some backtraces, it's difficult to go on. > From memory, there were a (very few) stability and security fixes > during the 1.4->1.5 XORP releases, so it's quite possible that you ran > into one of the issues which were fixed at that time. > > Some general comments: > * One great feature to have around would be an automated tool for > backtrace collection, etc. A patch for this has been on my 'wish list' > for a while. > > * Otherwise, it's probably best to make sure you have GDB installed > somewhere to catch analysis from crashed XORP processes. If you can > preserve the core file, you can do this offline from the production > systems themselves. Collection's another matter -- it's a good use of > NFS or even removable flash media. > > cheers, > BMS > > From arbatovevgeniy at gmail.com Wed Oct 28 03:23:52 2009 From: arbatovevgeniy at gmail.com (Evgeniy Arbatov) Date: Wed, 28 Oct 2009 12:23:52 +0200 Subject: [Xorp-users] Xorp throughput Message-ID: <56c989d50910280323w53f21234rcaa6caa5d1167817@mail.gmail.com> Hello, I have a question about BGP routing performance of Xorp. I don't need to run the full BGP table on Xorp, only a small subset. I am curious of how much throughput Xorp or any other Linux-based router (built on general purpose hardware) can deliver? As far as I understand, it is not possible to get above 100 Mbit/s without using one of the dedicated routers from Cisco or Juniper. Or am I wrong here? Thank you! Best regards, Evgeniy From crest at cyb0rg.org Wed Oct 28 07:01:01 2009 From: crest at cyb0rg.org (Crest) Date: Wed, 28 Oct 2009 15:01:01 +0100 Subject: [Xorp-users] Xorp throughput In-Reply-To: <56c989d50910280323w53f21234rcaa6caa5d1167817@mail.gmail.com> References: <56c989d50910280323w53f21234rcaa6caa5d1167817@mail.gmail.com> Message-ID: <4AE84E9D.2040803@cyb0rg.org> Evgeniy Arbatov schrieb: > Hello, > > I have a question about BGP routing performance of Xorp. I don't need > to run the full BGP table on Xorp, only a small subset. > > I am curious of how much throughput Xorp or any other Linux-based > router (built on general purpose hardware) can deliver? As far as I > understand, it is not possible to get above 100 Mbit/s without using > one of the dedicated routers from Cisco or Juniper. Or am I wrong > here? > I used this type of System as VPN Router and achieved about 55 MiB/s routing throughput where with 103 prefixes: Software: XORP 1.6, FreeBSD 7.1 with device polling and HZ=3000 Hardware: VIA C7 CPU, 2 x very cheap Realtek Gigabit Ethernet From syed.khalid at xorp.net Wed Oct 28 09:11:15 2009 From: syed.khalid at xorp.net (Syed Khalid) Date: Wed, 28 Oct 2009 09:11:15 -0700 Subject: [Xorp-users] Xorp throughput In-Reply-To: <4AE84E9D.2040803@cyb0rg.org> References: <56c989d50910280323w53f21234rcaa6caa5d1167817@mail.gmail.com> <4AE84E9D.2040803@cyb0rg.org> Message-ID: We ran some "simple" peering tests with an Agilent over a 1 gb link using a Dell 2950 (running Ubuntu 8.4) The learning time was 16 secs for 200k routes. This used the canned Agilent test where On Wed, Oct 28, 2009 at 7:01 AM, Crest wrote: > Evgeniy Arbatov schrieb: > > Hello, > > > > I have a question about BGP routing performance of Xorp. I don't need > > to run the full BGP table on Xorp, only a small subset. > > > > I am curious of how much throughput Xorp or any other Linux-based > > router (built on general purpose hardware) can deliver? As far as I > > understand, it is not possible to get above 100 Mbit/s without using > > one of the dedicated routers from Cisco or Juniper. Or am I wrong > > here? > > > > I used this type of System as VPN Router and achieved about 55 MiB/s > routing throughput where with 103 prefixes: > Software: XORP 1.6, FreeBSD 7.1 with device polling and HZ=3000 > Hardware: VIA C7 CPU, 2 x very cheap Realtek Gigabit Ethernet > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091028/f0e1f623/attachment.html From mnunna0 at gmail.com Wed Oct 28 15:54:57 2009 From: mnunna0 at gmail.com (mahendra nunna) Date: Wed, 28 Oct 2009 18:54:57 -0400 Subject: [Xorp-users] Xorp installation fails on Ubuntu Message-ID: <6e49b4d40910281554u4e2932f9mfcf21142e38588d4@mail.gmail.com> hi I am trying to install XORP on ubuntu 9.0.4 ... kernel 2.6.28-16-generic...... I have installed all the dependencies mentioned in the BUILD_NOTES...... ./configure make check make ---- everything PASSED however when i tried to use the xorp shell (xorpsh)... this is wat i m getting mahen at ubuntu:~$ xorpsh The program 'xorpsh' is currently not installed. You can install it by typing: sudo apt-get install xorp bash: xorpsh: command not found .. this is totally confusing to me ... can anyone help me with this... i have been working on this for 3 days... i m not good with the linux internals thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091028/d0abb40e/attachment.html From mnunna0 at gmail.com Wed Oct 28 16:02:26 2009 From: mnunna0 at gmail.com (mahendra nunna) Date: Wed, 28 Oct 2009 19:02:26 -0400 Subject: [Xorp-users] Xorp installation fails on Ubuntu Message-ID: <6e49b4d40910281602hade392ds95a5b626e49d2616@mail.gmail.com> hi I am trying to install XORP on ubuntu 9.0.4 ... kernel 2.6.28-16-generic...... I have installed all the dependencies mentioned in the BUILD_NOTES...... ./configure make check make ---- everything PASSED however when i tried to use the xorp shell (xorpsh)... this is wat i m getting mahen at ubuntu:~$ xorpsh The program 'xorpsh' is currently not installed. You can install it by typing: sudo apt-get install xorp bash: xorpsh: command not found .. this is totally confusing to me ... can anyone help me with this... i have been working on this for 3 days... i m not good with the linux internals thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091028/309fd763/attachment.html From greearb at candelatech.com Wed Oct 28 16:08:59 2009 From: greearb at candelatech.com (Ben Greear) Date: Wed, 28 Oct 2009 16:08:59 -0700 Subject: [Xorp-users] Xorp installation fails on Ubuntu In-Reply-To: <6e49b4d40910281554u4e2932f9mfcf21142e38588d4@mail.gmail.com> References: <6e49b4d40910281554u4e2932f9mfcf21142e38588d4@mail.gmail.com> Message-ID: <4AE8CF0B.9070402@candelatech.com> On 10/28/2009 03:54 PM, mahendra nunna wrote: > hi > > I am trying to install XORP on ubuntu 9.0.4 ... kernel > 2.6.28-16-generic...... > > I have installed all the dependencies mentioned in the BUILD_NOTES...... > > ./configure > > make > > check make ---- everything PASSED > > however when i tried to use the xorp shell (xorpsh)... this is wat i m > getting Where did you get the source that you are building? The latest stuff builds with scons, not configure & make. I'm about to build xorp on Ubuntu 9.10 (RC), and plan to get a dpkg out of the deal. I'll post here when I get that working. You might also see what: locate xorpsh gives you. Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From mnunna0 at gmail.com Wed Oct 28 22:36:51 2009 From: mnunna0 at gmail.com (mahendra nunna) Date: Thu, 29 Oct 2009 01:36:51 -0400 Subject: [Xorp-users] Using Java Native Interference with XORP Message-ID: <6e49b4d40910282236o4138d570ka7ab087ff2e75ea9@mail.gmail.com> hi I want to modify the xorp. Considering the complexities involved in the modification of native XORP code, it was proposed to use Java code on top of XORP, Use interfaces and manage the XORP behaviour through Java code. It could either be done as 1. Implementing the Java code and the native XORP code in the same process, using Java Native Interface (Faster Processing) 2. or having the java code and the native XORP code run in seperate process, using Inter Process Communication. is it good to do this... or should we proceed modifying the native xorp code and compile it Please advise us on this .... we need your opinion about this.... thanks mahen -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091029/2d84b961/attachment.html From greearb at candelatech.com Wed Oct 28 23:17:16 2009 From: greearb at candelatech.com (Ben Greear) Date: Wed, 28 Oct 2009 23:17:16 -0700 Subject: [Xorp-users] Using Java Native Interference with XORP In-Reply-To: <6e49b4d40910282236o4138d570ka7ab087ff2e75ea9@mail.gmail.com> References: <6e49b4d40910282236o4138d570ka7ab087ff2e75ea9@mail.gmail.com> Message-ID: <4AE9336C.5090107@candelatech.com> mahendra nunna wrote: > hi > > I want to modify the xorp. Considering the complexities involved in > the modification of native XORP code, it was proposed to use Java code > on top of XORP, Use interfaces and manage the XORP behaviour through > Java code. > It could either be done as > 1. Implementing the Java code and the native XORP code in the same > process, using Java Native Interface (Faster Processing) This seems like a bad idea...you'd have to understand Xorp well enough to bind to it, and then pay all the price of making JNI work on top of that. > 2. or having the java code and the native XORP code run in seperate > process, using Inter Process Communication. That might work, but probably painful to integrate with XRL since I don't think there is any automatic code generation for java. I'd just copy something relatively simple (maybe rip?) and start hacking C++ code, but perhaps I'm biased! Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From bms at incunabulum.net Thu Oct 29 08:27:01 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 29 Oct 2009 15:27:01 +0000 Subject: [Xorp-users] Xorp installation fails on Ubuntu In-Reply-To: <6e49b4d40910281554u4e2932f9mfcf21142e38588d4@mail.gmail.com> References: <6e49b4d40910281554u4e2932f9mfcf21142e38588d4@mail.gmail.com> Message-ID: <4AE9B445.8070005@incunabulum.net> Hi, Please let folk know which version(s) of the sources you are attempting to use, and supply a full log of error information. There is a Debian package which may work for you on Ubuntu, if you don't wish to build from source, but it won't be up-to-date. thanks, BMS From bms at incunabulum.net Thu Oct 29 08:30:29 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Thu, 29 Oct 2009 15:30:29 +0000 Subject: [Xorp-users] Using Java Native Interference with XORP In-Reply-To: <6e49b4d40910282236o4138d570ka7ab087ff2e75ea9@mail.gmail.com> References: <6e49b4d40910282236o4138d570ka7ab087ff2e75ea9@mail.gmail.com> Message-ID: <4AE9B515.1060901@incunabulum.net> mahendra nunna wrote: > ... > 1. Implementing the Java code and the native XORP code in the same > process, using Java Native Interface (Faster Processing) Regardless of JNI, cross-language interop isn't happening until the Thrift drop of XORP is done. I am edging closer to this goal. cheers, BMS From seong at etri.re.kr Thu Oct 29 19:13:47 2009 From: seong at etri.re.kr (SeongMoon) Date: Fri, 30 Oct 2009 11:13:47 +0900 Subject: [Xorp-users] how to stop xorp_rtrmgr Message-ID: <62FB011A96CC4A00A60A5BB4B788C31F@etrief6929b385> Hi there.. I can start xorp_rtrmgr in foreground or background... But I couldn't stop correctly rtrmgr. How can I stop xorp_rtrmgr ? regards seong.. From bms at incunabulum.net Sat Oct 31 09:55:32 2009 From: bms at incunabulum.net (Bruce Simpson) Date: Sat, 31 Oct 2009 16:55:32 +0000 Subject: [Xorp-users] how to stop xorp_rtrmgr In-Reply-To: <62FB011A96CC4A00A60A5BB4B788C31F@etrief6929b385> References: <62FB011A96CC4A00A60A5BB4B788C31F@etrief6929b385> Message-ID: <4AEC6C04.8040805@incunabulum.net> SeongMoon wrote: > Hi there.. > > I can start xorp_rtrmgr in foreground or background... > But I couldn't stop correctly rtrmgr. > How can I stop xorp_rtrmgr ? > Normally just sending its process a SIGINT (using the kill(1) command) should work.