From wubaochuan at seu.edu.cn Sat Jan 8 21:07:19 2011 From: wubaochuan at seu.edu.cn (wubaochuan) Date: Sun, 09 Jan 2011 13:07:19 +0800 Subject: [Xorp-users] Help, how to modify OSPF routing table Message-ID: <494549670.09127@seu.edu.cn> Dear everyone, After OSPF is working, there is OSPF routing table on every router, I want to delete some routes generated by OSPF and add some routes to OSPF routing table, how can I modify OSPF routing table? Thank you. Yours Chuan From alexey.misyurenko at gmail.com Fri Jan 28 10:49:02 2011 From: alexey.misyurenko at gmail.com (=?UTF-8?B?0JDQu9C10LrRgdC10Lkg0JzQuNGB0Y7RgNC10L3QutC+?=) Date: Fri, 28 Jan 2011 21:49:02 +0300 Subject: [Xorp-users] xorp and gre tunnel Message-ID: Hello! I try to use ospfv2 on my PC with OpenSUSE 11.3. Below my last try of xorp.conf before I write to mail-list. I try create tunnel gre1 in several way. ping work, but by tcpdump I can't see any packets related to ospf on GRE1 tunnel. protocols { ospf4 { router-id: 192.168.255.129 area 0.0.0.0 { area-range 192.168.130.0/30 { } area-range 192.168.255.129/32 { } interface gre1 { vif gre1 { address 192.168.130.2 { interface-cost: 10 } } } interface lo { vif lo { address 192.168.255.129 { passive { } } } } } } } fea { unicast-forwarding4 { } unicast-forwarding6 { disable: true } } interfaces { interface lo { vif lo { address 127.0.0.1 { prefix-length: 8 loopback: true } address 127.0.0.2 { prefix-length: 8 loopback: true } address 192.168.255.129 { prefix-length: 32 loopback: true } } } interface gre1 { description: "Link_To_DAL" vif gre1 { address 192.168.130.2 { prefix-length: 30 } } } } -- ? ?????????, ??????? ?????????. From jmitchell at ll.mit.edu Fri Jan 28 15:08:49 2011 From: jmitchell at ll.mit.edu (Jeff Mitchell) Date: Fri, 28 Jan 2011 18:08:49 -0500 Subject: [Xorp-users] Cannot find capability config for user root Message-ID: <4D434C81.9090505@ll.mit.edu> Hello, I just set up xorp on some new machines and it seems to work very well when I start it up with a configuration file at /etc/xorp/xorp.conf. However, when I try to do "configure" from xorpsh, I get: ERROR: You do not have permission for this operation, token: 0xorpsh-19303-nrm-rtr1****************62eef9d0db86a27dc1a2fd93d6 29752 reason: Cannot find capability: config in user: root (0). Does anyone know how to fix/get around this? Thanks, Jeff From jmitchell at ll.mit.edu Fri Jan 28 15:10:47 2011 From: jmitchell at ll.mit.edu (Jeff Mitchell) Date: Fri, 28 Jan 2011 18:10:47 -0500 Subject: [Xorp-users] Cannot find capability config for user root In-Reply-To: <4D434C81.9090505@ll.mit.edu> References: <4D434C81.9090505@ll.mit.edu> Message-ID: <4D434CF7.8050704@ll.mit.edu> On 01/28/2011 06:08 PM, Jeff Mitchell wrote: > Hello, > > I just set up xorp on some new machines and it seems to work very well > when I start it up with a configuration file at /etc/xorp/xorp.conf. > However, when I try to do "configure" from xorpsh, I get: > > ERROR: You do not have permission for this operation, token: > 0xorpsh-19303-nrm-rtr1****************62eef9d0db86a27dc1a2fd93d6 29752 > reason: Cannot find capability: config in user: root (0). > > Does anyone know how to fix/get around this? Sorry, I should mention: this is xorp.ct, revision 92e39c0e3b0244ce894cdbf85880ccdc2d5c7dd5 Thanks, Jeff From greearb at candelatech.com Fri Jan 28 15:13:43 2011 From: greearb at candelatech.com (Ben Greear) Date: Fri, 28 Jan 2011 15:13:43 -0800 Subject: [Xorp-users] Cannot find capability config for user root In-Reply-To: <4D434C81.9090505@ll.mit.edu> References: <4D434C81.9090505@ll.mit.edu> Message-ID: <4D434DA7.7090104@candelatech.com> On 01/28/2011 03:08 PM, Jeff Mitchell wrote: > Hello, > > I just set up xorp on some new machines and it seems to work very well > when I start it up with a configuration file at /etc/xorp/xorp.conf. > However, when I try to do "configure" from xorpsh, I get: > > ERROR: You do not have permission for this operation, token: > 0xorpsh-19303-nrm-rtr1****************62eef9d0db86a27dc1a2fd93d6 29752 > reason: Cannot find capability: config in user: root (0). > > Does anyone know how to fix/get around this? Probably you need to set up your xorp user & group. Please take a look at the xorp_install.bash script in the xorp/ dir in the git repository... Thanks, Ben > > Thanks, > Jeff > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Ben Greear Candela Technologies Inc http://www.candelatech.com From jmitchell at ll.mit.edu Fri Jan 28 15:28:39 2011 From: jmitchell at ll.mit.edu (Jeff Mitchell) Date: Fri, 28 Jan 2011 18:28:39 -0500 Subject: [Xorp-users] Cannot find capability config for user root In-Reply-To: <4D434DA7.7090104@candelatech.com> References: <4D434C81.9090505@ll.mit.edu> <4D434DA7.7090104@candelatech.com> Message-ID: <4D435127.3060105@ll.mit.edu> On 01/28/2011 06:13 PM, Ben Greear wrote: > On 01/28/2011 03:08 PM, Jeff Mitchell wrote: >> Hello, >> >> I just set up xorp on some new machines and it seems to work very well >> when I start it up with a configuration file at /etc/xorp/xorp.conf. >> However, when I try to do "configure" from xorpsh, I get: >> >> ERROR: You do not have permission for this operation, token: >> 0xorpsh-19303-nrm-rtr1****************62eef9d0db86a27dc1a2fd93d6 29752 >> reason: Cannot find capability: config in user: root (0). >> >> Does anyone know how to fix/get around this? > > Probably you need to set up your xorp user& group. > > Please take a look at the xorp_install.bash script in the > xorp/ dir in the git repository... Whoulda thunk. Thanks much, Jeff From alexey.misyurenko at gmail.com Sun Jan 30 12:17:50 2011 From: alexey.misyurenko at gmail.com (=?UTF-8?B?0JDQu9C10LrRgdC10Lkg0JzQuNGB0Y7RgNC10L3QutC+?=) Date: Sun, 30 Jan 2011 23:17:50 +0300 Subject: [Xorp-users] xorp-1.8-CTb under OpenSUSE 11.3 - register_vif is DOWN. Message-ID: Can some body help with PIM-SM ? Bellow configuration's files and show commands report root at dal01-mpdedicated# run show pim interface Interface State Mode V PIMstate Priority DRaddr Neighbors eth0 DISABLED Sparse 2 DR 1 10.14.117.74 0 eth1 DISABLED Sparse 2 DR 1 67.228.150.178 0 gre0 DISABLED Sparse 2 NotDR 1 0.0.0.0 0 lo DISABLED Sparse 2 DR 1 127.0.0.1 0 register_vif DOWN Sparse 2 DR 1 0.0.0.0 0 tun0 UP Sparse 2 DR 1 67.228.150.178 0 tun10 UP Sparse 2 DR 1 67.228.150.178 0 tun20 UP Sparse 2 DR 1 67.228.150.178 0 tun30 UP Sparse 2 DR 1 67.228.150.178 0 root at dal01-mpdedicated# run show host os Linux dal01-mpdedicated 2.6.34.7-0.5-desktop #1 SMP PREEMPT 2010-10-25 08:40:12 +0200 x86_64 x86_64 x86_64 GNU/Linux /* XORP configuration file * * Configuration format: 1.1 * XORP version: 1.8-CT * Date: 2011/01/30 22:00:35.358063 * Host: streamer03 * User: root */ protocols { fib2mrib { disable: false } igmp { disable: false interface eth0 { vif eth0 { disable: true version: 2 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } interface eth1 { vif eth1 { disable: true version: 2 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } interface tun0 { vif tun0 { 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 } } interface tun10 { vif tun10 { 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 } } interface tun20 { vif tun20 { 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 } } interface tun30 { vif tun30 { 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 } } } pimsm4 { disable: false interface eth0 { vif eth0 { disable: true dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface eth1 { vif eth1 { disable: true dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface tun0 { vif tun0 { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface tun10 { vif tun10 { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface tun20 { vif tun20 { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface tun30 { vif tun30 { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface "register_vif" { vif "register_vif" { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } bootstrap { disable: false cand-bsr { scope-zone 224.0.0.0/4 { is-scope-zone: false cand-bsr-by-vif-name: "tun10" cand-bsr-by-vif-addr: 0.0.0.0 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: "tun10" cand-rp-by-vif-addr: 0.0.0.0 rp-priority: 192 rp-holdtime: 150 } } } switch-to-spt-threshold { disable: false interval: 100 bytes: 102400 } } static { disable: false } } fea { unicast-forwarding4 { disable: false } unicast-forwarding6 { disable: true } } interfaces { restore-original-config-on-shutdown: false interface eth0 { description: "Outside interface" disable: false discard: false unreachable: false management: false default-system-config } interface eth1 { description: "Inside interface" disable: false discard: false unreachable: false management: false default-system-config } interface gre0 { description: "system interface gre0" disable: false discard: false unreachable: false management: false default-system-config } interface lo { description: "system loopback" disable: false discard: false unreachable: false management: false default-system-config } interface tun0 { description: "Tunnel to WDC" disable: false discard: false unreachable: false management: false default-system-config } interface tun10 { description: "Tunnel to DAL" disable: false discard: false unreachable: false management: false default-system-config } interface tun20 { description: "Tunnel to AMS" disable: false discard: false unreachable: false management: false default-system-config } interface tun30 { description: "Tunnel to LA" disable: false discard: false unreachable: false management: false default-system-config } interface "register_vif" { description: "" disable: false discard: false unreachable: false management: false vif "register_vif" { disable: false } } } plumbing { mfea4 { disable: false interface tun0 { vif tun0 { disable: false } } interface tun10 { vif tun10 { disable: false } } interface tun20 { vif tun20 { disable: false } } interface tun30 { vif tun30 { disable: false } } interface "register_vif" { vif "register_vif" { disable: false } } } } p.s. also exist troubles with ospf.. but this is subject to another message -- ? ?????????, ??????? ?????????.