From pmancheno at gmail.com Mon Jan 1 23:21:17 2007 From: pmancheno at gmail.com (Pepo) Date: Tue, 2 Jan 2007 02:21:17 -0500 Subject: [Xorp-users] Security in my multicast Message-ID: <200701020221.26987.pmancheno@gmail.com> Hi friends. With Xorp I can configure my multicast distribution tree, but, any PC attached to any multicast router can access to the tree if knows the multicast address. How do I configure some kind of restriction? something like keys or something like that. Thanks. -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070102/3a21d6c7/attachment.bin From pavlin at icir.org Tue Jan 2 10:59:57 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Tue, 02 Jan 2007 10:59:57 -0800 Subject: [Xorp-users] Security in my multicast In-Reply-To: Message from Pepo of "Tue, 02 Jan 2007 02:21:17 EST." <200701020221.26987.pmancheno@gmail.com> Message-ID: <200701021859.l02Ixvso073143@possum.icir.org> > With Xorp I can configure my multicast distribution tree, but, any PC > attached to any multicast router can access to the tree if knows the > multicast address. How do I configure some kind of restriction? something > like keys or something like that. The simple answer is: you can't (within XORP). There are lots of issues in the multicast+security space, so there is no easy or simple solution. If you are looking for an end-to-end solution (above the IGMP and PIM-SM level), this is the focus of the MSEC IETF Working Group: http://www.securemulticast.org/msec-index.htm See also RFC 3740 for description of the MSEC architecture. However, this work is relatively new and is not widely adopted. The brute-force solution is just to disable IGMP on a particular interface. This will stop all hosts connected to that interface to use IGMP to join any multicast group. If you need a finer granularity control (per interface per host), you could try to use IPsec for the IGMP messages (between the multicast router and the hosts allowed to join specific multicast groups). However, getting it working is probably going to be a nightmare (at best). In addition, if a legitimate host has joined group X, this won't prevent other hosts (connected to the same subnet) from receiving same multicast data. Regards, Pavlin From ross.cameron at linuxpro.co.za Fri Jan 5 00:32:35 2007 From: ross.cameron at linuxpro.co.za (Ross Cameron) Date: Fri, 5 Jan 2007 10:32:35 +0200 Subject: [Xorp-users] Compiling XORP on Slackware 11.0 Message-ID: <35f70db10701050032l352db00dn8331399077a6aef2@mail.gmail.com> Happy New Year list I'm having issues compiling XORP 1.3 on Slackware 11.0,... I'm trying to keep it as minimalistic as possible as far as the host OS goes just to ease management etc. >From my reading of the situation the ./configure runs ok its when I run make that things get fun. It seems that its having issues finding the header files: ethtool.h rtnetlink.h mroute.h Where does XORP look for these files by default? Or which package does this usually live in? Regards,... Ross Cameron -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070105/2bd978d9/attachment.html From pavlin at icir.org Fri Jan 5 12:42:54 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Fri, 05 Jan 2007 12:42:54 -0800 Subject: [Xorp-users] Compiling XORP on Slackware 11.0 In-Reply-To: Message from "Ross Cameron" of "Fri, 05 Jan 2007 10:32:35 +0200." <35f70db10701050032l352db00dn8331399077a6aef2@mail.gmail.com> Message-ID: <200701052042.l05Kgs06042028@possum.icir.org> > I'm having issues compiling XORP 1.3 on Slackware 11.0,... > I'm trying to keep it as minimalistic as possible as far as the host OS goes > just to ease management etc. > > From my reading of the situation the ./configure runs ok its when I run make > that things get fun. > It seems that its having issues finding the header files: > ethtool.h > rtnetlink.h > mroute.h I am not familiar with Slackware, but I believe you should have those files under /usr/include. E.g.: /usr/include/linux/ethtool.h /usr/include/linux/rtnetlink.h /usr/include/linux/mroute.h Did "./configure" find those files? Eventually, you should see messages like: checking linux/ethtool.h usability... yes checking linux/ethtool.h presence... yes checking for linux/ethtool.h... yes checking linux/rtnetlink.h usability... yes checking linux/rtnetlink.h presence... yes checking for linux/rtnetlink.h... yes ... checking linux/mroute.h usability... yes checking linux/mroute.h presence... yes checking for linux/mroute.h... yes You might also see messages like the following, which is also fine: checking linux/ethtool.h usability... no checking linux/ethtool.h presence... yes configure: WARNING: linux/ethtool.h: present but cannot be compiled configure: WARNING: linux/ethtool.h: check for missing prerequisite headers? configure: WARNING: linux/ethtool.h: proceeding with the preprocessor's result checking for linux/ethtool.h... yes checking linux/rtnetlink.h usability... no checking linux/rtnetlink.h presence... yes configure: WARNING: linux/rtnetlink.h: present but cannot be compiled configure: WARNING: linux/rtnetlink.h: check for missing prerequisite headers? configure: WARNING: linux/rtnetlink.h: proceeding with the preprocessor's result checking for linux/rtnetlink.h... yes > Where does XORP look for these files by default? Or which package does this > usually live in? For other Linux distrubutions they are typically available as part of the core system, though I have to admit that I haven't played with stripped-down minimalistic distributions. Hence, could you provide the following information: 1. Are the above files really inside the /usr/include/linux directory? 2. If yes, did "./configure" find them? 3. What are the exact compilation errors you see? Regards, Pavlin From yiwang at CS.Princeton.EDU Fri Jan 5 19:53:49 2007 From: yiwang at CS.Princeton.EDU (Yi Wang) Date: Fri, 05 Jan 2007 22:53:49 -0500 Subject: [Xorp-users] debug_msg malfunction Message-ID: <459F1D4D.7040903@cs.princeton.edu> Hello, When I build the XORP code with --enable-debug-msgs option on (I actually did ./configure --disable-ipv6 --enable-debug-msgs), it generates tons of debug messages and eats up all the cpu cycles. I suspect it runs into some sort of loop (but not 100% sure because I didn't do the pattern matching.) Anybody has a better way to view the debug messages (I'm only interested in those related to BGP)? Thanks, Yi From dvg at tjc.ru Sat Jan 6 01:45:46 2007 From: dvg at tjc.ru (=?utf-8?B?0JLRj9GH0LXRgdC70LDQsiDQlNGA0YPQttC40L3QuNC9?=) Date: Sat, 6 Jan 2007 12:45:46 +0300 (MSK) Subject: [Xorp-users] (no subject) Message-ID: <61344.87.240.10.121.1168076746.squirrel@mail.tjc.ru> Hi, I'm using FreeBSD 6.1p11 and XORP from net/xorp port 1.3_1 version. My provider uses cisco router for internet and igmp pim-sm TV multicasting, on my BSD box the VLC player works fine. I want to use the BSD box as multicast router for WinXP box. Here is my LAN scheme. (Provider CISCO) 87.240.10.97-------xl0 (87.240.10.121) BSD myk0 (192.168.250.1)----- 192.168.250.2 (WinXP box) I'm tried this xorp.conf ------------------- interfaces { restore-original-config-on-shutdown: false interface xl0 { description: "ext interface" disable: false /* default-system-config */ vif xl0 { disable: false address 87.240.10.121 { prefix-length: 27 broadcast: 87.240.10.127 disable: false } } } interface myk0 { description: "data interface" disable: false /* default-system-config */ vif myk0 { disable: false address 192.168.250.1 { prefix-length: 24 broadcast: 192.168.250.255 disable: false } } } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { disable: false interface xl0 { vif xl0 { disable: false } } interface myk0 { vif myk0 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } traceoptions { flag all { disable: false } } } } protocols { igmp { disable: false interface myk0 { vif myk0 { disable: false /* version: 2 */ /* enable-ip-router-alert-option-check: false */ /* query-interval: 125 */ /* query-last-member-interval: 1 */ /* query-response-interval: 10 */ /* robust-count: 2 */ } } traceoptions { flag all { disable: false } } } } protocols { pimsm4 { disable: false interface myk0 { vif myk0 { disable: false /* enable-ip-router-alert-option-check: false */ /* dr-priority: 1 */ /* hello-period: 30 */ /* hello-triggered-delay: 5 */ /* alternative-subnet 10.40.0.0/16 */ } } interface xl0 { vif xl0 { disable: false /* enable-ip-router-alert-option-check: false */ /* dr-priority: 1 */ /* hello-period: 30 */ /* hello-triggered-delay: 5 */ /* alternative-subnet 10.40.0.0/16 */ } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } static-rps { rp 192.168.250.1 { group-prefix 224.0.0.0/4 { /* rp-priority: 0 */ /* hash-mask-len: 30 */ } } } bootstrap { disable: true cand-bsr { scope-zone 224.0.0.0/4 { /* is-scope-zone: false */ cand-bsr-by-vif-name: "myk0" /* cand-bsr-by-vif-addr: 10.10.10.10 */ /* bsr-priority: 1 */ /* hash-mask-len: 30 */ } } cand-rp { group-prefix 224.0.0.0/4 { /* is-scope-zone: false */ cand-rp-by-vif-name: "myk0" /* cand-rp-by-vif-addr: 10.10.10.10 */ /* rp-priority: 192 */ /* rp-holdtime: 150 */ } } } switch-to-spt-threshold { /* approx. 1K bytes/s (10Kbps) threshold */ disable: false interval: 100 bytes: 102400 } traceoptions { flag all { disable: false } } } } protocols { fib2mrib { disable: false } } ------------------- Log ----------------- [ 2007/01/06 12:23:03 INFO xorp_rtrmgr:1726 RTRMGR +2228 task.cc run_task ] No more tasks to run [ 2007/01/06 12:23:04 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.22 on vif myk0 [ 2007/01/06 12:23:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 87.240.10.121 to 224.0.0.13 on vif xl0 [ 2007/01/06 12:23:07 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.250.1 to 224.0.0.13 on vif myk0 [ 2007/01/06 12:23:07 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.2 on vif myk0 [ 2007/01/06 12:23:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.13 on vif myk0 [ 2007/01/06 12:23:29 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 87.240.10.97 to 224.0.0.13 on vif xl0 [ 2007/01/06 12:23:29 TRACE xorp_pimsm4 PIM ] Added new neighbor 87.240.10.97 on vif xl0 [ 2007/01/06 12:23:30 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 87.240.10.121 to 224.0.0.13 on vif xl0 [ 2007/01/06 12:23:32 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from 192.168.250.1 to 224.0.0.1 [ 2007/01/06 12:23:32 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from 192.168.250.1 to 224.0.0.1 on vif myk0 [ 2007/01/06 12:23:35 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.22 on vif myk0 [ 2007/01/06 12:23:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 87.240.10.121 to 224.0.0.13 on vif xl0 [ 2007/01/06 12:23:35 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.13 on vif myk0 [ 2007/01/06 12:23:37 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.250.1 to 224.0.0.13 on vif myk0 [ 2007/01/06 12:23:39 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.2 on vif myk0 [ 2007/01/06 12:23:58 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 87.240.10.97 to 224.0.0.13 on vif xl0 [ 2007/01/06 12:24:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 87.240.10.121 to 224.0.0.13 on vif xl0 [ 2007/01/06 12:24:07 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.250.1 to 224.0.0.13 on vif myk0 [ 2007/01/06 12:24:12 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.2 to 239.255.2.1 on vif myk0 [ 2007/01/06 12:24:12 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (0.0.0.0, 239.255.2.1) on vif myk0 [ 2007/01/06 12:24:12 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0, 239.255.2.1) on vif myk0 [ 2007/01/06 12:24:13 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.2 to 239.255.2.1 on vif myk0 [ 2007/01/06 12:24:14 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.2 to 239.255.2.1 on vif myk0 [ 2007/01/06 12:24:28 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from 87.240.10.97 to 224.0.0.13 on vif xl0 [ 2007/01/06 12:24:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 87.240.10.121 to 224.0.0.13 on vif xl0 [ 2007/01/06 12:24:37 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.250.1 to 224.0.0.13 on vif myk0 ----------------- dvg at dvg.tjc.ru> show pim rps RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix 192.168.250.1 static 192 -1 -1 1 224.0.0.0/4 ------------------ dvg at dvg.tjc.ru> show pim join Group Source RP Flags 239.255.2.1 0.0.0.0 192.168.250.1 WC Upstream interface (RP): register_vif Upstream MRIB next hop (RP): UNKNOWN Upstream RPF'(*,G): UNKNOWN Upstream state: Joined Join timer: 2 Local receiver include WC: O.. Joins RP: ... Joins WC: ... Join state: ... Prune state: ... Prune pending state: ... I am assert winner state: ... I am assert loser state: ... Assert winner WC: ... Assert lost WC: ... Assert tracking WC: O.O Could assert WC: O.. I am DR: OOO Immediate olist RP: ... Immediate olist WC: O.. Inherited olist SG: O.. Inherited olist SG_RPT: O.. PIM include WC: O.. -------------------------- dvg at dvg.tjc.ru> show pim interface Interface State Mode V PIMstate Priority DRaddr Neighbors myk0 UP Sparse 2 DR 1 192.168.250.1 0 xl0 UP Sparse 2 DR 1 87.240.10.121 1 register_vif UP Sparse 2 DR 1 87.240.10.121 0 --------------------------- dvg at dvg.tjc.ru> show pim mrib DestPrefix NextHopRouter VifName VifIndex MetricPref Metric 0.0.0.0/0 87.240.10.97 xl0 1 254 65535 87.240.10.96/27 87.240.10.121 xl0 1 0 0 192.168.250.0/24 192.168.250.1 myk0 0 0 0 ---------------------------- dvg at dvg.tjc.ru> show route table ipv4 multicast final 0.0.0.0/0 [fib2mrib(254)/65535] > to 87.240.10.97 via xl0/xl0 192.168.250.0/24 [connected(0)/0] > via myk0/myk0 87.240.10.96/27 [connected(0)/0] > via xl0/xl0 ----------------------------- Using tcpdump I don't see any PIM Join messagaes, only PIM Hello and igmp reports like this: # tcpdump -i xl0 -vvv -n -s 0 -x proto \\igmp or proto \\pim ----------------------------- 12:40:36.838522 IP (tos 0x0, ttl 1, id 30044, offset 0, flags [none], proto: IGMP (2), length: 32, options ( RA (148) len 4 )) 87.240.35.113 > 239.255.255.250: igmp v2 report 239.255.255.250 0x0000: 4600 0020 755c 0000 0102 4420 57f0 2371 0x0010: efff fffa 9404 0000 1600 fa04 efff fffa 0x0020: 0000 0000 0000 0000 0000 0000 0000 12:40:44.422157 IP (tos 0xc0, ttl 1, id 12218, offset 0, flags [none], proto: PIM (103), length: 38) 87.240.10.97 > 224.0.0.13: PIMv2, length: 18 Hello Hold Time Option (1), length: 2, Value: 1m45s 0x0000: 0069 Generation ID Option (20), length: 4, Value: 0x00001412 0x0000: 0000 1412 0x0000: 45c0 0026 2fba 0000 0167 4699 57f0 0a61 0x0010: e000 000d 2000 cb69 0001 0002 0069 0014 0x0020: 0004 0000 1412 0000 0000 0000 0000 ------------------------------ And I see membership report from WinXP box but vlc on it not work. I think my xorp.conf contains some errors. Any ideas? --- With best regards. Vyacheslav From pmancheno at gmail.com Sun Jan 7 18:30:40 2007 From: pmancheno at gmail.com (Pepo) Date: Sun, 7 Jan 2007 21:30:40 -0500 Subject: [Xorp-users] ASM or SSM Message-ID: <200701072130.41049.pmancheno@gmail.com> Hi friends. With Xorp I can use multicast but i have a question; How do I know if I am using ASM or SSM? and How do I configure to use just one of these?. A lot of thanks. -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From pmancheno at gmail.com Mon Jan 8 04:42:45 2007 From: pmancheno at gmail.com (Pepo) Date: Mon, 8 Jan 2007 07:42:45 -0500 Subject: [Xorp-users] Simulate Message-ID: <200701080742.46981.pmancheno@gmail.com> Hi friends... I wanna use XORP for multicast; but How do I know if my LAN will support the traffic? Which tool do i can use to simulate my network, multicast traffic and routers using xorp? A lot of thanks. -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From pavlin at icir.org Mon Jan 8 11:34:57 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 08 Jan 2007 11:34:57 -0800 Subject: [Xorp-users] debug_msg malfunction In-Reply-To: Message from Yi Wang of "Fri, 05 Jan 2007 22:53:49 EST." <459F1D4D.7040903@cs.princeton.edu> Message-ID: <200701081934.l08JYveA082123@possum.icir.org> > When I build the XORP code with --enable-debug-msgs option on (I > actually did ./configure --disable-ipv6 --enable-debug-msgs), it > generates tons of debug messages and eats up all the cpu cycles. I > suspect it runs into some sort of loop (but not 100% sure because I > didn't do the pattern matching.) > > Anybody has a better way to view the debug messages (I'm only interested > in those related to BGP)? The --enable-debug-msgs will generate all possible debug messages. If you want the debug messages enabled only in a specific *.cc file, then don't use this configuration option at all. Instead, add the following definitions to the beginning of that file: #define DEBUG_LOGGING #define DEBUG_PRINT_FUNCTION_NAME Note that you must add those definitions before the inclusion of any header files. Regards, Pavlin From pavlin at icir.org Mon Jan 8 11:41:19 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 08 Jan 2007 11:41:19 -0800 Subject: [Xorp-users] (no subject) In-Reply-To: Message from =?utf-8?B?0JLRj9GH0LXRgdC70LDQsiDQlNGA0YPQttC40L3QuNC9?= of "Sat, 06 Jan 2007 12:45:46 +0300." <61344.87.240.10.121.1168076746.squirrel@mail.tjc.ru> Message-ID: <200701081941.l08JfJ9t082211@possum.icir.org> ???????? ???????? wrote: > Hi, > > I'm using FreeBSD 6.1p11 and XORP from net/xorp port 1.3_1 version. > My provider uses cisco router for internet and igmp pim-sm TV > multicasting, on my BSD box the VLC player works fine. I want to use the > BSD box as multicast router for WinXP box. Here is my LAN scheme. > > (Provider CISCO) > 87.240.10.97-------xl0 (87.240.10.121) BSD myk0 (192.168.250.1)----- > 192.168.250.2 (WinXP box) > > I'm tried this > xorp.conf Your XORP configuration looks fine, except that the static RP address is incorrectly set to your own IP address (192.168.250.1). Instead, it should be set to the RP address used by your provider (assuming your provider allows your PIM-SM router to be part of its PIM-SM domain). This is also the reason you don't see any PIM-SM Join messages from your BGP box to your provider. Hope that helps, Pavlin > ------------------- > interfaces { > restore-original-config-on-shutdown: false > interface xl0 { > description: "ext interface" > disable: false > /* default-system-config */ > vif xl0 { > disable: false > address 87.240.10.121 { > prefix-length: 27 > broadcast: 87.240.10.127 > disable: false > } > } > } > interface myk0 { > description: "data interface" > disable: false > /* default-system-config */ > vif myk0 { > disable: false > address 192.168.250.1 { > prefix-length: 24 > broadcast: 192.168.250.255 > disable: false > } > } > } > } > > fea { > unicast-forwarding4 { > disable: false > } > } > > plumbing { > mfea4 { > disable: false > interface xl0 { > vif xl0 { > disable: false > } > } > interface myk0 { > vif myk0 { > disable: false > } > } > > interface register_vif { > vif register_vif { > /* Note: this vif should be always enabled */ > disable: false > } > } > traceoptions { > flag all { > disable: false > } > } > } > } > > protocols { > igmp { > disable: false > interface myk0 { > vif myk0 { > disable: false > /* version: 2 */ > /* enable-ip-router-alert-option-check: false */ > /* query-interval: 125 */ > /* query-last-member-interval: 1 */ > /* query-response-interval: 10 */ > /* robust-count: 2 */ > } > } > traceoptions { > flag all { > disable: false > } > } > } > } > > protocols { > pimsm4 { > disable: false > interface myk0 { > vif myk0 { > disable: false > /* enable-ip-router-alert-option-check: false */ > /* dr-priority: 1 */ > /* hello-period: 30 */ > /* hello-triggered-delay: 5 */ > /* alternative-subnet 10.40.0.0/16 */ > } > } > interface xl0 { > vif xl0 { > disable: false > /* enable-ip-router-alert-option-check: false */ > /* dr-priority: 1 */ > /* hello-period: 30 */ > /* hello-triggered-delay: 5 */ > /* alternative-subnet 10.40.0.0/16 */ > } > } > interface register_vif { > vif register_vif { > /* Note: this vif should be always enabled */ > disable: false > } > } > > static-rps { > rp 192.168.250.1 { > group-prefix 224.0.0.0/4 { > /* rp-priority: 0 */ > /* hash-mask-len: 30 */ > } > } > } > bootstrap { > disable: true > cand-bsr { > scope-zone 224.0.0.0/4 { > /* is-scope-zone: false */ > cand-bsr-by-vif-name: "myk0" > /* cand-bsr-by-vif-addr: 10.10.10.10 */ > /* bsr-priority: 1 */ > /* hash-mask-len: 30 */ > } > } > > cand-rp { > group-prefix 224.0.0.0/4 { > /* is-scope-zone: false */ > cand-rp-by-vif-name: "myk0" > /* cand-rp-by-vif-addr: 10.10.10.10 */ > /* rp-priority: 192 */ > /* rp-holdtime: 150 */ > } > } > } > > switch-to-spt-threshold { > /* approx. 1K bytes/s (10Kbps) threshold */ > disable: false > interval: 100 > bytes: 102400 > } > > traceoptions { > flag all { > disable: false > } > } > } > > } > > protocols { > fib2mrib { > disable: false > } > } > ------------------- > > Log > ----------------- > [ 2007/01/06 12:23:03 INFO xorp_rtrmgr:1726 RTRMGR +2228 task.cc run_task > ] No more tasks to run > [ 2007/01/06 12:23:04 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.22 on vif myk0 > [ 2007/01/06 12:23:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 87.240.10.121 to 224.0.0.13 on vif xl0 > [ 2007/01/06 12:23:07 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.250.1 to 224.0.0.13 on vif myk0 > [ 2007/01/06 12:23:07 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.2 on vif myk0 > [ 2007/01/06 12:23:08 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.13 on vif myk0 > [ 2007/01/06 12:23:29 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from > 87.240.10.97 to 224.0.0.13 on vif xl0 > [ 2007/01/06 12:23:29 TRACE xorp_pimsm4 PIM ] Added new neighbor > 87.240.10.97 on vif xl0 > [ 2007/01/06 12:23:30 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 87.240.10.121 to 224.0.0.13 on vif xl0 > [ 2007/01/06 12:23:32 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY > from 192.168.250.1 to 224.0.0.1 > [ 2007/01/06 12:23:32 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY > from 192.168.250.1 to 224.0.0.1 on vif myk0 > [ 2007/01/06 12:23:35 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.22 on vif myk0 > [ 2007/01/06 12:23:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 87.240.10.121 to 224.0.0.13 on vif xl0 > [ 2007/01/06 12:23:35 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.13 on vif myk0 > [ 2007/01/06 12:23:37 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.250.1 to 224.0.0.13 on vif myk0 > [ 2007/01/06 12:23:39 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.1 to 224.0.0.2 on vif myk0 > [ 2007/01/06 12:23:58 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from > 87.240.10.97 to 224.0.0.13 on vif xl0 > [ 2007/01/06 12:24:05 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 87.240.10.121 to 224.0.0.13 on vif xl0 > [ 2007/01/06 12:24:07 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.250.1 to 224.0.0.13 on vif myk0 > [ 2007/01/06 12:24:12 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.2 to 239.255.2.1 on vif myk0 > [ 2007/01/06 12:24:12 TRACE xorp_igmp MLD6IGMP ] Notify routing add > membership for (0.0.0.0, 239.255.2.1) on vif myk0 > [ 2007/01/06 12:24:12 TRACE xorp_pimsm4 PIM ] Add membership for (0.0.0.0, > 239.255.2.1) on vif myk0 > [ 2007/01/06 12:24:13 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.2 to 239.255.2.1 on vif myk0 > [ 2007/01/06 12:24:14 TRACE xorp_igmp MLD6IGMP ] RX > IGMP_V2_MEMBERSHIP_REPORT from 192.168.250.2 to 239.255.2.1 on vif myk0 > [ 2007/01/06 12:24:28 TRACE xorp_pimsm4 PIM ] RX PIM_HELLO from > 87.240.10.97 to 224.0.0.13 on vif xl0 > [ 2007/01/06 12:24:35 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 87.240.10.121 to 224.0.0.13 on vif xl0 > [ 2007/01/06 12:24:37 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from > 192.168.250.1 to 224.0.0.13 on vif myk0 > ----------------- > > dvg at dvg.tjc.ru> show pim rps > RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix > 192.168.250.1 static 192 -1 -1 1 224.0.0.0/4 > ------------------ > dvg at dvg.tjc.ru> show pim join > Group Source RP Flags > 239.255.2.1 0.0.0.0 192.168.250.1 WC > Upstream interface (RP): register_vif > Upstream MRIB next hop (RP): UNKNOWN > Upstream RPF'(*,G): UNKNOWN > Upstream state: Joined > Join timer: 2 > Local receiver include WC: O.. > Joins RP: ... > Joins WC: ... > Join state: ... > Prune state: ... > Prune pending state: ... > I am assert winner state: ... > I am assert loser state: ... > Assert winner WC: ... > Assert lost WC: ... > Assert tracking WC: O.O > Could assert WC: O.. > I am DR: OOO > Immediate olist RP: ... > Immediate olist WC: O.. > Inherited olist SG: O.. > Inherited olist SG_RPT: O.. > PIM include WC: O.. > -------------------------- > dvg at dvg.tjc.ru> show pim interface > Interface State Mode V PIMstate Priority DRaddr Neighbors > myk0 UP Sparse 2 DR 1 192.168.250.1 0 > xl0 UP Sparse 2 DR 1 87.240.10.121 1 > register_vif UP Sparse 2 DR 1 87.240.10.121 0 > --------------------------- > dvg at dvg.tjc.ru> show pim mrib > DestPrefix NextHopRouter VifName VifIndex MetricPref Metric > 0.0.0.0/0 87.240.10.97 xl0 1 254 65535 > 87.240.10.96/27 87.240.10.121 xl0 1 0 0 > 192.168.250.0/24 192.168.250.1 myk0 0 0 0 > ---------------------------- > dvg at dvg.tjc.ru> show route table ipv4 multicast final > 0.0.0.0/0 [fib2mrib(254)/65535] > > to 87.240.10.97 via xl0/xl0 > 192.168.250.0/24 [connected(0)/0] > > via myk0/myk0 > 87.240.10.96/27 [connected(0)/0] > > via xl0/xl0 > ----------------------------- > > Using tcpdump I don't see any PIM Join messagaes, only PIM Hello and igmp > reports like this: > > # tcpdump -i xl0 -vvv -n -s 0 -x proto \\igmp or proto \\pim > ----------------------------- > 12:40:36.838522 IP (tos 0x0, ttl 1, id 30044, offset 0, flags [none], > proto: IGMP (2), length: 32, options ( RA (148) len 4 )) 87.240.35.113 > > 239.255.255.250: igmp v2 report 239.255.255.250 > 0x0000: 4600 0020 755c 0000 0102 4420 57f0 2371 > 0x0010: efff fffa 9404 0000 1600 fa04 efff fffa > 0x0020: 0000 0000 0000 0000 0000 0000 0000 > 12:40:44.422157 IP (tos 0xc0, ttl 1, id 12218, offset 0, flags [none], > proto: PIM (103), length: 38) 87.240.10.97 > 224.0.0.13: PIMv2, length: 18 > Hello > Hold Time Option (1), length: 2, Value: 1m45s > 0x0000: 0069 > Generation ID Option (20), length: 4, Value: 0x00001412 > 0x0000: 0000 1412 > 0x0000: 45c0 0026 2fba 0000 0167 4699 57f0 0a61 > 0x0010: e000 000d 2000 cb69 0001 0002 0069 0014 > 0x0020: 0004 0000 1412 0000 0000 0000 0000 > ------------------------------ > > And I see membership report from WinXP box but vlc on it not work. > I think my xorp.conf contains some errors. > Any ideas? > > --- > With best regards. > Vyacheslav > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at icir.org Mon Jan 8 11:56:58 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 08 Jan 2007 11:56:58 -0800 Subject: [Xorp-users] ASM or SSM In-Reply-To: Message from Pepo of "Sun, 07 Jan 2007 21:30:40 EST." <200701072130.41049.pmancheno@gmail.com> Message-ID: <200701081956.l08Juwsm082344@possum.icir.org> > With Xorp I can use multicast but i have a question; How do I know if I am > using ASM or SSM? and How do I configure to use just one of these?. Your application decides whether to use ASM or SSM. Note that the default IGMP version used by XORP is IGMPv2 (i.e., ASM only). If you want to enable SSM support as well, then you need to set the IGMP version (per vif) to 3. You could use the "show igmp group" xorpsh command to see various information about the directly-connected multicast receivers (one line per group or source-group). The output contains the IGMP version as well. Finally, I should note that the 232.0.0.0/8 multicast address space is reserved for SSM. Hence, eventually any multicast traffic in that address space is suppose to be SSM (and no ASM traffic should use 232/8). However, currently this distinction is not enforced by XORP, and I don't know whether it is enforced by other router vendors or OS (IGMP host stack) implementations. Regards, Pavlin From pavlin at icir.org Mon Jan 8 12:15:15 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 08 Jan 2007 12:15:15 -0800 Subject: [Xorp-users] Simulate In-Reply-To: Message from Pepo of "Mon, 08 Jan 2007 07:42:45 EST." <200701080742.46981.pmancheno@gmail.com> Message-ID: <200701082015.l08KFFFw082559@possum.icir.org> > I wanna use XORP for multicast; but How do I know if my LAN will support the > traffic? Which tool do i can use to simulate my network, multicast traffic > and routers using xorp? If you are concerned about the amount of bandwidth and whether your network will support it, this issue is outside the scope of XORP. XORP contains only control-plane software (the protocols needed to support unicast and multicast routing, etc), and you need to use other tools to design or test your network. I don't know what tools/mechanisms are used in that case. If your network is very simple, have you tried back-on-the-envelope calculations? :) Other folks on that list have first-hand ISP experience and should be able to tell you what they usually do. Regards, Pavlin From dvg at tjc.ru Tue Jan 9 13:01:55 2007 From: dvg at tjc.ru (Vyacheslav Druzhinin) Date: Wed, 10 Jan 2007 00:01:55 +0300 Subject: [Xorp-users] routing provider's TV (PIM-SM) In-Reply-To: <200701081941.l08JfJ9t082211@possum.icir.org> References: <200701081941.l08JfJ9t082211@possum.icir.org> Message-ID: <200701100001.56061.dvg@tjc.ru> Hi, 08.01.2007 22:41 you wrote: > > I'm using FreeBSD 6.1p11 and XORP from net/xorp port 1.3_1 version. > > My provider uses cisco router for internet and igmp pim-sm TV > > multicasting, on my BSD box the VLC player works fine. I want to use the > > BSD box as multicast router for WinXP box. Here is my LAN scheme. > > > > (Provider CISCO) > > 87.240.10.97-------xl0 (87.240.10.121) BSD myk0 (192.168.250.1)----- > > 192.168.250.2 (WinXP box) > > > > I'm tried this > > xorp.conf > > Your XORP configuration looks fine, except that the static RP > address is incorrectly set to your own IP address > (192.168.250.1). Instead, it should be set to the RP address used by > your provider (assuming your provider allows your PIM-SM router to > be part of its PIM-SM domain). > > This is also the reason you don't see any PIM-SM Join messages from > your BGP box to your provider. > > Hope that helps, > Pavlin Thank you very much. I've changed the static-rp string to provider's cisco router - 87.240.10.97, but vlc on winXP still does not work. But if I starting to view any TV channel on BSD box and at the same time starting to view the channel on winXP box it shows on it. Provider's tech support does not wish to tell me an RP IP address. I don't know the RP's IP, simply wrote my router's IP. I assume there are two variants. Provider has filtering PIM-SM Join messages or I don't know correct IP address of RP. There is the third variant, an igmp proxy software can helps me, but I don't know any igmp proxy solution for FreeBSD, only for linux (igmpproxy project on sourceforge, it is mix from pimd and smcroute). :( > > ------------------- > > interfaces { > > restore-original-config-on-shutdown: false > > interface xl0 { > > description: "ext interface" > > disable: false > > /* default-system-config */ > > vif xl0 { > > disable: false > > address 87.240.10.121 { > > prefix-length: 27 > > broadcast: 87.240.10.127 > > disable: false > > } > > } > > } > > interface myk0 { > > description: "data interface" > > disable: false > > /* default-system-config */ > > vif myk0 { > > disable: false > > address 192.168.250.1 { > > prefix-length: 24 > > broadcast: 192.168.250.255 > > disable: false > > } > > } > > } > > } > > > > fea { > > unicast-forwarding4 { > > disable: false > > } > > } > > > > plumbing { > > mfea4 { > > disable: false > > interface xl0 { > > vif xl0 { > > disable: false > > } > > } > > interface myk0 { > > vif myk0 { > > disable: false > > } > > } > > > > interface register_vif { > > vif register_vif { > > /* Note: this vif should be always enabled */ > > disable: false > > } > > } > > traceoptions { > > flag all { > > disable: false > > } > > } > > } > > } > > > > protocols { > > igmp { > > disable: false > > interface myk0 { > > vif myk0 { > > disable: false > > /* version: 2 */ > > /* enable-ip-router-alert-option-check: false */ > > /* query-interval: 125 */ > > /* query-last-member-interval: 1 */ > > /* query-response-interval: 10 */ > > /* robust-count: 2 */ > > } > > } > > traceoptions { > > flag all { > > disable: false > > } > > } > > } > > } > > > > protocols { > > pimsm4 { > > disable: false > > interface myk0 { > > vif myk0 { > > disable: false > > /* enable-ip-router-alert-option-check: false */ > > /* dr-priority: 1 */ > > /* hello-period: 30 */ > > /* hello-triggered-delay: 5 */ > > /* alternative-subnet 10.40.0.0/16 */ > > } > > } > > interface xl0 { > > vif xl0 { > > disable: false > > /* enable-ip-router-alert-option-check: false */ > > /* dr-priority: 1 */ > > /* hello-period: 30 */ > > /* hello-triggered-delay: 5 */ > > /* alternative-subnet 10.40.0.0/16 */ > > } > > } > > interface register_vif { > > vif register_vif { > > /* Note: this vif should be always enabled */ > > disable: false > > } > > } > > > > static-rps { > > rp 192.168.250.1 { > > group-prefix 224.0.0.0/4 { > > /* rp-priority: 0 */ > > /* hash-mask-len: 30 */ > > } > > } > > } > > bootstrap { > > disable: true > > cand-bsr { > > scope-zone 224.0.0.0/4 { > > /* is-scope-zone: false */ > > cand-bsr-by-vif-name: "myk0" > > /* cand-bsr-by-vif-addr: 10.10.10.10 */ > > /* bsr-priority: 1 */ > > /* hash-mask-len: 30 */ > > } > > } > > > > cand-rp { > > group-prefix 224.0.0.0/4 { > > /* is-scope-zone: false */ > > cand-rp-by-vif-name: "myk0" > > /* cand-rp-by-vif-addr: 10.10.10.10 */ > > /* rp-priority: 192 */ > > /* rp-holdtime: 150 */ > > } > > } > > } > > > > switch-to-spt-threshold { > > /* approx. 1K bytes/s (10Kbps) threshold */ > > disable: false > > interval: 100 > > bytes: 102400 > > } > > > > traceoptions { > > flag all { > > disable: false > > } > > } > > } > > > > } > > > > protocols { > > fib2mrib { > > disable: false > > } > > } > > ------------------- With best regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070110/b782b464/attachment.html From pavlin at icir.org Tue Jan 9 17:58:10 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Tue, 09 Jan 2007 17:58:10 -0800 Subject: [Xorp-users] routing provider's TV (PIM-SM) In-Reply-To: Message from Vyacheslav Druzhinin of "Wed, 10 Jan 2007 00:01:55 +0300." <200701100001.56061.dvg@tjc.ru> Message-ID: <200701100158.l0A1wAp8043804@possum.icir.org> > > > I'm using FreeBSD 6.1p11 and XORP from net/xorp port 1.3_1 version. > > > My provider uses cisco router for internet and igmp pim-sm TV > > > multicasting, on my BSD box the VLC player works fine. I want to use the > > > BSD box as multicast router for WinXP box. Here is my LAN scheme. > > > > > > (Provider CISCO) > > > 87.240.10.97-------xl0 (87.240.10.121) BSD myk0 (192.168.250.1)----- > > > 192.168.250.2 (WinXP box) > > > > > > I'm tried this > > > xorp.conf > > > > Your XORP configuration looks fine, except that the static RP > > address is incorrectly set to your own IP address > > (192.168.250.1). Instead, it should be set to the RP address used by > > your provider (assuming your provider allows your PIM-SM router to > > be part of its PIM-SM domain). > > > > This is also the reason you don't see any PIM-SM Join messages from > > your BGP box to your provider. > > > > Hope that helps, > > Pavlin > > Thank you very much. I've changed the static-rp string to > provider's cisco router - 87.240.10.97, but vlc on winXP still > does not work. But if I starting to view any TV channel on BSD box > and at the same time starting to view the channel on winXP box it > shows on it. It happens to work, because once your pull the multicast data down to your BSD box (with the application running on that box), then the XORP router running on the BSD box can forward the data to the WinXP box. > Provider's tech support does not wish to tell me an RP IP > address. I don't know the RP's IP, simply wrote my router's IP. Somehow I am not surprised they didn't tell you that info :) The way PIM-SM works is that all PIM-SM routers must agree on the same RP (per multicast group prefix). Hence, unfortunately without the RP address from your ISP you cannot become a part of the ISP's PIM-SM domain. > I assume there are two variants. Provider has filtering PIM-SM > Join messages or I don't know correct IP address of RP. The correct IP address of the RP is a must. On top of that they might be filtering the PIM-SM Join messages as well. In any case, it doesn't look like your ISP wants you to become a part of their PIM-SM domain, so you shouldn't try to tweak XORP to get it working. > There is the third variant, an igmp proxy software can helps me, > but I don't know any igmp proxy solution for FreeBSD, only for > linux (igmpproxy project on sourceforge, it is mix from pimd and > smcroute). :( IGMP proxy is what I was going to suggest as a solution of your problem. Unfortunately, currently XORP doesn't implement it (we have it on our radar though). One of the options is the IGMPproxy implementation (the one you mention above): http://sourceforge.net/projects/igmpproxy The other one is the IGMPv3proxy: http://potiron.loria.fr/projects/madynes/internals/perso/lahmadi/igmpv3proxy I haven't used either one, but if IGMPproxy from Sourceforge is only for Linux then you could try IGMPv3proxy. According to the Web site it is suppose to work for BSD as well. Note that it is suppose to be IGMPv3 proxy, but if it implements the full IGMPv3 specification, then it should work with IGMPv1 and IGMPv2 clients as well. Please let us know whether it works for you. Regards, Pavlin From dvg at tjc.ru Wed Jan 10 13:35:22 2007 From: dvg at tjc.ru (Vyacheslav Druzhinin) Date: Thu, 11 Jan 2007 00:35:22 +0300 Subject: [Xorp-users] routing provider's TV (PIM-SM) In-Reply-To: <200701100158.l0A1wAp8043804@possum.icir.org> References: <200701100158.l0A1wAp8043804@possum.icir.org> Message-ID: <200701110035.22262.dvg@tjc.ru> Hi, 10.01.2007 04:58 you wrote: > > Thank you very much. I've changed the static-rp string to > > provider's cisco router - 87.240.10.97, but vlc on winXP still > > does not work. But if I starting to view any TV channel on BSD box > > and at the same time starting to view the channel on winXP box it > > shows on it. > It happens to work, because once your pull the multicast data down > to your BSD box (with the application running on that box), then the > XORP router running on the BSD box can forward the data to the WinXP > box. I get it. > > Provider's tech support does not wish to tell me an RP IP > > address. I don't know the RP's IP, simply wrote my router's IP. > Somehow I am not surprised they didn't tell you that info :) I get it too :) > The correct IP address of the RP is a must. On top of that they > might be filtering the PIM-SM Join messages as well. > In any case, it doesn't look like your ISP wants you to become a > part of their PIM-SM domain, so you shouldn't try to tweak XORP to > get it working. Unfortunately, it is real. :( > IGMP proxy is what I was going to suggest as a solution of your > problem. Unfortunately, currently XORP doesn't implement it (we have > it on our radar though). hope proxy mode will appear in XORP :) > One of the options is the IGMPproxy implementation (the one you > mention above): > http://sourceforge.net/projects/igmpproxy Too hard work fo me to port it to BSD system :-( > The other one is the IGMPv3proxy: > http://potiron.loria.fr/projects/madynes/internals/perso/lahmadi/igmpv3proxy I can't compile it, gcc reports too many errors, I couldn't fix them, I'm newbie in C++ lang :( but I wrote a message to the author of IGMP v3 proxy Lahmadi Abdelkader and include error reports. Waiting for the answer. :) > I haven't used either one, but if IGMPproxy from Sourceforge is only > for Linux then you could try IGMPv3proxy. According to the Web site > it is suppose to work for BSD as well. Note that it is suppose to be > IGMPv3 proxy, but if it implements the full IGMPv3 specification, > then it should work with IGMPv1 and IGMPv2 clients as well. I googled for IGMP v.3 proxy, and nobody can compile the sources. :( I've checked provider's forums for my problem, and has found igmpproxy for linux work fine, but I like a BSD systems :-/ Btw, hardware routers like Dlink DI-808HV (or linksys wrt54g) work fine too. They are using igmpproxy afaik. > Please let us know whether it works for you. By all means I'll write about results. > Regards, > Pavlin -------------------- With best regards, Vyacheslav. From pmancheno at gmail.com Thu Jan 11 22:20:38 2007 From: pmancheno at gmail.com (Pepo) Date: Fri, 12 Jan 2007 01:20:38 -0500 Subject: [Xorp-users] snmp/mrtg with Xorp Message-ID: <200701120120.56226.pmancheno@gmail.com> Hi friends... I was trying to get statistics with MRTG about the traffic on the interface (and virtual interfaces of tunnels) of my PC that is using Xorp for multicast distribution, but I can't get good results, maybe the traffic is so small (is my test-LAN for my thesis) or, Do I have to compile again my xorp-sofware using "./configure --with-snmp" or can I use snmpd and snmp packages of my Debian-Etch distribution? A lot of thanks. -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070112/e7e66714/attachment.bin From pavlin at icir.org Thu Jan 11 22:45:43 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Thu, 11 Jan 2007 22:45:43 -0800 Subject: [Xorp-users] snmp/mrtg with Xorp In-Reply-To: Message from Pepo of "Fri, 12 Jan 2007 01:20:38 EST." <200701120120.56226.pmancheno@gmail.com> Message-ID: <200701120645.l0C6jhlX003928@possum.icir.org> > I was trying to get statistics with MRTG about the traffic on the interface > (and virtual interfaces of tunnels) of my PC that is using Xorp > for multicast > distribution, but I can't get good results, maybe the traffic is > so small (is > my test-LAN for my thesis) or, Do I have to compile again my xorp-sofware > using "./configure --with-snmp" or can I use snmpd and snmp packages of my > Debian-Etch distribution? Currently XORP has very limited SNMP support (practically only for BGP), and doesn't support any interface-related MIBs. Hence you need to configure and run outside of XORP an SNMP daemon that will serve the SNMP queries originated by MRTG. Regards, Pavlin From ashishkarpe at gmail.com Fri Jan 12 03:25:44 2007 From: ashishkarpe at gmail.com (Ashish Karpe) Date: Fri, 12 Jan 2007 03:25:44 -0800 Subject: [Xorp-users] basic problem Message-ID: hi all, can anyone tell me where does xorp gets installed by default ? Because 1st time when i installed it was installed in "/usr/local/xorp" . But now when i installed it on different machine i am not able to find it in "/usr/local/xorp" . What should i do ? As i have installed using source code i have xorp_rtrmgr & xorpsh in source directory so should i use this files from its current directory ? ps : I am using SuSe 9.0 within Vmware & ./configure gmake & gmake check were successful while compilation ! thanks, ashish From allan at vyatta.com Fri Jan 12 08:56:06 2007 From: allan at vyatta.com (Allan Leinwand) Date: Fri, 12 Jan 2007 08:56:06 -0800 Subject: [Xorp-users] snmp/mrtg with Xorp In-Reply-To: <200701120120.56226.pmancheno@gmail.com> Message-ID: <000901c7366a$8eda6860$6470c80a@pc.int> Hi Pepo, I believe that the XORP distribution has limited SNMP agent support. In the free Vyatta community edition we have SNMP agent support for MIB-2 that works well with MRTG: www.vyatta.com Thanks, allan -----Original Message----- From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of Pepo Sent: Thursday, January 11, 2007 10:21 PM To: xorp-users at xorp.org Subject: [Xorp-users] snmp/mrtg with Xorp Hi friends... I was trying to get statistics with MRTG about the traffic on the interface (and virtual interfaces of tunnels) of my PC that is using Xorp for multicast distribution, but I can't get good results, maybe the traffic is so small (is my test-LAN for my thesis) or, Do I have to compile again my xorp-sofware using "./configure --with-snmp" or can I use snmpd and snmp packages of my Debian-Etch distribution? A lot of thanks. -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From pavlin at icir.org Fri Jan 12 10:40:56 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Fri, 12 Jan 2007 10:40:56 -0800 Subject: [Xorp-users] basic problem In-Reply-To: Message from "Ashish Karpe" of "Fri, 12 Jan 2007 03:25:44 PST." Message-ID: <200701121840.l0CIeupK009727@possum.icir.org> Ashish Karpe wrote: > hi all, > can anyone tell me where does xorp gets installed by default ? > Because 1st time when i installed it was installed in > "/usr/local/xorp" . But now when i installed it on different machine i > am not able to find it in "/usr/local/xorp" . What should i do ? As i > have installed using source code i have xorp_rtrmgr & xorpsh in source > directory so should i use this files from its current directory ? > > ps : I am using SuSe 9.0 within Vmware & ./configure gmake & gmake > check were successful while compilation ! Yes, by default it should be installed in the /usr/local/xorp directory. However, if you installed using your system's packaging system (ports/portage/pkgsrc/etc), then this default might have been changed to something else. Assuming you didn't use your system's packaging, then when you run "gmake install" you should see lots of messages like those included below. The messages will include the path to the directory where the binaries are installed. In the example below the "xorp_fea" and "xorp_fea_dummy" binaries will be installed in the "/usr/local/xorp/fea" directory. The xorp_rtrmgr and xorpsh binaries should be installed in the /usr/local/xorp/bin directory. Hope that helps, Pavlin =========================================================== gmake[2]: Entering directory `/home/xorp12/u0/pavlin/work/xorp/FreeBSD-xorp/fea' gmake install-exec-am install-data-am gmake[3]: Entering directory `/home/xorp12/u0/pavlin/work/xorp/FreeBSD-xorp/fea' : /usr/local/bin/bash ../config/mkinstalldirs /usr/local/xorp/fea list='xorp_fea xorp_fea_dummy'; for p in $list; do \ p1=`echo $p|sed 's/$//'`; \ if test -f $p \ || test -f $p1 \ ; then \ f=`echo $p1|sed 's,x,x,;s/$//'`; \ echo " /usr/local/bin/bash ../libtool --mode=install /usr/bin/install -c $p /usr/local/xorp/fea/$f"; \ /usr/local/bin/bash ../libtool --mode=install /usr/bin/install -c $p /usr/local/xorp/fea/$f; \ else :; fi; \ done : /usr/local/bin/bash ../config/mkinstalldirs /usr/local/xorp/fea list='xorp_fea_click_config_generator'; for p in $list; do \ f="`echo $p|sed 's,x,x,'`"; \ if test -f $p; then \ echo " /usr/bin/install -c $p /usr/local/xorp/fea/$f"; \ /usr/bin/install -c $p /usr/local/xorp/fea/$f; \ elif test -f ./$p; then \ echo " /usr/bin/install -c ./$p /usr/local/xorp/fea/$f"; \ /usr/bin/install -c ./$p /usr/local/xorp/fea/$f; \ else :; fi; \ done gmake[3]: Nothing to be done for `install-data-am'. gmake[3]: Leaving directory `/home/xorp12/u0/pavlin/work/xorp/FreeBSD-xorp/fea' gmake[2]: Leaving directory `/home/xorp12/u0/pavlin/work/xorp/FreeBSD-xorp/fea' =========================================================== From koippa at gmail.com Fri Jan 12 14:09:21 2007 From: koippa at gmail.com (Kimmo Koivisto) Date: Sat, 13 Jan 2007 00:09:21 +0200 Subject: [Xorp-users] Help needed for basic PIM-SM configuration Message-ID: <200701130009.22387.koippa@gmail.com> Hello I don't have much experience from xorp or PIM-SM and I need some assistance setting up xorp for my simple testing environment. I have RHEL4 + xorp 1.3 based routers R1-R4, multicast sender S1 and receiver C1. Sender sends video to the multicast address 225.1.1.1. At this time, my network is very simple: [S1]--[R1]-[R2]-[R3]-[R4]-[C1] All the routers R1-R4 have the same kind of interface setup: <--{eth0}[Rn]{eth1}--> Eth0 is towards the S1 and eth1 is towards C1. I have enabled OSPF and routing is working okay. I have tried to configure PIM-SM but did not succeed (what "xorpsh>show pim rps" and "xorpsh>show pim bootstrap" should show when everything is in order?). All the routers have now this configuration: protocols { pimsm4 { disable: false interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { disable: false } } bootstrap { disable: false cand-bsr { scope-zone 225.0.0.1/32 { cand-bsr-by-vif-name: "eth0" } } cand-rp { group-prefix 225.0.0.1/32 { cand-rp-by-vif-name: "eth0" } } } switch-to-spt-threshold { disable: false interval: 100 bytes: 102400 } traceoptions { flag all { disable: false } } } } I would appreciate if someone could give me some instructions if my config is invalid and how xorp should be configured for this scenario. Best Regards Kimmo Koivisto From pavlin at icir.org Fri Jan 12 14:44:32 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Fri, 12 Jan 2007 14:44:32 -0800 Subject: [Xorp-users] Help needed for basic PIM-SM configuration In-Reply-To: Message from Kimmo Koivisto of "Sat, 13 Jan 2007 00:09:21 +0200." <200701130009.22387.koippa@gmail.com> Message-ID: <200701122244.l0CMiW21027438@possum.icir.org> > I don't have much experience from xorp or PIM-SM and I need some assistance > setting up xorp for my simple testing environment. > > I have RHEL4 + xorp 1.3 based routers R1-R4, multicast sender S1 and receiver > C1. Sender sends video to the multicast address 225.1.1.1. > > At this time, my network is very simple: > > [S1]--[R1]-[R2]-[R3]-[R4]-[C1] > > All the routers R1-R4 have the same kind of interface setup: > > <--{eth0}[Rn]{eth1}--> > > Eth0 is towards the S1 and eth1 is towards C1. > > I have enabled OSPF and routing is working okay. I have tried to configure > PIM-SM but did not succeed (what "xorpsh>show pim rps" and "xorpsh>show pim > bootstrap" should show when everything is in order?). The "show pim bootstrap" command should show information related to the election of the Bootstrap router (BSR). Once the BSR has been elected and it has propagated the Cand-RP information, you should be able to see the Cand-RP set using the "show pim rps" command. If the "show pim rps" output is empty, then your PIM-SM routers haven't received the Cand-RP information. Note that on startup it might take 1-3 minutes until the BSR election is completed and the Cand-RP set is propagated. Hence, for testing purpose I'd recommend to use static RP setup. Your PIM-SM configuration seems fine, but it is unclear whether you have configured other multicast-related modules like fib2mrib. This is what your multicast-specific oprtion of your configuration should look like. You would need to replace 10.10.10.10 with the IP address of one of your PIM-SM routers (the RP). Regards, Pavlin ===================================================== plumbing { mfea4 { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { disable: false } } } } protocols { igmp { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } } pimsm4 { interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { disable: false } } static-rps { rp 10.10.10.10 { group-prefix 224.0.0.0/4 { } } } } fib2mrib { disable: false } } ===================================================== From ashishkarpe at gmail.com Sat Jan 13 07:42:57 2007 From: ashishkarpe at gmail.com (Ashish Karpe) Date: Sat, 13 Jan 2007 07:42:57 -0800 Subject: [Xorp-users] Want help on static route config for xorp Message-ID: hi all, I am using Vmware & want to use Xorp ! i have following topology : A -------------------> B ---------------------> C 192.168.0.2 eth0 192.168.0.199 172.20.16.22 eth1 172.20.16.199 Now if xorp is configured properly on B then A will be able to ping C ! (please correct me if wrong) ********************************************************************************************************** This is my config file which i wrote with help of getting_started.html from www.xorp.org I want it to work for static configuration. interfaces { restore-original-config-on-shutdown: false interface eth0 { description: "data interface" disable: false /* default-system-config */ vif eth0 { disable: false address 192.168.0.199 { prefix-length: 24 broadcast: 192.168.0.255 disable: false } /* address 10:10:10:10:10:10:10:10 { prefix-length: 64 disable: false } */ } } interface eth1 { description: " Data Interface " disable: false vif eth1 { disable: false address 172.20.16.199 { prefix-length: 24 broadcast: 172.20.16.255 disable: false } } } } fea { unicast-forwarding4 { disable: false } unicast-forwarding6 { disable: false } } protocols { static { route 192.168.0.199/16 { next-hop: 172.20.16.199 metric: 1 } /* mrib-route 10.20.0.0/16 { next-hop: 10.10.10.30 metric: 1 } route 20:20:20:20::/64 { next-hop: 10:10:10:10:10:10:10:20 metric: 1 } mrib-route 20:20:20:20::/64 { next-hop: 10:10:10:10:10:10:10:30 metric: 1 } */ } } ******************************************************************************************************************************** This was o/p when i tried to run xorp_rtrmgr & i am not able to ping from A to C !! please let me know what is missing ??? linux:/usr/local/xorp # ./bin/xorp_rtrmgr -b ./static_config.boot [ 2007/01/13 07:50:10 INFO xorp_rtrmgr:4206 RTRMGR +240 master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, policy, static_routes [ 2007/01/13 07:50:10 INFO xorp_rtrmgr:4206 RTRMGR +99 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] MFEA enabled [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] CLI enabled [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] CLI started [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] MFEA enabled [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] CLI enabled [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] CLI started [ 2007/01/13 07:50:12 INFO xorp_rtrmgr:4206 RTRMGR +99 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2007/01/13 07:50:18 INFO xorp_rtrmgr:4206 RTRMGR +99 module_manager.cc execute ] Executing module: rib (rib/xorp_rib) [ 2007/01/13 07:50:20 INFO xorp_rtrmgr:4206 RTRMGR +99 module_manager.cc execute ] Executing module: policy (policy/xorp_policy) [ 2007/01/13 07:50:22 INFO xorp_rtrmgr:4206 RTRMGR +99 module_manager.cc execute ] Executing module: static_routes (static_routes/xorp_static_routes) [ 2007/01/13 07:50:24 INFO xorp_rtrmgr:4206 RTRMGR +2228 task.cc run_task ] No more tasks to run thanks, ashish From koippa at gmail.com Sat Jan 13 13:02:47 2007 From: koippa at gmail.com (Kimmo Koivisto) Date: Sat, 13 Jan 2007 23:02:47 +0200 Subject: [Xorp-users] Fwd: Re: Help needed for basic PIM-SM configuration Message-ID: <200701132302.47224.koippa@gmail.com> And my answer to Pavlin to the list too: On Saturday 13 January 2007 00:44, you wrote: > > I have enabled OSPF and routing is working okay. I have tried to > > configure PIM-SM but did not succeed (what "xorpsh>show pim rps" and > > "xorpsh>show pim bootstrap" should show when everything is in order?). > > The "show pim bootstrap" command should show information related to > the election of the Bootstrap router (BSR). Once the BSR has been > elected and it has propagated the Cand-RP information, you should be > able to see the Cand-RP set using the "show pim rps" command. > If the "show pim rps" output is empty, then your PIM-SM routers > haven't received the Cand-RP information. I simplified my environment so that I only ha sender S1, two routers R1-R2 and received C1. Multicast started working with the simplified configuration, I have to try again with four routers. Now "show pim bootstrap" shows: Active zones: BSR Pri LocalAddress Pri State Timeout SZTimeout 172.16.125.100 1 172.16.125.100 1 Elected 30 -1 192.168.210.100 1 0.0.0.0 0 AcceptPreferred 121 1291 Expiring zones: BSR Pri LocalAddress Pri State Timeout SZTimeout Configured zones: BSR Pri LocalAddress Pri State Timeout SZTimeout 172.16.125.100 1 172.16.125.100 1 Init -1 -1 and "show pim rps" shows: RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix 172.16.125.100 bootstrap 192 150 -1 1 225.1.1.1/32 192.168.210.100 bootstrap 192 -1 -1 0 225.1.1.1/32 Does this look like it should? Those IP addresses are from router R1 and R2. > Your PIM-SM configuration seems fine, but it is unclear whether you > have configured other multicast-related modules like fib2mrib. Yes, I have fib2mrib configured. My config is exactly as your example, only difference is that I don't have static RP. > This is what your multicast-specific oprtion of your configuration > should look like. You would need to replace 10.10.10.10 with the IP > address of one of your PIM-SM routers (the RP). > > Regards, > Pavlin Thanks for your help. I got my simplified environment working. Only problem is that I have to learn more about PIM-SM to understand xorp behaviour. Regards Kimmo ------------------------------------------------------- From koippa at gmail.com Sun Jan 14 03:36:06 2007 From: koippa at gmail.com (Kimmo Koivisto) Date: Sun, 14 Jan 2007 13:36:06 +0200 Subject: [Xorp-users] Compiling xorp, how to change default paths Message-ID: <200701141336.07051.koippa@gmail.com> Hello I'm using xorp 1.3 in RHEL4 from rpm (from Dries rpm repository). After installation, things are not as I would like them to be: 1. Default paths for templates etc are now: Boot file := /usr/config.boot Templates directory := /usr/etc/templates Xrl targets directory := /usr/xrl/targets but rpm installs all templates etc to the /usr/share/xorp. And I would like that xorp would use /etc/xorp.conf instead of config.boot as it's config file. Is there configure -option to do these things or do I need to edit some Makefile.in files? Rpm uses only this option to configure: --datadir=/usr/share/xorp 2. rpm installs xorp_rtrmgr to /usr/bin which is fine. Other parts such as xorp_fea are installed to /usr/bin too. And that is fine too. But when xorp_rtrmgr starts, it tries to find xorp_fea from /usr/fea/xorp_fea, same thing with other parts. So now I need to create /usr/"xorp-component" directories and symlink binaries from /usr/bin to /usr/"xorp-component". Can I change this easily so that xorp_rtrmgr would not use any static paths when starting those other parts? 3. I start xorp_rtrmgr to the backgroud and then kill it with SIGTERM. Is this proper way to shutdown xorp so that it can exit cleanly or should I use some other signal? 4. Template or Xrl files (I don't know what there are) have paths for commands, for example if file bgp.cmds has %command parameter: show bgp peers { %command: "bgp/tools/xorpsh_print_peers $0" %help: HELP; %module: bgp; %tag: HELP "Show BGP peers info"; } That has path bgp/tools in it. rpm installs xorpsh_print_peers to /usr/bin/ and xorpsh does not start. I had to change that file (and others too) so that there is no paths in %command: show bgp peers { %command: "xorpsh_print_peers $0" %help: HELP; %module: bgp; %tag: HELP "Show BGP peers info"; } Are those command paths somehow configurable when compiling? These questions might be quite stupid, I don't really know much about xorp :) Regards Kimmo Koivisto -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070114/5ec28cc8/attachment.html From pmancheno at gmail.com Sun Jan 14 16:58:58 2007 From: pmancheno at gmail.com (Pepo) Date: Sun, 14 Jan 2007 19:58:58 -0500 Subject: [Xorp-users] Virtual interfaces in GNU/Linux (now IPv6) In-Reply-To: <200612180829.kBI8TxGj055932@possum.icir.org> References: <200612180829.kBI8TxGj055932@possum.icir.org> Message-ID: <200701141958.59112.pmancheno@gmail.com> El Lunes, 18 de Diciembre de 2006 03:29, escribi?: > > The output using ip addr is: > > > > 1: lo: mtu 16436 qdisc noqueue > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > inet 127.0.0.1/8 scope host lo > > inet6 ::1/128 scope host > > valid_lft forever preferred_lft forever > > 2: eth1: mtu 1500 qdisc pfifo_fast qlen 1000 > > link/ether 52:54:00:12:34:86 brd ff:ff:ff:ff:ff:ff > > inet 192.168.1.10/24 brd 192.168.1.255 scope global eth1 > > inet 192.168.13.1/24 brd 192.168.13.255 scope global eth1:1 > > inet6 fe80::5054:ff:fe12:3486/64 scope link > > valid_lft forever preferred_lft forever > > 3: sit0: mtu 1480 qdisc noop > > link/sit 0.0.0.0 brd 0.0.0.0 > > > > What do you think? > > You have a single network interface (eth1) with two IP addresses. > For multicast routing purpose, this counts as a single interface. > If you have the limitation of only one physical network interface, > but you want to have a multicast router with several network > interfaces, then you need to create virtual interfaces/tunnels such > as GRE tunnels, OpenVPN tunnels, VLANs, etc. > > If you don't have much experience with tunnels setup, I'd recommend > to start with OpenVPN (http://openvpn.net/). It is quite portable > and easy to configure. E.g., you could just run a pair of > commands like the following on both sides of a tunnel: > > openvpn --local 10.6.0.2 --remote 10.9.0.2 --ifconfig 30.30.30.1 > 30.30.30.2 --dev tun0 > openvpn --local 10.9.0.2 --remote 10.6.0.2 --ifconfig 30.30.30.2 > 30.30.30.1 --dev tun0 > > FYI, you could use openvpn even across a NAT because it is TCP/UDP > based. > > After that you need to use the virtual tun0 interface as one of the > interfaces on the XORP router. > > Regards, > Pavlin Hi. I could use tunnels in IPv4, but now I am trying to make the same with IPv6 but I don't know how, this is my commands and error messages: ip link set dev eth0 up ip -6 addr add fec0:2006:2007::1:5/126 dev eth0 (with ping6 fec0:2006:2007::1:6 can see the remote PC) openvpn --remote fec0:2006:2007::1:6 --dev tun0 --tun-ipv6 --ifconfig fec0:2006:2007::2:5 fec0:2006:2007::2:6 Sun Jan 14 19:20:47 2007 OpenVPN 2.0.9 i486-pc-linux-gnu [SSL] [LZO] [EPOLL] built on Oct 10 2006 Sun Jan 14 19:20:47 2007 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port. Sun Jan 14 19:20:47 2007 ******* WARNING *******: all encryption and authentication features disabled -- all data will be tunnelled as cleartext Sun Jan 14 19:20:47 2007 RESOLVE: Cannot resolve host address: fec0:2006:2007::1:6: [HOST_NOT_FOUND] The specified host is unknown. Sun Jan 14 19:20:47 2007 RESOLVE: Cannot resolve host address: fec0:2006:2007::2:5: [HOST_NOT_FOUND] The specified host is unknown. Sun Jan 14 19:20:47 2007 Exiting Please, How do I get a tunnel in IPv6? (I need that to begin with PIM-SM configuration) -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From pavlin at icir.org Mon Jan 15 11:00:37 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 15 Jan 2007 11:00:37 -0800 Subject: [Xorp-users] Want help on static route config for xorp In-Reply-To: Message from "Ashish Karpe" of "Sat, 13 Jan 2007 07:42:57 PST." Message-ID: <200701151900.l0FJ0bBr086237@possum.icir.org> > I am using Vmware & want to use Xorp ! > > i have following topology : > > > A -------------------> B ---------------------> C > 192.168.0.2 eth0 192.168.0.199 172.20.16.22 > eth1 172.20.16.199 > > Now if xorp is configured properly on B then A will be able to ping C > ! (please correct me if wrong) Your configuration seems fine, except for this static route: route 192.168.0.199/16 { next-hop: 172.20.16.199 metric: 1 } You don't need to install static routes for directly-connected subnets, so you should remove this entry. Also, make sure that hos A itself has a route toward C and the next-hop router toward C is B. Same applies for C. Regards, Pavlin > > ********************************************************************************************************** > This is my config file which i wrote with help of getting_started.html > from www.xorp.org I want it to work for static configuration. > > interfaces { > restore-original-config-on-shutdown: false > interface eth0 { > description: "data interface" > disable: false > /* default-system-config */ > vif eth0 { > disable: false > address 192.168.0.199 { > prefix-length: 24 > broadcast: 192.168.0.255 > disable: false > } > /* > address 10:10:10:10:10:10:10:10 { > prefix-length: 64 > disable: false > } > */ > } > } > interface eth1 { > description: " Data Interface " > disable: false > vif eth1 { > disable: false > address 172.20.16.199 { > prefix-length: 24 > broadcast: 172.20.16.255 > disable: false > } > } > } > } > > fea { > unicast-forwarding4 { > disable: false > } > > unicast-forwarding6 { > disable: false > } > } > > > protocols { > static { > route 192.168.0.199/16 { > next-hop: 172.20.16.199 > metric: 1 > } > /* > mrib-route 10.20.0.0/16 { > next-hop: 10.10.10.30 > metric: 1 > } > > route 20:20:20:20::/64 { > next-hop: 10:10:10:10:10:10:10:20 > metric: 1 > } > mrib-route 20:20:20:20::/64 { > next-hop: 10:10:10:10:10:10:10:30 > metric: 1 > } > */ > } > } > > ******************************************************************************************************************************** > This was o/p when i tried to run xorp_rtrmgr & i am not able to ping > from A to C !! please let me know what is missing ??? > > linux:/usr/local/xorp # ./bin/xorp_rtrmgr -b ./static_config.boot > [ 2007/01/13 07:50:10 INFO xorp_rtrmgr:4206 RTRMGR +240 > master_conf_tree.cc execute ] Changed modules: interfaces, fea, rib, > policy, static_routes > [ 2007/01/13 07:50:10 INFO xorp_rtrmgr:4206 RTRMGR +99 > module_manager.cc execute ] Executing module: interfaces > (fea/xorp_fea) > [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] MFEA enabled > [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] CLI enabled > [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] CLI started > [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] MFEA enabled > [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] CLI enabled > [ 2007/01/13 07:50:12 INFO xorp_fea MFEA ] CLI started > [ 2007/01/13 07:50:12 INFO xorp_rtrmgr:4206 RTRMGR +99 > module_manager.cc execute ] Executing module: fea (fea/xorp_fea) > [ 2007/01/13 07:50:18 INFO xorp_rtrmgr:4206 RTRMGR +99 > module_manager.cc execute ] Executing module: rib (rib/xorp_rib) > [ 2007/01/13 07:50:20 INFO xorp_rtrmgr:4206 RTRMGR +99 > module_manager.cc execute ] Executing module: policy > (policy/xorp_policy) > [ 2007/01/13 07:50:22 INFO xorp_rtrmgr:4206 RTRMGR +99 > module_manager.cc execute ] Executing module: static_routes > (static_routes/xorp_static_routes) > [ 2007/01/13 07:50:24 INFO xorp_rtrmgr:4206 RTRMGR +2228 task.cc > run_task ] No more tasks to run > > > > thanks, > ashish > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pavlin at icir.org Mon Jan 15 11:04:56 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 15 Jan 2007 11:04:56 -0800 Subject: [Xorp-users] Fwd: Re: Help needed for basic PIM-SM configuration In-Reply-To: Message from Kimmo Koivisto of "Sat, 13 Jan 2007 23:02:47 +0200." <200701132302.47224.koippa@gmail.com> Message-ID: <200701151904.l0FJ4u6U086269@possum.icir.org> > I simplified my environment so that I only ha sender S1, two routers R1-R2 > and received C1. Multicast started working with the simplified > configuration, I have to try again with four routers. > > Now "show pim bootstrap" shows: > Active zones: > BSR Pri LocalAddress Pri State Timeout SZTimeout > 172.16.125.100 1 172.16.125.100 1 Elected 30 -1 > 192.168.210.100 1 0.0.0.0 0 AcceptPreferred 121 1291 > Expiring zones: > BSR Pri LocalAddress Pri State Timeout SZTimeout > Configured zones: > BSR Pri LocalAddress Pri State Timeout SZTimeout > 172.16.125.100 1 172.16.125.100 1 Init -1 -1 > > and "show pim rps" shows: > RP Type Pri Holdtime Timeout ActiveGroups GroupPrefix > 172.16.125.100 bootstrap 192 150 -1 1 225.1.1.1/32 > 192.168.210.100 bootstrap 192 -1 -1 0 225.1.1.1/32 > > Does this look like it should? Those IP addresses are from router R1 and R2. Yes, this seems correct. After you add more PIM-SM routers double-check that all routers agree that same IP address is the RP for group 225.1.1.1. Regards, Pavlin From pavlin at icir.org Mon Jan 15 11:34:13 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 15 Jan 2007 11:34:13 -0800 Subject: [Xorp-users] Compiling xorp, how to change default paths In-Reply-To: Message from Kimmo Koivisto of "Sun, 14 Jan 2007 13:36:06 +0200." <200701141336.07051.koippa@gmail.com> Message-ID: <200701151934.l0FJYDuZ086887@possum.icir.org> > I'm using xorp 1.3 in RHEL4 from rpm (from Dries rpm repository). After installation, things are not as I would like them to be: > > 1. Default paths for templates etc are now: > Boot file := /usr/config.boot > Templates directory := /usr/etc/templates > Xrl targets directory := /usr/xrl/targets > > but rpm installs all templates etc to the /usr/share/xorp. And I would like that xorp would use /etc/xorp.conf instead of config.boot as it's config file. > > Is there configure -option to do these things or do I need to edit some Makefile.in files? > Rpm uses only this option to configure: > --datadir=/usr/share/xorp The default XORP installation directory is /usr/local/xorp, so it seems that the RPM overwrites that value. If you compile XORP by hand, then you can use the following command to change the installation directory: ./configure --prefix=/path/to/installation/dir I am not familiar in details with RPM, but you can check the rpm manual page whether the rpm command itself gives you the option of overwriting the installation path. E.g., check the "--prefix" command line option. Regarding using a different configuration file, you can use the "-b" command line option. E.g. xorp_rtrmgr -b /etc/xorp.conf The templates directory can be specified with the "-t" command-line option to xorp_rtrmgr. The XRL targets directory can be specified with the "-x" command-line option. If everything was installed relative to the XORP installation directory, then you shouldn't need to explicitly specify the templates directory and the XRL targets directory. > 2. rpm installs xorp_rtrmgr to /usr/bin which is fine. Other parts such as xorp_fea are installed to /usr/bin too. And that is fine too. > But when xorp_rtrmgr starts, it tries to find xorp_fea from /usr/fea/xorp_fea, same thing with other parts. > So now I need to create /usr/"xorp-component" directories and symlink binaries from /usr/bin to /usr/"xorp-component". All binaries executed by the xorp_rtrmgr are relative from the XORP installation directory. E.g., the xorp_fea binary is suppose to be found in /fea/xorp_fea, the xorp_bgp binary is suppose to be found in /bgp/xorp_bgp, and so on. > Can I change this easily so that xorp_rtrmgr would not use any static paths when starting those other parts? To overwrite those values in XORP you need to edit the corresponding rtrmgr template files (the *.tp files that are installed in the template directory). It seems that the RPM installation has decided to break the default XORP setup and has scattered the XORP components (without providing the glue between them). Hence, you have the option of glueing things together (following the above advice), or just download the vanilla XORP tarball and then compile it and install it on your own. > 3. I start xorp_rtrmgr to the backgroud and then kill it with SIGTERM. Is this proper way to shutdown xorp so that it can exit cleanly or should I use some other signal? Yes, this should work. FYI, if you download the latest XORP code (from CVS), in the xorp/contrib/packages directory you will find scripts (currently only for Debian) how to start XORP during boot. You could try to adapt those scripts for your OS. > 4. Template or Xrl files (I don't know what there are) have paths for commands, for example if file bgp.cmds has %command parameter: > show bgp peers { > %command: "bgp/tools/xorpsh_print_peers $0" %help: HELP; > %module: bgp; > %tag: HELP "Show BGP peers info"; > } > > That has path bgp/tools in it. rpm installs xorpsh_print_peers to /usr/bin/ and xorpsh does not start. I had to change that file (and others too) so that there is no paths in %command: > > show bgp peers { > %command: "xorpsh_print_peers $0" %help: HELP; > %module: bgp; > %tag: HELP "Show BGP peers info"; > } > > Are those command paths somehow configurable when compiling? No those paths are not configurable (apart of editing the *.tp and *.cmds files themselves), and they are suppose to be relative to the XORP (installation) root directory. Again, given that the RPM breaks a number of things I'd recommend to stay away from it and use the vanilla XORP tarball+installation. It should compile for RedHat, but let us know if there are any compilation issues. Regards, Pavlin From pavlin at icir.org Mon Jan 15 11:46:50 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 15 Jan 2007 11:46:50 -0800 Subject: [Xorp-users] Virtual interfaces in GNU/Linux (now IPv6) In-Reply-To: Message from Pepo of "Sun, 14 Jan 2007 19:58:58 EST." <200701141958.59112.pmancheno@gmail.com> Message-ID: <200701151946.l0FJkoOj087048@possum.icir.org> > Hi. I could use tunnels in IPv4, but now I am trying to make the same with > IPv6 but I don't know how, this is my commands and error messages: > > ip link set dev eth0 up > ip -6 addr add fec0:2006:2007::1:5/126 dev eth0 > > (with ping6 fec0:2006:2007::1:6 can see the remote PC) > > openvpn --remote fec0:2006:2007::1:6 --dev tun0 --tun-ipv6 --ifconfig > fec0:2006:2007::2:5 fec0:2006:2007::2:6 > > Sun Jan 14 19:20:47 2007 OpenVPN 2.0.9 i486-pc-linux-gnu [SSL] [LZO] [EPOLL] > built on Oct 10 2006 > Sun Jan 14 19:20:47 2007 IMPORTANT: OpenVPN's default port number is now 1194, > based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and > earlier used 5000 as the default port. > Sun Jan 14 19:20:47 2007 ******* WARNING *******: all encryption and > authentication features disabled -- all data will be tunnelled as cleartext > Sun Jan 14 19:20:47 2007 RESOLVE: Cannot resolve host address: > fec0:2006:2007::1:6: [HOST_NOT_FOUND] The specified host is unknown. > Sun Jan 14 19:20:47 2007 RESOLVE: Cannot resolve host address: > fec0:2006:2007::2:5: [HOST_NOT_FOUND] The specified host is unknown. > Sun Jan 14 19:20:47 2007 Exiting > > Please, How do I get a tunnel in IPv6? (I need that to begin with PIM-SM > configuration) Unfortunately I haven't tried to use openvpn for IPv6 so I don't have the answer. You might want to ask the OpenVPN folks (http://www.openvpn.net/). Please let us know if you find anything. Regards, Pavlin From pmancheno at gmail.com Mon Jan 15 17:11:34 2007 From: pmancheno at gmail.com (Pepo) Date: Mon, 15 Jan 2007 20:11:34 -0500 Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. Message-ID: <200701152011.36086.pmancheno@gmail.com> Hi friends. I have PCs with just one nic each one, and these PCs are working like routers for my test-LAN (for my thesis); when have to route to different sub-nets I use tunnels in IPv4 with OpenVpn to virtual-connect directly each router. Now, I have to do the same thing but in IPv6. how do I make tunnels from IPv6 to other IPv6 address? In IPv4 use this: (A) openvpn --remote 192.168.13.2 --dev tun0 --ifconfig 30.30.30.1 30.30.30.2 (B) openvpn --remote 192.168.13.1 --dev tun0 --ifconfig 30.30.30.2 30.30.30.1 -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From jongwooh at gmail.com Mon Jan 15 17:36:44 2007 From: jongwooh at gmail.com (Jongwoo Han) Date: Tue, 16 Jan 2007 10:36:44 +0900 Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. In-Reply-To: <200701152011.36086.pmancheno@gmail.com> References: <200701152011.36086.pmancheno@gmail.com> Message-ID: <007e01c7390e$c99c0840$367ba8c0@jongwooh> You should use GRE tunnel to encapsulate IPv6 in IPv6, not openvpn. -------- jongwooh > -----Original Message----- > From: xorp-users-bounces at xorp.org > [mailto:xorp-users-bounces at xorp.org] On Behalf Of Pepo > Sent: Tuesday, January 16, 2007 10:12 AM > To: Vyatta-users at rio.vyatta.com; xorp-users at xorp.org > Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. > > Hi friends. > > I have PCs with just one nic each one, and these PCs are > working like routers > for my test-LAN (for my thesis); when have to route to > different sub-nets I > use tunnels in IPv4 with OpenVpn to virtual-connect directly > each router. > > Now, I have to do the same thing but in IPv6. how do I make > tunnels from IPv6 > to other IPv6 address? > > In IPv4 use this: > (A) > openvpn --remote 192.168.13.2 --dev tun0 --ifconfig > 30.30.30.1 30.30.30.2 > (B) > openvpn --remote 192.168.13.1 --dev tun0 --ifconfig > 30.30.30.2 30.30.30.1 > > -- > > Linux User Registered #232544 > Jabber : pepo at jabberes.org > Ekiga : pepo at ekiga.net > ICQ : 337889406 > GnuPG-key : www.keyserver.net > ----------------------------------------------- > dum loquimur, fugerit invida > aetas: carpe diem, quam minimum credula postero. > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pmancheno at gmail.com Mon Jan 15 17:54:24 2007 From: pmancheno at gmail.com (Pepo) Date: Mon, 15 Jan 2007 20:54:24 -0500 Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. In-Reply-To: <007e01c7390e$c99c0840$367ba8c0@jongwooh> References: <200701152011.36086.pmancheno@gmail.com> <007e01c7390e$c99c0840$367ba8c0@jongwooh> Message-ID: <200701152054.25261.pmancheno@gmail.com> El Lunes, 15 de Enero de 2007 20:36, Jongwoo Han escribi?: > You should use GRE tunnel to encapsulate IPv6 in IPv6, not openvpn. > > > -------- > jongwooh > Please, where do I can look up information about GRE to make ipv6-in-ipv6 ... I've used Google but I just found ipv6-in-ipv4 :( Can you help me please? > > -----Original Message----- > > From: xorp-users-bounces at xorp.org > > [mailto:xorp-users-bounces at xorp.org] On Behalf Of Pepo > > Sent: Tuesday, January 16, 2007 10:12 AM > > To: Vyatta-users at rio.vyatta.com; xorp-users at xorp.org > > Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. > > > > Hi friends. > > > > I have PCs with just one nic each one, and these PCs are > > working like routers > > for my test-LAN (for my thesis); when have to route to > > different sub-nets I > > use tunnels in IPv4 with OpenVpn to virtual-connect directly > > each router. > > > > Now, I have to do the same thing but in IPv6. how do I make > > tunnels from IPv6 > > to other IPv6 address? > > > > In IPv4 use this: > > (A) > > openvpn --remote 192.168.13.2 --dev tun0 --ifconfig > > 30.30.30.1 30.30.30.2 > > (B) > > openvpn --remote 192.168.13.1 --dev tun0 --ifconfig > > 30.30.30.2 30.30.30.1 > > -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From jongwooh at gmail.com Mon Jan 15 18:18:25 2007 From: jongwooh at gmail.com (Jongwoo Han) Date: Tue, 16 Jan 2007 11:18:25 +0900 Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. In-Reply-To: <200701152054.25261.pmancheno@gmail.com> References: <200701152011.36086.pmancheno@gmail.com> <007e01c7390e$c99c0840$367ba8c0@jongwooh> <200701152054.25261.pmancheno@gmail.com> Message-ID: <008c01c73914$9c2ea420$367ba8c0@jongwooh> Linux support for IPv6-in-IPv6 is not quite complete, but I think you can try 'ip6tunnel' command for it. -------- jongwooh > -----Original Message----- > From: Pepo [mailto:pmancheno at gmail.com] > Sent: Tuesday, January 16, 2007 10:54 AM > To: jongwooh at gmail.com; xorp-users at xorp.org > Subject: Re: [Xorp-users] Virtual interfaces in IPv6 for routing. > > El Lunes, 15 de Enero de 2007 20:36, Jongwoo Han escribi?: > > You should use GRE tunnel to encapsulate IPv6 in IPv6, not openvpn. > > > > > > -------- > > jongwooh > > > Please, where do I can look up information about GRE to make > ipv6-in-ipv6 ... > I've used Google but I just found ipv6-in-ipv4 :( > > Can you help me please? > > > > -----Original Message----- > > > From: xorp-users-bounces at xorp.org > > > [mailto:xorp-users-bounces at xorp.org] On Behalf Of Pepo > > > Sent: Tuesday, January 16, 2007 10:12 AM > > > To: Vyatta-users at rio.vyatta.com; xorp-users at xorp.org > > > Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. > > > > > > Hi friends. > > > > > > I have PCs with just one nic each one, and these PCs are > > > working like routers > > > for my test-LAN (for my thesis); when have to route to > > > different sub-nets I > > > use tunnels in IPv4 with OpenVpn to virtual-connect directly > > > each router. > > > > > > Now, I have to do the same thing but in IPv6. how do I make > > > tunnels from IPv6 > > > to other IPv6 address? > > > > > > In IPv4 use this: > > > (A) > > > openvpn --remote 192.168.13.2 --dev tun0 --ifconfig > > > 30.30.30.1 30.30.30.2 > > > (B) > > > openvpn --remote 192.168.13.1 --dev tun0 --ifconfig > > > 30.30.30.2 30.30.30.1 > > > > > -- > > Linux User Registered #232544 > Jabber : pepo at jabberes.org > Ekiga : pepo at ekiga.net > ICQ : 337889406 > GnuPG-key : www.keyserver.net > ----------------------------------------------- > dum loquimur, fugerit invida > aetas: carpe diem, quam minimum credula postero. > From pmancheno at gmail.com Mon Jan 15 18:27:10 2007 From: pmancheno at gmail.com (Pepo) Date: Mon, 15 Jan 2007 21:27:10 -0500 Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. In-Reply-To: <008c01c73914$9c2ea420$367ba8c0@jongwooh> References: <200701152011.36086.pmancheno@gmail.com> <200701152054.25261.pmancheno@gmail.com> <008c01c73914$9c2ea420$367ba8c0@jongwooh> Message-ID: <200701152127.11583.pmancheno@gmail.com> El Lunes, 15 de Enero de 2007 21:18, Jongwoo Han escribi?: > Linux support for IPv6-in-IPv6 is not quite complete, but I think you can > try 'ip6tunnel' command for it. > > -------- > jongwooh > > > -----Original Message----- > > From: Pepo [mailto:pmancheno at gmail.com] > > Sent: Tuesday, January 16, 2007 10:54 AM > > To: jongwooh at gmail.com; xorp-users at xorp.org > > Subject: Re: [Xorp-users] Virtual interfaces in IPv6 for routing. > > > > El Lunes, 15 de Enero de 2007 20:36, Jongwoo Han escribi?: > > > You should use GRE tunnel to encapsulate IPv6 in IPv6, not openvpn. > > > > > > > > > -------- > > > jongwooh > > > > Please, where do I can look up information about GRE to make > > ipv6-in-ipv6 ... > > I've used Google but I just found ipv6-in-ipv4 :( > > > > Can you help me please? > > > > > > -----Original Message----- > > > > From: xorp-users-bounces at xorp.org > > > > [mailto:xorp-users-bounces at xorp.org] On Behalf Of Pepo > > > > Sent: Tuesday, January 16, 2007 10:12 AM > > > > To: Vyatta-users at rio.vyatta.com; xorp-users at xorp.org > > > > Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. > > > > > > > > Hi friends. > > > > > > > > I have PCs with just one nic each one, and these PCs are > > > > working like routers > > > > for my test-LAN (for my thesis); when have to route to > > > > different sub-nets I > > > > use tunnels in IPv4 with OpenVpn to virtual-connect directly > > > > each router. > > > > > > > > Now, I have to do the same thing but in IPv6. how do I make > > > > tunnels from IPv6 > > > > to other IPv6 address? > > > > > > > > In IPv4 use this: > > > > (A) > > > > openvpn --remote 192.168.13.2 --dev tun0 --ifconfig > > > > 30.30.30.1 30.30.30.2 > > > > (B) > > > > openvpn --remote 192.168.13.1 --dev tun0 --ifconfig > > > > 30.30.30.2 30.30.30.1 ip6tunnel isn't in Debian Etch ... I was trying with ip tunnel add but just work with ipv4 addresses.. Any other idea? -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From pmancheno at gmail.com Mon Jan 15 19:01:08 2007 From: pmancheno at gmail.com (Pepo) Date: Mon, 15 Jan 2007 22:01:08 -0500 Subject: [Xorp-users] Virtual interfaces in IPv6 for routing. In-Reply-To: <008c01c73914$9c2ea420$367ba8c0@jongwooh> References: <200701152011.36086.pmancheno@gmail.com> <200701152054.25261.pmancheno@gmail.com> <008c01c73914$9c2ea420$367ba8c0@jongwooh> Message-ID: <200701152201.09286.pmancheno@gmail.com> I am using ip6_tunnel with modprobe ip6_tunnel and now I have: # ip addr show ip6tnl0: mtu 1460 qdisc noop link/tunnel6 00:00.... brd 00:00.... I think that i have to configure like a sit interface ... and hope that i can use that in XORP -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From pmancheno at gmail.com Tue Jan 16 22:52:25 2007 From: pmancheno at gmail.com (Pepo) Date: Wed, 17 Jan 2007 01:52:25 -0500 Subject: [Xorp-users] Why xorp dont multicast in IPv6 Message-ID: <200701170152.26908.pmancheno@gmail.com> Hi friends... I am trying to make multicast using IPv6 with XORP but when it runs give me an error message, you can look my test and my configuration at http://pepo.co.nr This is the error message: avernum:~# /opt/xorp/bin/xorp_rtrmgr -b /home/pepo/ruteador-A2.cis [ 2007/01/17 01:04:54 INFO xorp_rtrmgr:3873 RTRMGR +240 master_conf_tree.cc execute ] Changed modules: interfaces, fea, mfea6, mld, rib, pimsm6, policy, static_routes [ 2007/01/17 01:04:54 INFO xorp_rtrmgr:3873 RTRMGR +99 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] MFEA enabled [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] CLI enabled [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] CLI started [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] MFEA enabled [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] CLI enabled [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] CLI started [ 2007/01/17 01:04:57 INFO xorp_rtrmgr:3873 RTRMGR +99 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2007/01/17 01:05:03 INFO xorp_rtrmgr:3873 RTRMGR +99 module_manager.cc execute ] Executing module: mfea6 (fea/xorp_fea) [ 2007/01/17 01:05:03 ERROR xorp_fea:3874 MFEA +454 mfea_mrouter.cc adopt_mrouter_socket ] adopt_mrouter_socket() failed: IPv6 multicast routing not supported [ 2007/01/17 01:05:03 INFO xorp_fea MFEA ] Interface added: Vif[eth0] pif_index: 2 vif_index: 0 addr: fec0:2006:2007::1 subnet: fec0:2006:2007::/125 broadcast: :: peer: :: Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2007/01/17 01:05:03 INFO xorp_fea MFEA ] Interface added: Vif[tap0] pif_index: 6 vif_index: 1 addr: fec0:2006:2007:6:6:6:0:1 subnet: fec0:2006:2007:6:6:6::/126 broadcast: :: peer: :: Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 [ 2007/01/17 01:05:03 INFO xorp_fea MFEA ] MFEA started [ 2007/01/17 01:05:04 INFO xorp_fea MFEA ] Interface enabled Vif[eth0] pif_index: 2 vif_index: 0 addr: fec0:2006:2007::1 subnet: fec0:2006:2007::/125 broadcast: :: peer: :: Flags: MULTICAST BROADCAST UNDERLYING_VIF_UP MTU: 1500 DOWN IPv6 ENABLED [ 2007/01/17 01:05:04 ERROR xorp_fea:3874 MFEA +986 mfea_mrouter.cc add_multicast_vif ] add_multicast_vif() failed: IPv6 multicast routing not supported [ 2007/01/17 01:05:04 ERROR xorp_fea:3874 MFEA +910 mfea_node.cc start_vif ] Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2007/01/17 01:05:04 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 [ 2007/01/17 01:05:04 ERROR xorp_rtrmgr:3873 RTRMGR +671 master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2007/01/17 01:05:04 ERROR xorp_rtrmgr:3873 RTRMGR +252 master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Cannot start vif eth0: cannot add the multicast vif to the kernel [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +2228 task.cc run_task ] No more tasks to run [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +174 module_manager.cc terminate ] Terminating module: fea [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +174 module_manager.cc terminate ] Terminating module: interfaces [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +174 module_manager.cc terminate ] Terminating module: mfea6 [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +197 module_manager.cc terminate ] Killing module: mfea6 [ 2007/01/17 01:05:04 ERROR xorp_rtrmgr:3873 RTRMGR +750 module_manager.cc done_cb ] Command "/opt/xorp/fea/xorp_fea": terminated with signal 15. [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +285 module_manager.cc module_exited ] Module killed during shutdown: mfea6 I saw "IPv6 multicast routing not supported" maybe do I need change something in my GNU/Linux (Debian-Etch) to support IPv6 multicast? some modules or something like that? A lot of thanks. -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From pavlin at icir.org Wed Jan 17 10:25:07 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Wed, 17 Jan 2007 10:25:07 -0800 Subject: [Xorp-users] Why xorp dont multicast in IPv6 In-Reply-To: Message from Pepo of "Wed, 17 Jan 2007 01:52:25 EST." <200701170152.26908.pmancheno@gmail.com> Message-ID: <200701171825.l0HIP7kp026521@possum.icir.org> > I am trying to make multicast using IPv6 with XORP but when it runs give me an > error message, you can look my test and my configuration at http://pepo.co.nr The Linux kernel doesn't support IPv6 multicast forwarding out of the box, so you need to patch it (or use USAGI's snapshot which already includes the patch). See the following email for details: http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2005-November/000901.html Note that so far there is no confirmation whether the patched Linux kernel really works with XORP. If you decide to give it a try please send your feedbacks to the list. Regards, Pavlin > This is the error message: > > avernum:~# /opt/xorp/bin/xorp_rtrmgr -b /home/pepo/ruteador-A2.cis > [ 2007/01/17 01:04:54 INFO xorp_rtrmgr:3873 RTRMGR +240 master_conf_tree.cc > execute ] Changed modules: interfaces, fea, mfea6, mld, rib, pimsm6, policy, > static_routes > [ 2007/01/17 01:04:54 INFO xorp_rtrmgr:3873 RTRMGR +99 module_manager.cc > execute ] Executing module: interfaces (fea/xorp_fea) > [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] MFEA enabled > [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] CLI enabled > [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] CLI started > [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] MFEA enabled > [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] CLI enabled > [ 2007/01/17 01:04:55 INFO xorp_fea MFEA ] CLI started > [ 2007/01/17 01:04:57 INFO xorp_rtrmgr:3873 RTRMGR +99 module_manager.cc > execute ] Executing module: fea (fea/xorp_fea) > [ 2007/01/17 01:05:03 INFO xorp_rtrmgr:3873 RTRMGR +99 module_manager.cc > execute ] Executing module: mfea6 (fea/xorp_fea) > [ 2007/01/17 01:05:03 ERROR xorp_fea:3874 MFEA +454 mfea_mrouter.cc > adopt_mrouter_socket ] adopt_mrouter_socket() failed: IPv6 multicast routing > not supported > [ 2007/01/17 01:05:03 INFO xorp_fea MFEA ] Interface added: Vif[eth0] > pif_index: 2 vif_index: 0 addr: fec0:2006:2007::1 subnet: > fec0:2006:2007::/125 broadcast: :: peer: :: Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP MTU: 1500 > [ 2007/01/17 01:05:03 INFO xorp_fea MFEA ] Interface added: Vif[tap0] > pif_index: 6 vif_index: 1 addr: fec0:2006:2007:6:6:6:0:1 subnet: > fec0:2006:2007:6:6:6::/126 broadcast: :: peer: :: Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP MTU: 1500 > [ 2007/01/17 01:05:03 INFO xorp_fea MFEA ] MFEA started > [ 2007/01/17 01:05:04 INFO xorp_fea MFEA ] Interface enabled Vif[eth0] > pif_index: 2 vif_index: 0 addr: fec0:2006:2007::1 subnet: > fec0:2006:2007::/125 broadcast: :: peer: :: Flags: MULTICAST BROADCAST > UNDERLYING_VIF_UP MTU: 1500 DOWN IPv6 ENABLED > [ 2007/01/17 01:05:04 ERROR xorp_fea:3874 MFEA +986 mfea_mrouter.cc > add_multicast_vif ] add_multicast_vif() failed: IPv6 multicast routing not > supported > [ 2007/01/17 01:05:04 ERROR xorp_fea:3874 MFEA +910 mfea_node.cc start_vif ] > Cannot start vif eth0: cannot add the multicast vif to the kernel > [ 2007/01/17 01:05:04 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 > [ 2007/01/17 01:05:04 ERROR xorp_rtrmgr:3873 RTRMGR +671 master_conf_tree.cc > commit_pass2_done ] Commit failed: 102 Command failed Cannot start vif eth0: > cannot add the multicast vif to the kernel > [ 2007/01/17 01:05:04 ERROR xorp_rtrmgr:3873 RTRMGR +252 master_conf_tree.cc > config_done ] Configuration failed: 102 Command failed Cannot start vif eth0: > cannot add the multicast vif to the kernel > [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +2228 task.cc run_task ] > No more tasks to run > [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +174 module_manager.cc > terminate ] Terminating module: fea > [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +174 module_manager.cc > terminate ] Terminating module: interfaces > [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +174 module_manager.cc > terminate ] Terminating module: mfea6 > [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +197 module_manager.cc > terminate ] Killing module: mfea6 > [ 2007/01/17 01:05:04 ERROR xorp_rtrmgr:3873 RTRMGR +750 module_manager.cc > done_cb ] Command "/opt/xorp/fea/xorp_fea": terminated with signal 15. > [ 2007/01/17 01:05:04 INFO xorp_rtrmgr:3873 RTRMGR +285 module_manager.cc > module_exited ] Module killed during shutdown: mfea6 > > > I saw "IPv6 multicast routing not supported" maybe do I need change something > in my GNU/Linux (Debian-Etch) to support IPv6 multicast? some modules or > something like that? > > A lot of thanks. > -- > > Linux User Registered #232544 > Jabber : pepo at jabberes.org > Ekiga : pepo at ekiga.net > ICQ : 337889406 > GnuPG-key : www.keyserver.net > ----------------------------------------------- > dum loquimur, fugerit invida > aetas: carpe diem, quam minimum credula postero. > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From pmancheno at gmail.com Fri Jan 19 15:43:19 2007 From: pmancheno at gmail.com (Pepo) Date: Fri, 19 Jan 2007 18:43:19 -0500 Subject: [Xorp-users] Using XORP with other tools Message-ID: <200701191843.20786.pmancheno@gmail.com> Hi friends. Because Linux by default can't manage multicast in IPv6 with Xorp; I will try with mrd6 (I hope later patch my kernel and use just XORP). I think that now but: Will be in problems if use XORP for static unicast routing and MRD6 for multicast routing? I wan to use XORP because I hope that can present this tool for my thesis as other option and not just CISCO hardware/software. Thanks. -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From pavlin at icir.org Fri Jan 19 17:18:55 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Fri, 19 Jan 2007 17:18:55 -0800 Subject: [Xorp-users] Using XORP with other tools In-Reply-To: Message from Pepo of "Fri, 19 Jan 2007 18:43:19 EST." <200701191843.20786.pmancheno@gmail.com> Message-ID: <200701200118.l0K1ItPO002595@possum.icir.org> > Because Linux by default can't manage multicast in IPv6 with Xorp; I will try > with mrd6 (I hope later patch my kernel and use just XORP). I think that now > but: Will be in problems if use XORP for static unicast routing and MRD6 for > multicast routing? I wan to use XORP because I hope that can present this > tool for my thesis as other option and not just CISCO hardware/software. I don't see a reason why it shouldn't work. Please let us know if it doesn't. Regards, Pavlin From neeraj.prasad at gmail.com Fri Jan 19 23:36:59 2007 From: neeraj.prasad at gmail.com (Neeraj Prasad) Date: Sat, 20 Jan 2007 13:06:59 +0530 Subject: [Xorp-users] Problems with XORP - seeing error 102 - 102 Command failed Cannot enable vif register_vif: no such vif[edit protocols pimsm4] Message-ID: <1d413a090701192336w43454060n5574781e4250e157@mail.gmail.com> Hello, First of all thank you to all XORP developer for doing such a great job. I am a new user of XORP and am using XOPR for some testing. I am using LIVE CD v1.3 and I am facing certain problems - 1) If I change connection during runtime, i.e. XORP is up and running some interface goes down showing message 'NO CARRIER'. I need to restart the system 2) I am not able to add register_vif interface. I have successfully added the other physical interface for PIMSM4. When I try to add register_vif, it gives an error saying vif register_vif does not exist. I did following things serially What all I did - - Connected Physical Interfaces - Restarted PC with XORP Live CD v1.3 - Selected the interfaces during startup - When system booted up, I configured the interface address and verified using ping --- being PASTE ---- dc0/dc0: Flags: mtu 1500 inet 149.11.1.1 subnet 149.11.1.0/24 broadcast 149.11.1.255 physical index 2 ether 00:80:ad:85:1c:b1 fxp0/fxp0: Flags: mtu 1500 inet 192.168.10.149 subnet 192.168.10.0/24 broadcast 192.168.10.255 physical index 4 ether 00:11:25:38:56:d4 lo0/lo0: Flags: mtu 16384 physical index 9 rl0/rl0: Flags: mtu 1500 inet 149.10.1.1 subnet 149.10.1.0/24 broadcast 149.10.1.255 physical index 1 ether 00:00:a1:32:3b:fc vr0/vr0: Flags: mtu 1500 inet 149.12.1.1 subnet 149.12.1.0/24 broadcast 149.12.1.255 physical index 3 ether 00:80:c8:03:87:36 ----end PASTE--------------- - Enabled PIM routing process (set protocols pimsm4) - Added interface name to the pimsm4 --------------begin PASTE---------------------- xorp at LiveCD> show pim interface Interface State Mode V PIMstate Priority DRaddr Neighbors dc0 UP Sparse 2 DR 1 149.11.1.1 0 fxp0 DISABLED Sparse 2 DR 1 192.168.10.149 0 lo0 DISABLED Sparse 2 NotDR 1 0.0.0.0 0 rl0 UP Sparse 2 DR 1 149.10.1.1 0 vr0 UP Sparse 2 DR 1 149.12.1.1 0 xorp at LiveCD> ------------------end PASTE------------------------ - Now when I add special register_vif I get an error ------------------------being PASTE--------------------------------------------- xorp at LiveCD> configure Entering configuration mode. There are no other users in configuration mode. [edit] xorp at LiveCD# edit protocols pimsm4 [edit protocols pimsm4] xorp at LiveCD# set interface regs Possible completions: Configure IPv4 PIM-SM on a network interface xorp at LiveCD# set interface register_vif vif register_vif [edit protocols pimsm4] xorp at LiveCD# commit Commit Failed 102 Command failed Cannot enable vif register_vif: no such vif[edit protocols pimsm4] xorp at LiveCD# ------------------------end PASTE--------------------------------------------- And since it is mandatory to have the special vif installed, PIM is not working. Can someone guide me how to do it -- Thanks and Regards, Neeraj Prasad -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070120/ab2787dd/attachment.html From pavlin at icir.org Sat Jan 20 09:38:14 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Sat, 20 Jan 2007 09:38:14 -0800 Subject: [Xorp-users] Problems with XORP - seeing error 102 - 102 Command failed Cannot enable vif register_vif: no such vif[edit protocols pimsm4] In-Reply-To: Message from "Neeraj Prasad" of "Sat, 20 Jan 2007 13:06:59 +0530." <1d413a090701192336w43454060n5574781e4250e157@mail.gmail.com> Message-ID: <200701201738.l0KHcEd9011489@possum.icir.org> > I am a new user of XORP and am using XOPR for some testing. I am using LIVE > CD v1.3 and I am facing certain problems - > > 1) If I change connection during runtime, i.e. XORP is up and running some > interface goes down showing message 'NO CARRIER'. I need to restart the > system Yes, this is a known problem. After the cable is reconnected to the interface you can do the following: disable then enable (inside xorpsh) the affected interface. You need to disable and enable it in mfea4, igmp and pimsm4. E.g.: set protocols pimsm4 interface rl0 vif rl0 disable true # commit set protocols igmp interface rl0 vif rl0 disable true # commit set multicast mfea4 interface rl0 vif rl0 disable true commit set protocols pimsm4 interface rl0 vif rl0 disable false # commit set protocols igmp interface rl0 vif rl0 disable false # commit set multicast mfea4 interface rl0 vif rl0 disable false commit If this doesn't work, then you might need to use the commented-out "commit" commands as well. > 2) I am not able to add register_vif interface. I have successfully added > the other physical interface for PIMSM4. When I try to add register_vif, it > gives an error saying vif register_vif does not exist. I did following > things serially You need to add the register_vif to mfea4 before adding it to pimsm4. E.g. set plumbing mfea4 interface register_vif vif register_vif # commit set protocols pimsm4 interface register_vif vif register_vif commit Hope that helps, Pavlin > > What all I did - > - Connected Physical Interfaces > - Restarted PC with XORP Live CD v1.3 > - Selected the interfaces during startup > - When system booted up, I configured the interface address and verified > using ping > --- being PASTE ---- > dc0/dc0: Flags: mtu 1500 > inet 149.11.1.1 subnet 149.11.1.0/24 broadcast 149.11.1.255 > physical index 2 > ether 00:80:ad:85:1c:b1 > fxp0/fxp0: Flags: mtu 1500 > inet 192.168.10.149 subnet 192.168.10.0/24 broadcast 192.168.10.255 > physical index 4 > ether 00:11:25:38:56:d4 > lo0/lo0: Flags: mtu 16384 > physical index 9 > rl0/rl0: Flags: mtu 1500 > inet 149.10.1.1 subnet 149.10.1.0/24 broadcast 149.10.1.255 > physical index 1 > ether 00:00:a1:32:3b:fc > vr0/vr0: Flags: mtu 1500 > inet 149.12.1.1 subnet 149.12.1.0/24 broadcast 149.12.1.255 > physical index 3 > ether 00:80:c8:03:87:36 > ----end PASTE--------------- > - Enabled PIM routing process (set protocols pimsm4) > - Added interface name to the pimsm4 > --------------begin PASTE---------------------- > xorp at LiveCD> show pim interface > Interface State Mode V PIMstate Priority DRaddr Neighbors > dc0 UP Sparse 2 DR 1 149.11.1.1 0 > fxp0 DISABLED Sparse 2 DR 1 192.168.10.149 0 > lo0 DISABLED Sparse 2 NotDR 1 0.0.0.0 0 > rl0 UP Sparse 2 DR 1 149.10.1.1 0 > vr0 UP Sparse 2 DR 1 149.12.1.1 0 > xorp at LiveCD> > ------------------end PASTE------------------------ > > - Now when I add special register_vif I get an error > > ------------------------being > PASTE--------------------------------------------- > xorp at LiveCD> configure > Entering configuration mode. > There are no other users in configuration mode. > [edit] > xorp at LiveCD# edit protocols pimsm4 > [edit protocols pimsm4] > xorp at LiveCD# set interface regs > Possible completions: > Configure IPv4 PIM-SM on a network interface > xorp at LiveCD# set interface register_vif vif register_vif > [edit protocols pimsm4] > xorp at LiveCD# commit > Commit Failed > 102 Command failed Cannot enable vif register_vif: no such vif[edit > protocols pimsm4] > xorp at LiveCD# > ------------------------end > PASTE--------------------------------------------- > > And since it is mandatory to have the special vif installed, PIM is not > working. Can someone guide me how to do it > > -- > Thanks and Regards, > Neeraj Prasad > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From hugovn77 at gmail.com Sun Jan 21 03:32:48 2007 From: hugovn77 at gmail.com (Hugo van Niekerk) Date: Sun, 21 Jan 2007 13:32:48 +0200 Subject: [Xorp-users] Compiling Xorp on Slackware Message-ID: <66c5017e0701210332i6b8e54fdv5c4c9bbe17d4b47c@mail.gmail.com> Hi All Thank you for a great application. I've been playing with it and every time I run across something new and get impressed all over again. Like Ross from earlier, I am also ambitious and took on the challenge to try and make Xorp run on slackware. I run into a few problems, for which I need to be pointed in the right direction. Firstly, during the ./configure process it reports not to find any of the following files. I know that some of these are specific to certain distros,is this xorps way of determining what distro it is being compiled on or are there dependencies that I need to search for? nd.h if_dl.h if_media.h if_types.h if_var.h sockio.h linker.h mroute6.h ethernet.h if_ether.h vfork.h ip.h ip_mroute.h in6_var.h nd6.h ip6_mroute.h pim.h I realise that these might be header files but have been unsuccessful in determining where they fit in. regards Hugo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070121/14a50c69/attachment.html From neeraj.prasad at gmail.com Sun Jan 21 08:17:43 2007 From: neeraj.prasad at gmail.com (Neeraj Prasad) Date: Sun, 21 Jan 2007 21:47:43 +0530 Subject: [Xorp-users] IP Alert Option Check in PIM Message-ID: <1d413a090701210817v6771cc6h3d67f8416c6582ae@mail.gmail.com> Hello, I have a question, why does XORP have IP-ROUTER-ALERT-OPTION check in PIM. The PIM standard does not specify about the IP Router Alert Option. -- Thanks and Regards, Neeraj Prasad -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20070121/3e9b4961/attachment.html From pavlin at icir.org Mon Jan 22 12:31:26 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 22 Jan 2007 12:31:26 -0800 Subject: [Xorp-users] Compiling Xorp on Slackware In-Reply-To: Message from "Hugo van Niekerk" of "Sun, 21 Jan 2007 13:32:48 +0200." <66c5017e0701210332i6b8e54fdv5c4c9bbe17d4b47c@mail.gmail.com> Message-ID: <200701222031.l0MKVQ2d033368@possum.icir.org> > Thank you for a great application. I've been playing with it and every time > I run across something new and get impressed all over again. Like Ross from > earlier, I am also ambitious and took on the challenge to try and make Xorp > run on slackware. I run into a few problems, for which I need to be pointed > in the right direction. Firstly, during the ./configure process it reports > not to find any of the following files. I know that some of these are > specific to certain distros,is this xorps way of determining what distro it > is being compiled on or are there dependencies that I need to search for? > > nd.h > if_dl.h > if_media.h > if_types.h > if_var.h > sockio.h > linker.h > mroute6.h > ethernet.h > if_ether.h > vfork.h > ip.h > ip_mroute.h > in6_var.h > nd6.h > ip6_mroute.h > pim.h It is normal that ./configure doesn't find some header files, so it doesn't mean there is an error. The purpose of ./configure is to find various info about the OS and then conditionally define the corresponding tags (later used by the source code), so all the messages/warnings printed by ./configure indicate what was/wasn't found about the system. If there was any compilation error (after you execute "gmake"), please include that error. Regards, Pavlin > > > I realise that these might be header files but have been unsuccessful in > determining where they fit in. > > regards > > Hugo > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From a.greenhalgh at cs.ucl.ac.uk Mon Jan 22 12:43:32 2007 From: a.greenhalgh at cs.ucl.ac.uk (Adam Greenhalgh) Date: Mon, 22 Jan 2007 20:43:32 +0000 Subject: [Xorp-users] Compiling Xorp on Slackware In-Reply-To: <200701222031.l0MKVQ2d033368@possum.icir.org> References: <66c5017e0701210332i6b8e54fdv5c4c9bbe17d4b47c@mail.gmail.com> <200701222031.l0MKVQ2d033368@possum.icir.org> Message-ID: <4769af410701221243y27cf8175vd1b865e730c32ac8@mail.gmail.com> This looks like the kernel headers haven't been installed by slackware, you may need to add another package. Adam On 1/22/07, Pavlin Radoslavov wrote: > > Thank you for a great application. I've been playing with it and every time > > I run across something new and get impressed all over again. Like Ross from > > earlier, I am also ambitious and took on the challenge to try and make Xorp > > run on slackware. I run into a few problems, for which I need to be pointed > > in the right direction. Firstly, during the ./configure process it reports > > not to find any of the following files. I know that some of these are > > specific to certain distros,is this xorps way of determining what distro it > > is being compiled on or are there dependencies that I need to search for? > > > > nd.h > > if_dl.h > > if_media.h > > if_types.h > > if_var.h > > sockio.h > > linker.h > > mroute6.h > > ethernet.h > > if_ether.h > > vfork.h > > ip.h > > ip_mroute.h > > in6_var.h > > nd6.h > > ip6_mroute.h > > pim.h > > It is normal that ./configure doesn't find some header files, so it > doesn't mean there is an error. > > The purpose of ./configure is to find various info about the OS and > then conditionally define the corresponding tags (later used by the > source code), so all the messages/warnings printed by ./configure > indicate what was/wasn't found about the system. > > If there was any compilation error (after you execute "gmake"), > please include that error. > > Regards, > Pavlin > > > > > > > I realise that these might be header files but have been unsuccessful in > > determining where they fit in. > > > > regards > > > > Hugo > > _______________________________________________ > > 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 pavlin at icir.org Mon Jan 22 13:03:36 2007 From: pavlin at icir.org (Pavlin Radoslavov) Date: Mon, 22 Jan 2007 13:03:36 -0800 Subject: [Xorp-users] IP Alert Option Check in PIM In-Reply-To: Message from "Neeraj Prasad" of "Sun, 21 Jan 2007 21:47:43 +0530." <1d413a090701210817v6771cc6h3d67f8416c6582ae@mail.gmail.com> Message-ID: <200701222103.l0ML3bjp033755@possum.icir.org> > I have a question, why does XORP have IP-ROUTER-ALERT-OPTION check in PIM. > The PIM standard does not specify about the IP Router Alert Option. Yes, you are correct that the PIM spec doesn't specify it. The IP-ROUTER-ALERT-OPTION check was in earlier versions of the spec, but later it was removed. Given that the check is not needed anymore, in the future it will be removed from the XORP implementation as well. FYI, the IP-ROUTER-ALERT-OPTION check is disabled by default, so this shouldn't be an issue. Anyway, I just created a Bugzilla entry about completely removing the check it won't be forgotten: http://www.xorp.org/bugzilla/show_bug.cgi?id=691 Regards, Pavlin From ashishkarpe at gmail.com Wed Jan 24 14:35:30 2007 From: ashishkarpe at gmail.com (Ashish Karpe) Date: Wed, 24 Jan 2007 15:35:30 -0700 Subject: [Xorp-users] want help for PIM-SM Message-ID: hi all, i want to test PIM-SM in xorp. So can anyone please tell me what should be topology required for that purpose & it will be very helpfull if someone gives config file for that perticular topology. Currently i have this topology on Vmware !! A (Host)-------------------> B (Xorp router)---------------------> C (host) Thanks you, Ashish From pmancheno at gmail.com Wed Jan 24 23:14:50 2007 From: pmancheno at gmail.com (Pepo) Date: Thu, 25 Jan 2007 02:14:50 -0500 Subject: [Xorp-users] Vyatta vs CISCO Message-ID: <200701250214.51906.pmancheno@gmail.com> Hi friends... I have to choose equipment (hardware and software) to implement multicast in my university LAN, and I wanna choose Vyatta/Xorp, but I have to specify the features and cost of the equipment versus other solution like CISCO but in this I dont have any idea of the equipment that will be necesary. Please give me a hand because it is so important to finish my project and buy the hardware/software. A lot of thanks. -- Linux User Registered #232544 Jabber : pepo at jabberes.org Ekiga : pepo at ekiga.net ICQ : 337889406 GnuPG-key : www.keyserver.net ----------------------------------------------- dum loquimur, fugerit invida aetas: carpe diem, quam minimum credula postero. From neeraj.prasad at gmail.com Fri Jan 26 23:43:57 2007 From: neeraj.prasad at gmail.com (Neeraj Prasad) Date: Sat, 27 Jan 2007 13:13:57 +0530 Subject: [Xorp-users] Xorp-users Digest, Vol 10, Issue 17 In-Reply-To: References: Message-ID: <1d413a090701262343t15131890i34ee76b29a140b4f@mail.gmail.com> hi all, i want to test PIM-SM in xorp. So can anyone please tell me what should be topology required for that purpose & it will be very helpfull if someone gives config file for that perticular topology. Currently i have this topology on Vmware !! A (Host)-------------------> B (Xorp router)---------------------> C (host) Thanks you, Ashish Ashish you must specify the exact thing you want to test. Depending on that you may hav e different topology. For exapmle if you just want to check the Hello Exchange then only one test interface will do it. Test Interface---------------------------Xorp Interface. So, if you can specify an exact test case, we can provide you with better answers. For the config file of XORP I can give u an example having three interfaces Topology ------------- S1-------T1------------D1,D2-----------------T2 D3 | | T3 xorp at LiveCD# show -all protocols { fib2mrib { disable: false } igmp { disable: false interface rl0 { vif rl0 { disable: false version: 3 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } interface dc0 { vif dc0 { disable: false version: 3 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } interface vr0 { vif vr0 { disable: false version: 3 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } } pimsm4 { disable: false interface rl0 { vif rl0 { disable: false enable-ip-router-alert-option-check: false dr-priority: 2 hello-period: 30 hello-triggered-delay: 5 } } interface dc0 { vif dc0 { disable: false enable-ip-router-alert-option-check: false dr-priority: 2 hello-period: 30 hello-triggered-delay: 5 } } interface vr0 { vif vr0 { disable: false enable-ip-router-alert-option-check: false dr-priority: 2 hello-period: 30 hello-triggered-delay: 5 } } interface "register_vif" { vif "register_vif" { disable: false enable-ip-router-alert-option-check: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } } static { disable: false route 22.2.2.2/32 { next-hop: 149.10.1.2 metric: 1 } mrib-route 11.1.1.1/32 { next-hop: 149.10.1.2 metric: 10 } } } interfaces { restore-original-config-on-shutdown: false interface rl0 { disable: false discard: false description: "Ethernet" vif rl0 { disable: false address 149.10.1.1 { prefix-length: 24 disable: false } address 149:10::1:1 { prefix-length: 64 disable: false } } } interface dc0 { disable: false discard: false description: "Ethernet" vif dc0 { disable: false address 149.11.1.1 { prefix-length: 24 disable: false } address 149:11::1:1 { prefix-length: 64 disable: false } } } interface vr0 { disable: false discard: false description: "Ethernet" vif vr0 { disable: false address 149.12.1.1 { prefix-length: 24 disable: false } address 149:12::1:1 { prefix-length: 64 disa