From esj at cs.fiu.edu Thu Jul 1 07:51:33 2010 From: esj at cs.fiu.edu (Eric S. Johnson) Date: Thu, 01 Jul 2010 10:51:33 -0400 Subject: [Xorp-users] MFEA crashing on system with subinterfaces In-Reply-To: References: , <4C2BB211.80508@candelatech.com> Message-ID: <20100701145133.AB8DFB8841E@cheetah.cs.fiu.edu> Mark, Ive been using xorp on linux with vlans/multicast for a while. (Im not running the "current" .ct branch, but one that is close) I have found that to make it work you need to treat the vlan interfaces as separate interfaces not separate vif's of a single interface. I actually bring up the interfaces outside of xorp, but use xorp vif's that correspond. E My interfaces look like: eth0.14 Link encap:Ethernet HWaddr 00:06:5B:88:84:C6 inet addr:131.94.132.91 Bcast:131.94.132.255 Mask:255.255.255.0 inet6 addr: 2001:468:701:3803:206:5bff:fe88:84c6/64 Scope:Global inet6 addr: fe80::206:5bff:fe88:84c6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:74556615 errors:0 dropped:0 overruns:0 frame:0 TX packets:119107697 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2828663148 (2.6 GiB) TX bytes:3576639776 (3.3 GiB) eth0.15 Link encap:Ethernet HWaddr 00:06:5B:88:84:C6 inet addr:131.94.131.2 Bcast:131.94.131.31 Mask:255.255.255.224 inet6 addr: fe80::206:5bff:fe88:84c6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8522903 errors:0 dropped:0 overruns:0 frame:0 TX packets:125184 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:445383310 (424.7 MiB) TX bytes:5258196 (5.0 MiB) eth0.16 Link encap:Ethernet HWaddr 00:06:5B:88:84:C6 inet addr:131.94.134.131 Bcast:131.94.134.191 Mask:255.255.255.192 inet6 addr: fe80::206:5bff:fe88:84c6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:308961401 errors:0 dropped:0 overruns:0 frame:0 TX packets:8353961 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1102564519 (1.0 GiB) TX bytes:1326031999 (1.2 GiB) and my xorp configs look like: interfaces { interface "eth0.14" { description: "" disable: false discard: false unreachable: false management: false vif "eth0.14" { disable: false address 131.94.132.91 { prefix-length: 24 disable: false } } } interface "eth0.15" { description: "" disable: false discard: false unreachable: false management: false vif "eth0.15" { disable: false address 131.94.131.2 { prefix-length: 27 disable: false } } } interface "eth0.16" { description: "" disable: false discard: false unreachable: false management: false vif "eth0.16" { disable: false address 131.94.134.131 { prefix-length: 26 disable: false } } } } protocols { fib2mrib { disable: false } igmp { interface "eth0.14" { vif "eth0.14" { 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 "eth0.15" { vif "eth0.15" { 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 "eth0.16" { vif "eth0.16" { 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 { interface "eth0.14" { vif "eth0.14" { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface "eth0.15" { vif "eth0.15" { disable: true dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface "eth0.16" { vif "eth0.16" { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } } } plumbing { mfea4 { disable: false interface "eth0.14" { vif "eth0.14" { disable: false } } interface "eth0.15" { vif "eth0.15" { disable: false } } interface "eth0.16" { vif "eth0.16" { disable: false } } } } From peirce at maine.edu Thu Jul 1 08:30:31 2010 From: peirce at maine.edu (Garry Peirce) Date: Thu, 1 Jul 2010 11:30:31 -0400 Subject: [Xorp-users] MFEA crashing on system with subinterfaces In-Reply-To: References: , <4C2BB211.80508@candelatech.com>, Message-ID: <08b801cb1932$574e0060$05ea0120$@edu> A timely thread as I work on the same issue and running into the same. I got it running under 1.6 - took more effort than desirable to find the right method. I'd be very curious to know how it goes with xorp.ct. I had to define the interfaces within XORP, and not use default-system-config directive. It seemed the order of the config made a significant difference with respect to the mfea4 failing or not, and I sometimes had to back out/restart and then enter things in the right order. 1) configure interfaces Vlans are not defined as vifs under the major interface but a defined interface itself. do not use the default-system-config directive add the address on the vlan interface (addr is used by register_vif I believe) 1a) I then commit and restart xorp 2) enable fib2mrib 3) enable mfea4 4) enable pimsm4 * Addresses anonymized xorp at host> show pim neighbors Interface DRpriority NeighborAddr V Mode Holdtime Timeout eth0.605 1 10.1.1.81 2 Sparse 105 101 config =========== xorp at host# show -all protocols { fib2mrib { disable: false } pimsm4 { disable: false interface "register_vif" { vif "register_vif" { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface "eth0.605" { vif "eth0.605" { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } } static { disable: false } } fea { unicast-forwarding4 { disable: false forwarding-entries { retain-on-startup: true retain-on-shutdown: true } } } interfaces { restore-original-config-on-shutdown: true interface eth0 { description: "" disable: false discard: false unreachable: false management: false vif eth0 { disable: false address 10.3.3.10 { prefix-length: 23 disable: false } } } interface eth1 { description: "LAN" disable: false discard: false unreachable: false management: false } interface eth2 { description: "Available" disable: false discard: false unreachable: false management: false } interface eth3 { description: "Available" disable: false discard: false unreachable: false management: false } interface "eth0.605" { description: "" disable: false discard: false unreachable: false management: false vif "eth0.605" { disable: false address 10.1.1.82 { prefix-length: 30 disable: false } } } } plumbing { mfea4 { disable: false interface eth0 { vif eth0 { disable: false } } interface "register_vif" { vif "register_vif" { disable: false } } interface "eth0.605" { vif "eth0.605" { disable: false } } } } > -----Original Message----- > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] > On Behalf Of Williams, Mark > Sent: Wednesday, June 30, 2010 6:59 PM > To: xorp-users at xorp.org > Subject: Re: [Xorp-users] MFEA crashing on system with subinterfaces > > I was able to get some interfaces working by removing the default- > system-config primitive and specifying all the necessary information. > However, I cannot get the 802.1q tagged interfaces to work. It allows > me to create a vif with a vlan-id specified, but when I try to create > the mfea4 interface, I get an error saying that the underlying vif is > not up. > > -Mark Williams > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From william at losrios.edu Thu Jul 1 11:34:42 2010 From: william at losrios.edu (Williams, Mark) Date: Thu, 1 Jul 2010 18:34:42 +0000 Subject: [Xorp-users] MFEA crashing on system with subinterfaces In-Reply-To: <20100701145133.AB8DFB8841E@cheetah.cs.fiu.edu> References: , <4C2BB211.80508@candelatech.com> <20100701145133.AB8DFB8841E@cheetah.cs.fiu.edu> Message-ID: It looks like all I needed to do was place quotes around my interface names. Once I did that things started working. Must not have liked the . in the interface name? Thanks, -Mark Williams -----Original Message----- From: Eric S. Johnson [mailto:esj at cs.fiu.edu] Sent: Thursday, July 01, 2010 07:52 To: Williams, Mark Cc: Ben Greear; xorp-users at xorp.org Subject: Re: [Xorp-users] MFEA crashing on system with subinterfaces Mark, Ive been using xorp on linux with vlans/multicast for a while. (Im not running the "current" .ct branch, but one that is close) I have found that to make it work you need to treat the vlan interfaces as separate interfaces not separate vif's of a single interface. I actually bring up the interfaces outside of xorp, but use xorp vif's that correspond. E My interfaces look like: eth0.14 Link encap:Ethernet HWaddr 00:06:5B:88:84:C6 inet addr:131.94.132.91 Bcast:131.94.132.255 Mask:255.255.255.0 inet6 addr: 2001:468:701:3803:206:5bff:fe88:84c6/64 Scope:Global inet6 addr: fe80::206:5bff:fe88:84c6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:74556615 errors:0 dropped:0 overruns:0 frame:0 TX packets:119107697 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2828663148 (2.6 GiB) TX bytes:3576639776 (3.3 GiB) eth0.15 Link encap:Ethernet HWaddr 00:06:5B:88:84:C6 inet addr:131.94.131.2 Bcast:131.94.131.31 Mask:255.255.255.224 inet6 addr: fe80::206:5bff:fe88:84c6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8522903 errors:0 dropped:0 overruns:0 frame:0 TX packets:125184 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:445383310 (424.7 MiB) TX bytes:5258196 (5.0 MiB) eth0.16 Link encap:Ethernet HWaddr 00:06:5B:88:84:C6 inet addr:131.94.134.131 Bcast:131.94.134.191 Mask:255.255.255.192 inet6 addr: fe80::206:5bff:fe88:84c6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:308961401 errors:0 dropped:0 overruns:0 frame:0 TX packets:8353961 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1102564519 (1.0 GiB) TX bytes:1326031999 (1.2 GiB) and my xorp configs look like: interfaces { interface "eth0.14" { description: "" disable: false discard: false unreachable: false management: false vif "eth0.14" { disable: false address 131.94.132.91 { prefix-length: 24 disable: false } } } interface "eth0.15" { description: "" disable: false discard: false unreachable: false management: false vif "eth0.15" { disable: false address 131.94.131.2 { prefix-length: 27 disable: false } } } interface "eth0.16" { description: "" disable: false discard: false unreachable: false management: false vif "eth0.16" { disable: false address 131.94.134.131 { prefix-length: 26 disable: false } } } } protocols { fib2mrib { disable: false } igmp { interface "eth0.14" { vif "eth0.14" { 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 "eth0.15" { vif "eth0.15" { 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 "eth0.16" { vif "eth0.16" { 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 { interface "eth0.14" { vif "eth0.14" { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface "eth0.15" { vif "eth0.15" { disable: true dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface "eth0.16" { vif "eth0.16" { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } } } plumbing { mfea4 { disable: false interface "eth0.14" { vif "eth0.14" { disable: false } } interface "eth0.15" { vif "eth0.15" { disable: false } } interface "eth0.16" { vif "eth0.16" { disable: false } } } } From greearb at candelatech.com Thu Jul 1 11:46:22 2010 From: greearb at candelatech.com (Ben Greear) Date: Thu, 01 Jul 2010 11:46:22 -0700 Subject: [Xorp-users] MFEA crashing on system with subinterfaces In-Reply-To: References: , <4C2BB211.80508@candelatech.com> <20100701145133.AB8DFB8841E@cheetah.cs.fiu.edu> Message-ID: <4C2CE27E.8070404@candelatech.com> On 07/01/2010 11:34 AM, Williams, Mark wrote: > It looks like all I needed to do was place quotes around my interface names. Once I did that things started working. Must not have liked the . in the interface name? Yeah, it can be tricky about quotes. If you have a static config, you are probably good to go on 1.6. But, if you are going to be adding/removing VLANs (or any other network device) while xorp is running, you are probably going to have troubles on xorp 1.6. There are all sorts of races between fea & protocols detecting that the system has lost/added a device and xorpsh configuration in that older code that would lead to asserts. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From peirce at maine.edu Thu Jul 1 12:42:46 2010 From: peirce at maine.edu (Garry Peirce) Date: Thu, 1 Jul 2010 15:42:46 -0400 Subject: [Xorp-users] MFEA crashing on system with subinterfaces In-Reply-To: <20100701145133.AB8DFB8841E@cheetah.cs.fiu.edu> References: , <4C2BB211.80508@candelatech.com> <20100701145133.AB8DFB8841E@cheetah.cs.fiu.edu> Message-ID: <090201cb1955$94662db0$bd328910$@edu> Eric, Just a followup - is your config working without register_vif interfaces? > -----Original Message----- > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] > On Behalf Of Eric S. Johnson > Sent: Thursday, July 01, 2010 10:52 AM > To: Williams, Mark > Cc: xorp-users at xorp.org > Subject: Re: [Xorp-users] MFEA crashing on system with subinterfaces > > > Mark, > > Ive been using xorp on linux with vlans/multicast for a while. > (Im not running the "current" .ct branch, but one that > is close) > > I have found that to make it work you need to treat the > vlan interfaces as separate interfaces not separate vif's > of a single interface. I actually bring up the interfaces > outside of xorp, but use xorp vif's that correspond. > > > E > > > > > My interfaces look like: > > > eth0.14 Link encap:Ethernet HWaddr 00:06:5B:88:84:C6 > inet addr:131.94.132.91 Bcast:131.94.132.255 > Mask:255.255.255.0 > inet6 addr: 2001:468:701:3803:206:5bff:fe88:84c6/64 > Scope:Global > inet6 addr: fe80::206:5bff:fe88:84c6/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:74556615 errors:0 dropped:0 overruns:0 frame:0 > TX packets:119107697 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:2828663148 (2.6 GiB) TX bytes:3576639776 (3.3 GiB) > > eth0.15 Link encap:Ethernet HWaddr 00:06:5B:88:84:C6 > inet addr:131.94.131.2 Bcast:131.94.131.31 > Mask:255.255.255.224 > inet6 addr: fe80::206:5bff:fe88:84c6/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:8522903 errors:0 dropped:0 overruns:0 frame:0 > TX packets:125184 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:445383310 (424.7 MiB) TX bytes:5258196 (5.0 MiB) > > eth0.16 Link encap:Ethernet HWaddr 00:06:5B:88:84:C6 > inet addr:131.94.134.131 Bcast:131.94.134.191 > Mask:255.255.255.192 > inet6 addr: fe80::206:5bff:fe88:84c6/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:308961401 errors:0 dropped:0 overruns:0 frame:0 > TX packets:8353961 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:1102564519 (1.0 GiB) TX bytes:1326031999 (1.2 GiB) > > and my xorp configs look like: > > > interfaces { > interface "eth0.14" { > description: "" > disable: false > discard: false > unreachable: false > management: false > vif "eth0.14" { > disable: false > address 131.94.132.91 { > prefix-length: 24 > disable: false > } > } > } > interface "eth0.15" { > description: "" > disable: false > discard: false > unreachable: false > management: false > vif "eth0.15" { > disable: false > address 131.94.131.2 { > prefix-length: 27 > disable: false > } > } > } > interface "eth0.16" { > description: "" > disable: false > discard: false > unreachable: false > management: false > vif "eth0.16" { > disable: false > address 131.94.134.131 { > prefix-length: 26 > disable: false > } > } > } > } > > > > protocols { > fib2mrib { > disable: false > } > igmp { > interface "eth0.14" { > vif "eth0.14" { > 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 "eth0.15" { > vif "eth0.15" { > 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 "eth0.16" { > vif "eth0.16" { > 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 { > interface "eth0.14" { > vif "eth0.14" { > disable: false > dr-priority: 1 > hello-period: 30 > hello-triggered-delay: 5 > } > } > interface "eth0.15" { > vif "eth0.15" { > disable: true > dr-priority: 1 > hello-period: 30 > hello-triggered-delay: 5 > } > } > interface "eth0.16" { > vif "eth0.16" { > disable: false > dr-priority: 1 > hello-period: 30 > hello-triggered-delay: 5 > } > } > } > } > plumbing { > mfea4 { > disable: false > interface "eth0.14" { > vif "eth0.14" { > disable: false > } > } > interface "eth0.15" { > vif "eth0.15" { > disable: false > } > } > interface "eth0.16" { > vif "eth0.16" { > disable: false > } > } > } > } > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From naresh_raga at yahoo.co.in Thu Jul 1 13:26:52 2010 From: naresh_raga at yahoo.co.in (naresh raga) Date: Fri, 2 Jul 2010 01:56:52 +0530 (IST) Subject: [Xorp-users] Does xorp support equal cost multi path feature Message-ID: <682803.58698.qm@web94801.mail.in2.yahoo.com> Hi, I just want to know whether xorp supports Equal Cost Multi Path routing feature.From the user manual it seems that RFC 2991(ECMP feature) has not been implemented. Thanks, Naresh. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100702/ea441400/attachment.html From esj at cs.fiu.edu Thu Jul 1 14:18:54 2010 From: esj at cs.fiu.edu (Eric S. Johnson) Date: Thu, 01 Jul 2010 17:18:54 -0400 Subject: [Xorp-users] MFEA crashing on system with subinterfaces In-Reply-To: <090201cb1955$94662db0$bd328910$@edu> References: , <4C2BB211.80508@candelatech.com> <20100701145133.AB8DFB8841E@cheetah.cs.fiu.edu> <090201cb1955$94662db0$bd328910$@edu> Message-ID: <20100701211854.C8E4AB8841E@cheetah.cs.fiu.edu> peirce at maine.edu said: > Just a followup - is your config working without register_vif > interfaces? No they are there. I didn't include them in the example. E From excelsio at gmx.com Fri Jul 2 03:15:55 2010 From: excelsio at gmx.com (excelsio at gmx.com) Date: Fri, 02 Jul 2010 12:15:55 +0200 Subject: [Xorp-users] WARNING xorpsh LIBXORP ] read error: Message-ID: <20100702101841.304940@gmx.com> Hi, I want to setup a xorp testbed for playing with multicast routing. Well, I took Fedora Core 13 i386, made all updates and installed? "xorp-ct-1.8-1.fc13.i386.rpm XORP 1.8-CT 32-bit Fedora 13 RPM" So a fresh setup with no configuration at all. When I start xorpsh, with normal user or root, I get the following error: [root at localhost log]# Waiting for xorp_rtrmgr... Befehl wurde nicht gefunden. [root at localhost log]# [root at localhost log]# cat messages | grep xorp Jan 2 10:26:17 localhost yum: Installed: xorp-ct-1.8-1.fc13.i386 [root at localhost log]# xorpsh [ 2010/07/02 13:14:41.440175 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:41.540095 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:41.640224 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:41.740356 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:41.840499 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:41.940654 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.40793 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.140929 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.241067 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.341226 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.441360 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.541498 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.641649 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.741842 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.841930 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:42.942178 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.42346 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.142460 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.242631 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.342748 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.442977 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.543058 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.643185 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.743332 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.843479 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:43.943767 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:44.43808 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:44.144047 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:44.244088 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:44.344247 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused Waiting for xorp_rtrmgr... [ 2010/07/02 13:14:44.444418 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:44.544526 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:44.644777 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:44.744744 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:44.845036 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:44.945295 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.45347 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.145479 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.245613 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.345752 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.445890 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.546037 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.646181 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.746362 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.846502 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:45.946633 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:46.46775 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:46.148957 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:46.248989 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:46.349125 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:46.449259 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:46.549396 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:46.649542 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:46.749677 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused [ 2010/07/02 13:14:46.849810 WARNING xorpsh LIBXORP ] read error: _fd: 25 offset: 0 total-len: 4 error: Connection refused ^C [root at localhost log]# Well, something is going wrong, but I can?t get it. So, does anyone know what it wants to tell me? Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100702/fe6a238e/attachment-0001.html From excelsio at gmx.com Fri Jul 2 04:48:33 2010 From: excelsio at gmx.com (excelsio at gmx.com) Date: Fri, 02 Jul 2010 13:48:33 +0200 Subject: [Xorp-users] WARNING xorpsh LIBXORP ] read error: Message-ID: <20100702114835.304900@gmx.com> Well, I needed a .boot file So I think I have to RTFM... Another question about Fedora 13 and XORP. Do I have to add/modprobe a module, config or something else to get everything working? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100702/b166cd41/attachment.html From greearb at candelatech.com Fri Jul 2 09:31:51 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 02 Jul 2010 09:31:51 -0700 Subject: [Xorp-users] WARNING xorpsh LIBXORP ] read error: In-Reply-To: <20100702114835.304900@gmx.com> References: <20100702114835.304900@gmx.com> Message-ID: <4C2E1477.8030807@candelatech.com> On 07/02/2010 04:48 AM, excelsio at gmx.com wrote: > Well, I needed a .boot file > > So I think I have to RTFM... > > > Another question about Fedora 13 and XORP. Do I have to add/modprobe a > module, config or something else to get everything working? No, you shouldn't need to modprobe anything. You will need to make sure you have libraries such as libpcap-devel, openssl-devel, ncurses-devel. Thanks, Ben > > > > _______________________________________________ > 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 amarnath at copperheadsystems.com Sat Jul 3 06:29:14 2010 From: amarnath at copperheadsystems.com (amarnath at copperheadsystems.com) Date: Sat, 3 Jul 2010 07:29:14 -0600 Subject: [Xorp-users] Reg : Adding the new process to the Xorp. Message-ID: Hi All, I am facing problems when i am adding the new process to the existing xorp code.Is there any document available with any of you which specify how to add the new process to the Xorp. I want my process to run as a daemon waiting in the eventloop. Thanks in advance. Regards, Amarnath From greearb at candelatech.com Sat Jul 3 09:22:51 2010 From: greearb at candelatech.com (Ben Greear) Date: Sat, 03 Jul 2010 09:22:51 -0700 Subject: [Xorp-users] Reg : Adding the new process to the Xorp. In-Reply-To: References: Message-ID: <4C2F63DB.6070901@candelatech.com> On 07/03/2010 06:29 AM, amarnath at copperheadsystems.com wrote: > Hi All, > I am facing problems when i am adding the new process to the existing xorp > code.Is there any document available with any of you which specify how to > add the new process to the Xorp. > I want my process to run as a daemon waiting in the eventloop. There are some docs on this page that might be useful: http://www.candelatech.com/xorp.ct/design_docs.html You could also take a relatively simple protocol (maybe rip?) and copy it to use as a starting point. If anyone ever does put together a simple module for xorp, please post it and I'll archive it as an example. Thanks, Ben > > Thanks in advance. > > Regards, > Amarnath > > _______________________________________________ > 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 galaxy-huang at 163.com Mon Jul 5 22:45:18 2010 From: galaxy-huang at 163.com (xorp-users) Date: Tue, 6 Jul 2010 13:45:18 +0800 (CST) Subject: [Xorp-users] Dose Xorp support DiffServ? Message-ID: <6df728b3.1364a.129a649741b.Coremail.galaxy-huang@163.com> Hi everyone! Dose Xorp support DiffServ? i need to make some modification about DiffServ to support our project at college, i want to know whether Xorp implements DiffServ function in it or not? if so, how can i refer to the related code or classes? I am a newer to Xorp, Could anyone please do me the favor and give me some guidance, thank you very much! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100706/ef0d1d94/attachment.html From amarnath at copperheadsystems.com Tue Jul 6 01:02:03 2010 From: amarnath at copperheadsystems.com (amarnath at copperheadsystems.com) Date: Tue, 6 Jul 2010 02:02:03 -0600 Subject: [Xorp-users] Reg: Compilation flags in Xorp Message-ID: <5e6b9d061db6a40777714cec9eb9c48a.squirrel@mail.copperheadsystems.com> Hi All, Can any one please let me know how and where to change the compilation options in Xorp.I want to compile the Xorp code with the different compilation options. Thanks in Advance. Regards, Amarnath From greearb at candelatech.com Tue Jul 6 04:47:37 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 06 Jul 2010 04:47:37 -0700 Subject: [Xorp-users] Reg: Compilation flags in Xorp In-Reply-To: <5e6b9d061db6a40777714cec9eb9c48a.squirrel@mail.copperheadsystems.com> References: <5e6b9d061db6a40777714cec9eb9c48a.squirrel@mail.copperheadsystems.com> Message-ID: <4C3317D9.7070009@candelatech.com> On 07/06/2010 01:02 AM, amarnath at copperheadsystems.com wrote: > Hi All, > > Can any one please let me know how and where to change the compilation > options in Xorp.I want to compile the Xorp code with the different > compilation options. Check out the code, change to the xorp directory, then run: scons --help xorp/BUILD_NOTES has more info. Thanks, Ben > > Thanks in Advance. > > Regards, > Amarnath > > > > > _______________________________________________ > 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 shashikumar_249 at yahoo.co.in Wed Jul 7 22:23:50 2010 From: shashikumar_249 at yahoo.co.in (shashi kumar) Date: Thu, 8 Jul 2010 10:53:50 +0530 (IST) Subject: [Xorp-users] regarding static compilation of xorp Message-ID: <21821.93222.qm@web7907.mail.in.yahoo.com> Hi All, Is any body compiled xorp code with "static" option ? If yes, could you please send me the procedure . when i am trying with CXXFLAGS=-static i am getting libstdc++.so linking error, i also tryed with CXXFLAGS=--all-static but it is throwing errors while i am executing ./configure I want to know whether it is possible to compile xorp? statically. Could any one please help me out in this regard . Thanks in Advance, shashi? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100708/cd4e608c/attachment.html From greearb at candelatech.com Wed Jul 7 22:54:55 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 07 Jul 2010 22:54:55 -0700 Subject: [Xorp-users] regarding static compilation of xorp In-Reply-To: <21821.93222.qm@web7907.mail.in.yahoo.com> References: <21821.93222.qm@web7907.mail.in.yahoo.com> Message-ID: <4C35682F.2060107@candelatech.com> On 07/07/2010 10:23 PM, shashi kumar wrote: > Hi All, > > Is any body compiled xorp code with "static" option ? > If yes, could you please send me the procedure . > > when i am trying with CXXFLAGS=-static i am getting libstdc++.so linking > error, > i also tryed with CXXFLAGS=--all-static but it is throwing errors while > i am executing ./configure > > I want to know whether it is possible to compile xorp statically. > > Could any one please help me out in this regard . Looks like you are trying an older version, but I notice that xorp.ct also fails when you do: scons shared=no I'll work on fixing xorp.ct. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Thu Jul 8 00:38:25 2010 From: greearb at candelatech.com (Ben Greear) Date: Thu, 08 Jul 2010 00:38:25 -0700 Subject: [Xorp-users] regarding static compilation of xorp In-Reply-To: <4C35682F.2060107@candelatech.com> References: <21821.93222.qm@web7907.mail.in.yahoo.com> <4C35682F.2060107@candelatech.com> Message-ID: <4C358071.7030409@candelatech.com> On 07/07/2010 10:54 PM, Ben Greear wrote: > On 07/07/2010 10:23 PM, shashi kumar wrote: >> Hi All, >> >> Is any body compiled xorp code with "static" option ? >> If yes, could you please send me the procedure . >> >> when i am trying with CXXFLAGS=-static i am getting libstdc++.so linking >> error, >> i also tryed with CXXFLAGS=--all-static but it is throwing errors while >> i am executing ./configure >> >> I want to know whether it is possible to compile xorp statically. >> >> Could any one please help me out in this regard . > > Looks like you are trying an older version, but I notice that > xorp.ct also fails when you do: > > scons shared=no > > I'll work on fixing xorp.ct. It now compiles on my machine: Grab latest from github: http://github.com/greearb/xorp.ct Make sure you have static glibc, pcap and openssl, at least, installed. Change to the xorp directory, and run: scons shared=no No idea if the resulting binaries actually work, so please let me know if you try it out. I'll try to set up a build-bot for static builds next time I'm poking at buildbot. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From wp3891 at seu.edu.cn Thu Jul 8 03:17:05 2010 From: wp3891 at seu.edu.cn (wp3891) Date: Thu, 8 Jul 2010 18:17:05 +0800 Subject: [Xorp-users] Using XORP Message-ID: <478584222.08674@seu.edu.cn> Dear all, I want to use XORP to construct my experiment environment. So I want to see the XORP-users archieves. Thank you!! ? ? ?? wp3891 at seu.edu.cn ???? ?????????? ??????????????? ?????????????????? School of Computer Science and Engineering Southeast University Si Pai Lou 2#,Nanjing 210096, P.R.China 2010-07-08 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100708/06c1f83b/attachment.html From p_latini at hotmail.com Thu Jul 8 17:53:00 2010 From: p_latini at hotmail.com (Patricio Latini) Date: Fri, 9 Jul 2010 00:53:00 +0000 Subject: [Xorp-users] (no subject) Message-ID: Hello, just wanted to check if there are any plan in the development team to add IS-IS support for IPv4/v6 in any upcoming release. Thanks a lot! Patricio _________________________________________________________________ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100709/f9b9ae4d/attachment.html From greearb at candelatech.com Thu Jul 8 20:31:29 2010 From: greearb at candelatech.com (Ben Greear) Date: Thu, 08 Jul 2010 20:31:29 -0700 Subject: [Xorp-users] (no subject) In-Reply-To: References: Message-ID: <4C369811.7060304@candelatech.com> On 07/08/2010 05:53 PM, Patricio Latini wrote: > > Hello, just wanted to check if there are any plan in the development > team to add IS-IS support for IPv4/v6 in any upcoming release. Not by me, but maybe someone else is considering it. A quick read of wikipedia makes it seem like OSPF would be a good alternative...is there some reason you want IS-IS instead of OSPF? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From shashikumar_249 at yahoo.co.in Thu Jul 8 20:46:28 2010 From: shashikumar_249 at yahoo.co.in (shashi kumar) Date: Fri, 9 Jul 2010 09:16:28 +0530 (IST) Subject: [Xorp-users] Regarding libstdc++.a linking with xorp i.e static compilation problem Message-ID: <295410.20935.qm@web7903.mail.in.yahoo.com> ?Hi All, I am unable to link libstdc++ library statically. I am getting the ?following error ?" attempted static link of dynamic object `/usr/lib/./libstdc++.so' " ?My question is : is it not possible to link libstdc++.a statically to xorp , ?in usr/lib directory libstdc++.a is also present. ?could any one? please help me in this regard . ?Thanks in Advance, ?shashi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100709/ad23f853/attachment.html From p_latini at hotmail.com Thu Jul 8 21:09:01 2010 From: p_latini at hotmail.com (Patricio Latini) Date: Fri, 9 Jul 2010 04:09:01 +0000 Subject: [Xorp-users] (no subject) - ISIS In-Reply-To: <4C369811.7060304@candelatech.com> References: , <4C369811.7060304@candelatech.com> Message-ID: Ben, thanks for the prompt response. Right now i have Xorp running in a pretty nice lab enviroment with OSPF and BGP with PIM multicast. However two Service providers that i work with, have told me they are planning to switch in the short term to IS-IS in V4 to support a single protocol operation in V4/V6. That is why i was asking about ISIS, i understand that OSPFv2 and V3 can do the same but at least what i have seen is that seems to be a shift to ISIS in some service providers. BTW, I have used XORP in my lab for years and consider it the most stable and performant routing suite for linux Thanks! Patricio > Date: Thu, 8 Jul 2010 20:31:29 -0700 > From: greearb at candelatech.com > To: p_latini at hotmail.com > CC: xorp-users at xorp.org > Subject: Re: [Xorp-users] (no subject) > > On 07/08/2010 05:53 PM, Patricio Latini wrote: > > > > Hello, just wanted to check if there are any plan in the development > > team to add IS-IS support for IPv4/v6 in any upcoming release. > > Not by me, but maybe someone else is considering it. > > A quick read of wikipedia makes it seem like OSPF would be a good > alternative...is there some reason you want IS-IS instead of OSPF? > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com _________________________________________________________________ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100709/b64c38d3/attachment.html From greearb at candelatech.com Thu Jul 8 23:09:10 2010 From: greearb at candelatech.com (Ben Greear) Date: Thu, 08 Jul 2010 23:09:10 -0700 Subject: [Xorp-users] Regarding libstdc++.a linking with xorp i.e static compilation problem In-Reply-To: <295410.20935.qm@web7903.mail.in.yahoo.com> References: <295410.20935.qm@web7903.mail.in.yahoo.com> Message-ID: <4C36BD06.4050409@candelatech.com> On 07/08/2010 08:46 PM, shashi kumar wrote: > Hi All, > > I am unable to link libstdc++ library statically. I am getting the > following error > > " attempted static link of dynamic object `/usr/lib/./libstdc++.so' " > > My question is : is it not possible to link libstdc++.a statically to xorp , > in usr/lib directory libstdc++.a is also present. > > could any one please help me in this regard . Please post a complete compile log, and tell us what OS and version you are using to compile. Thanks, Ben > > Thanks in Advance, > shashi > > > > > _______________________________________________ > 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 greearb at candelatech.com Thu Jul 8 23:12:55 2010 From: greearb at candelatech.com (Ben Greear) Date: Thu, 08 Jul 2010 23:12:55 -0700 Subject: [Xorp-users] (no subject) - ISIS In-Reply-To: References: , <4C369811.7060304@candelatech.com> Message-ID: <4C36BDE7.5070800@candelatech.com> On 07/08/2010 09:09 PM, Patricio Latini wrote: > Ben, thanks for the prompt response. > Right now i have Xorp running in a pretty nice lab enviroment with OSPF > and BGP with PIM multicast. > However two Service providers that i work with, have told me they are > planning to switch in the short term to IS-IS in V4 to support a single > protocol operation in V4/V6. That is why i was asking about ISIS, i > understand that OSPFv2 and V3 can do the same but at least what i have > seen is that seems to be a shift to ISIS in some service providers. > > BTW, I have used XORP in my lab for years and consider it the most > stable and performant routing suite for linux Glad it's been working for you! It might be possible to take the IS-IS support in Quagga and wrap it into a xorp process, but likely it's not a trivial undertaking. Or, maybe copy the OSPF code and start hacking on it. Either way, I don't have time to do it..but can help answer questions if someone else wants to make the attempt. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From kristian at spritelink.net Thu Jul 8 23:28:58 2010 From: kristian at spritelink.net (Kristian Larsson) Date: Fri, 09 Jul 2010 08:28:58 +0200 Subject: [Xorp-users] (no subject) - ISIS In-Reply-To: <4C36BDE7.5070800@candelatech.com> References: , <4C369811.7060304@candelatech.com> <4C36BDE7.5070800@candelatech.com> Message-ID: <8c66a0f7-531f-4294-9056-5fd42923ec07@email.android.com> Sorry for top posting, I'm using my phone.. If anyone wants to take on this task I would just like to recommend going with the latter approach, ie take the OSPF process and hack away rather than try to integrate isisd from quagga as I think the resulting code, given my memory of it, would be rather fugly ;-) Just my .02$ Btw, how does the OSPF process do sockets today? Given that it idea neither UDP nor TCP I guess it uses some form of raw sockets, right? Does those sockets allow the manipulation of L2 data? How should one go about sending the LLC/SNAP frames that isis typically uses contrary to the ethernet2 that normal IP packets use? -K "Ben Greear" wrote: >On 07/08/2010 09:09 PM, Patricio Latini wrote: >> Ben, thanks for the prompt response. >> Right now i have Xorp running in a pretty nice lab enviroment with OSPF >> and BGP with PIM multicast. >> However two Service providers that i work with, have told me they are >> planning to switch in the short term to IS-IS in V4 to support a single >> protocol operation in V4/V6. That is why i was asking about ISIS, i >> understand that OSPFv2 and V3 can do the same but at least what i have >> seen is that seems to be a shift to ISIS in some service providers. >> >> BTW, I have used XORP in my lab for years and consider it the most >> stable and performant routing suite for linux > >Glad it's been working for you! > >It might be possible to take the IS-IS support in Quagga and wrap it >into a xorp process, but likely it's not a trivial undertaking. > >Or, maybe copy the OSPF code and start hacking on it. > >Either way, I don't have time to do it..but can help answer questions >if someone else wants to make the attempt. > >Thanks, >Ben > >-- >Ben Greear >Candela Technologies Inc http://www.candelatech.com > >_______________________________________________ >Xorp-users mailing list >Xorp-users at xorp.org >http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. From greearb at candelatech.com Thu Jul 8 23:34:31 2010 From: greearb at candelatech.com (Ben Greear) Date: Thu, 08 Jul 2010 23:34:31 -0700 Subject: [Xorp-users] (no subject) - ISIS In-Reply-To: <8c66a0f7-531f-4294-9056-5fd42923ec07@email.android.com> References: , <4C369811.7060304@candelatech.com> <4C36BDE7.5070800@candelatech.com> <8c66a0f7-531f-4294-9056-5fd42923ec07@email.android.com> Message-ID: <4C36C2F7.7020108@candelatech.com> On 07/08/2010 11:28 PM, Kristian Larsson wrote: > Sorry for top posting, I'm using my phone.. > > If anyone wants to take on this task I would just like to recommend going with the latter approach, ie take the OSPF process and hack away rather than try to integrate isisd from quagga as I think the resulting code, given my memory of it, would be rather fugly ;-) > > Just my .02$ > > Btw, how does the OSPF process do sockets today? Given that it idea neither UDP nor TCP I guess it uses some form of raw sockets, right? Does those sockets allow the manipulation of L2 data? How should one go about sending the LLC/SNAP frames that isis typically uses contrary to the ethernet2 that normal IP packets use? The FEA process offers API for generating/receiving raw IP frames and other such things. If it cannot already do raw Ethernet frames, it would not be difficult to add. If someone wants to deal with the ISIS protocol part, I'll be happy to make sure FEA can send/receive raw Ethernet frames. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From wubaochuan at seu.edu.cn Thu Jul 8 23:47:42 2010 From: wubaochuan at seu.edu.cn (wubaochuan) Date: Fri, 09 Jul 2010 14:47:42 +0800 Subject: [Xorp-users] How to export all routes into a file Message-ID: <478658377.04870@seu.edu.cn> Dear everyone, I can see all the routes using the following command in xorpsh: show route table ipv4 unicast final I want to write a C or C++ program which can get all the routes of a router, but I have no idea how to do that.Maybe I can export the output of the command above into a file, and then I write a program to process the file. My question is how can I export output of the command above into a file ? Thank you! Chuan From Nitin.Choudhary at nechclst.in Fri Jul 9 00:21:55 2010 From: Nitin.Choudhary at nechclst.in (Nitin Choudhary) Date: Fri, 9 Jul 2010 12:51:55 +0530 Subject: [Xorp-users] How to export all routes into a file References: <4C36C60E.4020109@seu.edu.cn> Message-ID: <0A8CFEC45B7F4C419F7543867C474423045DA8C5@mailserver.nechclst.in> There is a function named "system()" in library stdlib.h(gcc). You pass the xorp command as parameter to system() function and it will execute that command.. Command will be xorpsh -c "show route table ipv4 unicast final". Do google for details.. Nitin Choudhary -----Original Message----- From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of wubaochuan Sent: Friday, July 09, 2010 12:18 PM To: xorp-users at xorp.org Subject: [Xorp-users] How to export all routes into a file Dear everyone, I can see all the routes using the following command in xorpsh: show route table ipv4 unicast final I want to write a C or C++ program which can get all the routes of a router, but I have no idea how to do that.Maybe I can export the output of the command above into a file, and then I write a program to process the file. My question is how can I export output of the command above into a file ? Thank you! Chuan _______________________________________________ Xorp-users mailing list Xorp-users at xorp.org http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or NECHCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of NECHCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. . ----------------------------------------------------------------------------------------------------------------------- From wubaochuan at seu.edu.cn Fri Jul 9 00:19:34 2010 From: wubaochuan at seu.edu.cn (wubaochuan) Date: Fri, 09 Jul 2010 15:19:34 +0800 Subject: [Xorp-users] How to export all routes into a file In-Reply-To: <478659889.05412@seu.edu.cn> References: <4C36C60E.4020109@seu.edu.cn> <478659889.05412@seu.edu.cn> Message-ID: <478660282.06853@seu.edu.cn> Ok, I will try, thank you. Nitin Choudhary wrote: > There is a function named "system()" in library stdlib.h(gcc). You pass > the xorp command as parameter to system() function and it will execute > that command.. > Command will be xorpsh -c "show route table ipv4 unicast final". > Do google for details.. > > > Nitin Choudhary > > -----Original Message----- > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] > On Behalf Of wubaochuan > Sent: Friday, July 09, 2010 12:18 PM > To: xorp-users at xorp.org > Subject: [Xorp-users] How to export all routes into a file > > Dear everyone, > I can see all the routes using the following command in xorpsh: > show route table ipv4 unicast final > I want to write a C or C++ program which can get all the routes > > of a router, but I have no idea how to do that.Maybe I can export the > output of the command above into a file, and then I write a program to > process the file. My question is how can I export output of the command > above into a file ? > Thank you! > > Chuan > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > DISCLAIMER: > ----------------------------------------------------------------------------------------------------------------------- > The contents of this e-mail and any attachment(s) are confidential and > intended > for the named recipient(s) only. > It shall not attach any liability on the originator or NECHCL or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect the > opinions of NECHCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, > distribution and / or publication of > this message without the prior written consent of the author of this e-mail is > strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. . > ----------------------------------------------------------------------------------------------------------------------- > > From wubaochuan at seu.edu.cn Fri Jul 9 00:28:38 2010 From: wubaochuan at seu.edu.cn (wubaochuan) Date: Fri, 09 Jul 2010 15:28:38 +0800 Subject: [Xorp-users] How to export all routes into a file In-Reply-To: <478659889.05412@seu.edu.cn> References: <4C36C60E.4020109@seu.edu.cn> <478659889.05412@seu.edu.cn> Message-ID: <478660823.08506@seu.edu.cn> Dear Nitin Choudhary , I just wrote a C program using the following: system("/home/chuan/xorp-1.6/rtrmgr/xorpsh -c \"show route table ipv4 unicast final\""); and it works, thank you for your help. Chuan Nitin Choudhary wrote: > There is a function named "system()" in library stdlib.h(gcc). You pass > the xorp command as parameter to system() function and it will execute > that command.. > Command will be xorpsh -c "show route table ipv4 unicast final". > Do google for details.. > > > Nitin Choudhary > > -----Original Message----- > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] > On Behalf Of wubaochuan > Sent: Friday, July 09, 2010 12:18 PM > To: xorp-users at xorp.org > Subject: [Xorp-users] How to export all routes into a file > > Dear everyone, > I can see all the routes using the following command in xorpsh: > show route table ipv4 unicast final > I want to write a C or C++ program which can get all the routes > > of a router, but I have no idea how to do that.Maybe I can export the > output of the command above into a file, and then I write a program to > process the file. My question is how can I export output of the command > above into a file ? > Thank you! > > Chuan > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > DISCLAIMER: > ----------------------------------------------------------------------------------------------------------------------- > The contents of this e-mail and any attachment(s) are confidential and > intended > for the named recipient(s) only. > It shall not attach any liability on the originator or NECHCL or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect the > opinions of NECHCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, > distribution and / or publication of > this message without the prior written consent of the author of this e-mail is > strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. . > ----------------------------------------------------------------------------------------------------------------------- > > From amarnath at copperheadsystems.com Fri Jul 9 06:31:54 2010 From: amarnath at copperheadsystems.com (amarnath at copperheadsystems.com) Date: Fri, 9 Jul 2010 07:31:54 -0600 Subject: [Xorp-users] Reg :Thread creation inside a Xorp Process Message-ID: <801c2f531b9f2529555c63f24d6e4157.squirrel@mail.copperheadsystems.com> Hi All, I am trying to start a thread inside the Xorp process, pls let me know if this is allowed. Please share the documents or the related info regarding this if any one has tried to start a thread inside a xorp process. Thanks in Advance. Regards, Amarnath. From greearb at candelatech.com Fri Jul 9 08:00:32 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 09 Jul 2010 08:00:32 -0700 Subject: [Xorp-users] Reg :Thread creation inside a Xorp Process In-Reply-To: <801c2f531b9f2529555c63f24d6e4157.squirrel@mail.copperheadsystems.com> References: <801c2f531b9f2529555c63f24d6e4157.squirrel@mail.copperheadsystems.com> Message-ID: <4C373990.2020702@candelatech.com> On 07/09/2010 06:31 AM, amarnath at copperheadsystems.com wrote: > Hi All, > I am trying to start a thread inside the Xorp process, pls let me know if > this is allowed. > Please share the documents or the related info regarding this if any one > has tried to start a thread inside a xorp process. Xorp is not thread safe. Please use non-blocking IO and the event loop instead. If you really think you need threads, please explain in more detail. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From rps at maine.edu Fri Jul 9 11:32:27 2010 From: rps at maine.edu (Ray Soucy) Date: Fri, 9 Jul 2010 14:32:27 -0400 Subject: [Xorp-users] XORP 1.6 Questions and Comments (with examples) Message-ID: Wanted to give a little feedback and pick your brain about XORP as we're starting to try it in production for K12 as a cost-savings measure. I apologize in advance for how lengthy this turned out to be. Issue 1: I'm using RIP over point-to-point links to provide routing for XORP 1.6 on Linux One thing I notice is that in a setup with two links (for a backup path) XORP will only pass the winning routes to the kernel routing table. This is OK, but it does make troubleshooting routing issues a bit difficult. One would expect that within XORP you could view routes available from both paths but that isn't the case either. Example: Link A is 10.0.0.2/31 Link B is 10.0.0.4/31 XORP box has Link A and Link B coming in as 802.1Q tagged VLAN's 2 and 3. Link A has a metric of 1 and Link B has a metric of 2. XORP config: ----8<---- protocols { fib2mrib { disable: false } rip { interface eth0 { vif "eth0.2" { address 10.0.0.3 { metric: 1 horizon: "split-horizon-poison-reverse" disable: false passive: false accept-non-rip-requests: true accept-default-route: true advertise-default-route: false route-timeout: 180 deletion-delay: 120 triggered-delay: 3 triggered-jitter: 66 update-interval: 30 update-jitter: 16 request-interval: 30 interpacket-delay: 50 } } vif "eth0.3" { address 10.0.0.5 { metric: 2 horizon: "split-horizon-poison-reverse" disable: false passive: false accept-non-rip-requests: true accept-default-route: true advertise-default-route: false route-timeout: 180 deletion-delay: 120 triggered-delay: 3 triggered-jitter: 66 update-interval: 30 update-jitter: 16 request-interval: 30 interpacket-delay: 50 } } } } } fea { unicast-forwarding4 { disable: false forwarding-entries { retain-on-startup: true retain-on-shutdown: true } } } interfaces { restore-original-config-on-shutdown: true interface eth0 { description: "WAN" disable: false discard: false unreachable: false management: false default-system-config { } } interface eth1 { description: "LAN" disable: false discard: false unreachable: false management: false default-system-config { } } interface "eth0.2" { description: "Link A" disable: false discard: false unreachable: false management: false vif "eth0.2" { disable: false address 10.0.0.3 { prefix-length: 31 disable: false } } } interface "eth0.3" { description: "Link B" disable: false discard: false unreachable: false management: false vif "eth0.3" { disable: false address 10.0.0.5 { prefix-length: 31 disable: false } } } } ----8<---- One would expect that either: 1. Routes from both paths make it into the kernel routing table with the appropriate metric and the kernel decides which one to use. or 2. XORP displays routes for both paths internally but only sends the winning route to the kernel. What I would expect to see would be: 10.0.0.2 0.0.0.0 255.255.255.254 U 0 0 0 eth0.2 10.0.0.4 0.0.0.0 255.255.255.254 U 0 0 0 eth0.3 192.168.0.0 0.0.0.0 255.255.254.0 U 0 0 0 eth1 0.0.0.0 10.0.0.2 0.0.0.0 UG 1 0 0 eth0.2 0.0.0.0 10.0.0.4 0.0.0.0 UG 2 0 0 eth0.3 But in practice the route advertised from Link B doesn't show up in the kernel unless the route from Link A is absent. If I check the routing table in XORP it doesn't show any candidate routes either. Was this the intended behavior of XORP? Not being able to see candidate routes on a device can make troubleshooting a bit challenging. Issue 2: It seems that the only way I can get XORP to talk to 802.1Q interfaces consistantly is to define them as physical interfaces not as VIF's as the manual implies. e.g. ----8<---- interface eth0 { description: "WAN" disable: false discard: false unreachable: false management: false vif eth0 { disable: true } vif "eth0.2" { disable: false vlan { vlan-id: 2 } address 10.0.0.3 { prefix-length: 31 disable: false } } vif "eth0.3" { disable: false vlan { vlan-id: 3 } address 10.0.0.5 { prefix-length: 31 disable: false } } } ----8<---- Will seem to work for RIP but fail completely when MFEA is started. In addition if the 802.1Q interface already exists then XORP throws an error. If it doesn't exist XORP fails to create it and throws an error. Instead we found that the only thing that works is to manually create the 802.1Q interfaces and then define them as physical interfaces in XORP. e.g. ----8<---- interface "eth0.2" { description: "Link A" disable: false discard: false unreachable: false management: false vif "eth0.2" { disable: false address 10.0.0.3 { prefix-length: 31 disable: false } } } interface "eth0.3" { description: "Link B" disable: false discard: false unreachable: false management: false vif "eth0.3" { disable: false address 10.0.0.5 { prefix-length: 31 disable: false } } } ----8<---- Is this the correct way to configure XORP or is it just a work-around for a bug in 802.1Q implimentation? Issue 3: When configuring XORP for multicast under the MFEA the "register_vif" interface is required. We ran into a pretty confusing issue where if the "register_vif" interface is defined first XORP throws a fit and fails to start. If it's defined 2nd, last, or anyplace in between it works fine. e.g. ----8<---- plumbing { mfea4 { disable: false interface "register_vif" { vif "register_vif" { disable: false } } interface eth1 { vif eth1 { disable: false } } } } ----8<---- This will fail to start. ----8<---- plumbing { mfea4 { disable: false interface eth1 { vif eth1 { disable: false } } interface "register_vif" { vif "register_vif" { disable: false } } } } ----8<---- This one will work fine. Took a while to figure that one out... Also notice that for PIM-SM to work the IP addresses need to be explicitly defined in XORP. If we try default-system-config it fails. Recap: So while the manual implies that you should configure 802.1Q interfaces as VIF's that doesn't seem to work. The only way we've found to get things working is to manually create the interfaces then start XORP with them defined as physical interfaces. Is this correct or are we just doing it wrong? Ordering of "register_vif" interface being relavant is a little annoying. Not seeing any good way to see candidate routes in XORP. -- Ray Soucy Epic Communications Specialist Phone: +1 (207) 561-3526 Networkmaine, a Unit of the University of Maine System http://www.networkmaine.net/ From amarnath at copperheadsystems.com Fri Jul 9 21:34:37 2010 From: amarnath at copperheadsystems.com (amarnath at copperheadsystems.com) Date: Fri, 9 Jul 2010 22:34:37 -0600 Subject: [Xorp-users] Reg :Thread creation inside a Xorp Process In-Reply-To: <4C373990.2020702@candelatech.com> References: <801c2f531b9f2529555c63f24d6e4157.squirrel@mail.copperheadsystems.com> <4C373990.2020702@candelatech.com> Message-ID: Hi Ben, Thanks for your quick reply. I am trying to integrate the L2 protocol suite with the Xorp, for this I am starting the entire L2 suite as a single process and from that i want to start different threads to handle each L2 protocol.My L2 suite is implemented with multi-threaded architecture. Please suggest me a feasible method to do this. Regards, Amarnath. > On 07/09/2010 06:31 AM, amarnath at copperheadsystems.com wrote: >> Hi All, >> I am trying to start a thread inside the Xorp process, pls let me know >> if >> this is allowed. >> Please share the documents or the related info regarding this if any >> one >> has tried to start a thread inside a xorp process. > > Xorp is not thread safe. Please use non-blocking IO and the event > loop instead. > > If you really think you need threads, please explain in more detail. > > Thanks, > Ben > > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > From greearb at candelatech.com Fri Jul 9 22:45:38 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 09 Jul 2010 22:45:38 -0700 Subject: [Xorp-users] Reg :Thread creation inside a Xorp Process In-Reply-To: References: <801c2f531b9f2529555c63f24d6e4157.squirrel@mail.copperheadsystems.com> <4C373990.2020702@candelatech.com> Message-ID: <4C380902.4050209@candelatech.com> On 07/09/2010 09:34 PM, amarnath at copperheadsystems.com wrote: > Hi Ben, > Thanks for your quick reply. > > I am trying to integrate the L2 protocol suite with the Xorp, for this I > am starting the entire L2 suite as a single process and from that i want > to start different threads to handle each L2 protocol.My L2 suite is > implemented with multi-threaded architecture. > Please suggest me a feasible method to do this. If you already have a multi-threaded architecture, then why do you need xorp to start any threads? Either way, my suggestion is still to do it with non-blocking IO in a select or poll loop if at all possible. Programming with threads properly is very difficult for any non-trivial application. Can you provide more info on this 'L2' suite? Is this some open-source thing? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From amarnath at copperheadsystems.com Fri Jul 9 22:55:58 2010 From: amarnath at copperheadsystems.com (amarnath at copperheadsystems.com) Date: Fri, 9 Jul 2010 23:55:58 -0600 Subject: [Xorp-users] Reg :Thread creation inside a Xorp Process In-Reply-To: <4C380902.4050209@candelatech.com> References: <801c2f531b9f2529555c63f24d6e4157.squirrel@mail.copperheadsystems.com> <4C373990.2020702@candelatech.com> <4C380902.4050209@candelatech.com> Message-ID: Hi Ben, L2 suite is not open source. My L2 suite runs as a single process which fork different threads and in each thread i will wait in infinite loop for the events. So, I have created a process in the xorp and i am trying to start threads as it is implemented in the L2suite.Is there any module in Xorp which does this kind of implementation. Regards, Amarnath. > On 07/09/2010 09:34 PM, amarnath at copperheadsystems.com wrote: >> Hi Ben, >> Thanks for your quick reply. >> >> I am trying to integrate the L2 protocol suite with the Xorp, for this I >> am starting the entire L2 suite as a single process and from that i want >> to start different threads to handle each L2 protocol.My L2 suite is >> implemented with multi-threaded architecture. >> Please suggest me a feasible method to do this. > > If you already have a multi-threaded architecture, then why do > you need xorp to start any threads? > > Either way, my suggestion is still to do it with non-blocking > IO in a select or poll loop if at all possible. Programming with threads > properly > is very difficult for any non-trivial application. > > Can you provide more info on this 'L2' suite? Is this some open-source > thing? > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > From greearb at candelatech.com Sat Jul 10 06:23:19 2010 From: greearb at candelatech.com (Ben Greear) Date: Sat, 10 Jul 2010 06:23:19 -0700 Subject: [Xorp-users] Reg :Thread creation inside a Xorp Process In-Reply-To: References: <801c2f531b9f2529555c63f24d6e4157.squirrel@mail.copperheadsystems.com> <4C373990.2020702@candelatech.com> <4C380902.4050209@candelatech.com> Message-ID: <4C387447.8010200@candelatech.com> On 07/09/2010 10:55 PM, amarnath at copperheadsystems.com wrote: > Hi Ben, > L2 suite is not open source. > My L2 suite runs as a single process which fork different threads and in > each thread i will wait in infinite loop for the events. > So, I have created a process in the xorp and i am trying to start > threads as it is implemented in the L2suite.Is there any module in Xorp > which does this kind of implementation. No, there are no threads in Xorp. But, if you want to start threads, something like pthread_create may do what you want: https://computing.llnl.gov/tutorials/pthreads/ Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From peirce at maine.edu Sun Jul 11 09:46:25 2010 From: peirce at maine.edu (Garry Peirce) Date: Sun, 11 Jul 2010 12:46:25 -0400 Subject: [Xorp-users] XORP 1.6 Questions and Comments (with examples) In-Reply-To: References: Message-ID: <00b301cb2118$99d5f9e0$cd81eda0$@edu> 1 - As both paths are known via RIP you'll only see the best RIP route. The command in XORP 1.6 (from what I've seen) reports the rip table after the RIP filter bank. Given unequal metrics the lower one wins. Given equal metrics the first known path wins. You'd never see equal paths inserted into the kernel as XORP (to my knowledge) doesn't support ECMP. 2 - we must define vlan interfaces individual and not as vifs as mcast configuration will fail (via experience). 3 - register-vif requires the use of another interface's address and therefore (in 1.6) must be defined first. > -----Original Message----- > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] > On Behalf Of Ray Soucy > Sent: Friday, July 09, 2010 2:32 PM > To: xorp-users > Subject: [Xorp-users] XORP 1.6 Questions and Comments (with examples) > > Wanted to give a little feedback and pick your brain about XORP as > we're starting to try it in production for K12 as a cost-savings > measure. > > I apologize in advance for how lengthy this turned out to be. > > Issue 1: > > I'm using RIP over point-to-point links to provide routing for XORP > 1.6 on Linux > > One thing I notice is that in a setup with two links (for a backup > path) XORP will only pass the winning routes to the kernel routing > table. This is OK, but it does make troubleshooting routing issues a > bit difficult. One would expect that within XORP you could view > routes available from both paths but that isn't the case either. > > Example: > Link A is 10.0.0.2/31 > Link B is 10.0.0.4/31 > > XORP box has Link A and Link B coming in as 802.1Q tagged VLAN's 2 and > 3. > Link A has a metric of 1 and Link B has a metric of 2. > > XORP config: > ----8<---- > protocols { > fib2mrib { > disable: false > } > rip { > interface eth0 { > vif "eth0.2" { > address 10.0.0.3 { > metric: 1 > horizon: "split-horizon-poison-reverse" > disable: false > passive: false > accept-non-rip-requests: true > accept-default-route: true > advertise-default-route: false > route-timeout: 180 > deletion-delay: 120 > triggered-delay: 3 > triggered-jitter: 66 > update-interval: 30 > update-jitter: 16 > request-interval: 30 > interpacket-delay: 50 > } > } > vif "eth0.3" { > address 10.0.0.5 { > metric: 2 > horizon: "split-horizon-poison-reverse" > disable: false > passive: false > accept-non-rip-requests: true > accept-default-route: true > advertise-default-route: false > route-timeout: 180 > deletion-delay: 120 > triggered-delay: 3 > triggered-jitter: 66 > update-interval: 30 > update-jitter: 16 > request-interval: 30 > interpacket-delay: 50 > } > } > } > } > } > fea { > unicast-forwarding4 { > disable: false > forwarding-entries { > retain-on-startup: true > retain-on-shutdown: true > } > } > } > interfaces { > restore-original-config-on-shutdown: true > interface eth0 { > description: "WAN" > disable: false > discard: false > unreachable: false > management: false > default-system-config { > } > } > interface eth1 { > description: "LAN" > disable: false > discard: false > unreachable: false > management: false > default-system-config { > } > } > interface "eth0.2" { > description: "Link A" > disable: false > discard: false > unreachable: false > management: false > vif "eth0.2" { > disable: false > address 10.0.0.3 { > prefix-length: 31 > disable: false > } > } > } > interface "eth0.3" { > description: "Link B" > disable: false > discard: false > unreachable: false > management: false > vif "eth0.3" { > disable: false > address 10.0.0.5 { > prefix-length: 31 > disable: false > } > } > } > } > ----8<---- > > One would expect that either: > > 1. Routes from both paths make it into the kernel routing table with > the appropriate metric and the kernel decides which one to use. > > or > > 2. XORP displays routes for both paths internally but only sends the > winning route to the kernel. > > What I would expect to see would be: > > 10.0.0.2 0.0.0.0 255.255.255.254 U 0 0 0 > eth0.2 > 10.0.0.4 0.0.0.0 255.255.255.254 U 0 0 0 > eth0.3 > 192.168.0.0 0.0.0.0 255.255.254.0 U 0 0 0 > eth1 > 0.0.0.0 10.0.0.2 0.0.0.0 UG 1 0 0 > eth0.2 > 0.0.0.0 10.0.0.4 0.0.0.0 UG 2 0 0 > eth0.3 > > But in practice the route advertised from Link B doesn't show up in > the kernel unless the route from Link A is absent. > > If I check the routing table in XORP it doesn't show any candidate > routes either. > > Was this the intended behavior of XORP? Not being able to see > candidate routes on a device can make troubleshooting a bit > challenging. > > Issue 2: > > It seems that the only way I can get XORP to talk to 802.1Q interfaces > consistantly is to define them as physical interfaces not as VIF's as > the manual implies. > > e.g. > > ----8<---- > interface eth0 { > description: "WAN" > disable: false > discard: false > unreachable: false > management: false > vif eth0 { > disable: true > } > vif "eth0.2" { > disable: false > vlan { > vlan-id: 2 > } > address 10.0.0.3 { > prefix-length: 31 > disable: false > } > } > vif "eth0.3" { > disable: false > vlan { > vlan-id: 3 > } > address 10.0.0.5 { > prefix-length: 31 > disable: false > } > } > } > ----8<---- > > Will seem to work for RIP but fail completely when MFEA is started. > In addition if the 802.1Q interface already exists then XORP throws > an error. If it doesn't exist XORP fails to create it and throws > an error. > > Instead we found that the only thing that works is to manually create > the 802.1Q interfaces and then define them as physical interfaces in > XORP. > > e.g. > > ----8<---- > interface "eth0.2" { > description: "Link A" > disable: false > discard: false > unreachable: false > management: false > vif "eth0.2" { > disable: false > address 10.0.0.3 { > prefix-length: 31 > disable: false > } > } > } > interface "eth0.3" { > description: "Link B" > disable: false > discard: false > unreachable: false > management: false > vif "eth0.3" { > disable: false > address 10.0.0.5 { > prefix-length: 31 > disable: false > } > } > } > ----8<---- > > Is this the correct way to configure XORP or is it just a work-around > for a bug in 802.1Q implimentation? > > Issue 3: > > When configuring XORP for multicast under the MFEA the "register_vif" > interface is required. > > We ran into a pretty confusing issue where if the "register_vif" > interface is defined first XORP throws a fit and fails to start. If > it's defined 2nd, last, or anyplace in between it works fine. > > e.g. > > ----8<---- > plumbing { > mfea4 { > disable: false > interface "register_vif" { > vif "register_vif" { > disable: false > } > } > interface eth1 { > vif eth1 { > disable: false > } > } > } > } > ----8<---- > > This will fail to start. > > ----8<---- > plumbing { > mfea4 { > disable: false > interface eth1 { > vif eth1 { > disable: false > } > } > interface "register_vif" { > vif "register_vif" { > disable: false > } > } > } > } > ----8<---- > > This one will work fine. Took a while to figure that one out... > > Also notice that for PIM-SM to work the IP addresses need to be > explicitly defined in XORP. If we try default-system-config it fails. > > Recap: > > So while the manual implies that you should configure 802.1Q > interfaces as VIF's that doesn't seem to work. The only way we've > found to get things working is to manually create the interfaces then > start XORP with them defined as physical interfaces. > > Is this correct or are we just doing it wrong? > > Ordering of "register_vif" interface being relavant is a little > annoying. > > Not seeing any good way to see candidate routes in XORP. > > -- > Ray Soucy > > Epic Communications Specialist > > Phone: +1 (207) 561-3526 > > Networkmaine, a Unit of the University of Maine System > http://www.networkmaine.net/ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From greearb at candelatech.com Mon Jul 12 12:20:31 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 12 Jul 2010 12:20:31 -0700 Subject: [Xorp-users] XORP 1.6 Questions and Comments (with examples) In-Reply-To: <00b301cb2118$99d5f9e0$cd81eda0$@edu> References: <00b301cb2118$99d5f9e0$cd81eda0$@edu> Message-ID: <4C3B6AFF.3060206@candelatech.com> On 07/11/2010 09:46 AM, Garry Peirce wrote: > 2 - we must define vlan interfaces individual and not as vifs as mcast > configuration will fail (via experience). Is there any good reason to support vlans as sub-interfaces? We might could simplify fea quite a bit if we removed the support entirely, and if it already doesn't work, then we shouldn't be causing too much extra inconvenience. But, if there is a good reason to keep it, then this is something I can probably fix. > 3 - register-vif requires the use of another interface's address and > therefore (in 1.6) must be defined first. At the least we could offer a useful error message if this happens. I'm not sure if this bug exists in xorp.ct or not, so if someone reproduces this in xorp.ct, plz let me know. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From wjf198612 at 163.com Wed Jul 14 00:42:45 2010 From: wjf198612 at 163.com (123) Date: Wed, 14 Jul 2010 15:42:45 +0800 (CST) Subject: [Xorp-users] List Administrator Password Message-ID: <1dd7d8.1518d.129cfe7db52.Coremail.wjf198612@163.com> Good afternoon, may I ask how much the administrator password ? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100714/e55f8386/attachment.html From shashikumar_249 at yahoo.co.in Wed Jul 14 01:11:40 2010 From: shashikumar_249 at yahoo.co.in (shashi kumar) Date: Wed, 14 Jul 2010 01:11:40 -0700 (PDT) Subject: [Xorp-users] ELF file data encoding not big-endian Message-ID: <612653.39914.qm@web7906.mail.in.yahoo.com> Hi All, While I am trying to execute xorp on my? target board it is throwing the following error # ./xorp_rtrmgr ./xorp_rtrmgr: error while loading shared libraries: /opt/cross_compiler/ppc_82x x/lib/libstdc++.so.6: ELF file data encoding not big-endian I cross compiled it with Power PC compiler? ppc_82xx . Cn any one help me out in this regard. Thanks in Advance. shashi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100714/151039f0/attachment.html From greearb at candelatech.com Wed Jul 14 06:40:19 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 14 Jul 2010 06:40:19 -0700 Subject: [Xorp-users] ELF file data encoding not big-endian In-Reply-To: <612653.39914.qm@web7906.mail.in.yahoo.com> References: <612653.39914.qm@web7906.mail.in.yahoo.com> Message-ID: <4C3DBE43.2010109@candelatech.com> On 07/14/2010 01:11 AM, shashi kumar wrote: > Hi All, > > While I am trying to execute xorp on my target board it is throwing the > following error > > # ./xorp_rtrmgr > ./xorp_rtrmgr: error while loading shared libraries: > /opt/cross_compiler/ppc_82x > x/lib/libstdc++.so.6: ELF file data encoding not big-endian > > I cross compiled it with Power PC compiler ppc_82xx . > > Cn any one help me out in this regard. What xorp version? Also, have you tried compiling something simpler that uses shared libraries to make sure that your cross-compiler works? Thanks, Ben > > Thanks in Advance. > shashi > > > > > _______________________________________________ > 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 wjf198612 at 163.com Wed Jul 14 20:22:24 2010 From: wjf198612 at 163.com (123) Date: Thu, 15 Jul 2010 11:22:24 +0800 (CST) Subject: [Xorp-users] Problem In-Reply-To: References: Message-ID: <1cd179d.2fcd.129d41fdb0a.Coremail.wjf198612@163.com> Hello ,all good morning ! I now have a project, it about router,asked to use multi-queue scheduling algorithm, so I want to know how to achieve at the XORP platform ? thank you very much ! >Send Xorp-users mailing list submissions to > xorp-users at xorp.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >or, via email, send a message with subject or body 'help' to > xorp-users-request at xorp.org > >You can reach the person managing the list at > xorp-users-owner at xorp.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Xorp-users digest..." > > >Today's Topics: > > 1. List Administrator Password (123) > 2. ELF file data encoding not big-endian (shashi kumar) > 3. Re: ELF file data encoding not big-endian (Ben Greear) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Wed, 14 Jul 2010 15:42:45 +0800 (CST) >From: 123 >Subject: [Xorp-users] List Administrator Password >To: xorp-users at xorp.org >Message-ID: <1dd7d8.1518d.129cfe7db52.Coremail.wjf198612 at 163.com> >Content-Type: text/plain; charset="gbk" > >Good afternoon, may I ask how much the administrator password ? >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100714/e55f8386/attachment-0001.html > >------------------------------ > >Message: 2 >Date: Wed, 14 Jul 2010 01:11:40 -0700 (PDT) >From: shashi kumar >Subject: [Xorp-users] ELF file data encoding not big-endian >To: xorp-users at xorp.org >Message-ID: <612653.39914.qm at web7906.mail.in.yahoo.com> >Content-Type: text/plain; charset="iso-8859-1" > >Hi All, > >While I am trying to execute xorp on my? target board it is throwing the following error > ># ./xorp_rtrmgr >./xorp_rtrmgr: error while loading shared libraries: /opt/cross_compiler/ppc_82x >x/lib/libstdc++.so.6: ELF file data encoding not big-endian > >I cross compiled it with Power PC compiler? ppc_82xx . > >Cn any one help me out in this regard. > >Thanks in Advance. >shashi > > >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100714/151039f0/attachment-0001.html > >------------------------------ > >Message: 3 >Date: Wed, 14 Jul 2010 06:40:19 -0700 >From: Ben Greear >Subject: Re: [Xorp-users] ELF file data encoding not big-endian >To: shashi kumar >Cc: xorp-users at xorp.org >Message-ID: <4C3DBE43.2010109 at candelatech.com> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >On 07/14/2010 01:11 AM, shashi kumar wrote: >> Hi All, >> >> While I am trying to execute xorp on my target board it is throwing the >> following error >> >> # ./xorp_rtrmgr >> ./xorp_rtrmgr: error while loading shared libraries: >> /opt/cross_compiler/ppc_82x >> x/lib/libstdc++.so.6: ELF file data encoding not big-endian >> >> I cross compiled it with Power PC compiler ppc_82xx . >> >> Cn any one help me out in this regard. > >What xorp version? > >Also, have you tried compiling something simpler that uses shared libraries >to make sure that your cross-compiler works? > >Thanks, >Ben > >> >> Thanks in Advance. >> shashi >> >> >> >> >> _______________________________________________ >> 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 > > > >------------------------------ > >_______________________________________________ >Xorp-users mailing list >Xorp-users at xorp.org >http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > >End of Xorp-users Digest, Vol 52, Issue 12 >****************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100715/9d1d85a9/attachment.html From mannuarsid at gmail.com Fri Jul 16 04:16:22 2010 From: mannuarsid at gmail.com (manohar arsid) Date: Fri, 16 Jul 2010 16:46:22 +0530 Subject: [Xorp-users] Re :How to Send Packet to Xorp Router Message-ID: Hi All .,, I want to send Packet to XORP ROUTER .. could anybody please help me .. Thanks -- mannu arsid -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100716/eb07a843/attachment.html From juarez.paulino at gmail.com Fri Jul 16 05:33:56 2010 From: juarez.paulino at gmail.com (Juarez Paulino) Date: Fri, 16 Jul 2010 09:33:56 -0300 Subject: [Xorp-users] Report: XORP-CT cross-compilation with PPC In-Reply-To: References: Message-ID: I think my previous mail didn't get into the list because I have used some formatting. So here comes a copy... I hope it can helps someone. On Wed, Jul 14, 2010 at 5:40 PM, Juarez Paulino wrote: > > Hi All, > > I'm sending this message as a report of our successful cross-compilation of XORP-CT on a linux kernel PowerPC machine. > > Our group were able to cross-compile and identify some problems on the SCONS scripts, so we have to apply some patches on them to make they work fine. > > We use GDB server to debug things. It was really useful as we got into the executable from host and checked the code from guest. It's important to remember to use export optimize=no to correctly get the symbols on debugging. > > We just test it on Multicast PIM module, so I don know if it requires more improvements on other modules. > > So here are our appointments: > > 1) Cross-Compile important libraries: > > - libpcap; > - openssl; > - ncurses. > > Our buildroot toolchain already had all of them. > > > 2) Merging cross-compilation environment on SConstruct: > > We couldn't get SCons to work with previous export/guest/build options like: > > $ export CC=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc \ > export CXX=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++ \ > export RANLIB=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib \ > scons \ > # :( dont work yet... > > or: > > $ export CC=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc \ > export CXX=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++ \ > export RANLIB=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib \ > scons build=i686-pc-linux-gnu host=powerpc-83xx-linux-uclibc > # :P dont work either... > > > -> Solution: Merging options directly on SConstruct: > > #SConstruct line 145, > build = 'i686-pc-linux-gnu' #Spider: edited here, don't use ./config.guess on build machine! > build_cpu = 'i686' > build_vendor = 'pc' > build_os = 'linux-gnu' > > -------------------------------------- > > #SConstruct line 155, > host = 'powerpc-83xx-linux-uclibc' #Spider: edited here, Crosscompiling > host_cpu = 'powerpc' > host_vendor = '83xx' > host_os = 'linux-uclibc' > > ------------------------------------------- > > #line 190, SConstruct > #Spider: edited here. Just after ''env = Environment()'' above > #Extremely Zealous Environment!! > env['AR'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ar' > env['AS'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-as' > env['CC'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc' > env['CXX'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++' > env['LD'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ld' > env['LDCONFIG'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ldconfig' > env['LDD'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ldd' > env['NM'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-nm' > env['OBJCOPY'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-objcopy' > env['OBJDUMP'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-objdump' > env['RANLIB'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib' > env['STRIP'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-strip' > #Spider: edit ended > > > - As you can see, we have put other environment binaries either, just to be sure that it works! > > > 3) Eliminating Endianess problem > > After some terrible hours of debugging, we managed to cross-compile XORP-CT and not to get the endianess problem on FEA sockets. Our PowerPC machine uses BIG_ENDIAN, but our host cross-compilation machine uses LITTLE_ENDIAN, so endianess-check get wrong parameters when looking for it. > > Maybe there is some better ways, but we find it easy to "brute define" things by hand to get xorp_config.h correctly identify endianess. > > -> Solution: > > # Line 37, > # File: xorp/site_scons/config/allconfig.pym > # Mod: Check-endianess line comented > def DoAllConfig(env, conf, host_os): > ########## > # endian > # XXX Wot about cross compilation?? > # Pedro: Disable endianness check for cross compilation success > > # conf.CheckEndianness() > > -------------------------------------------------- > > # Line 578 > # File: xorp/SConstruct > my_custom_tests = { > 'CheckBoost' : CheckBoost, > 'CheckBoostLibrary' : CheckBoostLibrary, > > # Pedro: removing endianess check > # 'CheckEndianness' : CheckEndianness, > > 'CheckTypeMember' : CheckTypeMember, > 'CheckSysctl' : CheckSysctl > } > > ------------------------------------------------------ > > # Line 592 > # File: xorp/SConstruct > > # Juarez: Definition of endianess by force > conf.Define('WORDS_BIGENDIAN') > > > 4) More sockets errors > > More debugging time and we found a warning message that FEA were packeting PIM header with a different number of bytes that it was expected. > > It's due to a bad identification of our uclibc library on SConstruct script. > > -> Solution: Add our linux-uclibc symbol to host_os RAW check. > > # Linha 204 > # Pedro: adding the router libc in the if test > if host_os == 'linux-gnu' or host_os == 'openbsd' or host_os == 'linux-uclibc': > conf.Define('IPV4_RAW_OUTPUT_IS_RAW') > conf.Define('IPV4_RAW_INPUT_IS_RAW') > > > ============================================================================== > > > - With these modifications, we got XORP-CT top-of-tree Ben version to cross-compile and works fine with PIM module on PPC machine. > > - We've tested XORP-CT restricted space versions (only with PIM module and necessary) and it seems to work fine too on our SSM environment. > > - Our last stripped working version got around ~9.6MB space: > > sudo scons -j4 disable_ipv6=yes disable_fw=yes disable_warninglogs=yes disable_tracelogs=yes disable_fatallogs=yes disable_infologs=yes disable_assertlogs=yes disable_errorlogs=yes enable_olsr=no enable_bgp=no enable_vrrp=no enable_policy=no enable_rip=no optimize=size enable_fea_dummy=no enable_xorpsh=no disable_profile=yes > > * We had to enable and configure OSPF module too, as xorp can recognize (i think it inverts) the system metrics... > > Without OSPF, we got 8.4MB... > > > Our next work and probably most difficult is to reduce more our XORP version. > > So do you have any tips beyond Ben PATCHES (on getting out modules, xorpsh and IPv6 code) from where we could begin? > > > Thanks, > > Juarez Paulino > Universidade de Brasilia, Brazil > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100716/50d1fcf3/attachment.html From greearb at candelatech.com Fri Jul 16 07:45:55 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 16 Jul 2010 07:45:55 -0700 Subject: [Xorp-users] Report: XORP-CT cross-compilation with PPC In-Reply-To: References: Message-ID: <4C4070A3.1050404@candelatech.com> On 07/16/2010 05:33 AM, Juarez Paulino wrote: > I think my previous mail didn't get into the list because I have used > some formatting. > > So here comes a copy... I hope it can helps someone. Thanks for the detailed email! If it's not too much trouble, can you send the changes as a diff? git diff > /tmp/foo.patch If the list won't take it, send directly to me. I think some of these can be rolled in as is, and I can add some compile-time args to deal with things like endian-ness checks. I have a few more comments inline below: > > Our buildroot toolchain already had all of them. > > > > > > 2) Merging cross-compilation environment on SConstruct: > > > > We couldn't get SCons to work with previous export/guest/build > options like: > > > > $ export > CC=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc \ > > export > CXX=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++ \ > > export > RANLIB=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib \ > > scons \ > > # :( dont work yet... > > > > or: > > > > $ export > CC=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc \ > > export > CXX=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++ \ > > export > RANLIB=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib \ > > scons build=i686-pc-linux-gnu host=powerpc-83xx-linux-uclibc > > # :P dont work either... I used syntax like this when cross-compiling to ARM. Could you try this and see if it works? If not, plz send me the output of the failed attempt. Replace my paths with your tools, and change build= accordingly. scons build=arm-unknown-linux-gnu \ STRIP=${HOME}/x-tools/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-sstrip \ CC=${HOME}/x-tools/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc \ CXX=${HOME}/x-tools/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-g++ \ CFLAGS=-I${HOME}/x-tools/arm-unknown-linux-gnueabi/local/include \ CXXFLAGS=-I${HOME}/x-tools/arm-unknown-linux-gnueabi/local/include \ LINKFLAGS=-L${HOME}/x-tools/arm-unknown-linux-gnueabi/local/lib > > 3) Eliminating Endianess problem > > > > After some terrible hours of debugging, we managed to cross-compile > XORP-CT and not to get the endianess problem on FEA sockets. Our PowerPC > machine uses BIG_ENDIAN, but our host cross-compilation machine uses > LITTLE_ENDIAN, so endianess-check get wrong parameters when looking for it. > > > > Maybe there is some better ways, but we find it easy to "brute > define" things by hand to get xorp_config.h correctly identify endianess. I'll look into this check when I get some time. If it could use the (cross)-compiler to do the checks, it should be able to work properly regardless of cross-compiling or not. > ============================================================================== > > > > > > - With these modifications, we got XORP-CT top-of-tree Ben version to > cross-compile and works fine with PIM module on PPC machine. > > > > - We've tested XORP-CT restricted space versions (only with PIM > module and necessary) and it seems to work fine too on our SSM environment. > > > > - Our last stripped working version got around ~9.6MB space: > > > > sudo scons -j4 disable_ipv6=yes disable_fw=yes > disable_warninglogs=yes disable_tracelogs=yes disable_fatallogs=yes > disable_infologs=yes disable_assertlogs=yes disable_errorlogs=yes > enable_olsr=no enable_bgp=no enable_vrrp=no enable_policy=no > enable_rip=no optimize=size enable_fea_dummy=no enable_xorpsh=no > disable_profile=yes > > > > * We had to enable and configure OSPF module too, as xorp can > recognize (i think it inverts) the system metrics... Can you give me some details on the OSPF issue? I don't understand what you wrote above. > > Our next work and probably most difficult is to reduce more our XORP > version. > > > > So do you have any tips beyond Ben PATCHES (on getting out modules, > xorpsh and IPv6 code) from where we could begin? What is your goal for size? There is probably some more ipv6 code that can be eliminated from the core libraries and such. If you go this route, please do it in smaller chunks if possible and send me patches for each chunk. There may be tools that can help determine what is taking up the space in files (code, data, etc)..that might help narrow down things to look for. There is also some 'dead' code in xorp still. In particular, I have been meaning to remove the 'batch' logic from the libxipc logic. It's not used by any code. Not sure if it will save much space though. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Fri Jul 16 07:47:12 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 16 Jul 2010 07:47:12 -0700 Subject: [Xorp-users] Re :How to Send Packet to Xorp Router In-Reply-To: References: Message-ID: <4C4070F0.8050502@candelatech.com> On 07/16/2010 04:16 AM, manohar arsid wrote: > > Hi All .,, > > I want to send Packet to XORP ROUTER .. could anybody please help me .. You need to give a lot more details if you want help. Thanks, Ben > > > Thanks > -- > mannu arsid > > > > _______________________________________________ > 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 juarez.paulino at gmail.com Sat Jul 17 11:51:54 2010 From: juarez.paulino at gmail.com (Juarez Paulino) Date: Sat, 17 Jul 2010 15:51:54 -0300 Subject: [Xorp-users] Report: XORP-CT cross-compilation with PPC In-Reply-To: <4C4070A3.1050404@candelatech.com> References: <4C4070A3.1050404@candelatech.com> Message-ID: Sorry for lately replying, I was confirming some of the answers... Unfortunately I think I will only be able to execute "git diff" on Monday as I'm not going to lab this weekend. I don't have the original builder virtual machine with our XORP SConstruct file here... > I used syntax like this when cross-compiling to ARM. Could you try this and see if it works? It seems to work now. Sorry for that... I think that other commands were not doing well due to a bad library LINKFLAGS specification. Our toolchain was initially trying to link with an old libpcap that didn't have send_packet() function. We just cross-compiled a new libpcap version and replaced it on toolchain. >Can you give me some details on the OSPF issue? I don't understand what you wrote above. We were initially trying to use xorp without OSPF module on a PIM-SSM environment. So we disabled things like static RP or bootstrap options. We statically defined routes on the closed environment system giving them some "hand-write" metrics. When we executed the xorp_rtmgr on our config (IGMP, PIM, FIB2MRIB), it seems that xorp got lost since it recognized the path from client nodes with higher metrics rather than the smaller one. So it constructed an undesirable tree from SSM requirements point of view. Maybe it's just a weak configuration of xorp config file. We got it really simple. I have attached our final working (whith OSPF) simple config file on this message. If we remove the OSPF configuration, XORP doesn't understand the system static metrics. > What is your goal for size? We have to take it on less possible space. I think something ~5MB would be fine. By simple examining the lib dir on xorp install path, I realized that what is most space-used is what we really need on multicast task. Do you think STL could be a space bottleneck on this case? I'll try following your other tips on IPv6 and libxipc batch code. If I manage to get it, I'll post my patches. On Fri, Jul 16, 2010 at 11:45 AM, Ben Greear wrote: > On 07/16/2010 05:33 AM, Juarez Paulino wrote: > >> I think my previous mail didn't get into the list because I have used >> some formatting. >> >> So here comes a copy... I hope it can helps someone. >> > > Thanks for the detailed email! > > If it's not too much trouble, can you send the changes as a diff? > > git diff > /tmp/foo.patch > > If the list won't take it, send directly to me. > > > I think some of these can be rolled in as is, and I can add some > compile-time args to deal with things like endian-ness checks. > > I have a few more comments inline below: > > > > Our buildroot toolchain already had all of them. >> > >> > >> > 2) Merging cross-compilation environment on SConstruct: >> > >> > We couldn't get SCons to work with previous export/guest/build >> options like: >> > >> > $ export >> CC=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc \ >> > export >> CXX=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++ \ >> > export >> RANLIB=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib >> \ >> > scons \ >> > # :( dont work yet... >> > >> > or: >> > >> > $ export >> CC=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc \ >> > export >> CXX=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++ \ >> > export >> RANLIB=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib >> \ >> > scons build=i686-pc-linux-gnu host=powerpc-83xx-linux-uclibc >> > # :P dont work either... >> > > I used syntax like this when cross-compiling to ARM. Could you try this > and see if it works? If not, plz send me the output of the failed > attempt. Replace my paths with your tools, and change build= > accordingly. > > scons build=arm-unknown-linux-gnu \ > > STRIP=${HOME}/x-tools/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-sstrip > \ > > CC=${HOME}/x-tools/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc > \ > > CXX=${HOME}/x-tools/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-g++ > \ > CFLAGS=-I${HOME}/x-tools/arm-unknown-linux-gnueabi/local/include \ > CXXFLAGS=-I${HOME}/x-tools/arm-unknown-linux-gnueabi/local/include \ > LINKFLAGS=-L${HOME}/x-tools/arm-unknown-linux-gnueabi/local/lib > > > > > 3) Eliminating Endianess problem >> > >> > After some terrible hours of debugging, we managed to cross-compile >> XORP-CT and not to get the endianess problem on FEA sockets. Our PowerPC >> machine uses BIG_ENDIAN, but our host cross-compilation machine uses >> LITTLE_ENDIAN, so endianess-check get wrong parameters when looking for >> it. >> > >> > Maybe there is some better ways, but we find it easy to "brute >> define" things by hand to get xorp_config.h correctly identify endianess. >> > > I'll look into this check when I get some time. If it could use the > (cross)-compiler to do the checks, it should be able to work properly > regardless > of cross-compiling or not. > > > ============================================================================== >> > >> > >> > - With these modifications, we got XORP-CT top-of-tree Ben version to >> cross-compile and works fine with PIM module on PPC machine. >> > >> > - We've tested XORP-CT restricted space versions (only with PIM >> module and necessary) and it seems to work fine too on our SSM >> environment. >> > >> > - Our last stripped working version got around ~9.6MB space: >> > >> > sudo scons -j4 disable_ipv6=yes disable_fw=yes >> disable_warninglogs=yes disable_tracelogs=yes disable_fatallogs=yes >> disable_infologs=yes disable_assertlogs=yes disable_errorlogs=yes >> enable_olsr=no enable_bgp=no enable_vrrp=no enable_policy=no >> enable_rip=no optimize=size enable_fea_dummy=no enable_xorpsh=no >> disable_profile=yes >> > >> > * We had to enable and configure OSPF module too, as xorp can >> recognize (i think it inverts) the system metrics... >> > > Can you give me some details on the OSPF issue? I don't understand > what you wrote above. > > > > Our next work and probably most difficult is to reduce more our XORP >> version. >> > >> > So do you have any tips beyond Ben PATCHES (on getting out modules, >> xorpsh and IPv6 code) from where we could begin? >> > > What is your goal for size? > > There is probably some more ipv6 code that can be eliminated from > the core libraries and such. If you go this route, please do > it in smaller chunks if possible and send me patches for each chunk. > > There may be tools that can help determine what is taking up > the space in files (code, data, etc)..that might help narrow down > things to look for. > > There is also some 'dead' code in xorp still. In particular, I > have been meaning to remove the 'batch' logic from the libxipc > logic. It's not used by any code. Not sure if it will save > much space though. > > > Thanks, > Ben > > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100717/482d4adc/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: multi.conf Type: application/octet-stream Size: 2570 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100717/482d4adc/attachment.obj From wjf198612 at 163.com Sun Jul 18 05:50:01 2010 From: wjf198612 at 163.com (tsing) Date: Sun, 18 Jul 2010 20:50:01 +0800 (CST) Subject: [Xorp-users] Problem In-Reply-To: References: Message-ID: <1c0b943.5c2c.129e59a9983.Coremail.wjf198612@163.com> Hello ,All my teacher asked me to use multi-queue scheduling algorithm in the router, so I want to know how to achieve at the XORP platform ? can you give me some advice. I am a student! Thank you very much ! wu Jin-Fu >Send Xorp-users mailing list submissions to > xorp-users at xorp.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >or, via email, send a message with subject or body 'help' to > xorp-users-request at xorp.org > >You can reach the person managing the list at > xorp-users-owner at xorp.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Xorp-users digest..." > > >Today's Topics: > > 1. List Administrator Password (123) > 2. ELF file data encoding not big-endian (shashi kumar) > 3. Re: ELF file data encoding not big-endian (Ben Greear) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Wed, 14 Jul 2010 15:42:45 +0800 (CST) >From: 123 >Subject: [Xorp-users] List Administrator Password >To: xorp-users at xorp.org >Message-ID: <1dd7d8.1518d.129cfe7db52.Coremail.wjf198612 at 163.com> >Content-Type: text/plain; charset="gbk" > >Good afternoon, may I ask how much the administrator password ? >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100714/e55f8386/attachment-0001.html > >------------------------------ > >Message: 2 >Date: Wed, 14 Jul 2010 01:11:40 -0700 (PDT) >From: shashi kumar >Subject: [Xorp-users] ELF file data encoding not big-endian >To: xorp-users at xorp.org >Message-ID: <612653.39914.qm at web7906.mail.in.yahoo.com> >Content-Type: text/plain; charset="iso-8859-1" > >Hi All, > >While I am trying to execute xorp on my? target board it is throwing the following error > ># ./xorp_rtrmgr >./xorp_rtrmgr: error while loading shared libraries: /opt/cross_compiler/ppc_82x >x/lib/libstdc++.so.6: ELF file data encoding not big-endian > >I cross compiled it with Power PC compiler? ppc_82xx . > >Cn any one help me out in this regard. > >Thanks in Advance. >shashi > > >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100714/151039f0/attachment-0001.html > >------------------------------ > >Message: 3 >Date: Wed, 14 Jul 2010 06:40:19 -0700 >From: Ben Greear >Subject: Re: [Xorp-users] ELF file data encoding not big-endian >To: shashi kumar >Cc: xorp-users at xorp.org >Message-ID: <4C3DBE43.2010109 at candelatech.com> >Content-Type: text/plain; charset=ISO-8859-1; format=flowed > >On 07/14/2010 01:11 AM, shashi kumar wrote: >> Hi All, >> >> While I am trying to execute xorp on my target board it is throwing the >> following error >> >> # ./xorp_rtrmgr >> ./xorp_rtrmgr: error while loading shared libraries: >> /opt/cross_compiler/ppc_82x >> x/lib/libstdc++.so.6: ELF file data encoding not big-endian >> >> I cross compiled it with Power PC compiler ppc_82xx . >> >> Cn any one help me out in this regard. > >What xorp version? > >Also, have you tried compiling something simpler that uses shared libraries >to make sure that your cross-compiler works? > >Thanks, >Ben > >> >> Thanks in Advance. >> shashi >> >> >> >> >> _______________________________________________ >> 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 > > > >------------------------------ > >_______________________________________________ >Xorp-users mailing list >Xorp-users at xorp.org >http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > >End of Xorp-users Digest, Vol 52, Issue 12 >****************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100718/3b7f8659/attachment.html From greearb at candelatech.com Sun Jul 18 22:47:18 2010 From: greearb at candelatech.com (Ben Greear) Date: Sun, 18 Jul 2010 22:47:18 -0700 Subject: [Xorp-users] Problem In-Reply-To: <1c0b943.5c2c.129e59a9983.Coremail.wjf198612@163.com> References: <1c0b943.5c2c.129e59a9983.Coremail.wjf198612@163.com> Message-ID: <4C43E6E6.5010106@candelatech.com> On 07/18/2010 05:50 AM, tsing wrote: > Hello ,All > my teacher asked me to use multi-queue scheduling algorithm in the > router, so I want to know how to achieve at the XORP platform ? can you > give me some advice. I am a student! > > Thank you very much ! I'm not aware of any support in Xorp for this, and furthermore, I suspect it would be an kernel issue, not a xorp issue. If you can provide more details on what you are trying to accomplish we may be able to offer better suggestions. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From juarez.paulino at gmail.com Mon Jul 19 10:57:29 2010 From: juarez.paulino at gmail.com (Juarez Paulino) Date: Mon, 19 Jul 2010 14:57:29 -0300 Subject: [Xorp-users] Report: XORP-CT cross-compilation with PPC In-Reply-To: References: <4C4070A3.1050404@candelatech.com> Message-ID: I have attached the git diff for the entire project environment. There are some archives that we just change to apply debugging info. The main changes are those from my old message. -- Juarez Paulino On Sat, Jul 17, 2010 at 3:51 PM, Juarez Paulino wrote: > Sorry for lately replying, I was confirming some of the answers... > > > Unfortunately I think I will only be able to execute "git diff" on Monday > as I'm not going to lab this weekend. > > I don't have the original builder virtual machine with our XORP SConstruct > file here... > > > > > I used syntax like this when cross-compiling to ARM. Could you try this > and see if it works? > > > It seems to work now. Sorry for that... > > I think that other commands were not doing well due to a bad library > LINKFLAGS specification. Our toolchain was initially trying to link with an > old libpcap that didn't have send_packet() function. We just cross-compiled > a new libpcap version and replaced it on toolchain. > > > > >Can you give me some details on the OSPF issue? I don't understand what > you wrote above. > > We were initially trying to use xorp without OSPF module on a PIM-SSM > environment. So we disabled things like static RP or bootstrap options. > > We statically defined routes on the closed environment system giving them > some "hand-write" metrics. > > When we executed the xorp_rtmgr on our config (IGMP, PIM, FIB2MRIB), it > seems that xorp got lost since it recognized the path from client nodes with > higher metrics rather than the smaller one. So it constructed an undesirable > tree from SSM requirements point of view. > > Maybe it's just a weak configuration of xorp config file. We got it really > simple. I have attached our final working (whith OSPF) simple config file on > this message. If we remove the OSPF configuration, XORP doesn't understand > the system static metrics. > > > > > What is your goal for size? > > We have to take it on less possible space. I think something ~5MB would be > fine. > > By simple examining the lib dir on xorp install path, I realized that what > is most space-used is what we really need on multicast task. Do you think > STL could be a space bottleneck on this case? > > I'll try following your other tips on IPv6 and libxipc batch code. If I > manage to get it, I'll post my patches. > > > > On Fri, Jul 16, 2010 at 11:45 AM, Ben Greear wrote: > >> On 07/16/2010 05:33 AM, Juarez Paulino wrote: >> >>> I think my previous mail didn't get into the list because I have used >>> some formatting. >>> >>> So here comes a copy... I hope it can helps someone. >>> >> >> Thanks for the detailed email! >> >> If it's not too much trouble, can you send the changes as a diff? >> >> git diff > /tmp/foo.patch >> >> If the list won't take it, send directly to me. >> >> >> I think some of these can be rolled in as is, and I can add some >> compile-time args to deal with things like endian-ness checks. >> >> I have a few more comments inline below: >> >> >> > Our buildroot toolchain already had all of them. >>> > >>> > >>> > 2) Merging cross-compilation environment on SConstruct: >>> > >>> > We couldn't get SCons to work with previous export/guest/build >>> options like: >>> > >>> > $ export >>> CC=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc \ >>> > export >>> CXX=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++ \ >>> > export >>> RANLIB=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib >>> \ >>> > scons \ >>> > # :( dont work yet... >>> > >>> > or: >>> > >>> > $ export >>> CC=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc \ >>> > export >>> CXX=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++ \ >>> > export >>> RANLIB=/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib >>> \ >>> > scons build=i686-pc-linux-gnu host=powerpc-83xx-linux-uclibc >>> > # :P dont work either... >>> >> >> I used syntax like this when cross-compiling to ARM. Could you try this >> and see if it works? If not, plz send me the output of the failed >> attempt. Replace my paths with your tools, and change build= >> accordingly. >> >> scons build=arm-unknown-linux-gnu \ >> >> STRIP=${HOME}/x-tools/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-sstrip >> \ >> >> CC=${HOME}/x-tools/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc >> \ >> >> CXX=${HOME}/x-tools/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-g++ >> \ >> CFLAGS=-I${HOME}/x-tools/arm-unknown-linux-gnueabi/local/include \ >> CXXFLAGS=-I${HOME}/x-tools/arm-unknown-linux-gnueabi/local/include \ >> LINKFLAGS=-L${HOME}/x-tools/arm-unknown-linux-gnueabi/local/lib >> >> >> >> > 3) Eliminating Endianess problem >>> > >>> > After some terrible hours of debugging, we managed to cross-compile >>> XORP-CT and not to get the endianess problem on FEA sockets. Our PowerPC >>> machine uses BIG_ENDIAN, but our host cross-compilation machine uses >>> LITTLE_ENDIAN, so endianess-check get wrong parameters when looking for >>> it. >>> > >>> > Maybe there is some better ways, but we find it easy to "brute >>> define" things by hand to get xorp_config.h correctly identify endianess. >>> >> >> I'll look into this check when I get some time. If it could use the >> (cross)-compiler to do the checks, it should be able to work properly >> regardless >> of cross-compiling or not. >> >> >> ============================================================================== >>> > >>> > >>> > - With these modifications, we got XORP-CT top-of-tree Ben version to >>> cross-compile and works fine with PIM module on PPC machine. >>> > >>> > - We've tested XORP-CT restricted space versions (only with PIM >>> module and necessary) and it seems to work fine too on our SSM >>> environment. >>> > >>> > - Our last stripped working version got around ~9.6MB space: >>> > >>> > sudo scons -j4 disable_ipv6=yes disable_fw=yes >>> disable_warninglogs=yes disable_tracelogs=yes disable_fatallogs=yes >>> disable_infologs=yes disable_assertlogs=yes disable_errorlogs=yes >>> enable_olsr=no enable_bgp=no enable_vrrp=no enable_policy=no >>> enable_rip=no optimize=size enable_fea_dummy=no enable_xorpsh=no >>> disable_profile=yes >>> > >>> > * We had to enable and configure OSPF module too, as xorp can >>> recognize (i think it inverts) the system metrics... >>> >> >> Can you give me some details on the OSPF issue? I don't understand >> what you wrote above. >> >> >> > Our next work and probably most difficult is to reduce more our XORP >>> version. >>> > >>> > So do you have any tips beyond Ben PATCHES (on getting out modules, >>> xorpsh and IPv6 code) from where we could begin? >>> >> >> What is your goal for size? >> >> There is probably some more ipv6 code that can be eliminated from >> the core libraries and such. If you go this route, please do >> it in smaller chunks if possible and send me patches for each chunk. >> >> There may be tools that can help determine what is taking up >> the space in files (code, data, etc)..that might help narrow down >> things to look for. >> >> There is also some 'dead' code in xorp still. In particular, I >> have been meaning to remove the 'batch' logic from the libxipc >> logic. It's not used by any code. Not sure if it will save >> much space though. >> >> >> Thanks, >> Ben >> >> >> -- >> Ben Greear >> Candela Technologies Inc http://www.candelatech.com >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100719/c1502948/attachment-0001.html -------------- next part -------------- user at buildmachine:~/programs/xorp/xorp.ct$ git diff diff --git a/xorp/SConstruct b/xorp/SConstruct index 43346c3..d422a0a 100644 --- a/xorp/SConstruct +++ b/xorp/SConstruct @@ -135,12 +135,20 @@ if build_alias == None: build_alias = tgt_guess() build = tgt_canonicalize(build_alias) (build_cpu, build_vendor, build_os) = build.split('-', 2) +build = 'i686-pc-linux-gnu' #Spider: edited here, don't use ./config.guess on build machine +build_cpu = 'i686' +build_vendor = 'pc' +build_os = 'linux-gnu' host_alias = ARGUMENTS.get('host', None) if host_alias == None: host_alias = build_alias host = tgt_canonicalize(host_alias) (host_cpu, host_vendor, host_os) = host.split('-', 2) +host = 'powerpc-83xx-linux-uclibc' #Spider: edited here, Crosscompiling +host_cpu = 'powerpc' +host_vendor = '83xx' +host_os = 'linux-uclibc' sourcedir=Dir(".").abspath @@ -174,11 +182,28 @@ env = Environment( ENV = os.environ, BUILDDIR = builddir, CPPPATH=['$BUILDDIR'], - LIBPATH=['usr/lib'], + LIBPATH=['$BUILDDIR'], variables = vars) prefix = env['prefix'] +#Spider: edited here +#Extreme zealous environment +env['AR'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ar' +env['AS'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-as' +env['CC'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-gcc' +env['CXX'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-g++' +env['LD'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ld' +env['LDCONFIG'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ldconfig' +env['LDD'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ldd' +env['NM'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-nm' +env['OBJCOPY'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-objcopy' +env['OBJDUMP'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-objdump' +env['RANLIB'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-ranlib' +env['STRIP'] = '/opt/ppc83xx-linux-uclibc/usr/bin/powerpc-83xx-linux-uclibc-strip' + +#Spider: ended edit + print 'Build System Type: ', build print 'Host System Type: ', host print 'Source path: ', sourcedir @@ -523,7 +548,7 @@ if not env.GetOption('clean') and \ my_custom_tests = { 'CheckBoost' : CheckBoost, 'CheckBoostLibrary' : CheckBoostLibrary, - 'CheckEndianness' : CheckEndianness, + # 'CheckEndianness' : CheckEndianness, 'CheckTypeMember' : CheckTypeMember, 'CheckSysctl' : CheckSysctl } @@ -535,6 +560,9 @@ if not env.GetOption('clean') and \ ########## # target os + # Juarez: Definition of the endianess by force + conf.Define('WORDS_BIGENDIAN') + # friendly name of target osname = host_os if fnmatch.fnmatch(host_os, 'freebsd*'): diff --git a/xorp/fea/data_plane/io/io_ip_socket.cc b/xorp/fea/data_plane/io/io_ip_socket.cc old mode 100644 new mode 100755 index f66e1b8..bb4d3ad --- a/xorp/fea/data_plane/io/io_ip_socket.cc +++ b/xorp/fea/data_plane/io/io_ip_socket.cc @@ -1427,33 +1427,37 @@ IoIpSocket::proto_socket_read(XorpFd fd, IoEventType type) is_datalen_error = false; do { if (ip_hdr_len + ip_data_len == static_cast(nbytes)) { - is_datalen_error = false; - break; // OK + is_datalen_error = false; + puts(">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1431"); + break; // OK } if (nbytes < static_cast(ip_hdr_len)) { - is_datalen_error = true; - break; + is_datalen_error = true; + puts(">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1436"); + break; } if (ip4.ip_p() == IPPROTO_PIM) { - if (nbytes < static_cast(ip_hdr_len + PIM_REG_MINLEN)) { - is_datalen_error = true; - break; - } - struct pim pim; - memcpy(&pim, ip4.data() + ip_hdr_len, sizeof(pim)); - if (PIM_VT_T(pim.pim_vt) != PIM_REGISTER) { - is_datalen_error = true; - break; - } - // - // XXX: the *BSD kernel might truncate the encapsulated data - // in PIM Register messages before passing the message up - // to user level. The reason for the truncation is to reduce - // the bandwidth overhead, but the price for this is - // messages with weird IP header. Sigh... - // - is_datalen_error = false; - break; + if (nbytes < static_cast(ip_hdr_len + PIM_REG_MINLEN)) { + is_datalen_error = true; + puts(">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1442"); + break; + } + struct pim pim; + memcpy(&pim, ip4.data() + ip_hdr_len, sizeof(pim)); + if (PIM_VT_T(pim.pim_vt) != PIM_REGISTER) { + is_datalen_error = true; + puts(">>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1449"); + break; + } + // + // XXX: the *BSD kernel might truncate the encapsulated data + // in PIM Register messages before passing the message up + // to user level. The reason for the truncation is to reduce + // the bandwidth overhead, but the price for this is + // messages with weird IP header. Sigh... + // + is_datalen_error = false; + break; } break; } while (false); diff --git a/xorp/libxorp/xlog.c b/xorp/libxorp/xlog.c index 9963366..fed6288 100644 --- a/xorp/libxorp/xlog.c +++ b/xorp/libxorp/xlog.c @@ -1030,9 +1030,9 @@ int xlog_add_default_output(void) { const char* defaults[] = { /* The default outputs (in preference order) */ - "/dev/stderr", /* XXX: temporary this is the default */ - "/dev/console", - "/dev/stdout" + "/mnt/pendrive_1/stderr.txt", /* XXX: temporary this is the default */ + "/mnt/pendrive_1/console.txt", + "/mnt/pendrive_1/stdout.txt" }; size_t ndefaults = sizeof(defaults) / sizeof(defaults[0]); size_t i; diff --git a/xorp/site_scons/config/allconfig.py b/xorp/site_scons/config/allconfig.py old mode 100644 new mode 100755 index ed16660..4c1c5d0 --- a/xorp/site_scons/config/allconfig.py +++ b/xorp/site_scons/config/allconfig.py @@ -34,7 +34,8 @@ def DoAllConfig(env, conf, host_os): ########## # endian # XXX Wot about cross compilation?? - conf.CheckEndianness() + # Pedro: Disable endianness check for cross compilition success + # conf.CheckEndianness() ########## # c99 @@ -200,7 +201,8 @@ def DoAllConfig(env, conf, host_os): conf.Define('HAVE_TCPUDP_UNIX_SOCKETS') if has_af_inet and has_sock_raw: conf.Define('HAVE_IP_RAW_SOCKETS') - if host_os == 'linux-gnu' or host_os == 'openbsd': + # Pedro: adding the nrx router libc in the if test + if host_os == 'linux-gnu' or host_os == 'openbsd' or host_os == 'linux-uclibc': conf.Define('IPV4_RAW_OUTPUT_IS_RAW') conf.Define('IPV4_RAW_INPUT_IS_RAW') From manohar at copperheadsystems.com Tue Jul 20 21:35:47 2010 From: manohar at copperheadsystems.com (manohar at copperheadsystems.com) Date: Tue, 20 Jul 2010 22:35:47 -0600 Subject: [Xorp-users] Re : Unable to update RIP statistics Message-ID: <9ccaf00bcda5acf83892b89204e7a4fa.squirrel@mail.copperheadsystems.com> Hi all I have configured rip in 2 machines using Xorp in individual machine .I am able to capture the packets but am unable to see the update in XORP_RIP_STATISTICS . Thanks Manohar From greearb at candelatech.com Wed Jul 21 11:29:14 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 21 Jul 2010 11:29:14 -0700 Subject: [Xorp-users] Report: XORP-CT cross-compilation with PPC In-Reply-To: References: <4C4070A3.1050404@candelatech.com> Message-ID: <4C473C7A.5040808@candelatech.com> On 07/19/2010 10:57 AM, Juarez Paulino wrote: > I have attached the git diff for the entire project environment. > > There are some archives that we just change to apply debugging info. > > The main changes are those from my old message. Thanks...it's likely going to be a few days before I can get to this..trying to track down some tricky problem in our virtual-router stuff (doesn't appear to be Xorp related...) Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Wed Jul 28 11:42:30 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 28 Jul 2010 20:42:30 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process Message-ID: <08653524-E882-440F-BDF5-63B40FB4483A@spacebugs.nl> Hello list., Maybe someone here can help me out on the following issue. I'm working on it now for a couple weeks to get this solved, but I can't find a solution. I'm using xorp version 1.06 on FreeBSD 8.0 (AMD64). xorp is running inside vimages. When I start xorp I receive the following messages: [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +527 fibconfig_entry_set_routing_socket.cc delete_entry ] Error writing to routing socket: No such process [ 2010/07/28 20:03:37 ERROR xorp_rib:2208 RIB +916 redist_xrl.cc dispatch_complete ] Failed to commit transaction: 102 Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +80 fibconfig_transaction.cc operation_result ] FIB transaction commit failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2010/07/28 20:03:37 WARNING xorp_fea XrlFeaTarget ] Handling method for redist_transaction4/0.1/commit_transaction failed: XrlCmdError 102 Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false The route table looks like: beheer at router1> show route table ipv4 unicast final 0.0.0.0/0 [static(1)/1] > to 172.19.0.2 via epair4a/epair4a 10.0.0.0/24 [connected(0)/0] > via epair1a/epair1a 10.1.0.0/24 [connected(0)/0] > via epair3a/epair3a 172.19.0.0/30 [connected(0)/0] > via epair4a/epair4a Interface information: beheer at router1> show interfaces epair1a/epair1a: Flags: mtu 1500 speed unknown inet 10.0.0.1 subnet 10.0.0.0/24 broadcast 10.0.0.255 physical index 2 ether 02:ca:d0:00:05:0a epair3a/epair3a: Flags: mtu 1500 speed unknown inet 10.1.0.1 subnet 10.1.0.0/24 broadcast 10.1.0.255 physical index 3 ether 02:ca:cb:00:05:0a epair4a/epair4a: Flags: mtu 1500 speed unknown inet 172.19.0.1 subnet 172.19.0.0/30 broadcast 172.19.0.3 physical index 4 ether 02:ca:d0:00:05:0a The config file I'm using: /*XORP Configuration File, v1.0*/ protocols { ospf4 { router-id: 10.0.0.1 rfc1583-compatibility: false ip-router-alert: false area 0.0.0.0 { area-type: "normal" interface epair1a { link-type: "broadcast" vif epair1a { address 10.0.0.1 { priority: 128 hello-interval: 10 router-dead-interval: 40 interface-cost: 1 retransmit-interval: 5 transit-delay: 1 disable: false } } } interface epair3a { link-type: "broadcast" vif epair3a { address 10.1.0.1 { priority: 128 hello-interval: 10 router-dead-interval: 40 interface-cost: 1 retransmit-interval: 5 transit-delay: 1 disable: false } } } } export: "red-static-rt" } static { disable: false route 0.0.0.0/0 { next-hop: 172.19.0.2 metric: 1 } } } policy { policy-statement "red-static-rt" { term a { from { protocol: "static" } then { accept { } reject { } } } } } fea { unicast-forwarding4 { disable: false } } interfaces { restore-original-config-on-shutdown: false interface epair1a { description: "" disable: false discard: false unreachable: false management: false vif epair1a { disable: false address 10.0.0.1 { prefix-length: 24 broadcast: 10.0.0.255 disable: false } } } interface epair3a { description: "" disable: false discard: false unreachable: false management: false vif epair3a { disable: false address 10.1.0.1 { prefix-length: 24 disable: false } } } interface epair4a { description: "" disable: false discard: false unreachable: false management: false vif epair4a { disable: false address 172.19.0.1 { prefix-length: 30 disable: false } } } } rtrmgr { config-directory: "/root/chaos/vrd/edwin/router1/boot" load-file-command: "/root/chaos/vrd/edwin/router1/boot/config.boot" load-file-command-args: "-o" load-ftp-command: "fetch" load-ftp-command-args: "-o" load-http-command: "fetch" load-http-command-args: "-o" load-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" load-tftp-command-args: "" save-file-command: "/root/chaos/vrd/edwin/router1/boot/config.boot" save-file-command-args: "" save-ftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" save-ftp-command-args: "" save-http-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" save-http-command-args: "" save-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" save-tftp-command-args: "" } The vimages are started with the following options: sysctl net.inet.ip.forwarding=1 sysctl security.jail.allow_raw_sockets=1 I seems that the error messages appear when I apply the policy. What can I do to solve the error messages ? Hades From greearb at candelatech.com Wed Jul 28 11:56:27 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 28 Jul 2010 11:56:27 -0700 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <08653524-E882-440F-BDF5-63B40FB4483A@spacebugs.nl> References: <08653524-E882-440F-BDF5-63B40FB4483A@spacebugs.nl> Message-ID: <4C507D5B.70104@candelatech.com> On 07/28/2010 11:42 AM, Edwin Schokkenbroek wrote: > Hello list., > > Maybe someone here can help me out on the following issue. I'm working on it now for a couple weeks to get this solved, but I can't find a solution. > > I'm using xorp version 1.06 on FreeBSD 8.0 (AMD64). Any chance you could try the latest xorp.ct top-of-tree: http://github.com/greearb/xorp.ct I'll attempt to fix the bug if you can reproduce it there, though I don't have any BSD systems so I'm not sure how much luck I'd have. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From peirce at maine.edu Wed Jul 28 12:15:20 2010 From: peirce at maine.edu (Garry Peirce) Date: Wed, 28 Jul 2010 15:15:20 -0400 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <08653524-E882-440F-BDF5-63B40FB4483A@spacebugs.nl> References: <08653524-E882-440F-BDF5-63B40FB4483A@spacebugs.nl> Message-ID: <096401cb2e89$385e9130$a91bb390$@edu> Not sure I understand your policy statement - I assume you desire to accept static routes. Do you actually mean the following? > term a { > from { > protocol: "static" > } > then { > accept { > } > } > } > then { > reject { > } > } > -----Original Message----- > From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] > On Behalf Of Edwin Schokkenbroek > Sent: Wednesday, July 28, 2010 2:43 PM > To: xorp-users at xorp.org > Subject: [Xorp-users] Error writing to routing socket: No such process > > Hello list., > > Maybe someone here can help me out on the following issue. I'm working > on it now for a couple weeks to get this solved, but I can't find a > solution. > > I'm using xorp version 1.06 on FreeBSD 8.0 (AMD64). > xorp is running inside vimages. When I start xorp I receive the > following messages: > > [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +527 > fibconfig_entry_set_routing_socket.cc delete_entry ] Error writing to > routing socket: No such process > [ 2010/07/28 20:03:37 ERROR xorp_rib:2208 RIB +916 redist_xrl.cc > dispatch_complete ] Failed to commit transaction: 102 Command failed > DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a > vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true > is_deleted = false is_unresolved = false is_connected_route = false > [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +80 > fibconfig_transaction.cc operation_result ] FIB transaction commit > failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = > epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = > true is_deleted = false is_unresolved = false is_connected_route = > false > [ 2010/07/28 20:03:37 WARNING xorp_fea XrlFeaTarget ] Handling method > for redist_transaction4/0.1/commit_transaction failed: XrlCmdError 102 > Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 > ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 > xorp_route = true is_deleted = false is_unresolved = false > is_connected_route = false > > The route table looks like: > > beheer at router1> show route table ipv4 unicast final > 0.0.0.0/0 [static(1)/1] > > to 172.19.0.2 via epair4a/epair4a > 10.0.0.0/24 [connected(0)/0] > > via epair1a/epair1a > 10.1.0.0/24 [connected(0)/0] > > via epair3a/epair3a > 172.19.0.0/30 [connected(0)/0] > > via epair4a/epair4a > > Interface information: > > beheer at router1> show interfaces > epair1a/epair1a: Flags: mtu 1500 speed > unknown > inet 10.0.0.1 subnet 10.0.0.0/24 broadcast 10.0.0.255 > physical index 2 > ether 02:ca:d0:00:05:0a > epair3a/epair3a: Flags: mtu 1500 speed > unknown > inet 10.1.0.1 subnet 10.1.0.0/24 broadcast 10.1.0.255 > physical index 3 > ether 02:ca:cb:00:05:0a > epair4a/epair4a: Flags: mtu 1500 speed > unknown > inet 172.19.0.1 subnet 172.19.0.0/30 broadcast 172.19.0.3 > physical index 4 > ether 02:ca:d0:00:05:0a > > The config file I'm using: > > /*XORP Configuration File, v1.0*/ > protocols { > ospf4 { > router-id: 10.0.0.1 > rfc1583-compatibility: false > ip-router-alert: false > area 0.0.0.0 { > area-type: "normal" > interface epair1a { > link-type: "broadcast" > vif epair1a { > address 10.0.0.1 { > priority: 128 > hello-interval: 10 > router-dead-interval: 40 > interface-cost: 1 > retransmit-interval: 5 > transit-delay: 1 > disable: false > } > } > } > interface epair3a { > link-type: "broadcast" > vif epair3a { > address 10.1.0.1 { > priority: 128 > hello-interval: 10 > router-dead-interval: 40 > interface-cost: 1 > retransmit-interval: 5 > transit-delay: 1 > disable: false > } > } > } > } > export: "red-static-rt" > } > static { > disable: false > route 0.0.0.0/0 { > next-hop: 172.19.0.2 > metric: 1 > } > } > } > policy { > policy-statement "red-static-rt" { > term a { > from { > protocol: "static" > } > then { > accept { > } > reject { > } > } > } > } > } > fea { > unicast-forwarding4 { > disable: false > } > } > interfaces { > restore-original-config-on-shutdown: false > interface epair1a { > description: "" > disable: false > discard: false > unreachable: false > management: false > vif epair1a { > disable: false > address 10.0.0.1 { > prefix-length: 24 > broadcast: 10.0.0.255 > disable: false > } > } > } > interface epair3a { > description: "" > disable: false > discard: false > unreachable: false > management: false > vif epair3a { > disable: false > address 10.1.0.1 { > prefix-length: 24 > disable: false > } > } > } > interface epair4a { > description: "" > disable: false > discard: false > unreachable: false > management: false > vif epair4a { > disable: false > address 172.19.0.1 { > prefix-length: 30 > disable: false > } > } > } > } > rtrmgr { > config-directory: "/root/chaos/vrd/edwin/router1/boot" > load-file-command: "/root/chaos/vrd/edwin/router1/boot/config.boot" > load-file-command-args: "-o" > load-ftp-command: "fetch" > load-ftp-command-args: "-o" > load-http-command: "fetch" > load-http-command-args: "-o" > load-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" > load-tftp-command-args: "" > save-file-command: "/root/chaos/vrd/edwin/router1/boot/config.boot" > save-file-command-args: "" > save-ftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" > save-ftp-command-args: "" > save-http-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" > save-http-command-args: "" > save-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" > save-tftp-command-args: "" > } > > > The vimages are started with the following options: > > sysctl net.inet.ip.forwarding=1 > sysctl security.jail.allow_raw_sockets=1 > > > I seems that the error messages appear when I apply the policy. What > can I do to solve the error messages ? > > > > > > Hades > > > > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users From edwin at spacebugs.nl Wed Jul 28 12:18:30 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 28 Jul 2010 21:18:30 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process Message-ID: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> Hello Ben, Thank you for your quick response. I already started to experiment with xopr.ct. I ran into it when trying to solve the errors mentioned earlier. I compile xorp.ct (1.8) And when I start it I receive messages like: ssion denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.cwKcRV" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.POm5vR. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.POm5vR [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.cwKcRV" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.POm5vR. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.POm5vR [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.cwKcRV" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.POm5vR. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.POm5vR [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.cwKcRV" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.POm5vR. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.POm5vR [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.cwKcRV" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.POm5vR. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.POm5vR [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.cwKcRV" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.POm5vR. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.POm5vR [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV (These messages are going on forever.) The message is clear, and easy to explain, xorp_rtrmgr is started as the root user. However I start the xorpsh as a other user with less privileges. When I change the ownership of the file in /var/tmp I'm able to login. But when I reboot the machine or I start another vimage (or jail with vnet ) I ran into the same problem again. I guess xorp_rtrmgr is creating the files as root. Since the messages appear very quickly I'm not able to see the messages when xorp_rtrmgr is started. Edwin From edwin at spacebugs.nl Wed Jul 28 12:23:30 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 28 Jul 2010 21:23:30 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <096401cb2e89$385e9130$a91bb390$@edu> References: <08653524-E882-440F-BDF5-63B40FB4483A@spacebugs.nl> <096401cb2e89$385e9130$a91bb390$@edu> Message-ID: Hello Garry, The goal is to export static routes into OSPF. I normally work with Juniper routers and in junos policies are used to redistribute routes. So I figured this is the same in Xorp. Or isn't this the way to do it in Xorp ? Edwin On Jul 28, 2010, at 9:15 PM, Garry Peirce wrote: > Not sure I understand your policy statement - I assume you desire to accept > static routes. > Do you actually mean the following? > >> term a { >> from { >> protocol: "static" >> } >> then { >> accept { >> } >> } >> } >> then { >> reject { >> } >> } > > > >> -----Original Message----- >> From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] >> On Behalf Of Edwin Schokkenbroek >> Sent: Wednesday, July 28, 2010 2:43 PM >> To: xorp-users at xorp.org >> Subject: [Xorp-users] Error writing to routing socket: No such process >> >> Hello list., >> >> Maybe someone here can help me out on the following issue. I'm working >> on it now for a couple weeks to get this solved, but I can't find a >> solution. >> >> I'm using xorp version 1.06 on FreeBSD 8.0 (AMD64). >> xorp is running inside vimages. When I start xorp I receive the >> following messages: >> >> [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +527 >> fibconfig_entry_set_routing_socket.cc delete_entry ] Error writing to >> routing socket: No such process >> [ 2010/07/28 20:03:37 ERROR xorp_rib:2208 RIB +916 redist_xrl.cc >> dispatch_complete ] Failed to commit transaction: 102 Command failed >> DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a >> vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true >> is_deleted = false is_unresolved = false is_connected_route = false >> [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +80 >> fibconfig_transaction.cc operation_result ] FIB transaction commit >> failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = >> epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = >> true is_deleted = false is_unresolved = false is_connected_route = >> false >> [ 2010/07/28 20:03:37 WARNING xorp_fea XrlFeaTarget ] Handling method >> for redist_transaction4/0.1/commit_transaction failed: XrlCmdError 102 >> Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 >> ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 >> xorp_route = true is_deleted = false is_unresolved = false >> is_connected_route = false >> >> The route table looks like: >> >> beheer at router1> show route table ipv4 unicast final >> 0.0.0.0/0 [static(1)/1] >>> to 172.19.0.2 via epair4a/epair4a >> 10.0.0.0/24 [connected(0)/0] >>> via epair1a/epair1a >> 10.1.0.0/24 [connected(0)/0] >>> via epair3a/epair3a >> 172.19.0.0/30 [connected(0)/0] >>> via epair4a/epair4a >> >> Interface information: >> >> beheer at router1> show interfaces >> epair1a/epair1a: Flags: mtu 1500 speed >> unknown >> inet 10.0.0.1 subnet 10.0.0.0/24 broadcast 10.0.0.255 >> physical index 2 >> ether 02:ca:d0:00:05:0a >> epair3a/epair3a: Flags: mtu 1500 speed >> unknown >> inet 10.1.0.1 subnet 10.1.0.0/24 broadcast 10.1.0.255 >> physical index 3 >> ether 02:ca:cb:00:05:0a >> epair4a/epair4a: Flags: mtu 1500 speed >> unknown >> inet 172.19.0.1 subnet 172.19.0.0/30 broadcast 172.19.0.3 >> physical index 4 >> ether 02:ca:d0:00:05:0a >> >> The config file I'm using: >> >> /*XORP Configuration File, v1.0*/ >> protocols { >> ospf4 { >> router-id: 10.0.0.1 >> rfc1583-compatibility: false >> ip-router-alert: false >> area 0.0.0.0 { >> area-type: "normal" >> interface epair1a { >> link-type: "broadcast" >> vif epair1a { >> address 10.0.0.1 { >> priority: 128 >> hello-interval: 10 >> router-dead-interval: 40 >> interface-cost: 1 >> retransmit-interval: 5 >> transit-delay: 1 >> disable: false >> } >> } >> } >> interface epair3a { >> link-type: "broadcast" >> vif epair3a { >> address 10.1.0.1 { >> priority: 128 >> hello-interval: 10 >> router-dead-interval: 40 >> interface-cost: 1 >> retransmit-interval: 5 >> transit-delay: 1 >> disable: false >> } >> } >> } >> } >> export: "red-static-rt" >> } >> static { >> disable: false >> route 0.0.0.0/0 { >> next-hop: 172.19.0.2 >> metric: 1 >> } >> } >> } >> policy { >> policy-statement "red-static-rt" { >> term a { >> from { >> protocol: "static" >> } >> then { >> accept { >> } >> reject { >> } >> } >> } >> } >> } >> fea { >> unicast-forwarding4 { >> disable: false >> } >> } >> interfaces { >> restore-original-config-on-shutdown: false >> interface epair1a { >> description: "" >> disable: false >> discard: false >> unreachable: false >> management: false >> vif epair1a { >> disable: false >> address 10.0.0.1 { >> prefix-length: 24 >> broadcast: 10.0.0.255 >> disable: false >> } >> } >> } >> interface epair3a { >> description: "" >> disable: false >> discard: false >> unreachable: false >> management: false >> vif epair3a { >> disable: false >> address 10.1.0.1 { >> prefix-length: 24 >> disable: false >> } >> } >> } >> interface epair4a { >> description: "" >> disable: false >> discard: false >> unreachable: false >> management: false >> vif epair4a { >> disable: false >> address 172.19.0.1 { >> prefix-length: 30 >> disable: false >> } >> } >> } >> } >> rtrmgr { >> config-directory: "/root/chaos/vrd/edwin/router1/boot" >> load-file-command: "/root/chaos/vrd/edwin/router1/boot/config.boot" >> load-file-command-args: "-o" >> load-ftp-command: "fetch" >> load-ftp-command-args: "-o" >> load-http-command: "fetch" >> load-http-command-args: "-o" >> load-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" >> load-tftp-command-args: "" >> save-file-command: "/root/chaos/vrd/edwin/router1/boot/config.boot" >> save-file-command-args: "" >> save-ftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" >> save-ftp-command-args: "" >> save-http-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" >> save-http-command-args: "" >> save-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" >> save-tftp-command-args: "" >> } >> >> >> The vimages are started with the following options: >> >> sysctl net.inet.ip.forwarding=1 >> sysctl security.jail.allow_raw_sockets=1 >> >> >> I seems that the error messages appear when I apply the policy. What >> can I do to solve the error messages ? >> >> >> >> >> >> Hades >> >> >> >> >> >> >> _______________________________________________ >> Xorp-users mailing list >> Xorp-users at xorp.org >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > Edwin Schokkenbroek edwin at spacebugs.nl Engineers are full of great ideas. Making things better is what we're built to do. However, when it comes to engineers, there seems to be an inverse relationship between great ideas and great communication skills. This is what gets us into trouble. From greearb at candelatech.com Wed Jul 28 12:35:44 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 28 Jul 2010 12:35:44 -0700 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> References: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> Message-ID: <4C508690.9080803@candelatech.com> On 07/28/2010 12:18 PM, Edwin Schokkenbroek wrote: > Hello Ben, > > Thank you for your quick response. I already started to experiment with xopr.ct. I ran into it when trying to solve the errors mentioned earlier. > > 010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" > [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied > [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV > > (These messages are going on forever.) > > The message is clear, and easy to explain, xorp_rtrmgr is started as the root user. However I start the xorpsh as a other user with less privileges. > When I change the ownership of the file in /var/tmp I'm able to login. > > But when I reboot the machine or I start another vimage (or jail with vnet ) I ran into the same problem again. I guess xorp_rtrmgr is creating the files as root. > > Since the messages appear very quickly I'm not able to see the messages when xorp_rtrmgr is started. I could add an option to create the /var/tmp/ file as read/write by everyone (or maybe just the xorp group), I suppose. One thing I just noticed: I have 126,000 or so xrl files in /var/tmp/ on one of my test machines. That can't be good :P Aside from the permissions issue, does xorp.ct fix that other bug you reported? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Wed Jul 28 12:44:04 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 28 Jul 2010 21:44:04 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <4C508690.9080803@candelatech.com> References: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> <4C508690.9080803@candelatech.com> Message-ID: On Jul 28, 2010, at 9:35 PM, Ben Greear wrote: > On 07/28/2010 12:18 PM, Edwin Schokkenbroek wrote: >> Hello Ben, >> >> Thank you for your quick response. I already started to experiment with xopr.ct. I ran into it when trying to solve the errors mentioned earlier. >> >> 010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" >> [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied >> [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV >> >> (These messages are going on forever.) >> >> The message is clear, and easy to explain, xorp_rtrmgr is started as the root user. However I start the xorpsh as a other user with less privileges. >> When I change the ownership of the file in /var/tmp I'm able to login. >> >> But when I reboot the machine or I start another vimage (or jail with vnet ) I ran into the same problem again. I guess xorp_rtrmgr is creating the files as root. >> >> Since the messages appear very quickly I'm not able to see the messages when xorp_rtrmgr is started. > > I could add an option to create the /var/tmp/ file as read/write by everyone (or maybe > just the xorp group), I suppose. I think a xorp group is the most clean way . read/write everyone could maybe introduce a security issue ? The dir /var/tmp is already world writeable permissions (on my system): drwxrwxrwt 3 beheer wheel 2048 Jul 28 21:27 /var/tmp/ > > One thing I just noticed: I have 126,000 or so xrl files in /var/tmp/ > on one of my test machines. > > That can't be good :P Nope.... hopefully the filesystem has enough inodes ;-) > > Aside from the permissions issue, does xorp.ct fix that other bug you reported? Well I managed to start one xopr_rtmgr in a vimage, however the other xorp_rtr_mgr seems to hang. I recieve a lot of messages : Not doing pidfile... [ 2010/07/28 21:26:48.671719 INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/master_conf_tree.cc:234 execute ] Changed modules: interfaces, rtrmgr, firewall, fea, rib, policy, ospf4 [ 2010/07/28 21:26:48.673113 WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/module_command.cc:327 startup_validation ] WARNING: Using DelayValidation, module_name: rtrmgr [ 2010/07/28 21:26:48.673178 WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/module_command.cc:348 config_validation ] WARNING: Using DelayValidation, module_name: rtrmgr [ 2010/07/28 21:26:48.673971 WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/module_command.cc:369 ready_validation ] WARNING: Using DelayValidation, module_name: rtrmgr [ 2010/07/28 21:26:48.674057 INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: interfaces (xorp_fea) [ 2010/07/28 21:26:48.678313 WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "fea" does not exist or is not enabled. [ 2010/07/28 21:26:48.679305 WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/28 21:26:49.710205 INFO xorp_fea:2274 MFEA fea/mfea_node.cc:317 enable ] MFEA enabled [ 2010/07/28 21:26:49.710685 INFO xorp_fea:2274 MFEA fea/mfea_node_cli.cc:126 enable ] CLI enabled [ 2010/07/28 21:26:49.712299 INFO xorp_fea:2274 MFEA fea/mfea_node_cli.cc:92 start ] CLI started [ 2010/07/28 21:26:49.712464 INFO xorp_fea:2274 MFEA fea/mfea_node.cc:317 enable ] MFEA enabled [ 2010/07/28 21:26:49.712543 INFO xorp_fea:2274 MFEA fea/mfea_node_cli.cc:126 enable ] CLI enabled [ 2010/07/28 21:26:49.713527 INFO xorp_fea:2274 MFEA fea/mfea_node_cli.cc:92 start ] CLI started [ 2010/07/28 21:26:49.751207 INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: rtrmgr () [ 2010/07/28 21:26:55.811914 INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: firewall (xorp_fea) [ 2010/07/28 21:26:55.815042 INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: fea (xorp_fea) [ 2010/07/28 21:26:55.815764 INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: rib (xorp_rib) [ 2010/07/28 21:26:55.828681 WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2010/07/28 21:26:55.829153 WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/28 21:26:56.865792 INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: policy (xorp_policy) [ 2010/07/28 21:26:56.868770 WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "policy" does not exist or is not enabled. [ 2010/07/28 21:26:56.869172 WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/28 21:26:57.905775 INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: ospf4 (xorp_ospfv2) [ 2010/07/28 21:26:57.908040 WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ospfv2" does not exist or is not enabled. [ 2010/07/28 21:26:57.908473 WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/28 21:27:24.210672 WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 20.414893 seconds [ 2010/07/28 21:27:24.210784 WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 18.395036 seconds [ 2010/07/28 21:27:24.210896 WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 17.345121 seconds [ 2010/07/28 21:27:24.211157 WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 16.305401 seconds [ 2010/07/28 21:27:24.211476 WARNING xorp_rtrmgr:2273 LIBXORP libxorp/timer.cc:426 expire_one ] Timer Expiry *much* later than scheduled: behind by 25.303181 seconds [ 2010/07/28 21:27:24.212195 WARNING xorp_rtrmgr:2273 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Xrl target is not enabled. [ 2010/07/28 21:27:24.212371 WARNING xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 1 max_retries: 30 [ 2010/07/28 21:27:24.389087 WARNING xorp_ospfv2:2277 OSPF ospf/xrl_io.cc:948 updates_made ] XrlIO::updates_made, _iftree: [ 2010/07/28 21:27:25.251905 WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:294 set_link_status ] Setting PeerOut link status to: 1 dbg: create_peer vif: epair3b/epair3b old-status: 0 [ 2010/07/28 21:27:25.251984 WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair3b/epair3b running: 0 status: 0 link-status: 1 [ 2010/07/28 21:27:25.260140 WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair3b/epair3b running: 0 status: 1 link-status: 1 [ 2010/07/28 21:27:25.260297 WARNING xorp_ospfv2:2277 OSPF ospf/xrl_io.cc:170 enable_interface_vif ] XRL-IO: Enable Interface epair3b Vif epair3b [ 2010/07/28 21:27:25.263083 WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:294 set_link_status ] Setting PeerOut link status to: 1 dbg: create_peer vif: epair2b/epair2b old-status: 0 [ 2010/07/28 21:27:25.263159 WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair2b/epair2b running: 0 status: 0 link-status: 1 [ 2010/07/28 21:27:25.271045 WARNING xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:230 IoIpSocket ] Registering with iftree: pushed-config [ 2010/07/28 21:27:25.272803 INFO xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair3b vif epair3b socket: 43 [ 2010/07/28 21:27:25.274128 WARNING xorp_ospfv2:2277 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair2b/epair2b running: 0 status: 1 link-status: 1 [ 2010/07/28 21:27:25.274128 WARNING xorp_ospfv2:2277 OSPF ospf/xrl_io.cc:170 enable_interface_vif ] XRL-IO: Enable Interface epair2b Vif epair2b [ 2010/07/28 21:27:25.274721 INFO xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair2b vif epair2b socket: 43 [ 2010/07/28 21:27:25.277490 INFO xorp_rtrmgr:2273 RTRMGR rtrmgr/task.cc:2242 run_task ] No more tasks to run Welcome to XORP on router3 beheer at router3> [ 2010/07/28 21:27:34.966123 INFO xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.6 on interface epair2b vif epair2b socket: 43 [ 2010/07/28 21:28:05.280182 INFO xorp_fea:2274 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.6 on interface epair3b vif epair3b socket: 43 Maybe I did something wrong installing xorp ? or is xorp.ct not compatible with the configuration file ? > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > Edwin Schokkenbroek edwin at spacebugs.nl Engineers are full of great ideas. Making things better is what we're built to do. However, when it comes to engineers, there seems to be an inverse relationship between great ideas and great communication skills. This is what gets us into trouble. From greearb at candelatech.com Wed Jul 28 12:54:56 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 28 Jul 2010 12:54:56 -0700 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: References: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> <4C508690.9080803@candelatech.com> Message-ID: <4C508B10.5070000@candelatech.com> On 07/28/2010 12:44 PM, Edwin Schokkenbroek wrote: > > On Jul 28, 2010, at 9:35 PM, Ben Greear wrote: > >> On 07/28/2010 12:18 PM, Edwin Schokkenbroek wrote: >>> Hello Ben, >>> >>> Thank you for your quick response. I already started to experiment with xopr.ct. I ran into it when trying to solve the errors mentioned earlier. >>> >>> 010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" >>> [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied >>> [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV >>> >>> (These messages are going on forever.) >>> >>> The message is clear, and easy to explain, xorp_rtrmgr is started as the root user. However I start the xorpsh as a other user with less privileges. >>> When I change the ownership of the file in /var/tmp I'm able to login. >>> >>> But when I reboot the machine or I start another vimage (or jail with vnet ) I ran into the same problem again. I guess xorp_rtrmgr is creating the files as root. >>> >>> Since the messages appear very quickly I'm not able to see the messages when xorp_rtrmgr is started. >> >> I could add an option to create the /var/tmp/ file as read/write by everyone (or maybe >> just the xorp group), I suppose. > > I think a xorp group is the most clean way . read/write everyone could maybe introduce a security issue ? > > The dir /var/tmp is already world writeable permissions (on my system): > > drwxrwxrwt 3 beheer wheel 2048 Jul 28 21:27 /var/tmp/ > >> >> One thing I just noticed: I have 126,000 or so xrl files in /var/tmp/ >> on one of my test machines. >> >> That can't be good :P > > Nope.... hopefully the filesystem has enough inodes ;-) >> >> Aside from the permissions issue, does xorp.ct fix that other bug you reported? > > Well I managed to start one xopr_rtmgr in a vimage, however the other xorp_rtr_mgr seems to hang. > > I recieve a lot of messages : The messages look OK to me (some seem scary, but I've been seeing them for years and they don't seem to cause harm, so I haven't bothered to track them down yet). The one issue that might be a problem is the timer expiry warnings, but if the system is slow/virtual, that might be normal and it will probably work better once all the processes are started. I don't know anything about vimages, but you might have to do some tricks to get two xorps to run on the same OS at the same time. If the vimage looks like a separate machine (like vmware, xemu, etc), then it should be OK. For the process that hangs, what makes you think so? Can you run 'strace' or whatever the BSD equiv is to see if it's really hung in a system call, or 'top' to see if it's spinning 100% CPU? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From peirce at maine.edu Wed Jul 28 13:06:07 2010 From: peirce at maine.edu (Garry Peirce) Date: Wed, 28 Jul 2010 16:06:07 -0400 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: References: <08653524-E882-440F-BDF5-63B40FB4483A@spacebugs.nl> <096401cb2e89$385e9130$a91bb390$@edu> Message-ID: <098801cb2e90$50f51b40$f2df51c0$@edu> Edwin, You can do what you desire, but your config includes both actions in the same THEN clause which I'm not sure xorp will like. I assume you want to accept statics and reject any others for which I would put the reject clause outside 'term a', either as 'term b' or as a final global action as I re-wrote it. You might see if re-writing that way results in different behavior. > -----Original Message----- > From: Edwin Schokkenbroek [mailto:edwin at spacebugs.nl] > Sent: Wednesday, July 28, 2010 3:24 PM > To: Garry Peirce > Cc: xorp-users at xorp.org > Subject: Re: [Xorp-users] Error writing to routing socket: No such > process > > Hello Garry, > > The goal is to export static routes into OSPF. I normally work with > Juniper routers and in junos policies are used to redistribute routes. > So I figured this is the same in Xorp. Or isn't this the way to do it > in Xorp ? > > Edwin > > > On Jul 28, 2010, at 9:15 PM, Garry Peirce wrote: > > > Not sure I understand your policy statement - I assume you desire to > accept > > static routes. > > Do you actually mean the following? > > > >> term a { > >> from { > >> protocol: "static" > >> } > >> then { > >> accept { > >> } > >> } > >> } > >> then { > >> reject { > >> } > >> } > > > > > > > >> -----Original Message----- > >> From: xorp-users-bounces at xorp.org [mailto:xorp-users- > bounces at xorp.org] > >> On Behalf Of Edwin Schokkenbroek > >> Sent: Wednesday, July 28, 2010 2:43 PM > >> To: xorp-users at xorp.org > >> Subject: [Xorp-users] Error writing to routing socket: No such > process > >> > >> Hello list., > >> > >> Maybe someone here can help me out on the following issue. I'm > working > >> on it now for a couple weeks to get this solved, but I can't find a > >> solution. > >> > >> I'm using xorp version 1.06 on FreeBSD 8.0 (AMD64). > >> xorp is running inside vimages. When I start xorp I receive the > >> following messages: > >> > >> [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +527 > >> fibconfig_entry_set_routing_socket.cc delete_entry ] Error writing > to > >> routing socket: No such process > >> [ 2010/07/28 20:03:37 ERROR xorp_rib:2208 RIB +916 redist_xrl.cc > >> dispatch_complete ] Failed to commit transaction: 102 Command failed > >> DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a > >> vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true > >> is_deleted = false is_unresolved = false is_connected_route = false > >> [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +80 > >> fibconfig_transaction.cc operation_result ] FIB transaction commit > >> failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname > = > >> epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = > >> true is_deleted = false is_unresolved = false is_connected_route = > >> false > >> [ 2010/07/28 20:03:37 WARNING xorp_fea XrlFeaTarget ] Handling > method > >> for redist_transaction4/0.1/commit_transaction failed: XrlCmdError > 102 > >> Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 > >> ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 > >> xorp_route = true is_deleted = false is_unresolved = false > >> is_connected_route = false > >> > >> The route table looks like: > >> > >> beheer at router1> show route table ipv4 unicast final > >> 0.0.0.0/0 [static(1)/1] > >>> to 172.19.0.2 via epair4a/epair4a > >> 10.0.0.0/24 [connected(0)/0] > >>> via epair1a/epair1a > >> 10.1.0.0/24 [connected(0)/0] > >>> via epair3a/epair3a > >> 172.19.0.0/30 [connected(0)/0] > >>> via epair4a/epair4a > >> > >> Interface information: > >> > >> beheer at router1> show interfaces > >> epair1a/epair1a: Flags: mtu 1500 speed > >> unknown > >> inet 10.0.0.1 subnet 10.0.0.0/24 broadcast 10.0.0.255 > >> physical index 2 > >> ether 02:ca:d0:00:05:0a > >> epair3a/epair3a: Flags: mtu 1500 speed > >> unknown > >> inet 10.1.0.1 subnet 10.1.0.0/24 broadcast 10.1.0.255 > >> physical index 3 > >> ether 02:ca:cb:00:05:0a > >> epair4a/epair4a: Flags: mtu 1500 speed > >> unknown > >> inet 172.19.0.1 subnet 172.19.0.0/30 broadcast 172.19.0.3 > >> physical index 4 > >> ether 02:ca:d0:00:05:0a > >> > >> The config file I'm using: > >> > >> /*XORP Configuration File, v1.0*/ > >> protocols { > >> ospf4 { > >> router-id: 10.0.0.1 > >> rfc1583-compatibility: false > >> ip-router-alert: false > >> area 0.0.0.0 { > >> area-type: "normal" > >> interface epair1a { > >> link-type: "broadcast" > >> vif epair1a { > >> address 10.0.0.1 { > >> priority: 128 > >> hello-interval: 10 > >> router-dead-interval: 40 > >> interface-cost: 1 > >> retransmit-interval: 5 > >> transit-delay: 1 > >> disable: false > >> } > >> } > >> } > >> interface epair3a { > >> link-type: "broadcast" > >> vif epair3a { > >> address 10.1.0.1 { > >> priority: 128 > >> hello-interval: 10 > >> router-dead-interval: 40 > >> interface-cost: 1 > >> retransmit-interval: 5 > >> transit-delay: 1 > >> disable: false > >> } > >> } > >> } > >> } > >> export: "red-static-rt" > >> } > >> static { > >> disable: false > >> route 0.0.0.0/0 { > >> next-hop: 172.19.0.2 > >> metric: 1 > >> } > >> } > >> } > >> policy { > >> policy-statement "red-static-rt" { > >> term a { > >> from { > >> protocol: "static" > >> } > >> then { > >> accept { > >> } > >> reject { > >> } > >> } > >> } > >> } > >> } > >> fea { > >> unicast-forwarding4 { > >> disable: false > >> } > >> } > >> interfaces { > >> restore-original-config-on-shutdown: false > >> interface epair1a { > >> description: "" > >> disable: false > >> discard: false > >> unreachable: false > >> management: false > >> vif epair1a { > >> disable: false > >> address 10.0.0.1 { > >> prefix-length: 24 > >> broadcast: 10.0.0.255 > >> disable: false > >> } > >> } > >> } > >> interface epair3a { > >> description: "" > >> disable: false > >> discard: false > >> unreachable: false > >> management: false > >> vif epair3a { > >> disable: false > >> address 10.1.0.1 { > >> prefix-length: 24 > >> disable: false > >> } > >> } > >> } > >> interface epair4a { > >> description: "" > >> disable: false > >> discard: false > >> unreachable: false > >> management: false > >> vif epair4a { > >> disable: false > >> address 172.19.0.1 { > >> prefix-length: 30 > >> disable: false > >> } > >> } > >> } > >> } > >> rtrmgr { > >> config-directory: "/root/chaos/vrd/edwin/router1/boot" > >> load-file-command: > "/root/chaos/vrd/edwin/router1/boot/config.boot" > >> load-file-command-args: "-o" > >> load-ftp-command: "fetch" > >> load-ftp-command-args: "-o" > >> load-http-command: "fetch" > >> load-http-command-args: "-o" > >> load-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" > >> load-tftp-command-args: "" > >> save-file-command: > "/root/chaos/vrd/edwin/router1/boot/config.boot" > >> save-file-command-args: "" > >> save-ftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" > >> save-ftp-command-args: "" > >> save-http-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" > >> save-http-command-args: "" > >> save-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" > >> save-tftp-command-args: "" > >> } > >> > >> > >> The vimages are started with the following options: > >> > >> sysctl net.inet.ip.forwarding=1 > >> sysctl security.jail.allow_raw_sockets=1 > >> > >> > >> I seems that the error messages appear when I apply the policy. What > >> can I do to solve the error messages ? > >> > >> > >> > >> > >> > >> Hades > >> > >> > >> > >> > >> > >> > >> _______________________________________________ > >> Xorp-users mailing list > >> Xorp-users at xorp.org > >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > > > Edwin Schokkenbroek > edwin at spacebugs.nl > > Engineers are full of great ideas. Making things better is what we're > built to do. However, when it comes to engineers, there seems to be an > inverse relationship between great ideas and great communication > skills. This is what gets us into trouble. > > > > > From edwin at spacebugs.nl Wed Jul 28 13:12:40 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 28 Jul 2010 22:12:40 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <4C508B10.5070000@candelatech.com> References: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> <4C508690.9080803@candelatech.com> <4C508B10.5070000@candelatech.com> Message-ID: <67068A4B-1BEA-45F0-B865-8A95E3B6C7D0@spacebugs.nl> On Jul 28, 2010, at 9:54 PM, Ben Greear wrote: > On 07/28/2010 12:44 PM, Edwin Schokkenbroek wrote: >> >> On Jul 28, 2010, at 9:35 PM, Ben Greear wrote: >> >>> On 07/28/2010 12:18 PM, Edwin Schokkenbroek wrote: >>>> Hello Ben, >>>> >>>> Thank you for your quick response. I already started to experiment with xopr.ct. I ran into it when trying to solve the errors mentioned earlier. >>>> >>>> 010/07/28 21:07:59 ERROR xorpsh:1807 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.POm5vR" >>>> [ 2010/07/28 21:07:59 ERROR xorpsh:1807 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.cwKcRV. Error: Permission denied >>>> [ 2010/07/28 21:07:59 ERROR xorpsh:1807 XRL +63 xrl_pf_factory.cc create_sender ] XrlPFSenderFactory::create failed: XrlPFConstructorError from line 131 of xrl_pf_unix.cc: Could not connect to /var/tmp/xrl.cwKcRV >>>> >>>> (These messages are going on forever.) >>>> >>>> The message is clear, and easy to explain, xorp_rtrmgr is started as the root user. However I start the xorpsh as a other user with less privileges. >>>> When I change the ownership of the file in /var/tmp I'm able to login. >>>> >>>> But when I reboot the machine or I start another vimage (or jail with vnet ) I ran into the same problem again. I guess xorp_rtrmgr is creating the files as root. >>>> >>>> Since the messages appear very quickly I'm not able to see the messages when xorp_rtrmgr is started. >>> >>> I could add an option to create the /var/tmp/ file as read/write by everyone (or maybe >>> just the xorp group), I suppose. >> >> I think a xorp group is the most clean way . read/write everyone could maybe introduce a security issue ? >> >> The dir /var/tmp is already world writeable permissions (on my system): >> >> drwxrwxrwt 3 beheer wheel 2048 Jul 28 21:27 /var/tmp/ >> >>> >>> One thing I just noticed: I have 126,000 or so xrl files in /var/tmp/ >>> on one of my test machines. >>> >>> That can't be good :P >> >> Nope.... hopefully the filesystem has enough inodes ;-) >>> >>> Aside from the permissions issue, does xorp.ct fix that other bug you reported? >> >> Well I managed to start one xopr_rtmgr in a vimage, however the other xorp_rtr_mgr seems to hang. >> >> I recieve a lot of messages : > > The messages look OK to me (some seem scary, but I've been seeing them for years > and they don't seem to cause harm, so I haven't bothered to track them down yet). > > The one issue that might be a problem is the timer expiry warnings, but if the > system is slow/virtual, that might be normal and it will probably work better > once all the processes are started. The FreeBSD system is running inside a virtual machine (vmware fusion). > > I don't know anything about vimages, but you might have to do some tricks > to get two xorps to run on the same OS at the same time. If the vimage looks > like a separate machine (like vmware, xemu, etc), then it should be OK. I don't know if you know jails on FreeBSD ? These "vimages" are jails , and they have a own ip stack. (For more info see : http://imunes.tel.fer.hr/virtnet/ ) I'm playing around with it since it appeared in FreeBSD 7. And I even use it in a production environment (by a dutch ISP) > > For the process that hangs, what makes you think so? Can you run 'strace' or > whatever the BSD equiv is to see if it's really hung in a system call, or > 'top' to see if it's spinning 100% CPU? I just figured it out. the xorp_rtrmgr died, and the xorpsh was just waiting. So I killed the xoprsh and restarted xorp_rtrmgr. On the other xorp_rtrmgr I see the following messages appear: [ 2010/07/28 21:52:25.981458 ERROR xorp_fea:2274 FEA fea/data_plane/fibconfig/fibconfig_entry_set_routing_socket.cc:527 delete_entry ] Error writing to routing socket: No such process [ 2010/07/28 21:52:25.983762 ERROR xorp_fea:2274 FEA fea/fibconfig_transaction.cc:80 operation_result ] FIB transaction commit failed on DeleteEntry4: net = 10.0.0.0/24 nexthop = 10.2.0.1 ifname = epair2b vifname = epair2b metric = 2 admin_distance = 110 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2010/07/28 21:52:25.984558 WARNING xorp_fea:2274 XrlFeaTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/fea_base.cc:3978 handle_redist_transaction4_0_1_commit_transaction ] Handling method for redist_transaction4/0.1/commit_transaction failed: XrlCmdError 102 Command failed DeleteEntry4: net = 10.0.0.0/24 nexthop = 10.2.0.1 ifname = epair2b vifname = epair2b metric = 2 admin_distance = 110 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2010/07/28 21:52:25.985962 ERROR xorp_rib:2275 RIB rib/redist_xrl.cc:948 dispatch_complete ] Failed to commit transaction: 102 Command failed DeleteEntry4: net = 10.0.0.0/24 nexthop = 10.2.0.1 ifname = epair2b vifname = epair2b metric = 2 admin_distance = 110 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false I started the xorp_rtrmgr as : /usr/local/xorp/sbin/xorp_rtrmgr -m /usr/local/xorp/lib/xorp/sbin/ -b /root/chaos/vrd/edwin/router1/boot/config.boot -d And I received the messages: Not doing pidfile... [ 2010/07/28 21:51:54.616952 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/master_conf_tree.cc:234 execute ] Changed modules: interfaces, rtrmgr, firewall, fea, rib, policy, static_routes, ospf4 [ 2010/07/28 21:51:54.619137 WARNING xorp_rtrmgr:2330 RTRMGR rtrmgr/module_command.cc:327 startup_validation ] WARNING: Using DelayValidation, module_name: rtrmgr [ 2010/07/28 21:51:54.619200 WARNING xorp_rtrmgr:2330 RTRMGR rtrmgr/module_command.cc:348 config_validation ] WARNING: Using DelayValidation, module_name: rtrmgr [ 2010/07/28 21:51:54.620622 WARNING xorp_rtrmgr:2330 RTRMGR rtrmgr/module_command.cc:369 ready_validation ] WARNING: Using DelayValidation, module_name: rtrmgr [ 2010/07/28 21:51:54.620770 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: interfaces (xorp_fea) [ 2010/07/28 21:51:54.625817 WARNING xorp_rtrmgr:2330 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "fea" does not exist or is not enabled. [ 2010/07/28 21:51:54.626844 WARNING xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/28 21:51:55.656722 INFO xorp_fea:2331 MFEA fea/mfea_node.cc:317 enable ] MFEA enabled [ 2010/07/28 21:51:55.657260 INFO xorp_fea:2331 MFEA fea/mfea_node_cli.cc:126 enable ] CLI enabled [ 2010/07/28 21:51:55.659055 INFO xorp_fea:2331 MFEA fea/mfea_node_cli.cc:92 start ] CLI started [ 2010/07/28 21:51:55.659268 INFO xorp_fea:2331 MFEA fea/mfea_node.cc:317 enable ] MFEA enabled [ 2010/07/28 21:51:55.659364 INFO xorp_fea:2331 MFEA fea/mfea_node_cli.cc:126 enable ] CLI enabled [ 2010/07/28 21:51:55.659809 INFO xorp_fea:2331 MFEA fea/mfea_node_cli.cc:92 start ] CLI started [ 2010/07/28 21:51:55.695317 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: rtrmgr () [ 2010/07/28 21:52:01.748221 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: firewall (xorp_fea) [ 2010/07/28 21:52:01.750650 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: fea (xorp_fea) [ 2010/07/28 21:52:01.752797 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: rib (xorp_rib) [ 2010/07/28 21:52:01.755686 WARNING xorp_rtrmgr:2330 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2010/07/28 21:52:01.756492 WARNING xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/28 21:52:02.795582 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: policy (xorp_policy) [ 2010/07/28 21:52:02.798833 WARNING xorp_rtrmgr:2330 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "policy" does not exist or is not enabled. [ 2010/07/28 21:52:02.799463 WARNING xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/28 21:52:03.862706 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: static_routes (xorp_static_routes) [ 2010/07/28 21:52:03.868031 WARNING xorp_rtrmgr:2330 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "static_routes" does not exist or is not enabled. [ 2010/07/28 21:52:03.868473 WARNING xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/28 21:52:04.903984 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: ospf4 (xorp_ospfv2) [ 2010/07/28 21:52:04.907514 WARNING xorp_rtrmgr:2330 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ospfv2" does not exist or is not enabled. [ 2010/07/28 21:52:04.908267 WARNING xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/28 21:52:05.182318 WARNING xorp_ospfv2:2335 OSPF ospf/xrl_io.cc:948 updates_made ] XrlIO::updates_made, _iftree: [ 2010/07/28 21:52:05.952538 WARNING xorp_ospfv2:2335 OSPF ospf/peer.cc:294 set_link_status ] Setting PeerOut link status to: 1 dbg: create_peer vif: epair1a/epair1a old-status: 0 [ 2010/07/28 21:52:05.952667 WARNING xorp_ospfv2:2335 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair1a/epair1a running: 0 status: 0 link-status: 1 [ 2010/07/28 21:52:05.961775 WARNING xorp_ospfv2:2335 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair1a/epair1a running: 0 status: 1 link-status: 1 [ 2010/07/28 21:52:05.961951 WARNING xorp_ospfv2:2335 OSPF ospf/xrl_io.cc:170 enable_interface_vif ] XRL-IO: Enable Interface epair1a Vif epair1a [ 2010/07/28 21:52:05.963574 WARNING xorp_ospfv2:2335 OSPF ospf/peer.cc:294 set_link_status ] Setting PeerOut link status to: 1 dbg: create_peer vif: epair3a/epair3a old-status: 0 [ 2010/07/28 21:52:05.963602 WARNING xorp_ospfv2:2335 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair3a/epair3a running: 0 status: 0 link-status: 1 [ 2010/07/28 21:52:05.973755 WARNING xorp_fea:2331 FEA fea/data_plane/io/io_ip_socket.cc:230 IoIpSocket ] Registering with iftree: pushed-config [ 2010/07/28 21:52:05.976051 INFO xorp_fea:2331 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair1a vif epair1a socket: 45 [ 2010/07/28 21:52:05.976685 WARNING xorp_ospfv2:2335 OSPF ospf/peer.cc:304 peer_change ] PeerOut, peer_change on interface: epair3a/epair3a running: 0 status: 1 link-status: 1 [ 2010/07/28 21:52:05.976928 WARNING xorp_ospfv2:2335 OSPF ospf/xrl_io.cc:170 enable_interface_vif ] XRL-IO: Enable Interface epair3a Vif epair3a [ 2010/07/28 21:52:05.978695 INFO xorp_fea:2331 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair3a vif epair3a socket: 45 [ 2010/07/28 21:52:05.985697 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:2242 run_task ] No more tasks to run [root at router1 /]# [ 2010/07/28 21:52:07.70452 ERROR xorp_fea:2331 FEA fea/data_plane/fibconfig/fibconfig_entry_set_routing_socket.cc:527 delete_entry ] Error writing to routing socket: No such process [ 2010/07/28 21:52:07.70660 ERROR xorp_fea:2331 FEA fea/fibconfig_transaction.cc:80 operation_result ] FIB transaction commit failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2010/07/28 21:52:07.70947 WARNING xorp_fea:2331 XrlFeaTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/fea_base.cc:3978 handle_redist_transaction4_0_1_commit_transaction ] Handling method for redist_transaction4/0.1/commit_transaction failed: XrlCmdError 102 Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2010/07/28 21:52:07.71468 ERROR xorp_rib:2332 RIB rib/redist_xrl.cc:948 dispatch_complete ] Failed to commit transaction: 102 Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [root at router1 /]# [ 2010/07/28 21:52:10.41438 ERROR xorp_fea:2331 FEA fea/data_plane/fibconfig/fibconfig_entry_set_routing_socket.cc:527 delete_entry ] Error writing to routing socket: No such process [ 2010/07/28 21:52:10.41706 ERROR xorp_fea:2331 FEA fea/fibconfig_transaction.cc:80 operation_result ] FIB transaction commit failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2010/07/28 21:52:10.41868 WARNING xorp_fea:2331 XrlFeaTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/fea_base.cc:3978 handle_redist_transaction4_0_1_commit_transaction ] Handling method for redist_transaction4/0.1/commit_transaction failed: XrlCmdError 102 Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2010/07/28 21:52:10.42125 ERROR xorp_rib:2332 RIB rib/redist_xrl.cc:948 dispatch_complete ] Failed to commit transaction: 102 Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false [ 2010/07/28 21:52:14.967225 INFO xorp_fea:2331 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.6 on interface epair1a vif epair1a socket: 45 [ 2010/07/28 21:52:15.301767 INFO xorp_fea:2331 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.6 on interface epair3a vif epair3a socket: 45 [root at router1 /]# [ 2010/07/28 21:52:20.2743 TRACE xorp_ospfv2 OSPF ] Rejecting LSA last one arrived less than 1 second(s) ago Router-LSA: LS age 1 Options 0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x1 Link State ID 10.1.0.2 Advertising Router 10.1.0.2 LS sequence number 0x80000002 LS checksum 0x6e84 length 48 bit Nt false bit V false bit E false bit B false Type 2 Transit network IP address of Designated router 10.1.0.2 Routers interface address 10.1.0.2 Metric 1 Type 2 Transit network IP address of Designated router 10.2.0.1 Routers interface address 10.2.0.2 Metric 1 Router-LSA: LS age 1481 Options 0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x1 Link State ID 10.1.0.2 Advertising Router 10.1.0.2 LS sequence number 0x80000001 LS checksum 0xd42d length 48 bit Nt false bit V false bit E false bit B false Type 3 Stub network Subnet number 10.1.0.0 Mask 255.255.255.0 Metric 1 Type 2 Transit network IP address of Designated router 10.2.0.1 Routers interface address 10.2.0.2 Metric 1 [ 2010/07/28 21:52:20.4661 TRACE xorp_ospfv2 OSPF ] Rejecting LSA last one arrived less than 1 second(s) ago Router-LSA: LS age 2 Options 0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x1 Link State ID 10.1.0.2 Advertising Router 10.1.0.2 LS sequence number 0x80000002 LS checksum 0x6e84 length 48 bit Nt false bit V false bit E false bit B false Type 2 Transit network IP address of Designated router 10.1.0.2 Routers interface address 10.1.0.2 Metric 1 Type 2 Transit network IP address of Designated router 10.2.0.1 Routers interface address 10.2.0.2 Metric 1 Router-LSA: LS age 1481 Options 0x2 DC: 0 EA: 0 N/P: 0 MC: 0 E: 1 LS type 0x1 Link State ID 10.1.0.2 Advertising Router 10.1.0.2 LS sequence number 0x80000001 LS checksum 0xd42d length 48 bit Nt false bit V false bit E false bit B false Type 3 Stub network Subnet number 10.1.0.0 Mask 255.255.255.0 Metric 1 Type 2 Transit network IP address of Designated router 10.2.0.1 Routers interface address 10.2.0.2 Metric 1 Tomorrow I'm going to reboot the whole machine and going to do it step by step.... To make sure I don't make stupid mistakes. Edwin > > Thanks, > Ben > > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > Edwin Schokkenbroek edwin at spacebugs.nl Engineers are full of great ideas. Making things better is what we're built to do. However, when it comes to engineers, there seems to be an inverse relationship between great ideas and great communication skills. This is what gets us into trouble. From edwin at spacebugs.nl Wed Jul 28 13:16:11 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 28 Jul 2010 22:16:11 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <098801cb2e90$50f51b40$f2df51c0$@edu> References: <08653524-E882-440F-BDF5-63B40FB4483A@spacebugs.nl> <096401cb2e89$385e9130$a91bb390$@edu> <098801cb2e90$50f51b40$f2df51c0$@edu> Message-ID: On Jul 28, 2010, at 10:06 PM, Garry Peirce wrote: > Edwin, > You can do what you desire, but your config includes both actions in the > same THEN clause which I'm not sure xorp will like. I assume you want to > accept statics and reject any others for which I would put the reject clause > outside 'term a', either as 'term b' or as a final global action as I > re-wrote it. > > You might see if re-writing that way results in different behavior. Thanks Garry for pointing this out. I'm still trying and figuring out the xorp way of doing things :-) I tried to put the reject in other clause, but I didn't think about putting it into another term. Going to try this as well. How can I define a global action ? Or is this explained in the user manual ? > > >> -----Original Message----- >> From: Edwin Schokkenbroek [mailto:edwin at spacebugs.nl] >> Sent: Wednesday, July 28, 2010 3:24 PM >> To: Garry Peirce >> Cc: xorp-users at xorp.org >> Subject: Re: [Xorp-users] Error writing to routing socket: No such >> process >> >> Hello Garry, >> >> The goal is to export static routes into OSPF. I normally work with >> Juniper routers and in junos policies are used to redistribute routes. >> So I figured this is the same in Xorp. Or isn't this the way to do it >> in Xorp ? >> >> Edwin >> >> >> On Jul 28, 2010, at 9:15 PM, Garry Peirce wrote: >> >>> Not sure I understand your policy statement - I assume you desire to >> accept >>> static routes. >>> Do you actually mean the following? >>> >>>> term a { >>>> from { >>>> protocol: "static" >>>> } >>>> then { >>>> accept { >>>> } >>>> } >>>> } >>>> then { >>>> reject { >>>> } >>>> } >>> >>> >>> >>>> -----Original Message----- >>>> From: xorp-users-bounces at xorp.org [mailto:xorp-users- >> bounces at xorp.org] >>>> On Behalf Of Edwin Schokkenbroek >>>> Sent: Wednesday, July 28, 2010 2:43 PM >>>> To: xorp-users at xorp.org >>>> Subject: [Xorp-users] Error writing to routing socket: No such >> process >>>> >>>> Hello list., >>>> >>>> Maybe someone here can help me out on the following issue. I'm >> working >>>> on it now for a couple weeks to get this solved, but I can't find a >>>> solution. >>>> >>>> I'm using xorp version 1.06 on FreeBSD 8.0 (AMD64). >>>> xorp is running inside vimages. When I start xorp I receive the >>>> following messages: >>>> >>>> [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +527 >>>> fibconfig_entry_set_routing_socket.cc delete_entry ] Error writing >> to >>>> routing socket: No such process >>>> [ 2010/07/28 20:03:37 ERROR xorp_rib:2208 RIB +916 redist_xrl.cc >>>> dispatch_complete ] Failed to commit transaction: 102 Command failed >>>> DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a >>>> vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true >>>> is_deleted = false is_unresolved = false is_connected_route = false >>>> [ 2010/07/28 20:03:37 ERROR xorp_fea:2207 FEA +80 >>>> fibconfig_transaction.cc operation_result ] FIB transaction commit >>>> failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname >> = >>>> epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = >>>> true is_deleted = false is_unresolved = false is_connected_route = >>>> false >>>> [ 2010/07/28 20:03:37 WARNING xorp_fea XrlFeaTarget ] Handling >> method >>>> for redist_transaction4/0.1/commit_transaction failed: XrlCmdError >> 102 >>>> Command failed DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 >>>> ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 >>>> xorp_route = true is_deleted = false is_unresolved = false >>>> is_connected_route = false >>>> >>>> The route table looks like: >>>> >>>> beheer at router1> show route table ipv4 unicast final >>>> 0.0.0.0/0 [static(1)/1] >>>>> to 172.19.0.2 via epair4a/epair4a >>>> 10.0.0.0/24 [connected(0)/0] >>>>> via epair1a/epair1a >>>> 10.1.0.0/24 [connected(0)/0] >>>>> via epair3a/epair3a >>>> 172.19.0.0/30 [connected(0)/0] >>>>> via epair4a/epair4a >>>> >>>> Interface information: >>>> >>>> beheer at router1> show interfaces >>>> epair1a/epair1a: Flags: mtu 1500 speed >>>> unknown >>>> inet 10.0.0.1 subnet 10.0.0.0/24 broadcast 10.0.0.255 >>>> physical index 2 >>>> ether 02:ca:d0:00:05:0a >>>> epair3a/epair3a: Flags: mtu 1500 speed >>>> unknown >>>> inet 10.1.0.1 subnet 10.1.0.0/24 broadcast 10.1.0.255 >>>> physical index 3 >>>> ether 02:ca:cb:00:05:0a >>>> epair4a/epair4a: Flags: mtu 1500 speed >>>> unknown >>>> inet 172.19.0.1 subnet 172.19.0.0/30 broadcast 172.19.0.3 >>>> physical index 4 >>>> ether 02:ca:d0:00:05:0a >>>> >>>> The config file I'm using: >>>> >>>> /*XORP Configuration File, v1.0*/ >>>> protocols { >>>> ospf4 { >>>> router-id: 10.0.0.1 >>>> rfc1583-compatibility: false >>>> ip-router-alert: false >>>> area 0.0.0.0 { >>>> area-type: "normal" >>>> interface epair1a { >>>> link-type: "broadcast" >>>> vif epair1a { >>>> address 10.0.0.1 { >>>> priority: 128 >>>> hello-interval: 10 >>>> router-dead-interval: 40 >>>> interface-cost: 1 >>>> retransmit-interval: 5 >>>> transit-delay: 1 >>>> disable: false >>>> } >>>> } >>>> } >>>> interface epair3a { >>>> link-type: "broadcast" >>>> vif epair3a { >>>> address 10.1.0.1 { >>>> priority: 128 >>>> hello-interval: 10 >>>> router-dead-interval: 40 >>>> interface-cost: 1 >>>> retransmit-interval: 5 >>>> transit-delay: 1 >>>> disable: false >>>> } >>>> } >>>> } >>>> } >>>> export: "red-static-rt" >>>> } >>>> static { >>>> disable: false >>>> route 0.0.0.0/0 { >>>> next-hop: 172.19.0.2 >>>> metric: 1 >>>> } >>>> } >>>> } >>>> policy { >>>> policy-statement "red-static-rt" { >>>> term a { >>>> from { >>>> protocol: "static" >>>> } >>>> then { >>>> accept { >>>> } >>>> reject { >>>> } >>>> } >>>> } >>>> } >>>> } >>>> fea { >>>> unicast-forwarding4 { >>>> disable: false >>>> } >>>> } >>>> interfaces { >>>> restore-original-config-on-shutdown: false >>>> interface epair1a { >>>> description: "" >>>> disable: false >>>> discard: false >>>> unreachable: false >>>> management: false >>>> vif epair1a { >>>> disable: false >>>> address 10.0.0.1 { >>>> prefix-length: 24 >>>> broadcast: 10.0.0.255 >>>> disable: false >>>> } >>>> } >>>> } >>>> interface epair3a { >>>> description: "" >>>> disable: false >>>> discard: false >>>> unreachable: false >>>> management: false >>>> vif epair3a { >>>> disable: false >>>> address 10.1.0.1 { >>>> prefix-length: 24 >>>> disable: false >>>> } >>>> } >>>> } >>>> interface epair4a { >>>> description: "" >>>> disable: false >>>> discard: false >>>> unreachable: false >>>> management: false >>>> vif epair4a { >>>> disable: false >>>> address 172.19.0.1 { >>>> prefix-length: 30 >>>> disable: false >>>> } >>>> } >>>> } >>>> } >>>> rtrmgr { >>>> config-directory: "/root/chaos/vrd/edwin/router1/boot" >>>> load-file-command: >> "/root/chaos/vrd/edwin/router1/boot/config.boot" >>>> load-file-command-args: "-o" >>>> load-ftp-command: "fetch" >>>> load-ftp-command-args: "-o" >>>> load-http-command: "fetch" >>>> load-http-command-args: "-o" >>>> load-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" >>>> load-tftp-command-args: "" >>>> save-file-command: >> "/root/chaos/vrd/edwin/router1/boot/config.boot" >>>> save-file-command-args: "" >>>> save-ftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" >>>> save-ftp-command-args: "" >>>> save-http-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" >>>> save-http-command-args: "" >>>> save-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" >>>> save-tftp-command-args: "" >>>> } >>>> >>>> >>>> The vimages are started with the following options: >>>> >>>> sysctl net.inet.ip.forwarding=1 >>>> sysctl security.jail.allow_raw_sockets=1 >>>> >>>> >>>> I seems that the error messages appear when I apply the policy. What >>>> can I do to solve the error messages ? >>>> >>>> >>>> >>>> >>>> >>>> Hades >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Xorp-users mailing list >>>> Xorp-users at xorp.org >>>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users >>> >> >> >> Edwin Schokkenbroek >> edwin at spacebugs.nl >> >> Engineers are full of great ideas. Making things better is what we're >> built to do. However, when it comes to engineers, there seems to be an >> inverse relationship between great ideas and great communication >> skills. This is what gets us into trouble. >> >> >> >> >> > > Edwin Schokkenbroek edwin at spacebugs.nl Engineers are full of great ideas. Making things better is what we're built to do. However, when it comes to engineers, there seems to be an inverse relationship between great ideas and great communication skills. This is what gets us into trouble. From greearb at candelatech.com Wed Jul 28 14:35:49 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 28 Jul 2010 14:35:49 -0700 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <67068A4B-1BEA-45F0-B865-8A95E3B6C7D0@spacebugs.nl> References: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> <4C508690.9080803@candelatech.com> <4C508B10.5070000@candelatech.com> <67068A4B-1BEA-45F0-B865-8A95E3B6C7D0@spacebugs.nl> Message-ID: <4C50A2B5.8000906@candelatech.com> On 07/28/2010 01:12 PM, Edwin Schokkenbroek wrote: [ 2010/07/28 21:52:05.978695 INFO xorp_fea:2331 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair3a vif epair3a socket: 45 [ 2010/07/28 21:52:05.985697 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:2242 run_task ] No more tasks to run [root at router1 /]# [ 2010/07/28 21:52:07.70452 ERROR xorp_fea:2331 FEA fea/data_plane/fibconfig/fibconfig_entry_set_routing_socket.cc:527 delete_entry ] Error writing to routing socket: No such process [ 2010/07/28 21:52:07.70660 ERROR xorp_fea:2331 FEA fea/fibconfig_transaction.cc:80 operation_result ] FIB transaction commit failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false Looks like it tries to remove a route that is already removed. I just pushed a change that should cause that cause to not return an error. Please grab the top-of-tree and see if that fixes the problem for you. I don't have BSD system to build or test on, so let me know if you see any troubles. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Thu Jul 29 11:38:18 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Thu, 29 Jul 2010 20:38:18 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <4C50A2B5.8000906@candelatech.com> References: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> <4C508690.9080803@candelatech.com> <4C508B10.5070000@candelatech.com> <67068A4B-1BEA-45F0-B865-8A95E3B6C7D0@spacebugs.nl> <4C50A2B5.8000906@candelatech.com> Message-ID: On Jul 28, 2010, at 11:35 PM, Ben Greear wrote: > On 07/28/2010 01:12 PM, Edwin Schokkenbroek wrote: > > > [ 2010/07/28 21:52:05.978695 INFO xorp_fea:2331 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair3a vif epair3a socket: 45 > [ 2010/07/28 21:52:05.985697 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:2242 run_task ] No more tasks to run > [root at router1 /]# [ 2010/07/28 21:52:07.70452 ERROR xorp_fea:2331 FEA fea/data_plane/fibconfig/fibconfig_entry_set_routing_socket.cc:527 delete_entry ] Error writing to routing socket: No such process > [ 2010/07/28 21:52:07.70660 ERROR xorp_fea:2331 FEA fea/fibconfig_transaction.cc:80 operation_result ] FIB transaction commit failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false > > > Looks like it tries to remove a route that is already removed. I just pushed a change > that should cause that cause to not return an error. > > Please grab the top-of-tree and see if that fixes the problem for you. > > I don't have BSD system to build or test on, so let me know if you > see any troubles. The change seems to work. After compiling I now see the following messages, which seems good: Not doing pidfile... [ 2010/07/29 14:51:06.463603 INFO xorp_rtrmgr:1986 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x801d22a80 path: /var/tmp/xrl.HYQU81 [ 2010/07/29 14:51:06.464764 INFO xorp_rtrmgr:1986 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x801d22ac0 path: /var/tmp/xrl.7pKyDf [ 2010/07/29 14:51:06.528369 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/master_conf_tree.cc:234 execute ] Changed modules: interfaces, rtrmgr, firewall, fea, rib, policy, static_routes, ospf4 [ 2010/07/29 14:51:06.549516 WARNING xorp_rtrmgr:1986 RTRMGR rtrmgr/module_command.cc:327 startup_validation ] WARNING: Using DelayValidation, module_name: rtrmgr [ 2010/07/29 14:51:06.549629 WARNING xorp_rtrmgr:1986 RTRMGR rtrmgr/module_command.cc:348 config_validation ] WARNING: Using DelayValidation, module_name: rtrmgr [ 2010/07/29 14:51:06.551230 WARNING xorp_rtrmgr:1986 RTRMGR rtrmgr/module_command.cc:369 ready_validation ] WARNING: Using DelayValidation, module_name: rtrmgr [ 2010/07/29 14:51:06.551379 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: interfaces (xorp_fea) [ 2010/07/29 14:51:06.554783 WARNING xorp_rtrmgr:1986 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "fea" does not exist or is not enabled. [ 2010/07/29 14:51:06.556098 WARNING xorp_rtrmgr:1986 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/29 14:51:07.85408 INFO xorp_fea:1987 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x803804480 path: /var/tmp/xrl.1WpsX3 [ 2010/07/29 14:51:07.86033 INFO xorp_fea:1987 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x8038044c0 path: /var/tmp/xrl.dJkPsd [ 2010/07/29 14:51:07.89675 INFO xorp_fea:1987 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x803804880 path: /var/tmp/xrl.W83VmT [ 2010/07/29 14:51:07.103624 INFO xorp_fea:1987 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x8038048c0 path: /var/tmp/xrl.Goszxf [ 2010/07/29 14:51:07.104794 INFO xorp_fea:1987 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x80383eb80 path: /var/tmp/xrl.h3IF2p [ 2010/07/29 14:51:07.105168 INFO xorp_fea:1987 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x80383ebc0 path: /var/tmp/xrl.0adCgy [ 2010/07/29 14:51:07.106197 INFO xorp_fea:1987 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x803843100 path: /var/tmp/xrl.CYziCM [ 2010/07/29 14:51:07.106399 INFO xorp_fea:1987 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x803843140 path: /var/tmp/xrl.sctbYQ [ 2010/07/29 14:51:07.644194 INFO xorp_fea:1987 MFEA fea/mfea_node.cc:317 enable ] MFEA enabled [ 2010/07/29 14:51:07.644289 INFO xorp_fea:1987 MFEA fea/mfea_node_cli.cc:126 enable ] CLI enabled [ 2010/07/29 14:51:07.644945 INFO xorp_fea:1987 MFEA fea/mfea_node_cli.cc:92 start ] CLI started [ 2010/07/29 14:51:07.644991 INFO xorp_fea:1987 MFEA fea/mfea_node.cc:317 enable ] MFEA enabled [ 2010/07/29 14:51:07.645011 INFO xorp_fea:1987 MFEA fea/mfea_node_cli.cc:126 enable ] CLI enabled [ 2010/07/29 14:51:07.645126 INFO xorp_fea:1987 MFEA fea/mfea_node_cli.cc:92 start ] CLI started [ 2010/07/29 14:51:07.695455 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: rtrmgr () [ 2010/07/29 14:51:13.753257 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: firewall (xorp_fea) [ 2010/07/29 14:51:13.755613 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: fea (xorp_fea) [ 2010/07/29 14:51:13.757596 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: rib (xorp_rib) [ 2010/07/29 14:51:13.781099 WARNING xorp_rtrmgr:1986 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "rib" does not exist or is not enabled. [ 2010/07/29 14:51:13.781730 WARNING xorp_rtrmgr:1986 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/29 14:51:14.43877 INFO xorp_rib XRL ] Creating XlfPFUNIXListener: 0x802c04440 path: /var/tmp/xrl.9XvES7 [ 2010/07/29 14:51:14.44441 INFO xorp_rib XRL ] Creating XlfPFUNIXListener: 0x802c04480 path: /var/tmp/xrl.8zsQTL [ 2010/07/29 14:51:14.114469 INFO xorp_rib XRL ] Creating XlfPFUNIXListener: 0x802c77d40 path: /var/tmp/xrl.o4jIfq [ 2010/07/29 14:51:14.114670 INFO xorp_rib XRL ] Creating XlfPFUNIXListener: 0x802c77d80 path: /var/tmp/xrl.4W0u5a [ 2010/07/29 14:51:14.813341 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: policy (xorp_policy) [ 2010/07/29 14:51:14.822795 WARNING xorp_rtrmgr:1986 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "policy" does not exist or is not enabled. [ 2010/07/29 14:51:14.823188 WARNING xorp_rtrmgr:1986 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/29 14:51:14.924074 INFO xorp_policy:1989 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x801f043c0 path: /var/tmp/xrl.sO1C11 [ 2010/07/29 14:51:14.924572 INFO xorp_policy:1989 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x801f04400 path: /var/tmp/xrl.ZoX54F [ 2010/07/29 14:51:15.875352 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: static_routes (xorp_static_routes) [ 2010/07/29 14:51:15.889637 WARNING xorp_rtrmgr:1986 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "static_routes" does not exist or is not enabled. [ 2010/07/29 14:51:15.890025 WARNING xorp_rtrmgr:1986 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/29 14:51:15.930994 INFO xorp_static_routes XRL ] Creating XlfPFUNIXListener: 0x8022043c0 path: /var/tmp/xrl.CRAlDT [ 2010/07/29 14:51:15.931501 INFO xorp_static_routes XRL ] Creating XlfPFUNIXListener: 0x802204400 path: /var/tmp/xrl.cuBfml [ 2010/07/29 14:51:15.979305 INFO xorp_static_routes XRL ] Creating XlfPFUNIXListener: 0x802263780 path: /var/tmp/xrl.HAhh00 [ 2010/07/29 14:51:15.979544 INFO xorp_static_routes XRL ] Creating XlfPFUNIXListener: 0x8022637c0 path: /var/tmp/xrl.PywhCp [ 2010/07/29 14:51:16.924594 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/module_manager.cc:94 execute ] Executing module: ospf4 (xorp_ospfv2) [ 2010/07/29 14:51:16.938708 WARNING xorp_rtrmgr:1986 XrlFinderTarget obj/x86_64-unknown-freebsd8.0/xrl/targets/finder_base.cc:482 handle_finder_0_2_resolve_xrl ] Handling method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command failed Target "ospfv2" does not exist or is not enabled. [ 2010/07/29 14:51:16.939335 WARNING xorp_rtrmgr:1986 RTRMGR rtrmgr/task.cc:215 xrl_done ] Failed to receive reply, code: 201 Resolve failed retries: 0 max_retries: 30 [ 2010/07/29 14:51:17.36131 INFO xorp_ospfv2:1991 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x8027043c0 path: /var/tmp/xrl.cCYEpE [ 2010/07/29 14:51:17.36685 INFO xorp_ospfv2:1991 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x802704400 path: /var/tmp/xrl.koQ5Fk [ 2010/07/29 14:51:17.94009 INFO xorp_ospfv2:1991 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x80276cbc0 path: /var/tmp/xrl.5HwIQt [ 2010/07/29 14:51:17.94179 INFO xorp_ospfv2:1991 XRL libxipc/xrl_pf_unix.cc:50 XrlPFUNIXListener ] Creating XlfPFUNIXListener: 0x80276cc00 path: /var/tmp/xrl.NRL59w [ 2010/07/29 14:51:17.193679 WARNING xorp_ospfv2:1991 OSPF ospf/xrl_io.cc:948 updates_made ] XrlIO::updates_made, _iftree: [ 2010/07/29 14:51:17.982929 WARNING xorp_ospfv2:1991 OSPF ospf/peer.cc:295 set_link_status ] Setting PeerOut link status to: 1 dbg: create_peer vif: epair1a/epair1a old-status: 0 [ 2010/07/29 14:51:17.983135 WARNING xorp_ospfv2:1991 OSPF ospf/peer.cc:305 peer_change ] PeerOut, peer_change on interface: epair1a/epair1a running: 0 status: 0 link-status: 1 [ 2010/07/29 14:51:17.992923 WARNING xorp_ospfv2:1991 OSPF ospf/peer.cc:305 peer_change ] PeerOut, peer_change on interface: epair1a/epair1a running: 0 status: 1 link-status: 1 [ 2010/07/29 14:51:17.993403 WARNING xorp_ospfv2:1991 OSPF ospf/xrl_io.cc:170 enable_interface_vif ] XRL-IO: Enable Interface epair1a Vif epair1a [ 2010/07/29 14:51:17.995652 WARNING xorp_ospfv2:1991 OSPF ospf/peer.cc:295 set_link_status ] Setting PeerOut link status to: 1 dbg: create_peer vif: epair3a/epair3a old-status: 0 [ 2010/07/29 14:51:17.995708 WARNING xorp_ospfv2:1991 OSPF ospf/peer.cc:305 peer_change ] PeerOut, peer_change on interface: epair3a/epair3a running: 0 status: 0 link-status: 1 [ 2010/07/29 14:51:17.998663 WARNING xorp_fea:1987 FEA fea/data_plane/io/io_ip_socket.cc:230 IoIpSocket ] Registering with iftree: pushed-config [ 2010/07/29 14:51:18.449 INFO xorp_fea:1987 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair1a vif epair1a socket: 45 [ 2010/07/29 14:51:18.1511 WARNING xorp_ospfv2:1991 OSPF ospf/peer.cc:305 peer_change ] PeerOut, peer_change on interface: epair3a/epair3a running: 0 status: 1 link-status: 1 [ 2010/07/29 14:51:18.1611 WARNING xorp_ospfv2:1991 OSPF ospf/xrl_io.cc:170 enable_interface_vif ] XRL-IO: Enable Interface epair3a Vif epair3a [ 2010/07/29 14:51:18.2771 INFO xorp_fea:1987 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair3a vif epair3a socket: 45 [ 2010/07/29 14:51:18.5283 INFO xorp_rtrmgr:1986 RTRMGR rtrmgr/task.cc:2242 run_task ] No more tasks to run Welcome to XORP on router1 Is there a way to start the xorp_rtrmgr in a less verbose way ? > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > Edwin Schokkenbroek edwin at spacebugs.nl Engineers are full of great ideas. Making things better is what we're built to do. However, when it comes to engineers, there seems to be an inverse relationship between great ideas and great communication skills. This is what gets us into trouble. From skjo at etri.re.kr Thu Jul 29 19:20:29 2010 From: skjo at etri.re.kr (=?ks_c_5601-1987?B?wba8urHV?=) Date: Fri, 30 Jul 2010 11:20:29 +0900 Subject: [Xorp-users] Question on XORP PIM-SSM Configuration Message-ID: <001f01cb2f8d$c7691d00$563b5700$@etri.re.kr> Hi, I?m new to XORP and now configuring simple PIM-SSM test scenario with two XORP routers and VLC server/client. Detailed configuration information is as below. Multicast Server 192.168.96.49 / 24 Window XP SP3 VLC Server Router #1 eth0: 192.169.96.50 / 24 eth1: 10.3.2.18 / 16 Fedora Core 9 / 2.6.25-14 Manually configured as RP Router #2 eth0: 10.3.2.20 / 16 eth1: 192.168.97.50 / 24 Multicast Client 192.168.97.49 / 24 Fedora Core 10 / 2.7.41 VLC Client When I start to run xorp with boot configuration (see attached files), I can check Wiresharks and each router sends ?PIM Hello? message. However they can?t update their neighbor table. Xorp> show pim neighbors Interface DRpriority NeighborAddr V Mode Holdtime Timeout Do I need to configure more additional information or pre-configuration? (I read some articles about PIM-SSM posted on xorp-user group and tried it. But it couldn?t help) Please let us know how it goes. Sincerely yours, S. K. Jo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100730/9743356c/attachment.html -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: config(R1).txt Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100730/9743356c/attachment.txt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: config(R2).txt Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100730/9743356c/attachment-0001.txt From greearb at candelatech.com Fri Jul 30 11:04:18 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 30 Jul 2010 11:04:18 -0700 Subject: [Xorp-users] Question on XORP PIM-SSM Configuration In-Reply-To: <001f01cb2f8d$c7691d00$563b5700$@etri.re.kr> References: <001f01cb2f8d$c7691d00$563b5700$@etri.re.kr> Message-ID: <4C531422.8090100@candelatech.com> On 07/29/2010 07:20 PM, ??? wrote: > Hi, > > I?m new to XORP and now configuring simple PIM-SSM test scenario with > two XORP routers and VLC server/client. > > Detailed configuration information is as below. I'm not sure if it will help, but I just committed two example config files for two routers using ospf and multicast. I just tested this in our product and it appears to work as expected. See the ospf-mcast* files in this link: http://github.com/greearb/xorp.ct/tree/c8853f641172683f4e444eea79d03442f4f0157c/xorp/rtrmgr/config I am not sure how valid the rest of those example configs are..they haven't been modified in years, but they may work. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Fri Jul 30 12:28:29 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 30 Jul 2010 12:28:29 -0700 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: References: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> <4C508690.9080803@candelatech.com> <4C508B10.5070000@candelatech.com> <67068A4B-1BEA-45F0-B865-8A95E3B6C7D0@spacebugs.nl> <4C50A2B5.8000906@candelatech.com> Message-ID: <4C5327DD.9040705@candelatech.com> On 07/29/2010 11:38 AM, Edwin Schokkenbroek wrote: > > On Jul 28, 2010, at 11:35 PM, Ben Greear wrote: > >> On 07/28/2010 01:12 PM, Edwin Schokkenbroek wrote: >> >> >> [ 2010/07/28 21:52:05.978695 INFO xorp_fea:2331 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair3a vif epair3a socket: 45 >> [ 2010/07/28 21:52:05.985697 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:2242 run_task ] No more tasks to run >> [root at router1 /]# [ 2010/07/28 21:52:07.70452 ERROR xorp_fea:2331 FEA fea/data_plane/fibconfig/fibconfig_entry_set_routing_socket.cc:527 delete_entry ] Error writing to routing socket: No such process >> [ 2010/07/28 21:52:07.70660 ERROR xorp_fea:2331 FEA fea/fibconfig_transaction.cc:80 operation_result ] FIB transaction commit failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false >> >> >> Looks like it tries to remove a route that is already removed. I just pushed a change >> that should cause that cause to not return an error. >> >> Please grab the top-of-tree and see if that fixes the problem for you. >> >> I don't have BSD system to build or test on, so let me know if you >> see any troubles. > > The change seems to work. After compiling I now see the following messages, which seems good: [snip] > Is there a way to start the xorp_rtrmgr in a less verbose way ? You can have it log all the messages to a file: -l xorp_log.txt You can also compile out tracing with several options, see 'scons --help' Might be a way to twiddle logging levels in the config file, but I'm too lazy to go look right now. A lot of the more verbose stuff I put in there to provide more info if certain hard-to-reproduce bugs happen again, and the PFUNIX Listener stuff is already gone from top-of-tree, as it was breaking some regression tests. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From peirce at maine.edu Fri Jul 30 13:52:19 2010 From: peirce at maine.edu (Garry Peirce) Date: Fri, 30 Jul 2010 16:52:19 -0400 Subject: [Xorp-users] Question on XORP PIM-SSM Configuration In-Reply-To: <001f01cb2f8d$c7691d00$563b5700$@etri.re.kr> References: <001f01cb2f8d$c7691d00$563b5700$@etri.re.kr> Message-ID: <0c6801cb3029$1a18b3d0$4e4a1b70$@edu> I assume you can ping between your routers? You might verify that there are no FW rules on these routers blocking PIM traffic (224.0.0.13). From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of ??? Sent: Thursday, July 29, 2010 10:20 PM To: xorp-users at xorp.org Subject: [Xorp-users] Question on XORP PIM-SSM Configuration Hi, I?m new to XORP and now configuring simple PIM-SSM test scenario with two XORP routers and VLC server/client. Detailed configuration information is as below. Multicast Server 192.168.96.49 / 24 Window XP SP3 VLC Server Router #1 eth0: 192.169.96.50 / 24 eth1: 10.3.2.18 / 16 Fedora Core 9 / 2.6.25-14 Manually configured as RP Router #2 eth0: 10.3.2.20 / 16 eth1: 192.168.97.50 / 24 Multicast Client 192.168.97.49 / 24 Fedora Core 10 / 2.7.41 VLC Client When I start to run xorp with boot configuration (see attached files), I can check Wiresharks and each router sends ?PIM Hello? message. However they can?t update their neighbor table. Xorp> show pim neighbors Interface DRpriority NeighborAddr V Mode Holdtime Timeout Do I need to configure more additional information or pre-configuration? (I read some articles about PIM-SSM posted on xorp-user group and tried it. But it couldn?t help) Please let us know how it goes. Sincerely yours, S. K. Jo -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100730/03347eb5/attachment.html From edwin at spacebugs.nl Fri Jul 30 14:35:35 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Fri, 30 Jul 2010 23:35:35 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <4C5327DD.9040705@candelatech.com> References: <69D92A03-AE67-41C9-A50D-DC60AE65BE8A@spacebugs.nl> <4C508690.9080803@candelatech.com> <4C508B10.5070000@candelatech.com> <67068A4B-1BEA-45F0-B865-8A95E3B6C7D0@spacebugs.nl> <4C50A2B5.8000906@candelatech.com> <4C5327DD.9040705@candelatech.com> Message-ID: <9924A386-F570-4E5D-9294-53A2E78A18B1@spacebugs.nl> On Jul 30, 2010, at 9:28 PM, Ben Greear wrote: > On 07/29/2010 11:38 AM, Edwin Schokkenbroek wrote: >> >> On Jul 28, 2010, at 11:35 PM, Ben Greear wrote: >> >>> On 07/28/2010 01:12 PM, Edwin Schokkenbroek wrote: >>> >>> >>> [ 2010/07/28 21:52:05.978695 INFO xorp_fea:2331 FEA fea/data_plane/io/io_ip_socket.cc:523 join_multicast_group ] Joined IPv4 group: 224.0.0.5 on interface epair3a vif epair3a socket: 45 >>> [ 2010/07/28 21:52:05.985697 INFO xorp_rtrmgr:2330 RTRMGR rtrmgr/task.cc:2242 run_task ] No more tasks to run >>> [root at router1 /]# [ 2010/07/28 21:52:07.70452 ERROR xorp_fea:2331 FEA fea/data_plane/fibconfig/fibconfig_entry_set_routing_socket.cc:527 delete_entry ] Error writing to routing socket: No such process >>> [ 2010/07/28 21:52:07.70660 ERROR xorp_fea:2331 FEA fea/fibconfig_transaction.cc:80 operation_result ] FIB transaction commit failed on DeleteEntry4: net = 0.0.0.0/0 nexthop = 172.19.0.2 ifname = epair4a vifname = epair4a metric = 1 admin_distance = 1 xorp_route = true is_deleted = false is_unresolved = false is_connected_route = false >>> >>> >>> Looks like it tries to remove a route that is already removed. I just pushed a change >>> that should cause that cause to not return an error. >>> >>> Please grab the top-of-tree and see if that fixes the problem for you. >>> >>> I don't have BSD system to build or test on, so let me know if you >>> see any troubles. >> >> The change seems to work. After compiling I now see the following messages, which seems good: > > [snip] > >> Is there a way to start the xorp_rtrmgr in a less verbose way ? > > You can have it log all the messages to a file: -l xorp_log.txt Well, that's very effective. thanks. xorp_rtrmgr starts very quiet now :-) Why didn't I think of this ? > > You can also compile out tracing with several options, see 'scons --help' I looked at the scons --help, as I'm not a programmer I didn't find an option which seems to do this. And from the output of scons I understand that most debug options are disabled: Debug messages: False Debug function names: False Debug callbacks: False > > Might be a way to twiddle logging levels in the config file, but > I'm too lazy to go look right now. > > A lot of the more verbose stuff I put in there to provide more info > if certain hard-to-reproduce bugs happen again, and the PFUNIX Listener > stuff is already gone from top-of-tree, as it was breaking some > regression tests. Thank you for pointing this out, and providing and solving this in a very quick way. And did I already mention that Xorp is fun to work with ? Edwin > > Thanks, > Ben > > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > Edwin Schokkenbroek edwin at spacebugs.nl Engineers are full of great ideas. Making things better is what we're built to do. However, when it comes to engineers, there seems to be an inverse relationship between great ideas and great communication skills. This is what gets us into trouble.