From edwin at spacebugs.nl Sun Aug 1 06:23:48 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Sun, 1 Aug 2010 15:23:48 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <9924A386-F570-4E5D-9294-53A2E78A18B1@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> <4C50A2B5.8000906@candelatech.com> <4C5327DD.9040705@candelatech.com> <9924A386-F570-4E5D-9294-53A2E78A18B1@spacebugs.nl> Message-ID: On Jul 30, 2010, at 11:35 PM, Edwin Schokkenbroek wrote: > > 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: Well the route message is solved but while testing the change further, by complete recreating the configs I noticed that there seems to be another issue, when I use a show command the permissions on files the /var/tmp directory are causing trouble: Welcome to XORP on router2 beheer at router2> show interfaces epair1b/epair1b: Flags: mtu 1500 speed unknown inet6 fe80::ff:fe00:70b prefixlen 64 inet 192.168.2.2 subnet 192.168.2.0/24 broadcast 192.168.2.255 physical index 2 ether 02:00:00:00:07:0b epair4b/epair4b: Flags: mtu 1500 speed unknown inet6 fe80::ff:fe00:70b prefixlen 64 inet 192.168.4.2 subnet 192.168.4.0/24 broadcast 192.168.4.255 physical index 3 ether 02:00:00:00:07:0b beheer at router2> configure Entering configuration mode. There are no other users in configuration mode. [edit] beheer at router2# set protocols ospf4 area 0.0.0.0 interface epair1b vif epair1b abeheer at router2# set protocols ospf4 area 0.0.0.0 interface epair1b vif epair1b address 192.168.2.2 [edit] beheer at router2# set protocols ospf4 area 0.0.0.0 interface epair4b vif epair4b abeheer at router2# set protocols ospf4 area 0.0.0.0 interface epair4b vif epair4b address 192.168.4.2 [edit] beheer at router2# commit OK [edit] beheer at router2# save config.boot Save done. beheer at router2# exit beheer at router2> show ospf4 neighbor [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.0jdQAP. Error: Permission denied [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 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.0jdQAP [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.0jdQAP" [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.6K9MrI. Error: Permission denied [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 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.6K9MrI [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.6K9MrI" [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.0jdQAP. Error: Permission denied [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 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.0jdQAP [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.0jdQAP" [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.6K9MrI. Error: Permission denied [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 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.6K9MrI [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 XRL +468 xrl_router.cc get_sender ] Could not create XrlPFSender for protocol = "unix" address = ":var:tmp:xrl.6K9MrI" [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 LIBCOMM +831 comm_user.c comm_connect_unix ] Error connecting to unix socket. Path: /var/tmp/xrl.0jdQAP. Error: Permission denied [ 2010/08/01 15:17:31 ERROR print_neighbours:2192 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.0jdQAP >> >> [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. > > > > > > 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 Sun Aug 1 15:25:08 2010 From: greearb at candelatech.com (Ben Greear) Date: Sun, 01 Aug 2010 15:25:08 -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> <4C5327DD.9040705@candelatech.com> <9924A386-F570-4E5D-9294-53A2E78A18B1@spacebugs.nl> Message-ID: <4C55F444.80109@candelatech.com> > Well the route message is solved but while testing the change further, by complete recreating the configs I noticed that there seems to be another issue, when I use a show command the permissions on files the /var/tmp directory are causing trouble: I haven't had time to make the permission changes yet. Patches welcome if someone else has the time..otherwise, I'll try to get to it soon. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From skjo at etri.re.kr Tue Aug 3 04:33:55 2010 From: skjo at etri.re.kr (=?ks_c_5601-1987?B?wba8urHV?=) Date: Tue, 3 Aug 2010 20:33:55 +0900 Subject: [Xorp-users] Question on XORP PIM-SSM Configuration In-Reply-To: <0c6801cb3029$1a18b3d0$4e4a1b70$@edu> References: <001f01cb2f8d$c7691d00$563b5700$@etri.re.kr> <0c6801cb3029$1a18b3d0$4e4a1b70$@edu> Message-ID: <007601cb32ff$c1512140$43f363c0$@etri.re.kr> Dear Garry Peirce,, Thanks for your reply. Yes, I can ping between two routers. And monitoring Router #1 on ?eth1? (or Router #2 on ?eth0?), I can see PIM Hello Message from 10.3.2.18 to 224.0.0.13 and 10.3.2.20 to 224.0.0.13 periodically. However, nothing added on Router #1. Xorp> show pim neighbors Interface DRpriority NeighborAddr V Mode Holdtime Timeout ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Do I have to check internal XORP process on receiving PIM Hello message? Sincerely yours, S. K. Jo From: Garry Peirce [mailto:peirce at maine.edu] Sent: Saturday, July 31, 2010 5:52 AM To: '???'; xorp-users at xorp.org Subject: RE: [Xorp-users] Question on XORP PIM-SSM Configuration 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 *********************************** Configuration Router #1 ************************************ interfaces { interface eth0 { description: "upstream interface" disable: false default-system-config } interface eth1 { description: "downstream interface" disable: false default-system-config } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { disable: false interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { disable: false } } traceoptions { flag all { disable: false } } } } protocols { igmp { disable: false interface eth0 { vif eth0 { version: 3 disable: false } } interface eth1 { vif eth1 { version: 3 disable: false } } traceoptions { flag all { disable: false } } } } protocols { pimsm4 { disable: false interface eth0 { vif eth0 { version: 3 disable: false } } interface eth1 { vif eth1 { version: 3 disable: false } } interface register_vif { vif register_vif { disable: false } } traceoptions { flag all { disable: false } } } } protocols { fib2mrib { disable: false } } *********************************** Configuration Router #2 ************************************ interfaces { interface eth0 { description: "upstream interface" disable: false default-system-config } interface eth1 { description: "downstream interface" disable: false default-system-config } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { disable: false interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { disable: false } } traceoptions { flag all { disable: false } } } } protocols { igmp { disable: false interface eth0 { vif eth0 { version: 3 disable: false } } interface eth1 { vif eth1 { version: 3 disable: false } } traceoptions { flag all { disable: false } } } } protocols { pimsm4 { disable: false interface eth0 { vif eth0 { version: 3 disable: false } } interface eth1 { vif eth1 { version: 3 disable: false } } interface register_vif { vif register_vif { disable: false } } traceoptions { flag all { disable: false } } static-rps { rp 10.3.2.18 { group-prefix 224.0.0.0/4 } } } } protocols { fib2mrib { disable: false } } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100803/22673ac1/attachment-0001.html From peirce at maine.edu Tue Aug 3 05:59:10 2010 From: peirce at maine.edu (Garry Peirce) Date: Tue, 3 Aug 2010 08:59:10 -0400 Subject: [Xorp-users] Question on XORP PIM-SSM Configuration In-Reply-To: <007601cb32ff$c1512140$43f363c0$@etri.re.kr> References: <001f01cb2f8d$c7691d00$563b5700$@etri.re.kr> <0c6801cb3029$1a18b3d0$4e4a1b70$@edu> <007601cb32ff$c1512140$43f363c0$@etri.re.kr> Message-ID: <010a01cb330b$aa2d6670$fe883350$@edu> At which point are you seeing these PIM messages? - at the receiving end via tcpdump? (which occurs prior to iptables). What is the output of ?show pim interface? and ?show logging? (looks like you have pimsm4 traceoptions enabled). Your kernel is configured to support mcast correct? (see section 15.3.1 of the 1.6 manual) From: ??? [mailto:skjo at etri.re.kr] Sent: Tuesday, August 03, 2010 7:34 AM To: 'Garry Peirce' Cc: xorp-users at xorp.org Subject: RE: [Xorp-users] Question on XORP PIM-SSM Configuration Dear Garry Peirce,, Thanks for your reply. Yes, I can ping between two routers. And monitoring Router #1 on ?eth1? (or Router #2 on ?eth0?), I can see PIM Hello Message from 10.3.2.18 to 224.0.0.13 and 10.3.2.20 to 224.0.0.13 periodically. However, nothing added on Router #1. Xorp> show pim neighbors Interface DRpriority NeighborAddr V Mode Holdtime Timeout ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Do I have to check internal XORP process on receiving PIM Hello message? Sincerely yours, S. K. Jo From: Garry Peirce [mailto:peirce at maine.edu] Sent: Saturday, July 31, 2010 5:52 AM To: '???'; xorp-users at xorp.org Subject: RE: [Xorp-users] Question on XORP PIM-SSM Configuration 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 *********************************** Configuration Router #1 ************************************ interfaces { interface eth0 { description: "upstream interface" disable: false default-system-config } interface eth1 { description: "downstream interface" disable: false default-system-config } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { disable: false interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { disable: false } } traceoptions { flag all { disable: false } } } } protocols { igmp { disable: false interface eth0 { vif eth0 { version: 3 disable: false } } interface eth1 { vif eth1 { version: 3 disable: false } } traceoptions { flag all { disable: false } } } } protocols { pimsm4 { disable: false interface eth0 { vif eth0 { version: 3 disable: false } } interface eth1 { vif eth1 { version: 3 disable: false } } interface register_vif { vif register_vif { disable: false } } traceoptions { flag all { disable: false } } } } protocols { fib2mrib { disable: false } } *********************************** Configuration Router #2 ************************************ interfaces { interface eth0 { description: "upstream interface" disable: false default-system-config } interface eth1 { description: "downstream interface" disable: false default-system-config } } fea { unicast-forwarding4 { disable: false } } plumbing { mfea4 { disable: false interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } interface register_vif { vif register_vif { disable: false } } traceoptions { flag all { disable: false } } } } protocols { igmp { disable: false interface eth0 { vif eth0 { version: 3 disable: false } } interface eth1 { vif eth1 { version: 3 disable: false } } traceoptions { flag all { disable: false } } } } protocols { pimsm4 { disable: false interface eth0 { vif eth0 { version: 3 disable: false } } interface eth1 { vif eth1 { version: 3 disable: false } } interface register_vif { vif register_vif { disable: false } } traceoptions { flag all { disable: false } } static-rps { rp 10.3.2.18 { group-prefix 224.0.0.0/4 } } } } protocols { fib2mrib { disable: false } } -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100803/836d4753/attachment-0001.html From shashikumar_249 at yahoo.co.in Tue Aug 10 05:33:34 2010 From: shashikumar_249 at yahoo.co.in (shashi kumar) Date: Tue, 10 Aug 2010 18:03:34 +0530 (IST) Subject: [Xorp-users] Reg:terminated with signal 25 xorp process Message-ID: <625668.61002.qm@web137312.mail.in.yahoo.com> Hi All, While I am running rtrmgr , my new process is getting killed after some time by throwing the following error Command "/xorp-1.6/newprocess": terminated with signal 25. ?could anyone 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/20100810/bbf34f60/attachment.html From greearb at candelatech.com Tue Aug 10 07:28:02 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 10 Aug 2010 07:28:02 -0700 Subject: [Xorp-users] Reg:terminated with signal 25 xorp process In-Reply-To: <625668.61002.qm@web137312.mail.in.yahoo.com> References: <625668.61002.qm@web137312.mail.in.yahoo.com> Message-ID: <4C6161F2.1050607@candelatech.com> On 08/10/2010 05:33 AM, shashi kumar wrote: > Hi All, > > While I am running rtrmgr , my new process is getting killed after some time by throwing the following error > > Command "/xorp-1.6/newprocess": terminated with signal 25. Run 'kill -l' to see what signal that is on your platform. Thanks, Ben > > could anyone please help me in this regard. > > 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 Tue Aug 10 14:22:30 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 10 Aug 2010 14:22:30 -0700 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <4C55F444.80109@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> <9924A386-F570-4E5D-9294-53A2E78A18B1@spacebugs.nl> <4C55F444.80109@candelatech.com> Message-ID: <4C61C316.3060209@candelatech.com> On 08/01/2010 03:25 PM, Ben Greear wrote: > >> Well the route message is solved but while testing the change further, by complete recreating the configs I noticed that there seems to be another issue, when I use a show command the permissions on files the /var/tmp directory are causing trouble: > > I haven't had time to make the permission changes yet. Patches welcome if someone else > has the time..otherwise, I'll try to get to it soon. Can you try top-of-tree xorp.ct? I added chmod logic that might fix your problem. Thanks, Ben > > Thanks, > Ben > -- Ben Greear Candela Technologies Inc http://www.candelatech.com From luca.belforte at student.uclouvain.be Wed Aug 11 16:49:05 2010 From: luca.belforte at student.uclouvain.be (Luca Belforte) Date: Thu, 12 Aug 2010 01:49:05 +0200 Subject: [Xorp-users] Xorp starting problem Message-ID: Hello everyone, Today i had a strange problem with xorp: [ 2010/08/12 01:40:45 ERROR xorp_fea:2450 FEA +450 fea/data_plane/ifconfig/ifconfig_set.cc push_interface_end ] Interface error on eth1: Failed to end interface configuration: Cannot set the interface flags to 0x1003 on interface eth1: AF_NETLINK NLMSG_ERROR message: Operation not supported [ 2010/08/12 01:40:45 WARNING xorp_fea XrlFeaTarget ] Handling method for ifmgr/0.1/commit_transaction failed: XrlCmdError 102 Command failed Interface error on eth1: Failed to end interface configuration: Cannot set the interface flags to 0x1003 on interface eth1: AF_NETLINK NLMSG_ERROR message: Operation not supported [ 2010/08/12 01:40:45 ERROR xorp_rtrmgr:2449 RTRMGR +674 rtrmgr/master_conf_tree.cc commit_pass2_done ] Commit failed: 102 Command failed Interface error on eth1: Failed to end interface configuration: Cannot set the interface flags to 0x1003 on interface eth1: AF_NETLINK NLMSG_ERROR message: Operation not supported [ 2010/08/12 01:40:45 ERROR xorp_rtrmgr:2449 RTRMGR +244 rtrmgr/master_conf_tree.cc config_done ] Configuration failed: 102 Command failed Interface error on eth1: Failed to end interface configuration: Cannot set the interface flags to 0x1003 on interface eth1: AF_NETLINK NLMSG_ERROR message: Operation not supported I run xorp 1.7 (last on the svn server) on a ubunut 9.04 in virtualbox. I have tried to reinstall xorp, cleain install. And on a clean image of ubuntu. (Xorp is started with sudo, and i tried different interface type on Virtualbox) I only added a little program in Xorp, but is a separate one (another executable), so the Xorp code is the same. Any idea? P.S. The configuration file is : /* R1 */ interfaces { interface eth1 { vif eth1 { address 10.10.10.10 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false } } protocols { ospf4 { router-id: 10.10.10.10 area 0.0.0.0 { interface eth1 { vif eth1 { address 10.10.10.10 { } } } } } } Realy easy one, who worked before on xorp 1.6 Thanks in advance * * * ------------------------------ Luca Belforte* -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100812/546ab9db/attachment.html From greearb at candelatech.com Wed Aug 11 16:55:25 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 11 Aug 2010 16:55:25 -0700 Subject: [Xorp-users] Xorp starting problem In-Reply-To: References: Message-ID: <4C63386D.6090800@candelatech.com> On 08/11/2010 04:49 PM, Luca Belforte wrote: > Hello everyone, > > Today i had a strange problem with xorp: Was it previously running fine in the same configuration? Any chance you could try xorp.ct top-of-tree? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From luca.belforte at student.uclouvain.be Wed Aug 11 17:00:32 2010 From: luca.belforte at student.uclouvain.be (Luca Belforte) Date: Thu, 12 Aug 2010 02:00:32 +0200 Subject: [Xorp-users] Xorp starting problem In-Reply-To: <4C63386D.6090800@candelatech.com> References: <4C63386D.6090800@candelatech.com> Message-ID: Well the same config fimle worked, on the same virtualbox instance, only xorp changed. The funny part is it worked like a month ago, only think changed is a new folder in xorp route and the upgrade to the last svn version (tried with the other version but same probleme). I will try the ct version. * * * ------------------------------ Luca Belforte* On Thu, Aug 12, 2010 at 1:55 AM, Ben Greear wrote: > On 08/11/2010 04:49 PM, Luca Belforte wrote: > >> Hello everyone, >> >> Today i had a strange problem with xorp: >> > > Was it previously running fine in the same configuration? > > Any chance you could try xorp.ct top-of-tree? > > 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/20100812/a41b4e56/attachment.html From srinivas.bandi at wipro.com Wed Aug 11 21:29:53 2010 From: srinivas.bandi at wipro.com (srinivas.bandi at wipro.com) Date: Thu, 12 Aug 2010 09:59:53 +0530 Subject: [Xorp-users] Problem to unsubscribe In-Reply-To: References: <4C63386D.6090800@candelatech.com> Message-ID: <6324F38CCF371D40AD68BF1439B6488404479CC7@BLR-EC-MBX04.wipro.com> Hi, I?m not able to unsubscribe to this mailing group. @Moderate, Kindly request you to remove my id (srinivas.bandi at wipro.com) from subscription list. Regards Bandi. Branch of Wipro Limited, Place of Commercial Register of the Branch: Kiel Commercial Registration Number of the branch : HRB 7178 KI VAT registration number - German Tax No:19/294/30609 Company name as Registered in Commercial Register : Wipro Limited (India) Zweigniederlassung Deutschland Legal form of the Company : Domestic Branch of the Foreign Limited liability Company. Company seat: Registered office at Doddakannelli, Sarjapur Road, Bangalore, India : 560 035. Tel : 91-80-28440011, Fax : 91-80-28440051, website: www.wipro.com Managing Director : Mr Azim H Premji Zweigniederlassung der Wipro Limited Registergericht: Kiel Handelsregisternummer: HRB 7178 KI Steuernummer: 19/294/30609 Firma laut Handelsregistereintrag: Wipro Limited (India) Zweigniederlassung Deutschland Rechtsform der Gesellschaft: inl?ndische Zweigniederlassung einer Aktiengesellschaft ausl?ndischen Rechts Sitz der Gesellschaft: Doddakannelli, Sarjapur Road, Bangalore, Indien 560 035 Tel. +91 80 28440011, Fax: +91 80 28440051, website: www.wipro.com Vorstandsvorsitzender: Azim H Premji The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100812/999428f5/attachment-0001.html From luca.belforte at student.uclouvain.be Thu Aug 12 02:37:14 2010 From: luca.belforte at student.uclouvain.be (Luca Belforte) Date: Thu, 12 Aug 2010 11:37:14 +0200 Subject: [Xorp-users] Xorp starting problem In-Reply-To: References: <4C63386D.6090800@candelatech.com> Message-ID: It work with xorp.ct ;) thanks a lot. * Luca Belforte* On Thu, Aug 12, 2010 at 2:00 AM, Luca Belforte < luca.belforte at student.uclouvain.be> wrote: > > Well the same config fimle worked, on the same virtualbox instance, only > xorp changed. > The funny part is it worked like a month ago, only think changed is a new > folder in xorp route and the upgrade to the last svn version (tried with the > other version but same probleme). > > I will try the ct version. > > * * > * > ------------------------------ > Luca Belforte* > > On Thu, Aug 12, 2010 at 1:55 AM, Ben Greear wrote: > >> On 08/11/2010 04:49 PM, Luca Belforte wrote: >> >>> Hello everyone, >>> >>> Today i had a strange problem with xorp: >>> >> >> Was it previously running fine in the same configuration? >> >> Any chance you could try xorp.ct top-of-tree? >> >> 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/20100812/64a47c16/attachment.html From edwin at spacebugs.nl Sun Aug 15 08:09:09 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Sun, 15 Aug 2010 17:09:09 +0200 Subject: [Xorp-users] Error writing to routing socket: No such process In-Reply-To: <4C61C316.3060209@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> <9924A386-F570-4E5D-9294-53A2E78A18B1@spacebugs.nl> <4C55F444.80109@candelatech.com> <4C61C316.3060209@candelatech.com> Message-ID: <5BB584A2-EB89-47C7-ABE0-1A4374A55ECF@spacebugs.nl> On Aug 10, 2010, at 11:22 PM, Ben Greear wrote: > On 08/01/2010 03:25 PM, Ben Greear wrote: >> >>> Well the route message is solved but while testing the change further, by complete recreating the configs I noticed that there seems to be another issue, when I use a show command the permissions on files the /var/tmp directory are causing trouble: >> >> I haven't had time to make the permission changes yet. Patches welcome if someone else >> has the time..otherwise, I'll try to get to it soon. > > Can you try top-of-tree xorp.ct? I added chmod logic that might fix your problem. I tested your changes and It works :-) Thanks a lot. Edwin > > Thanks, > Ben > >> >> 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 luca.belforte at student.uclouvain.be Sun Aug 15 09:58:55 2010 From: luca.belforte at student.uclouvain.be (Luca Belforte) Date: Sun, 15 Aug 2010 18:58:55 +0200 Subject: [Xorp-users] Xorp starting problem In-Reply-To: References: <4C63386D.6090800@candelatech.com> Message-ID: Hello, just a question about XORP.CT, it support OSPF ECMP? Otherwise is it normal if i have 3 route (with same cost) to a destination XORP i can't ping the destination? but if i broke one of the 3 route it work perfectly. Thanks * * * ------------------------------ Luca Belforte* On Thu, Aug 12, 2010 at 11:37 AM, Luca Belforte < luca.belforte at student.uclouvain.be> wrote: > > It work with xorp.ct ;) thanks a lot. > > * Luca Belforte* > > On Thu, Aug 12, 2010 at 2:00 AM, Luca Belforte < > luca.belforte at student.uclouvain.be> wrote: > >> >> Well the same config fimle worked, on the same virtualbox instance, only >> xorp changed. >> The funny part is it worked like a month ago, only think changed is a new >> folder in xorp route and the upgrade to the last svn version (tried with the >> other version but same probleme). >> >> I will try the ct version. >> >> * * >> * >> ------------------------------ >> Luca Belforte* >> >> On Thu, Aug 12, 2010 at 1:55 AM, Ben Greear wrote: >> >>> On 08/11/2010 04:49 PM, Luca Belforte wrote: >>> >>>> Hello everyone, >>>> >>>> Today i had a strange problem with xorp: >>>> >>> >>> Was it previously running fine in the same configuration? >>> >>> Any chance you could try xorp.ct top-of-tree? >>> >>> 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/20100815/f296e532/attachment.html From jmitchell at ll.mit.edu Mon Aug 16 07:33:49 2010 From: jmitchell at ll.mit.edu (Jeff Mitchell) Date: Mon, 16 Aug 2010 10:33:49 -0400 Subject: [Xorp-users] "Reloading" config Message-ID: <4C694C4D.8080001@ll.mit.edu> Hi there, AFAIK there is no option from outside xorpsh to write out a XORP config file and read it into a running XORP instance. However, if I write out a XORP config file and then use something like Expect to enter xorpsh and run the "load" command, followed by "commit", will this effectively perform such a "reload"? What limitations might I run into? For instance, if the configuration I am replacing the running configuration with is fairly different in terms of either running protocols, parameters to those protocols, or both? Thanks, Jeff From greearb at candelatech.com Mon Aug 16 08:21:11 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 16 Aug 2010 08:21:11 -0700 Subject: [Xorp-users] "Reloading" config In-Reply-To: <4C694C4D.8080001@ll.mit.edu> References: <4C694C4D.8080001@ll.mit.edu> Message-ID: <4C695767.8070206@candelatech.com> On 08/16/2010 07:33 AM, Jeff Mitchell wrote: > Hi there, > > AFAIK there is no option from outside xorpsh to write out a XORP config > file and read it into a running XORP instance. > > However, if I write out a XORP config file and then use something like > Expect to enter xorpsh and run the "load" command, followed by "commit", > will this effectively perform such a "reload"? One thing we noticed is that we needed to commit after un-loading old stuff, and again after loading the new stuff. Xorp.ct makes commit much faster, but it's still around 1 second for big changes on moderate machines. Some of those limitations may be removed in xorp.ct, but I haven't tried removing my intermediate 'commit' logic from my scripts. In xorp 1.6 and such, you are unlikely to have much luck with this as removing config often ran into assertions in FEA and the protocols. > What limitations might I run into? For instance, if the configuration I > am replacing the running configuration with is fairly different in terms > of either running protocols, parameters to those protocols, or both? Technically, I think it should handle anything you throw at it..and I'm interested in bug reports and/or patches if you find anything that breaks (in xorp.ct). Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From jmitchell at ll.mit.edu Mon Aug 16 09:29:07 2010 From: jmitchell at ll.mit.edu (Jeff Mitchell) Date: Mon, 16 Aug 2010 12:29:07 -0400 Subject: [Xorp-users] "Reloading" config In-Reply-To: <4C695767.8070206@candelatech.com> References: <4C694C4D.8080001@ll.mit.edu> <4C695767.8070206@candelatech.com> Message-ID: <4C696753.8040208@ll.mit.edu> I should have made it clear I'm on xorp.ct, fairly recent git. Comments inline: On 08/16/2010 11:21 AM, Ben Greear wrote: > On 08/16/2010 07:33 AM, Jeff Mitchell wrote: >> Hi there, >> >> AFAIK there is no option from outside xorpsh to write out a XORP config >> file and read it into a running XORP instance. >> >> However, if I write out a XORP config file and then use something like >> Expect to enter xorpsh and run the "load" command, followed by "commit", >> will this effectively perform such a "reload"? > > One thing we noticed is that we needed to commit after un-loading old stuff, > and again after loading the new stuff. Xorp.ct makes commit much faster, > but it's still around 1 second for big changes on moderate machines. > > Some of those limitations may be removed in xorp.ct, but I haven't > tried removing my intermediate 'commit' logic from my scripts. The xorp config file I need to use is getting generated dynamically...it'd be quite difficult to unload old stuff and then load the new stuff in. I think. Or is it? Any advice on the topic appreciated. Ideally, I'd be able to change configs over with minimal interruption to routing protocols and no packet loss for static routes. I am using the system routes within xorp, but if it does something like turns off IPv4 forwarding when one config is removed/committed and then only turns it back on when the next config is loaded/committed then that might be an issue. > In xorp 1.6 and such, you are unlikely to have much luck with this > as removing config often ran into assertions in FEA and the protocols. > >> What limitations might I run into? For instance, if the configuration I >> am replacing the running configuration with is fairly different in terms >> of either running protocols, parameters to those protocols, or both? > > Technically, I think it should handle anything you throw at it..and I'm > interested in bug reports and/or patches if you find anything that breaks > (in xorp.ct). Will certainly bug you about bugs. :-) Thanks, Jeff From greearb at candelatech.com Mon Aug 16 09:37:39 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 16 Aug 2010 09:37:39 -0700 Subject: [Xorp-users] "Reloading" config In-Reply-To: <4C696753.8040208@ll.mit.edu> References: <4C694C4D.8080001@ll.mit.edu> <4C695767.8070206@candelatech.com> <4C696753.8040208@ll.mit.edu> Message-ID: <4C696953.5040405@candelatech.com> On 08/16/2010 09:29 AM, Jeff Mitchell wrote: > I should have made it clear I'm on xorp.ct, fairly recent git. Comments > inline: > > On 08/16/2010 11:21 AM, Ben Greear wrote: >> One thing we noticed is that we needed to commit after un-loading old >> stuff, >> and again after loading the new stuff. Xorp.ct makes commit much faster, >> but it's still around 1 second for big changes on moderate machines. >> >> Some of those limitations may be removed in xorp.ct, but I haven't >> tried removing my intermediate 'commit' logic from my scripts. > > The xorp config file I need to use is getting generated > dynamically...it'd be quite difficult to unload old stuff and then load > the new stuff in. I think. Or is it? Yeah, it's not trivial..but you are going to have to do a 'diff' somehow, which means delete the un-needed stuff and add new. In my case, if I am going to change IP on an interface, I might just remove the interface completely (from the protocol sections) and then re-add it. Actually, xorpsh will do a 'diff' for you, but again, at least when I started, it was flaky unless I committed after deleting and before re-adding. Especially if you have time to debug and help fix things, you might try using xorpsh to do all the 'diff' logic and not worry about any extra commits..and just help fix bugs that might pop up. > Any advice on the topic appreciated. Ideally, I'd be able to change > configs over with minimal interruption to routing protocols and no > packet loss for static routes. I am using the system routes within xorp, > but if it does something like turns off IPv4 forwarding when one config > is removed/committed and then only turns it back on when the next config > is loaded/committed then that might be an issue. I don't think it would be that bad..but you'd want to do lots of testing to make sure it does what you want. Each protocol handles changes slightly different. We've dealt primarily with OSPF and multicast for dynamic changes..and those work pretty well in xorp.ct, but other protocols may be a bit more touchy still. I guess my suggestion would be to try to use xorpsh in the easiest manner possible, and see how that works. If you find bugs, maybe we can just fix them, and if not, you can start adding more commits and such to xorpsh to work around them. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From jmitchell at ll.mit.edu Mon Aug 16 09:40:36 2010 From: jmitchell at ll.mit.edu (Jeff Mitchell) Date: Mon, 16 Aug 2010 12:40:36 -0400 Subject: [Xorp-users] "Reloading" config In-Reply-To: <4C696953.5040405@candelatech.com> References: <4C694C4D.8080001@ll.mit.edu> <4C695767.8070206@candelatech.com> <4C696753.8040208@ll.mit.edu> <4C696953.5040405@candelatech.com> Message-ID: <4C696A04.9000804@ll.mit.edu> On 08/16/2010 12:37 PM, Ben Greear wrote: > On 08/16/2010 09:29 AM, Jeff Mitchell wrote: >> I should have made it clear I'm on xorp.ct, fairly recent git. Comments >> inline: >> >> On 08/16/2010 11:21 AM, Ben Greear wrote: > >>> One thing we noticed is that we needed to commit after un-loading old >>> stuff, >>> and again after loading the new stuff. Xorp.ct makes commit much faster, >>> but it's still around 1 second for big changes on moderate machines. >>> >>> Some of those limitations may be removed in xorp.ct, but I haven't >>> tried removing my intermediate 'commit' logic from my scripts. >> >> The xorp config file I need to use is getting generated >> dynamically...it'd be quite difficult to unload old stuff and then load >> the new stuff in. I think. Or is it? > > Yeah, it's not trivial..but you are going to have to do a 'diff' somehow, > which means delete the un-needed stuff and add new. > > In my case, if I am going to change IP on an interface, I might > just remove the interface completely (from the protocol sections) > and then re-add it. > > Actually, xorpsh will do a 'diff' for you, but again, at least when > I started, it was flaky unless I committed after deleting and before > re-adding. Especially if you have time to debug and help fix things, > you might try using xorpsh to do all the 'diff' logic and not worry > about any extra commits..and just help fix bugs that might pop up. Perhaps my best bet would be to keep the previous config file around, then to step through the relevant sections and remove that config from xorp, then switch to the new file and add that config to xorp? Thanks, Jeff From greearb at candelatech.com Mon Aug 16 09:44:29 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 16 Aug 2010 09:44:29 -0700 Subject: [Xorp-users] "Reloading" config In-Reply-To: <4C696A04.9000804@ll.mit.edu> References: <4C694C4D.8080001@ll.mit.edu> <4C695767.8070206@candelatech.com> <4C696753.8040208@ll.mit.edu> <4C696953.5040405@candelatech.com> <4C696A04.9000804@ll.mit.edu> Message-ID: <4C696AED.50904@candelatech.com> On 08/16/2010 09:40 AM, Jeff Mitchell wrote: > On 08/16/2010 12:37 PM, Ben Greear wrote: >> On 08/16/2010 09:29 AM, Jeff Mitchell wrote: >>> I should have made it clear I'm on xorp.ct, fairly recent git. Comments >>> inline: >>> >>> On 08/16/2010 11:21 AM, Ben Greear wrote: >> >>>> One thing we noticed is that we needed to commit after un-loading old >>>> stuff, >>>> and again after loading the new stuff. Xorp.ct makes commit much >>>> faster, >>>> but it's still around 1 second for big changes on moderate machines. >>>> >>>> Some of those limitations may be removed in xorp.ct, but I haven't >>>> tried removing my intermediate 'commit' logic from my scripts. >>> >>> The xorp config file I need to use is getting generated >>> dynamically...it'd be quite difficult to unload old stuff and then load >>> the new stuff in. I think. Or is it? >> >> Yeah, it's not trivial..but you are going to have to do a 'diff' somehow, >> which means delete the un-needed stuff and add new. >> >> In my case, if I am going to change IP on an interface, I might >> just remove the interface completely (from the protocol sections) >> and then re-add it. >> >> Actually, xorpsh will do a 'diff' for you, but again, at least when >> I started, it was flaky unless I committed after deleting and before >> re-adding. Especially if you have time to debug and help fix things, >> you might try using xorpsh to do all the 'diff' logic and not worry >> about any extra commits..and just help fix bugs that might pop up. > > Perhaps my best bet would be to keep the previous config file around, > then to step through the relevant sections and remove that config from > xorp, then switch to the new file and add that config to xorp? If xorpsh works according to design (and likely it does not in all cases), you *should* be able to remove everything, re-add everything you want, and then commit. Xorpsh would then make the appropriate changes. It has the logic to (attempt to) make the minimal set of changes for you. Getting this working makes xorp much easier to automate, so I'm willing to put some effort into fixing any issues you find..but, I don't have an over abundance of time, so no promises! Thanks, Ben > > Thanks, > Jeff -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Mon Aug 16 10:09:45 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 16 Aug 2010 10:09:45 -0700 Subject: [Xorp-users] Xorp starting problem In-Reply-To: References: <4C63386D.6090800@candelatech.com> Message-ID: <4C6970D9.9080604@candelatech.com> On 08/15/2010 09:58 AM, Luca Belforte wrote: > Hello, just a question about XORP.CT, it support OSPF ECMP? No, I don't think it does. At least, I haven't added it, and I don't think the old xorp did either. > > Otherwise is it normal if i have 3 route (with same cost) to a > destination XORP i can't ping the destination? but if i broke one of the > 3 route it work perfectly. That's not nearly enough information, but I'd expect it to route properly if properly configured. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From luca.belforte at student.uclouvain.be Mon Aug 16 10:44:32 2010 From: luca.belforte at student.uclouvain.be (Luca Belforte) Date: Mon, 16 Aug 2010 19:44:32 +0200 Subject: [Xorp-users] Xorp starting problem In-Reply-To: <4C6970D9.9080604@candelatech.com> References: <4C63386D.6090800@candelatech.com> <4C6970D9.9080604@candelatech.com> Message-ID: Ok for ECMP i have found nothing. In fact i only configured a network with 8 routers, realy simple only OSPF and using Linux forwarding. the topology is as following (sorry for the poor draw) R1 -------------------------- R2 | \ / | | R5-----------R6 | | | \ / | | | | X | | | | / \ | | | R7-----------R8 | | / \ | R3----------------------------R4 So basically two square, and each edge is connected with the same edge in the other square. All costs are 1. If i want to ping from R4 the interface on R5 facing R1 i have 3 possible path: R4 - R2 - R1 or R4 - R8 - R5 or R4 - R3 - R1 all costs 3. In this case ping doesn't work from R4. If put down one link, example R4 to R8, only two will remain, and in this case i can ping the interface. If i do not put down the link all the routers excepted for R4 can ping the interface R5-R1. I hope is a little bit clear. Thanks * * * ------------------------------ Luca Belforte* On Mon, Aug 16, 2010 at 7:09 PM, Ben Greear wrote: > On 08/15/2010 09:58 AM, Luca Belforte wrote: > >> Hello, just a question about XORP.CT, it support OSPF ECMP? >> > > No, I don't think it does. At least, I haven't added it, and I don't > think the old xorp did either. > > > >> Otherwise is it normal if i have 3 route (with same cost) to a >> destination XORP i can't ping the destination? but if i broke one of the >> 3 route it work perfectly. >> > > That's not nearly enough information, but I'd expect > it to route properly if properly configured. > > > 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/20100816/6b130354/attachment-0001.html From greearb at candelatech.com Mon Aug 16 10:55:40 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 16 Aug 2010 10:55:40 -0700 Subject: [Xorp-users] Xorp starting problem In-Reply-To: References: <4C63386D.6090800@candelatech.com> <4C6970D9.9080604@candelatech.com> Message-ID: <4C697B9C.1000106@candelatech.com> On 08/16/2010 10:44 AM, Luca Belforte wrote: > Ok for ECMP i have found nothing. > > In fact i only configured a network with 8 routers, realy simple only > OSPF and using Linux forwarding. > > the topology is as following (sorry for the poor draw) > > R1 -------------------------- R2 > | \ / | > | R5-----------R6 | > | | \ / | | > | | X | | > | | / \ | | > | R7-----------R8 | > | / \ | > R3----------------------------R4 > > So basically two square, and each edge is connected with the same edge > in the other square. All costs are 1. > If i want to ping from R4 the interface on R5 facing R1 i have 3 > possible path: R4 - R2 - R1 or R4 - R8 - R5 or R4 - R3 - R1 all costs > 3. In this case ping doesn't work from R4. If put down one link, example > R4 to R8, only two will remain, and in this case i can ping the interface. > > If i do not put down the link all the routers excepted for R4 can ping > the interface R5-R1. > > I hope is a little bit clear. Yes, thanks. This should work with normal OSPF as far as I can tell. To debug, you will probably need to investigate each router in the path and check to see which one has improper routes. Traceroute might be a quick way to get started on this. Then, check the xorp neighbors and other info to see which router is broken. Maybe it's a config issue..or maybe a bug. Plz let us know which version(s) of xorp are you using when finding this problem. I can only help with potential coding bugs if you are using xorp.ct. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Mon Aug 16 11:01:07 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 16 Aug 2010 11:01:07 -0700 Subject: [Xorp-users] xorp problem reporting & questions guidelines Message-ID: <4C697CE3.6010906@candelatech.com> For anyone asking questions or reporting issues with xorp, please state near top of email what version of xorp (or xorp.ct) you are using, and what OS (and hardware platform, if non x86). If replying to such an email, please don't delete that information. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From luca.belforte at student.uclouvain.be Mon Aug 16 13:21:46 2010 From: luca.belforte at student.uclouvain.be (Luca Belforte) Date: Mon, 16 Aug 2010 22:21:46 +0200 Subject: [Xorp-users] Xorp starting problem In-Reply-To: <4C697B9C.1000106@candelatech.com> References: <4C63386D.6090800@candelatech.com> <4C6970D9.9080604@candelatech.com> <4C697B9C.1000106@candelatech.com> Message-ID: I'm using xorp.ct, i get on the git, no sure about the version but it was downloaded 3 days ago. The route on all routers are correct, traceroute block on the 2 hop. (If i'm pinging R1 to R8-R4 interface it stop on R2) but if i do a traceroute on R2 it works. All tables are correct and show the correct next-hop. Neighbors are all well established What is more amazing is that sometimes it works for let's say 5-10 traceroute and after it stop again to work. configuration are really basic, only attach an ip to the interface and activate ospf: the R1 configuration is: /* R1 */ interfaces { interface eth0 { vif eth0 { address 10.1.0.1 { prefix-length: 24 } } } interface eth1 { vif eth1 { address 10.4.0.2 { prefix-length: 24 } } } interface eth2 { vif eth2 { address 10.5.0.1 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false } } protocols { ospf4 { router-id: 10.1.0.1 area 0.0.0.0 { interface eth0 { vif eth0 { address 10.1.0.1 { } } } interface eth1 { vif eth1 { address 10.4.0.2 { } } } interface eth2 { vif eth2 { address 10.5.0.1 { } } } } } } The others routers have similar configuration. Well maybe is the virtualbox internal network who have problems. In any case for my test this is not really problematic. * * * ------------------------------ Luca Belforte* On Mon, Aug 16, 2010 at 7:55 PM, Ben Greear wrote: > On 08/16/2010 10:44 AM, Luca Belforte wrote: > >> Ok for ECMP i have found nothing. >> >> In fact i only configured a network with 8 routers, realy simple only >> OSPF and using Linux forwarding. >> >> the topology is as following (sorry for the poor draw) >> >> R1 -------------------------- R2 >> | \ / | >> | R5-----------R6 | >> | | \ / | | >> | | X | | >> | | / \ | | >> | R7-----------R8 | >> | / \ | >> R3----------------------------R4 >> >> So basically two square, and each edge is connected with the same edge >> in the other square. All costs are 1. >> If i want to ping from R4 the interface on R5 facing R1 i have 3 >> possible path: R4 - R2 - R1 or R4 - R8 - R5 or R4 - R3 - R1 all costs >> 3. In this case ping doesn't work from R4. If put down one link, example >> R4 to R8, only two will remain, and in this case i can ping the interface. >> >> If i do not put down the link all the routers excepted for R4 can ping >> the interface R5-R1. >> >> I hope is a little bit clear. >> > > Yes, thanks. This should work with normal OSPF as far as I can > tell. > > To debug, you will probably need to investigate each router in the > path and check to see which one has improper routes. Traceroute might > be a quick way to get started on this. > > Then, check the xorp neighbors and other info to see which router > is broken. Maybe it's a config issue..or maybe a bug. > > Plz let us know which version(s) of xorp are you using when > finding this problem. I can only help with potential coding bugs > if you are using xorp.ct. > > > 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/20100816/2bd2a997/attachment.html From greearb at candelatech.com Mon Aug 16 13:43:52 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 16 Aug 2010 13:43:52 -0700 Subject: [Xorp-users] Xorp starting problem In-Reply-To: References: <4C63386D.6090800@candelatech.com> <4C6970D9.9080604@candelatech.com> <4C697B9C.1000106@candelatech.com> Message-ID: <4C69A308.4080306@candelatech.com> On 08/16/2010 01:21 PM, Luca Belforte wrote: > I'm using xorp.ct, i get on the git, no sure about the version but it > was downloaded 3 days ago. Thanks..as long as it's relatively current, it should be fine. > The route on all routers are correct, traceroute block on the 2 hop. (If > i'm pinging R1 to R8-R4 interface it stop on R2) but if i do a > traceroute on R2 it works. All tables are correct and show the correct > next-hop. Neighbors are all well established > What is more amazing is that sometimes it works for let's say 5-10 > traceroute and after it stop again to work. You might try: ip monitor (or similar command if you are not on Linux) and see if routes are flapping. Also, I'd start some sniffers on R2..if it receives a pkt, and has proper route, then it should forward it regardless of any other xorp behaviour, as xorp is NOT in the packet forwarding path for normal IP traffic. You might also sniff all interfaces to make sure it forwards out the correct one. > The others routers have similar configuration. > > Well maybe is the virtualbox internal network who have problems. In any > case for my test this is not really problematic. It would be good to verify with real hardware or some different virtualization technique. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From luca.belforte at student.uclouvain.be Mon Aug 16 14:04:11 2010 From: luca.belforte at student.uclouvain.be (Luca Belforte) Date: Mon, 16 Aug 2010 23:04:11 +0200 Subject: [Xorp-users] Xorp starting problem In-Reply-To: <4C69A308.4080306@candelatech.com> References: <4C63386D.6090800@candelatech.com> <4C6970D9.9080604@candelatech.com> <4C697B9C.1000106@candelatech.com> <4C69A308.4080306@candelatech.com> Message-ID: I will make some other test, but i can't test on a real hardware. * * * ------------------------------ Luca Belforte* On Mon, Aug 16, 2010 at 10:43 PM, Ben Greear wrote: > On 08/16/2010 01:21 PM, Luca Belforte wrote: > >> I'm using xorp.ct, i get on the git, no sure about the version but it >> was downloaded 3 days ago. >> > > Thanks..as long as it's relatively current, it should be fine. > > > The route on all routers are correct, traceroute block on the 2 hop. (If >> i'm pinging R1 to R8-R4 interface it stop on R2) but if i do a >> traceroute on R2 it works. All tables are correct and show the correct >> next-hop. Neighbors are all well established >> What is more amazing is that sometimes it works for let's say 5-10 >> traceroute and after it stop again to work. >> > > You might try: ip monitor (or similar command if you are not on Linux) > and see if routes are flapping. > > Also, I'd start some sniffers on R2..if it receives a pkt, and has > proper route, then it should forward it regardless of any other xorp > behaviour, as xorp is NOT in the packet forwarding path for normal > IP traffic. > > You might also sniff all interfaces to make sure it forwards out the > correct one. > > > The others routers have similar configuration. >> >> Well maybe is the virtualbox internal network who have problems. In any >> case for my test this is not really problematic. >> > > It would be good to verify with real hardware or some different > virtualization > technique. > > > 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/20100816/9a63ca0e/attachment.html From greearb at candelatech.com Mon Aug 16 19:06:21 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 16 Aug 2010 19:06:21 -0700 Subject: [Xorp-users] Some recent xorp.ct improvements. Message-ID: <4C69EE9D.9030606@candelatech.com> Today I finished up some xorp.ct bugs I've been meaning to fix for a while. With these in, I'm planning to do some testing and if all goes well, put out an official point release (probably 1.8.3). Here's my list of notable changes/fixes since the 1.8 release: * Add more options for disabling compile of certain modules. See: scons --help * Add support for IPv6 multicast with virtual routing tables. Requires Linux kernel 2.6.35 or higher. * Support compiling with clang + llvm compiler: Install latest clang and llvm from their SVN repositories and: scons CC=clang CXX=clang++ * Add some changes to make it easier to support uSTL, but it does not actually work as uSTL had too many limitations and bugs, and didn't seem to gain much space improvements anyway. See BUILD_NOTES for more info. * Support cross-compiling. See BUILD_NOTES. * BSD: Don't crash FEA when interface disappears. * BSD: Don't fail commit if cannot remove route that doesn't exist. * Add signal handling for more graceful exit. Helps clean up /var/tmp/xrl.* files and lets valgrind report more useful information. * timers: Fix memory leak related to the Heap class. * BGP: Fix up tear-down logic to make sure it exits promptly in all cases. * pim: Fix a recursive delete issue in pim code, exposed by the ability to gracefully shut down processes with SIGTERM. * rtrmgr: Allow starting helper processes under valgrind. Just create a file called XORP_USE_VALGRIND in the working directory. If you want xorp_rtrmgr to use valgrind, you have to start it under valgrind manually. For those of you that are able, please test out the xorp.ct top of tree and report any problems (and successes) you might find. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Mon Aug 16 22:06:37 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 16 Aug 2010 22:06:37 -0700 Subject: [Xorp-users] Report: XORP-CT cross-compilation with PPC In-Reply-To: References: <4C4070A3.1050404@candelatech.com> Message-ID: <4C6A18DD.8020602@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. I just pushed an attempt to fix the endian-ness problem you found. If you get a chance, could you try the latest xorp.ct and see if it properly detects endian-ness w/out your explicit over-ride? Basically, it should work if you have , but otherwise, you'll still need the override. I also added a check in xorp_rtrmgr that should detect invalid endian-ness detection at runtime, so at least there shouldn't be supprises now. I don't have anything other than x86 to test this on, however. I also added the hack to detect RAW IP output for 'linux-uclibc', but that really needs a better fix someday. If you have any further improvements to share, please post them. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Tue Aug 17 06:26:09 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Tue, 17 Aug 2010 15:26:09 +0200 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: References: Message-ID: Hello Ben, On FreeBSD 8.0-RELEASE AMD64 running under Vmware Fusion (Version 3.1.1 (282344) ) I receive the following core dump after compiling the sources: /usr/local/xorp/sbin/xorp_rtrmgr -b /root/vrd/edwin/R4/boot/config.boot Assertion failed: (0x12345678 == htonl(0x12345678)), function main, file rtrmgr/main_rtrmgr.cc, line 536. Abort trap: 6 (core dumped) Edwin > > > Today I finished up some xorp.ct bugs I've been meaning to fix for a while. > > With these in, I'm planning to do some testing and if all goes well, put > out an official point release (probably 1.8.3). > > Here's my list of notable changes/fixes since the 1.8 release: > > * Add more options for disabling compile of certain modules. > See: scons --help > > * Add support for IPv6 multicast with virtual routing tables. > Requires Linux kernel 2.6.35 or higher. > > * Support compiling with clang + llvm compiler: > Install latest clang and llvm from their SVN repositories and: > scons CC=clang CXX=clang++ > > * Add some changes to make it easier to support uSTL, but it does not > actually work as uSTL had too many limitations and bugs, and didn't seem > to gain much space improvements anyway. > See BUILD_NOTES for more info. > > * Support cross-compiling. See BUILD_NOTES. > > * BSD: Don't crash FEA when interface disappears. > > * BSD: Don't fail commit if cannot remove route that doesn't exist. > > * Add signal handling for more graceful exit. Helps clean up /var/tmp/xrl.* > files and lets valgrind report more useful information. > > * timers: Fix memory leak related to the Heap class. > > * BGP: Fix up tear-down logic to make sure it exits promptly in > all cases. > > * pim: Fix a recursive delete issue in pim code, exposed by the ability to > gracefully shut down processes with SIGTERM. > > * rtrmgr: Allow starting helper processes under valgrind. Just > create a file called XORP_USE_VALGRIND in the working directory. > If you want xorp_rtrmgr to use valgrind, you have to start it under > valgrind manually. > > For those of you that are able, please test out the xorp.ct top of tree and report > any problems (and successes) you might find. > > 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/20100817/2c35ccd0/attachment.html From greearb at candelatech.com Tue Aug 17 08:03:50 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 17 Aug 2010 08:03:50 -0700 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: References: Message-ID: <4C6AA4D6.70903@candelatech.com> On 08/17/2010 06:26 AM, Edwin Schokkenbroek wrote: > Hello Ben, > > On FreeBSD 8.0-RELEASE AMD64 running under Vmware Fusion (Version 3.1.1 (282344) ) I receive the following core dump after compiling the sources: > > /usr/local/xorp/sbin/xorp_rtrmgr -b /root/vrd/edwin/R4/boot/config.boot > Assertion failed: (0x12345678 == htonl(0x12345678)), function main, file rtrmgr/main_rtrmgr.cc, line 536. > Abort trap: 6 (core dumped) Thanks for testing. I must have messed up the endian-ness stuff I did last night. Can you check to see if you have on your compile system? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Tue Aug 17 08:10:55 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Tue, 17 Aug 2010 17:10:55 +0200 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <4C6AA4D6.70903@candelatech.com> References: <4C6AA4D6.70903@candelatech.com> Message-ID: <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> On Aug 17, 2010, at 5:03 PM, Ben Greear wrote: > On 08/17/2010 06:26 AM, Edwin Schokkenbroek wrote: >> Hello Ben, >> >> On FreeBSD 8.0-RELEASE AMD64 running under Vmware Fusion (Version 3.1.1 (282344) ) I receive the following core dump after compiling the sources: >> >> /usr/local/xorp/sbin/xorp_rtrmgr -b /root/vrd/edwin/R4/boot/config.boot >> Assertion failed: (0x12345678 == htonl(0x12345678)), function main, file rtrmgr/main_rtrmgr.cc, line 536. >> Abort trap: 6 (core dumped) > > Thanks for testing. I must have messed up the endian-ness stuff I did last night. > > Can you check to see if you have on your compile system? beastie# find / -name 'endian.h' /usr/include/machine/endian.h /usr/include/netatalk/endian.h /usr/include/sys/endian.h /usr/src/sys/amd64/include/endian.h /usr/src/sys/arm/include/endian.h /usr/src/sys/i386/include/endian.h /usr/src/sys/ia64/include/endian.h /usr/src/sys/mips/include/endian.h /usr/src/sys/pc98/include/endian.h /usr/src/sys/powerpc/include/endian.h /usr/src/sys/sparc64/include/endian.h /usr/src/sys/sun4v/include/endian.h /usr/src/sys/sys/endian.h /usr/src/sys/netatalk/endian.h /usr/src/contrib/openbsm/compat/endian.h Edwin > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Tue Aug 17 09:14:34 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 17 Aug 2010 09:14:34 -0700 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> Message-ID: <4C6AB56A.6060705@candelatech.com> On 08/17/2010 08:10 AM, Edwin Schokkenbroek wrote: > > On Aug 17, 2010, at 5:03 PM, Ben Greear wrote: > >> On 08/17/2010 06:26 AM, Edwin Schokkenbroek wrote: >>> Hello Ben, >>> >>> On FreeBSD 8.0-RELEASE AMD64 running under Vmware Fusion (Version 3.1.1 (282344) ) I receive the following core dump after compiling the sources: >>> >>> /usr/local/xorp/sbin/xorp_rtrmgr -b /root/vrd/edwin/R4/boot/config.boot >>> Assertion failed: (0x12345678 == htonl(0x12345678)), function main, file rtrmgr/main_rtrmgr.cc, line 536. >>> Abort trap: 6 (core dumped) >> >> Thanks for testing. I must have messed up the endian-ness stuff I did last night. >> >> Can you check to see if you have on your compile system? Can you try the latest xorp.ct please? I think I have a fix in place now. I need to get my BSD system in build-bot, and then will see if I can get BSD to use so we don't depend on the scons CheckEndian logic, which is broken for cross-compiles. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Tue Aug 17 11:28:43 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Tue, 17 Aug 2010 20:28:43 +0200 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <4C6AB56A.6060705@candelatech.com> References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> <4C6AB56A.6060705@candelatech.com> Message-ID: <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> On Aug 17, 2010, at 6:14 PM, Ben Greear wrote: > On 08/17/2010 08:10 AM, Edwin Schokkenbroek wrote: >> >> On Aug 17, 2010, at 5:03 PM, Ben Greear wrote: >> >>> On 08/17/2010 06:26 AM, Edwin Schokkenbroek wrote: >>>> Hello Ben, >>>> >>>> On FreeBSD 8.0-RELEASE AMD64 running under Vmware Fusion (Version 3.1.1 (282344) ) I receive the following core dump after compiling the sources: >>>> >>>> /usr/local/xorp/sbin/xorp_rtrmgr -b /root/vrd/edwin/R4/boot/config.boot >>>> Assertion failed: (0x12345678 == htonl(0x12345678)), function main, file rtrmgr/main_rtrmgr.cc, line 536. >>>> Abort trap: 6 (core dumped) >>> >>> Thanks for testing. I must have messed up the endian-ness stuff I did last night. >>> >>> Can you check to see if you have on your compile system? > > Can you try the latest xorp.ct please? I think I have a fix in place > now. Compiled the latest source and I was able to start xorp_rtrmgr again :-) BGP and OSPF seems to work fine to. Thanks ! Edwin > > I need to get my BSD system in build-bot, and then will see if I can get > BSD to use so we don't depend on the scons CheckEndian logic, > which is broken for cross-compiles. > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Tue Aug 17 12:15:52 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Tue, 17 Aug 2010 21:15:52 +0200 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> <4C6AB56A.6060705@candelatech.com> <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> Message-ID: On Aug 17, 2010, at 8:28 PM, Edwin Schokkenbroek wrote: > > On Aug 17, 2010, at 6:14 PM, Ben Greear wrote: > >> On 08/17/2010 08:10 AM, Edwin Schokkenbroek wrote: >>> >>> On Aug 17, 2010, at 5:03 PM, Ben Greear wrote: >>> >>>> On 08/17/2010 06:26 AM, Edwin Schokkenbroek wrote: >>>>> Hello Ben, >>>>> >>>>> On FreeBSD 8.0-RELEASE AMD64 running under Vmware Fusion (Version 3.1.1 (282344) ) I receive the following core dump after compiling the sources: >>>>> >>>>> /usr/local/xorp/sbin/xorp_rtrmgr -b /root/vrd/edwin/R4/boot/config.boot >>>>> Assertion failed: (0x12345678 == htonl(0x12345678)), function main, file rtrmgr/main_rtrmgr.cc, line 536. >>>>> Abort trap: 6 (core dumped) >>>> >>>> Thanks for testing. I must have messed up the endian-ness stuff I did last night. >>>> >>>> Can you check to see if you have on your compile system? >> >> Can you try the latest xorp.ct please? I think I have a fix in place >> now. > > Compiled the latest source and I was able to start xorp_rtrmgr again :-) BGP and OSPF seems to work fine to. Thanks ! > > Edwin > Maybe I was to enthusiast I tested with a wrong version .. sorry about that. What I noticed is now that I use the latest compiled version, that I receive messages like: [ 2010/08/17 21:01:01 ERROR xorpsh:4089 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 19999): Connection refused [ 2010/08/17 21:01:01 ERROR xorpsh:4089 FINDER +390 finder_tcp_messenger.cc do_auto_connect ] Failed to connect to 127.0.0.1/19999: Connection refused Waiting for xorp_rtrmgr... [ 2010/08/17 21:01:10 ERROR xorpsh:4089 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 19999): Connection refused [ 2010/08/17 21:01:10 ERROR xorpsh:4089 FINDER +390 finder_tcp_messenger.cc do_auto_connect ] Failed to connect to 127.0.0.1/19999: Connection refused Which tells me the xorp_rtrmgr is not started (or failed to start) for some reason. I start the xorp_rtrmgr from a script, and when I start the xorp_rtrmgr manual (from the command line) with the same config file .. the xorp_rtrmgr just starts. When I use the xorp version builds from the ports of FreeBSD (and earlier builds of xorp.ct) it just works .. as in I can start xorp_rtrmgr from my script. Don't know what is causing this. I'm searching at this moment. Hopefully a log file will tell me what is going on.... Edwin >> >> I need to get my BSD system in build-bot, and then will see if I can get >> BSD to use so we don't depend on the scons CheckEndian logic, >> which is broken for cross-compiles. >> >> Thanks, >> Ben >> >> -- >> Ben Greear >> Candela Technologies Inc http://www.candelatech.com > > > > > > > From edwin at spacebugs.nl Tue Aug 17 13:00:22 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Tue, 17 Aug 2010 22:00:22 +0200 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> <4C6AB56A.6060705@candelatech.com> <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> Message-ID: <4E5642C7-03A6-48FC-AF1D-B8B6A22A7E98@spacebugs.nl> On Aug 17, 2010, at 9:15 PM, Edwin Schokkenbroek wrote: > > On Aug 17, 2010, at 8:28 PM, Edwin Schokkenbroek wrote: > >> >> On Aug 17, 2010, at 6:14 PM, Ben Greear wrote: >> >>> On 08/17/2010 08:10 AM, Edwin Schokkenbroek wrote: >>>> >>>> On Aug 17, 2010, at 5:03 PM, Ben Greear wrote: >>>> >>>>> On 08/17/2010 06:26 AM, Edwin Schokkenbroek wrote: >>>>>> Hello Ben, >>>>>> >>>>>> On FreeBSD 8.0-RELEASE AMD64 running under Vmware Fusion (Version 3.1.1 (282344) ) I receive the following core dump after compiling the sources: >>>>>> >>>>>> /usr/local/xorp/sbin/xorp_rtrmgr -b /root/vrd/edwin/R4/boot/config.boot >>>>>> Assertion failed: (0x12345678 == htonl(0x12345678)), function main, file rtrmgr/main_rtrmgr.cc, line 536. >>>>>> Abort trap: 6 (core dumped) >>>>> >>>>> Thanks for testing. I must have messed up the endian-ness stuff I did last night. >>>>> >>>>> Can you check to see if you have on your compile system? >>> >>> Can you try the latest xorp.ct please? I think I have a fix in place >>> now. >> >> Compiled the latest source and I was able to start xorp_rtrmgr again :-) BGP and OSPF seems to work fine to. Thanks ! >> >> Edwin >> > > Maybe I was to enthusiast I tested with a wrong version .. sorry about that. What I noticed is now that I use the latest compiled version, that I receive messages like: > > [ 2010/08/17 21:01:01 ERROR xorpsh:4089 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 19999): Connection refused > [ 2010/08/17 21:01:01 ERROR xorpsh:4089 FINDER +390 finder_tcp_messenger.cc do_auto_connect ] Failed to connect to 127.0.0.1/19999: Connection refused > Waiting for xorp_rtrmgr... > [ 2010/08/17 21:01:10 ERROR xorpsh:4089 LIBCOMM +610 comm_sock.c comm_sock_connect4 ] Error connecting socket (family = 2, remote_addr = 127.0.0.1, remote_port = 19999): Connection refused > [ 2010/08/17 21:01:10 ERROR xorpsh:4089 FINDER +390 finder_tcp_messenger.cc do_auto_connect ] Failed to connect to 127.0.0.1/19999: Connection refused > > > Which tells me the xorp_rtrmgr is not started (or failed to start) for some reason. > > I start the xorp_rtrmgr from a script, and when I start the xorp_rtrmgr manual (from the command line) with the same config file .. the xorp_rtrmgr just starts. When I use the xorp version builds from the ports of FreeBSD (and earlier builds of xorp.ct) it just works .. as in I can start xorp_rtrmgr from my script. > > Don't know what is causing this. I'm searching at this moment. Hopefully a log file will tell me what is going on.... > > Edwin > > Hmm not sure what is going on ... If I look in the log file I see the following messages: [ 2010/08/17 21:46:27.835350 ERROR xorp_rtrmgr:3761 LIBCOMM libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address [ 2010/08/17 21:46:27.837998 ERROR xorp_rtrmgr:3761 RTRMGR rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder may already be running. Some extra information: > beastie# jexec R10 /usr/local/xorp/sbin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R10/boot/config.boot -P /xorp_rtrmgr.pid -d[ 2010/08/17 21:54:31.401294 ERROR xorp_rtrmgr:3783 LIBCOMM libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address > [ 2010/08/17 21:54:31.403459 ERROR xorp_rtrmgr:3783 RTRMGR rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder may already be running. > beastie# When activating a shell in the jail R10: beastie# jexec R10 bash [root at R10 /]# ps ax PID TT STAT TIME COMMAND 3800 2 SJ 0:00.02 bash 3801 2 R+J 0:00.00 ps ax [root at R10 /]# root at R10 /]# ifconfig lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff000000 epair1b: flags=8843 metric 0 mtu 1500 ether 02:00:00:00:07:0b inet 10.1.100.2 netmask 0xfffffffc broadcast 10.1.100.3 inet6 fe80::ff:fe00:70b%epair1b prefixlen 64 scopeid 0x2 epair4b: flags=8843 metric 0 mtu 1500 ether 02:00:00:00:07:0b inet 10.1.100.14 netmask 0xfffffffc broadcast 10.1.100.15 inet6 fe80::ff:fe00:70b%epair4b prefixlen 64 scopeid 0x3 ebr0: flags=8843 metric 0 mtu 1500 ether 00:16:3e:a0:b9:ef inet6 fe80::30df:7d55:41bc:941%ebr0 prefixlen 64 scopeid 0x4 inet 10.1.3.10 netmask 0xffffff00 broadcast 10.1.3.255 ebr1: flags=8802 metric 0 mtu 1500 ether 00:00:00:00:00:00 When I start Xorp (build from the ports) : beastie# jexec R10 /usr/local/bin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R10/boot/config.boot -P /xorp_rtrmgr.pid -d [ 2010/08/17 21:57:14 INFO xorp_rtrmgr:3803 RTRMGR +249 master_conf_tree.cc execute ] Changed modules: interfaces, rtrmgr, firewall, fea, rib, policy, bgp, ospf4 [ 2010/08/17 21:57:14 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: interfaces (fea/xorp_fea) [ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] MFEA enabled [ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] CLI enabled [ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] CLI started [ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] MFEA enabled [ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] CLI enabled [ 2010/08/17 21:57:15 INFO xorp_fea MFEA ] CLI started [ 2010/08/17 21:57:16 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: rtrmgr () [ 2010/08/17 21:57:23 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: firewall (fea/xorp_fea) [ 2010/08/17 21:57:27 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: fea (fea/xorp_fea) [ 2010/08/17 21:57:31 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: rib (rib/xorp_rib) [ 2010/08/17 21:57:33 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: policy (policy/xorp_policy) [ 2010/08/17 21:57:35 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: bgp (bgp/xorp_bgp) [ 2010/08/17 21:57:39 INFO xorp_rtrmgr:3803 RTRMGR +101 module_manager.cc execute ] Executing module: ospf4 (ospf/xorp_ospfv2) [ 2010/08/17 21:57:41 INFO xorp_rtrmgr:3803 RTRMGR +2233 task.cc run_task ] No more tasks to run In the jail xorp_rtrmgr is running : beastie# jexec R10 bash [root at R10 /]# ps ax PID TT STAT TIME COMMAND 3809 ?? SsJ 0:00.16 /usr/local/bin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R 3804 2 SJ 0:01.21 xorp_fea 3805 2 SJ 0:00.30 xorp_rib 3806 2 SJ 0:00.09 xorp_policy 3807 2 SJ 0:00.53 xorp_bgp 3808 2 SJ 0:00.34 xorp_ospfv2 3810 2 SJ 0:00.06 bash 3811 2 R+J 0:00.00 ps ax Edwin > > > > > > > > > >>> >>> I need to get my BSD system in build-bot, and then will see if I can get >>> BSD to use so we don't depend on the scons CheckEndian logic, >>> which is broken for cross-compiles. >>> >>> 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/20100817/c32a49fd/attachment-0001.html From greearb at candelatech.com Tue Aug 17 14:30:28 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 17 Aug 2010 14:30:28 -0700 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <4E5642C7-03A6-48FC-AF1D-B8B6A22A7E98@spacebugs.nl> References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> <4C6AB56A.6060705@candelatech.com> <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> <4E5642C7-03A6-48FC-AF1D-B8B6A22A7E98@spacebugs.nl> Message-ID: <4C6AFF74.6050302@candelatech.com> On 08/17/2010 01:00 PM, Edwin Schokkenbroek wrote: > Hmm not sure what is going on ... If I look in the log file I see the > following messages: > > [ 2010/08/17 21:46:27.835350 ERROR xorp_rtrmgr:3761 LIBCOMM > libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = > 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address > [ 2010/08/17 21:46:27.837998 ERROR xorp_rtrmgr:3761 RTRMGR > rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder > may already be running. Can you make sure you have a clean compile? That looks like endian-ness issues again. Maybe rm -fr the 'obj' dir and rebuild fresh? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Wed Aug 18 04:27:29 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 18 Aug 2010 13:27:29 +0200 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <4C6AFF74.6050302@candelatech.com> References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> <4C6AB56A.6060705@candelatech.com> <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> <4E5642C7-03A6-48FC-AF1D-B8B6A22A7E98@spacebugs.nl> <4C6AFF74.6050302@candelatech.com> Message-ID: <43C4A3D2-364F-42CE-9723-839150EE7E29@spacebugs.nl> On Aug 17, 2010, at 11:30 PM, Ben Greear wrote: > On 08/17/2010 01:00 PM, Edwin Schokkenbroek wrote: > >> Hmm not sure what is going on ... If I look in the log file I see the >> following messages: >> >> [ 2010/08/17 21:46:27.835350 ERROR xorp_rtrmgr:3761 LIBCOMM >> libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = >> 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address >> [ 2010/08/17 21:46:27.837998 ERROR xorp_rtrmgr:3761 RTRMGR >> rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder >> may already be running. > > Can you make sure you have a clean compile? That looks like endian-ness issues > again. Maybe rm -fr the 'obj' dir and rebuild fresh? I removed the obj directory, recompiled to source and I receive another error. This time the xorp_rtrtmgr seems to start. But xorpsh bails out. : jexec R4 /usr/local/xorp/sbin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R4/boot/config.boot -l /root/chaos/vrd/edwin/R4/var/R4.log -P /root/chaos/vrd/edwin/R4/var/run/xorp_rtrmgr.pid -d beastie# jexec R4 xorpsh [ 2010/08/18 13:16:29 ERROR xorpsh:4131 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" beastie# [ 2010/08/18 13:01:05 ERROR xorpsh:3972 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" Note sure why xorpsh bails out with a parse error. The xorp_rtrmgr is running: beastie# jexec R4 bash [root at R4 /]# ps ax PID TT STAT TIME COMMAND 3970 ?? SsJ 0:00.06 /usr/local/xorp/sbin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R4/boot/config.boot -l / 3965 0 SJ 0:00.43 xorp_fea 3966 0 SJ 0:00.20 xorp_rib 3967 0 SJ 0:00.08 xorp_policy 3968 0 SJ 0:00.21 xorp_bgp 3969 0 SJ 0:00.17 xorp_ospfv2 3983 1 SJ 0:00.04 bash 3984 1 R+J 0:00.01 ps ax When I start xorpsh with the verbose flag the output is: beastie# jexec R4 xorpsh -v [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] XORP root directory := /usr/local [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] Templates directory := /usr/local/etc/templates [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] Xrl targets directory := /usr/local/xrl/targets [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] Print verbose information := true [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] rtrmgr PID=3970 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] Registry with rtrmgr successful: token is /tmp/rtrmgr-xorpsh-4133-R4 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] authtoken = > 0xorpsh-4133-R4**************************b8178353d1d5e84321c0fbbdd053f612< [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] Waiting to receive configuration from rtrmgr... [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] module status: bgp changed to status 0 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] module status: fea changed to status 0 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] module status: firewall changed to status 0 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] module status: interfaces changed to status 0 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] module status: ospf4 changed to status 0 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] module status: policy changed to status 0 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] module status: rib changed to status 0 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] module status: rtrmgr changed to status 0 [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] config changed: user_id: 0 DELTAS: %1 0% protocols { %1 0% bgp { %1 0% bgp-id: 10.1.100.5 %2 1% local-as: "65100" %3 2% enable-4byte-as-numbers: false %5 3% peer "10.1.100.6" { %1 0% peer-port: 179 %2 1% local-port: 179 %3 2% local-ip: "10.1.100.5" %17 3% local-dev: "" %4 3% as: "65100" %5 4% next-hop: 10.1.100.6 %6 5% holdtime: 90 %7 6% delay-open-time: 0 %8 7% client: false %9 8% confederation-member: false %10 9% disable: false %11 10% ipv4-unicast: true %12 11% ipv4-multicast: false %13 12% ipv6-unicast: false %14 13% ipv6-multicast: false %15 14% import: "" %16 15% export: "" } %6 5% peer "10.1.100.2" { %1 0% peer-port: 179 %2 1% local-port: 179 %3 2% local-ip: "10.1.100.1" %17 3% local-dev: "" %4 3% as: "65100" %5 4% next-hop: 10.1.100.2 %6 5% holdtime: 90 %7 6% delay-open-time: 0 %8 7% client: false %9 8% confederation-member: false %10 9% disable: false %11 10% ipv4-unicast: true %12 11% ipv4-multicast: false %13 12% ipv6-unicast: false %14 13% ipv6-multicast: false %15 14% import: "" %16 15% export: "" } %7 4% import: "" %8 7% export: "" } %2 1% ospf4 { %1 0% router-id: 10.1.100.1 %2 1% rfc1583-compatibility: false %3 2% ip-router-alert: false %5 3% area 0.0.0.0 { %1 0% area-type: "normal" %3 1% interface epair1a { %1 0% link-type: "broadcast" %3 1% vif epair1a { %2 0% address 10.1.100.1 { %1 0% priority: 128 %2 1% hello-interval: 10 %3 2% router-dead-interval: 40 %4 3% interface-cost: 1 %5 4% retransmit-interval: 5 %6 5% transit-delay: 1 %7 6% disable: false } } } %4 3% interface epair2a { %1 0% link-type: "broadcast" %3 1% vif epair2a { %2 0% address 10.1.100.5 { %1 0% priority: 128 %2 1% hello-interval: 10 %3 2% router-dead-interval: 40 %4 3% interface-cost: 1 %5 4% retransmit-interval: 5 %6 5% transit-delay: 1 %7 6% disable: false } } } %5 4% interface ebr0 { %1 0% link-type: "broadcast" %3 1% vif ebr0 { %2 0% address 10.1.100.1 { %1 0% priority: 128 %2 1% hello-interval: 10 %3 2% router-dead-interval: 40 %4 3% interface-cost: 1 %5 4% retransmit-interval: 5 %6 5% transit-delay: 1 %7 6% passive { %1 0% disable: false %2 1% host: false } %8 7% disable: false } } } } } } %2 1% interfaces { %1 0% restore-original-config-on-shutdown: false %3 1% interface epair1a { %1 0% description: "" %2 1% disable: false %3 2% discard: false %4 3% unreachable: false %5 4% management: false %7 5% vif epair1a { %1 0% disable: false %3 1% address 10.1.100.1 { %1 0% prefix-length: 30 %2 1% disable: false } } } %4 3% interface epair2a { %1 0% description: "" %2 1% disable: false %3 2% discard: false %4 3% unreachable: false %5 4% management: false %7 5% vif epair2a { %1 0% disable: false %3 1% address 10.1.100.5 { %1 0% prefix-length: 30 %2 1% disable: false } } } %5 4% interface ebr0 { %1 0% description: "" %2 1% disable: false %3 2% discard: false %4 3% unreachable: false %5 4% management: false %7 5% vif ebr0 { %1 0% disable: false %3 1% address 10.1.1.4 { %1 0% prefix-length: 24 %2 1% disable: false } } } } %3 2% rtrmgr { %1 0% config-directory: "/root/chaos/vrd/edwin/R4/boot" %2 1% load-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" %3 2% load-file-command-args: "-o" %4 3% load-ftp-command: "fetch" %5 4% load-ftp-command-args: "-o" %6 5% load-http-command: "fetch" %7 6% load-http-command-args: "-o" %8 7% load-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" %9 8% load-tftp-command-args: "" %10 9% save-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" %11 10% save-file-command-args: "" %12 11% save-ftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" %13 12% save-ftp-command-args: "" %14 13% save-http-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" %15 14% save-http-command-args: "" %16 15% save-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" %17 16% save-tftp-command-args: "" } DELETIONS: [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] ========================================================== [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] %1 0% protocols { %1 0% bgp { %1 0% bgp-id: 10.1.100.5 %2 1% local-as: "65100" %3 2% enable-4byte-as-numbers: false %5 3% peer "10.1.100.6" { %1 0% peer-port: 179 %2 1% local-port: 179 %3 2% local-ip: "10.1.100.5" %17 3% local-dev: "" %4 3% as: "65100" %5 4% next-hop: 10.1.100.6 %6 5% holdtime: 90 %7 6% delay-open-time: 0 %8 7% client: false %9 8% confederation-member: false %10 9% disable: false %11 10% ipv4-unicast: true %12 11% ipv4-multicast: false %13 12% ipv6-unicast: false %14 13% ipv6-multicast: false %15 14% import: "" %16 15% export: "" } %6 5% peer "10.1.100.2" { %1 0% peer-port: 179 %2 1% local-port: 179 %3 2% local-ip: "10.1.100.1" %17 3% local-dev: "" %4 3% as: "65100" %5 4% next-hop: 10.1.100.2 %6 5% holdtime: 90 %7 6% delay-open-time: 0 %8 7% client: false %9 8% confederation-member: false %10 9% disable: false %11 10% ipv4-unicast: true %12 11% ipv4-multicast: false %13 12% ipv6-unicast: false %14 13% ipv6-multicast: false %15 14% import: "" %16 15% export: "" } %7 4% import: "" %8 7% export: "" } %2 1% ospf4 { %1 0% router-id: 10.1.100.1 %2 1% rfc1583-compatibility: false %3 2% ip-router-alert: false %5 3% area 0.0.0.0 { %1 0% area-type: "normal" %3 1% interface epair1a { %1 0% link-type: "broadcast" %3 1% vif epair1a { %2 0% address 10.1.100.1 { %1 0% priority: 128 %2 1% hello-interval: 10 %3 2% router-dead-interval: 40 %4 3% interface-cost: 1 %5 4% retransmit-interval: 5 %6 5% transit-delay: 1 %7 6% disable: false } } } %4 3% interface epair2a { %1 0% link-type: "broadcast" %3 1% vif epair2a { %2 0% address 10.1.100.5 { %1 0% priority: 128 %2 1% hello-interval: 10 %3 2% router-dead-interval: 40 %4 3% interface-cost: 1 %5 4% retransmit-interval: 5 %6 5% transit-delay: 1 %7 6% disable: false } } } %5 4% interface ebr0 { %1 0% link-type: "broadcast" %3 1% vif ebr0 { %2 0% address 10.1.100.1 { %1 0% priority: 128 %2 1% hello-interval: 10 %3 2% router-dead-interval: 40 %4 3% interface-cost: 1 %5 4% retransmit-interval: 5 %6 5% transit-delay: 1 %7 6% passive { %1 0% disable: false %2 1% host: false } %8 7% disable: false } } } } } } %2 1% interfaces { %1 0% restore-original-config-on-shutdown: false %3 1% interface epair1a { %1 0% description: "" %2 1% disable: false %3 2% discard: false %4 3% unreachable: false %5 4% management: false %7 5% vif epair1a { %1 0% disable: false %3 1% address 10.1.100.1 { %1 0% prefix-length: 30 %2 1% disable: false } } } %4 3% interface epair2a { %1 0% description: "" %2 1% disable: false %3 2% discard: false %4 3% unreachable: false %5 4% management: false %7 5% vif epair2a { %1 0% disable: false %3 1% address 10.1.100.5 { %1 0% prefix-length: 30 %2 1% disable: false } } } %5 4% interface ebr0 { %1 0% description: "" %2 1% disable: false %3 2% discard: false %4 3% unreachable: false %5 4% management: false %7 5% vif ebr0 { %1 0% disable: false %3 1% address 10.1.1.4 { %1 0% prefix-length: 24 %2 1% disable: false } } } } %3 2% rtrmgr { %1 0% config-directory: "/root/chaos/vrd/edwin/R4/boot" %2 1% load-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" %3 2% load-file-command-args: "-o" %4 3% load-ftp-command: "fetch" %5 4% load-ftp-command-args: "-o" %6 5% load-http-command: "fetch" %7 6% load-http-command-args: "-o" %8 7% load-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" %9 8% load-tftp-command-args: "" %10 9% save-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" %11 10% save-file-command-args: "" %12 11% save-ftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" %13 12% save-ftp-command-args: "" %14 13% save-http-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" %15 14% save-http-command-args: "" %16 15% save-tftp-command: "sh -c 'echo Not implemented 1>&2 && exit 1'" %17 16% save-tftp-command-args: "" } [ 2010/08/18 13:17:54 TRACE xorpsh RTRMGR ] ========================================================== [ 2010/08/18 13:17:54 ERROR xorpsh:4133 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" Edwin > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > From greearb at candelatech.com Wed Aug 18 10:17:06 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 18 Aug 2010 10:17:06 -0700 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <43C4A3D2-364F-42CE-9723-839150EE7E29@spacebugs.nl> References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> <4C6AB56A.6060705@candelatech.com> <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> <4E5642C7-03A6-48FC-AF1D-B8B6A22A7E98@spacebugs.nl> <4C6AFF74.6050302@candelatech.com> <43C4A3D2-364F-42CE-9723-839150EE7E29@spacebugs.nl> Message-ID: <4C6C1592.1040106@candelatech.com> On 08/18/2010 04:27 AM, Edwin Schokkenbroek wrote: > > On Aug 17, 2010, at 11:30 PM, Ben Greear wrote: > >> On 08/17/2010 01:00 PM, Edwin Schokkenbroek wrote: >> >>> Hmm not sure what is going on ... If I look in the log file I see the >>> following messages: >>> >>> [ 2010/08/17 21:46:27.835350 ERROR xorp_rtrmgr:3761 LIBCOMM >>> libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = >>> 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address >>> [ 2010/08/17 21:46:27.837998 ERROR xorp_rtrmgr:3761 RTRMGR >>> rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder >>> may already be running. >> >> Can you make sure you have a clean compile? That looks like endian-ness issues >> again. Maybe rm -fr the 'obj' dir and rebuild fresh? > > > I removed the obj directory, recompiled to source and I receive another error. This time the xorp_rtrtmgr seems to start. But xorpsh bails out. : > > jexec R4 /usr/local/xorp/sbin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R4/boot/config.boot -l /root/chaos/vrd/edwin/R4/var/R4.log -P /root/chaos/vrd/edwin/R4/var/run/xorp_rtrmgr.pid -d > > > beastie# jexec R4 xorpsh > [ 2010/08/18 13:16:29 ERROR xorpsh:4131 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" > beastie# > [ 2010/08/18 13:01:05 ERROR xorpsh:3972 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" > > Note sure why xorpsh bails out with a parse error. The xorp_rtrmgr is running: That local_dev is something I added in (some time back), so it's possible I messed something up. It has been working fine for me on Linux though. Can you double-check you are using the xorpsh that you just compiled and not some older version? Another possibility is that you somehow have old xorp template files on your system? If your xorpsh is up to date and still you see this problem, please post your xorp config file and I'll see if I can reproduce the problem on my bsd virtual machine. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Wed Aug 18 11:01:19 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 18 Aug 2010 20:01:19 +0200 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <4C6C1592.1040106@candelatech.com> References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> <4C6AB56A.6060705@candelatech.com> <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> <4E5642C7-03A6-48FC-AF1D-B8B6A22A7E98@spacebugs.nl> <4C6AFF74.6050302@candelatech.com> <43C4A3D2-364F-42CE-9723-839150EE7E29@spacebugs.nl> <4C6C1592.1040106@candelatech.com> Message-ID: <575F24F1-775C-4F94-B1E4-A1822765E865@spacebugs.nl> On Aug 18, 2010, at 7:17 PM, Ben Greear wrote: > On 08/18/2010 04:27 AM, Edwin Schokkenbroek wrote: >> >> On Aug 17, 2010, at 11:30 PM, Ben Greear wrote: >> >>> On 08/17/2010 01:00 PM, Edwin Schokkenbroek wrote: >>> >>>> Hmm not sure what is going on ... If I look in the log file I see the >>>> following messages: >>>> >>>> [ 2010/08/17 21:46:27.835350 ERROR xorp_rtrmgr:3761 LIBCOMM >>>> libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = >>>> 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address >>>> [ 2010/08/17 21:46:27.837998 ERROR xorp_rtrmgr:3761 RTRMGR >>>> rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder >>>> may already be running. >>> >>> Can you make sure you have a clean compile? That looks like endian-ness issues >>> again. Maybe rm -fr the 'obj' dir and rebuild fresh? >> >> >> I removed the obj directory, recompiled to source and I receive another error. This time the xorp_rtrtmgr seems to start. But xorpsh bails out. : >> >> jexec R4 /usr/local/xorp/sbin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R4/boot/config.boot -l /root/chaos/vrd/edwin/R4/var/R4.log -P /root/chaos/vrd/edwin/R4/var/run/xorp_rtrmgr.pid -d >> >> >> beastie# jexec R4 xorpsh >> [ 2010/08/18 13:16:29 ERROR xorpsh:4131 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" >> beastie# >> [ 2010/08/18 13:01:05 ERROR xorpsh:3972 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" >> >> Note sure why xorpsh bails out with a parse error. The xorp_rtrmgr is running: > > That local_dev is something I added in (some time back), so it's possible I messed something up. > It has been working fine for me on Linux though. Can you double-check you are using the xorpsh > that you just compiled and not some older version? > Need a very solid brick wall to bang my head against. In the script I can switch between xorp versions. Due to a bug in the script.. the xorpsh var was not correctly adjusted. And so .. yes I was using old version of xorpsh against the latest version of xorp_rtrmgr. I fixed this bugs .. and it works :-) Sorry for the noise. edwin > Another possibility is that you somehow have old xorp template files on your system? > > If your xorpsh is up to date and still you see this problem, please post your xorp config file > and I'll see if I can reproduce the problem on my bsd virtual machine. > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Wed Aug 18 11:05:44 2010 From: greearb at candelatech.com (Ben Greear) Date: Wed, 18 Aug 2010 11:05:44 -0700 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <575F24F1-775C-4F94-B1E4-A1822765E865@spacebugs.nl> References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> <4C6AB56A.6060705@candelatech.com> <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> <4E5642C7-03A6-48FC-AF1D-B8B6A22A7E98@spacebugs.nl> <4C6AFF74.6050302@candelatech.com> <43C4A3D2-364F-42CE-9723-839150EE7E29@spacebugs.nl> <4C6C1592.1040106@candelatech.com> <575F24F1-775C-4F94-B1E4-A1822765E865@spacebugs.nl> Message-ID: <4C6C20F8.1010107@candelatech.com> On 08/18/2010 11:01 AM, Edwin Schokkenbroek wrote: > > On Aug 18, 2010, at 7:17 PM, Ben Greear wrote: > >> On 08/18/2010 04:27 AM, Edwin Schokkenbroek wrote: >>> >>> On Aug 17, 2010, at 11:30 PM, Ben Greear wrote: >>> >>>> On 08/17/2010 01:00 PM, Edwin Schokkenbroek wrote: >>>> >>>>> Hmm not sure what is going on ... If I look in the log file I see the >>>>> following messages: >>>>> >>>>> [ 2010/08/17 21:46:27.835350 ERROR xorp_rtrmgr:3761 LIBCOMM >>>>> libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = >>>>> 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address >>>>> [ 2010/08/17 21:46:27.837998 ERROR xorp_rtrmgr:3761 RTRMGR >>>>> rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder >>>>> may already be running. >>>> >>>> Can you make sure you have a clean compile? That looks like endian-ness issues >>>> again. Maybe rm -fr the 'obj' dir and rebuild fresh? >>> >>> >>> I removed the obj directory, recompiled to source and I receive another error. This time the xorp_rtrtmgr seems to start. But xorpsh bails out. : >>> >>> jexec R4 /usr/local/xorp/sbin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R4/boot/config.boot -l /root/chaos/vrd/edwin/R4/var/R4.log -P /root/chaos/vrd/edwin/R4/var/run/xorp_rtrmgr.pid -d >>> >>> >>> beastie# jexec R4 xorpsh >>> [ 2010/08/18 13:16:29 ERROR xorpsh:4131 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" >>> beastie# >>> [ 2010/08/18 13:01:05 ERROR xorpsh:3972 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" >>> >>> Note sure why xorpsh bails out with a parse error. The xorp_rtrmgr is running: >> >> That local_dev is something I added in (some time back), so it's possible I messed something up. >> It has been working fine for me on Linux though. Can you double-check you are using the xorpsh >> that you just compiled and not some older version? >> > > Need a very solid brick wall to bang my head against. In the script I can switch between xorp versions. Due to a bug in the script.. the xorpsh var was not correctly adjusted. And so .. yes I was using old version of xorpsh against the latest version of xorp_rtrmgr. I fixed this bugs .. and it works :-) > > Sorry for the noise. No problem, I've done worse and I'm sure I will again :) I do notice that buildbot is reporting bgp failures on freebsd, though at first look, it appears to be a bug with test harness and/or scons on bsd. But, if you do see issues with bgp or any other xorp thing, do let us know. Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Wed Aug 18 11:18:44 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Wed, 18 Aug 2010 20:18:44 +0200 Subject: [Xorp-users] Some recent xorp.ct improvements. (Ben Greear) In-Reply-To: <4C6C20F8.1010107@candelatech.com> References: <4C6AA4D6.70903@candelatech.com> <78100DDF-18AA-4B5F-8ADE-C7C7919EE675@spacebugs.nl> <4C6AB56A.6060705@candelatech.com> <90852F9F-1FEB-47A8-974E-D174085A1ED1@spacebugs.nl> <4E5642C7-03A6-48FC-AF1D-B8B6A22A7E98@spacebugs.nl> <4C6AFF74.6050302@candelatech.com> <43C4A3D2-364F-42CE-9723-839150EE7E29@spacebugs.nl> <4C6C1592.1040106@candelatech.com> <575F24F1-775C-4F94-B1E4-A1822765E865@spacebugs.nl> <4C6C20F8.1010107@candelatech.com> Message-ID: <093465D1-70FF-4C68-A6A8-076C16DD3CCF@spacebugs.nl> On Aug 18, 2010, at 8:05 PM, Ben Greear wrote: > On 08/18/2010 11:01 AM, Edwin Schokkenbroek wrote: >> >> On Aug 18, 2010, at 7:17 PM, Ben Greear wrote: >> >>> On 08/18/2010 04:27 AM, Edwin Schokkenbroek wrote: >>>> >>>> On Aug 17, 2010, at 11:30 PM, Ben Greear wrote: >>>> >>>>> On 08/17/2010 01:00 PM, Edwin Schokkenbroek wrote: >>>>> >>>>>> Hmm not sure what is going on ... If I look in the log file I see the >>>>>> following messages: >>>>>> >>>>>> [ 2010/08/17 21:46:27.835350 ERROR xorp_rtrmgr:3761 LIBCOMM >>>>>> libcomm/comm_sock.c:163 comm_sock_bind4 ] Error binding socket (family = >>>>>> 2, my_addr = 1.0.0.127, my_port = 19999): Can't assign requested address >>>>>> [ 2010/08/17 21:46:27.837998 ERROR xorp_rtrmgr:3761 RTRMGR >>>>>> rtrmgr/main_rtrmgr.cc:297 run ] Can't assign requested address: a finder >>>>>> may already be running. >>>>> >>>>> Can you make sure you have a clean compile? That looks like endian-ness issues >>>>> again. Maybe rm -fr the 'obj' dir and rebuild fresh? >>>> >>>> >>>> I removed the obj directory, recompiled to source and I receive another error. This time the xorp_rtrtmgr seems to start. But xorpsh bails out. : >>>> >>>> jexec R4 /usr/local/xorp/sbin/xorp_rtrmgr -b /root/chaos/vrd/edwin/R4/boot/config.boot -l /root/chaos/vrd/edwin/R4/var/R4.log -P /root/chaos/vrd/edwin/R4/var/run/xorp_rtrmgr.pid -d >>>> >>>> >>>> beastie# jexec R4 xorpsh >>>> [ 2010/08/18 13:16:29 ERROR xorpsh:4131 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" >>>> beastie# >>>> [ 2010/08/18 13:01:05 ERROR xorpsh:3972 RTRMGR +906 xorpsh_main.cc main ] xorpsh exiting due to an init error: Shutting down due to a parse error: PARSE ERROR [line 11]: No template found in template map; Last symbol parsed was "local-dev" >>>> >>>> Note sure why xorpsh bails out with a parse error. The xorp_rtrmgr is running: >>> >>> That local_dev is something I added in (some time back), so it's possible I messed something up. >>> It has been working fine for me on Linux though. Can you double-check you are using the xorpsh >>> that you just compiled and not some older version? >>> >> >> Need a very solid brick wall to bang my head against. In the script I can switch between xorp versions. Due to a bug in the script.. the xorpsh var was not correctly adjusted. And so .. yes I was using old version of xorpsh against the latest version of xorp_rtrmgr. I fixed this bugs .. and it works :-) >> >> Sorry for the noise. > > No problem, I've done worse and I'm sure I will again :) > > I do notice that buildbot is reporting bgp failures on > freebsd, though at first look, it appears to be a bug with > test harness and/or scons on bsd. > > But, if you do see issues with bgp or any other xorp thing, > do let us know. Thanks, and I will ;-) Right now I'm building a BGP setup. So if you have something specific to test , then let me know. Perhaps I can test it. Edwin > > 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 Thu Aug 19 10:39:56 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Thu, 19 Aug 2010 19:39:56 +0200 Subject: [Xorp-users] BGP router is not receiving BGP routes Message-ID: Hello list, I'm running Version 1.8-CT (latest build) on FreeBSD 8.0 AMD 64 in Vmware fusion virtual machine. Vmware version is : Version 3.1.1 (282344) In this setup I'm trying to get BGP working. At this moment I ran into several problems. If someone can point out what Im doing wrong, or what I'm missing it would be much appreciated. I've setup two routers : R4 -------- R13 R4 is located in AS 65100 R13 is located in AS 65105 In AS 65100 more routers are located, which all run OSPF (IGP). All the routers are fully meshed (iBGP) In AS 65105 two routers are located. Only static routing is used. R13 Should receive all routes from AS65100 R13 Should only once a default route to AS65100. I've tried to set this up, by converting Cisco configuration to Xorp. Till now I don't get it working. Maybe I messed up some policies. Because when I want to test the policy I receive the following error: beheer at R13> test policy re-dist-static 0.0.0.0/0 "-protocol=static" Error: 102 Command failed PolicyException from line 312 of policy/visitor_test.cc: Can't read uninitialized attribute neighbor ERROR: Command "/usr/local/xorp/lib/xorp/bin/cli_send_processor_xrl": exited with exit status 1. Besides that error I receive a error when I run the command : show bgp peers: [ 2010/08/19 18:38:29.880750 ERROR bgp_print_peers:12960 LIBXORP libxorp/heap.cc:163 pop_obj ] Extract from empty heap 0x0x8025031e0 Peer 1: local 10.1.1.4/179 remote 10.1.1.1/179 Peer 2: local 10.1.1.4/179 remote 10.1.1.2/179 Peer 3: local 10.1.1.4/179 remote 10.1.1.13/179 Peer 4: local 10.1.100.1/179 remote 10.1.100.2/179 Peer 5: local 10.1.100.5/179 remote 10.1.100.6/179 Peer 6: local 10.1.100.5/179 remote 10.1.100.10/179 beheer at R4> The config of both routers: #-------------------# # Config of R4 # #-------------------# beheer at R4# show protocols { bgp { bgp-id: 10.1.100.5 local-as: "65100" peer "10.1.100.6" { local-ip: "10.1.100.5" as: "65100" next-hop: 10.1.100.5 } peer "10.1.100.2" { local-ip: "10.1.100.1" as: "65100" next-hop: 10.1.100.5 } peer "10.1.1.1" { local-ip: "10.1.1.4" as: "65101" next-hop: 10.1.1.1 } peer "10.1.1.2" { local-ip: "10.1.1.4" as: "65101" next-hop: 10.1.1.2 } peer "10.1.100.10" { local-ip: "10.1.100.5" as: "65100" next-hop: 10.1.100.5 } peer "10.1.1.13" { local-ip: "10.1.1.4" as: "65105" next-hop: 10.1.1.13 } } ospf4 { router-id: 10.1.100.1 area 0.0.0.0 { interface epair1a { vif epair1a { address 10.1.100.1 { } } } interface epair2a { vif epair2a { address 10.1.100.5 { } } } interface ebr0 { vif ebr0 { address 10.1.1.4 { passive { } } } } } } } interfaces { interface epair1a { vif epair1a { address 10.1.100.1 { prefix-length: 30 } } } interface epair2a { vif epair2a { address 10.1.100.5 { prefix-length: 30 } } } interface ebr0 { vif ebr0 { address 10.1.1.4 { prefix-length: 24 } } } } rtrmgr { config-directory: "/root/chaos/vrd/edwin/R4/boot" load-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" save-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" } [edit] Routing information for router R4 beheer at R4> show route table ipv4 unicast final 10.1.1.0/24 [connected(0)/0] > via ebr0/ebr0 10.1.3.0/24 [ospf(110)/2] > to 10.1.100.2 via epair1a/epair1a 10.1.100.0/30 [connected(0)/0] > via epair1a/epair1a 10.1.100.4/30 [connected(0)/0] > via epair2a/epair2a 10.1.100.8/30 [ospf(110)/2] > to 10.1.100.6 via epair2a/epair2a 10.1.100.12/30 [ospf(110)/2] > to 10.1.100.2 via epair1a/epair1a beheer at R4> show bgp routes Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ------ ------- ---- ------- * 10.1.3.0/24 10.1.3.12 10.1.100.2 65105 i *> 10.1.1.0/24 10.1.100.6 10.1.100.6 i *> 10.1.3.0/24 10.1.100.10 10.1.100.6 i *> 10.1.100.0/30 10.1.100.6 10.1.100.6 i *> 10.1.100.12/30 10.1.100.10 10.1.100.6 i * 10.1.1.0/24 10.1.100.14 10.1.100.10 i * 10.1.3.0/24 10.1.100.14 10.1.100.10 i * 10.1.100.0/30 10.1.100.14 10.1.100.10 i *> 10.1.100.4/30 10.1.100.9 10.1.100.10 i #--------------------# # Config of R13 # #--------------------# beheer at R13# show protocols { bgp { bgp-id: 10.1.1.13 local-as: "65105" peer "10.1.1.4" { local-ip: "10.1.1.13" as: "65100" next-hop: 10.1.1.4 } export: "re-dist-static" } static { route 0.0.0.0/0 { next-hop: 172.17.1.2 } } } policy { policy-statement "re-dist-static" { term "announce-st" { from { protocol: "static" } to { neighbor: 10.1.1.4..10.1.1.4 } then { accept { } } } } } interfaces { interface ebr0 { vif ebr0 { address 10.1.1.13 { prefix-length: 24 broadcast: 10.1.1.255 } } } interface epair6a { vif epair6a { address 172.17.1.1 { prefix-length: 24 } } } } rtrmgr { config-directory: "/root/chaos/vrd/edwin/R13/boot" load-file-command: "/root/chaos/vrd/edwin/R13/boot/config.boot" save-file-command: "/root/chaos/vrd/edwin/R13/boot/config.boot" } [edit] Route information for router R10 : beheer at R13> show route table ipv4 unicast final 0.0.0.0/0 [static(1)/1] > to 172.17.1.2 via epair6a/epair6a 10.1.1.0/24 [connected(0)/0] > via ebr0/ebr0 172.17.1.0/24 [connected(0)/0] > via epair6a/epair6a beheer at R13> show bgp routes Peer 1: local 10.1.1.13/179 remote 10.1.1.4/179 beheer at R13> show bgp routes Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ------ ------- ---- ------- *> 0.0.0.0/0 172.17.1.2 0.0.0.0 i beheer at R13> With best regards, Edwin From weaver at ascr.doe.gov Thu Aug 19 11:16:40 2010 From: weaver at ascr.doe.gov (Mike Weaver) Date: Thu, 19 Aug 2010 14:16:40 -0400 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT Message-ID: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> Hi, I'm a bit confused. The release notes state that xorp SNMP support was removed in version 1.7, but a whole chapter still exists in the v1.8-CT User Manual. Since none of the MIBs or scripts or library objects exist on my 1.8.2 system, I am assuming that the release notes are correct and the User Manual has yet to catch up. Are there plans to (re)support router monitoring via SNMP in future builds? Thanks, Mike -- Mike Weaver Office of Advanced Scientific Computing Research US Department of Energy T: 301-903-0072 F: 301-903-7774 weaver at ascr.doe.gov From greearb at candelatech.com Thu Aug 19 11:21:46 2010 From: greearb at candelatech.com (Ben Greear) Date: Thu, 19 Aug 2010 11:21:46 -0700 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> Message-ID: <4C6D763A.9010608@candelatech.com> On 08/19/2010 11:16 AM, Mike Weaver wrote: > Hi, > > I'm a bit confused. The release notes state that xorp SNMP support was > removed in version 1.7, but a whole chapter still exists in the v1.8-CT User > Manual. Since none of the MIBs or scripts or library objects exist on my > 1.8.2 system, I am assuming that the release notes are correct and the User > Manual has yet to catch up. > > Are there plans to (re)support router monitoring via SNMP in future builds? SNMP is well and truly gone from the code. I'll try to scrub the user-manual of it as well. I've no plans to re-add it, but would accept patches if they are not overly intrusive. I suspect one could use standard OS snmp support, but have never tried it. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From aleksandar.cvjetic at gmail.com Thu Aug 19 11:36:02 2010 From: aleksandar.cvjetic at gmail.com (Aleksandar Cvjetic) Date: Thu, 19 Aug 2010 20:36:02 +0200 Subject: [Xorp-users] BGP router is not receiving BGP routes In-Reply-To: References: Message-ID: Hello, On R4 try to configure a policy matching protocol OSPF routes and apply it as export BGP policy (as you did for static routes on R13). I think that Cisco logic doesn't work here, at least you don't have an option for "network" statement to advertise routes into BGP. Regards, Alex On Thu, Aug 19, 2010 at 7:39 PM, Edwin Schokkenbroek wrote: > > Hello list, > > I'm running Version 1.8-CT (latest build) on FreeBSD 8.0 AMD 64 in Vmware > fusion virtual machine. Vmware version is : Version 3.1.1 (282344) > In this setup I'm trying to get BGP working. At this moment I ran into > several problems. If someone can point out what Im doing wrong, or what I'm > missing it would be much appreciated. > > I've setup two routers : > > > R4 -------- R13 > > > R4 is located in AS 65100 > R13 is located in AS 65105 > > In AS 65100 more routers are located, which all run OSPF (IGP). All the > routers are fully meshed (iBGP) > In AS 65105 two routers are located. Only static routing is used. > > R13 Should receive all routes from AS65100 > R13 Should only once a default route to AS65100. > > I've tried to set this up, by converting Cisco configuration to Xorp. Till > now I don't get it working. Maybe I messed up some policies. Because when I > want to test the policy I receive the following error: > > beheer at R13> test policy re-dist-static 0.0.0.0/0 "-protocol=static" > Error: 102 Command failed PolicyException from line 312 of > policy/visitor_test.cc: Can't read uninitialized attribute neighbor > ERROR: Command "/usr/local/xorp/lib/xorp/bin/cli_send_processor_xrl": > exited with exit status 1. > > > Besides that error I receive a error when I run the command : show bgp > peers: > > [ 2010/08/19 18:38:29.880750 ERROR bgp_print_peers:12960 LIBXORP > libxorp/heap.cc:163 pop_obj ] Extract from empty heap 0x0x8025031e0 > Peer 1: local 10.1.1.4/179 remote 10.1.1.1/179 > Peer 2: local 10.1.1.4/179 remote 10.1.1.2/179 > Peer 3: local 10.1.1.4/179 remote 10.1.1.13/179 > Peer 4: local 10.1.100.1/179 remote 10.1.100.2/179 > Peer 5: local 10.1.100.5/179 remote 10.1.100.6/179 > Peer 6: local 10.1.100.5/179 remote 10.1.100.10/179 > beheer at R4> > > > The config of both routers: > #-------------------# > # Config of R4 # > #-------------------# > > beheer at R4# show > protocols { > bgp { > bgp-id: 10.1.100.5 > local-as: "65100" > peer "10.1.100.6" { > local-ip: "10.1.100.5" > as: "65100" > next-hop: 10.1.100.5 > } > peer "10.1.100.2" { > local-ip: "10.1.100.1" > as: "65100" > next-hop: 10.1.100.5 > } > peer "10.1.1.1" { > local-ip: "10.1.1.4" > as: "65101" > next-hop: 10.1.1.1 > } > peer "10.1.1.2" { > local-ip: "10.1.1.4" > as: "65101" > next-hop: 10.1.1.2 > } > peer "10.1.100.10" { > local-ip: "10.1.100.5" > as: "65100" > next-hop: 10.1.100.5 > } > peer "10.1.1.13" { > local-ip: "10.1.1.4" > as: "65105" > next-hop: 10.1.1.13 > } > } > ospf4 { > router-id: 10.1.100.1 > area 0.0.0.0 { > interface epair1a { > vif epair1a { > address 10.1.100.1 { > } > } > } > interface epair2a { > vif epair2a { > address 10.1.100.5 { > } > } > } > interface ebr0 { > vif ebr0 { > address 10.1.1.4 { > passive { > } > } > } > } > } > } > } > interfaces { > interface epair1a { > vif epair1a { > address 10.1.100.1 { > prefix-length: 30 > } > } > } > interface epair2a { > vif epair2a { > address 10.1.100.5 { > prefix-length: 30 > } > } > } > interface ebr0 { > vif ebr0 { > address 10.1.1.4 { > prefix-length: 24 > } > } > } > } > rtrmgr { > config-directory: "/root/chaos/vrd/edwin/R4/boot" > load-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" > save-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" > } > > [edit] > > > Routing information for router R4 > > beheer at R4> show route table ipv4 unicast final > 10.1.1.0/24 [connected(0)/0] > > via ebr0/ebr0 > 10.1.3.0/24 [ospf(110)/2] > > to 10.1.100.2 via epair1a/epair1a > 10.1.100.0/30 [connected(0)/0] > > via epair1a/epair1a > 10.1.100.4/30 [connected(0)/0] > > via epair2a/epair2a > 10.1.100.8/30 [ospf(110)/2] > > to 10.1.100.6 via epair2a/epair2a > 10.1.100.12/30 [ospf(110)/2] > > to 10.1.100.2 via epair1a/epair1a > > > beheer at R4> show bgp routes > Status Codes: * valid route, > best route > Origin Codes: i IGP, e EGP, ? incomplete > > Prefix Nexthop Peer AS Path > ------ ------- ---- ------- > * 10.1.3.0/24 10.1.3.12 10.1.100.2 65105 i > *> 10.1.1.0/24 10.1.100.6 10.1.100.6 i > *> 10.1.3.0/24 10.1.100.10 10.1.100.6 i > *> 10.1.100.0/30 10.1.100.6 10.1.100.6 i > *> 10.1.100.12/30 10.1.100.10 10.1.100.6 i > * 10.1.1.0/24 10.1.100.14 10.1.100.10 i > * 10.1.3.0/24 10.1.100.14 10.1.100.10 i > * 10.1.100.0/30 10.1.100.14 10.1.100.10 i > *> 10.1.100.4/30 10.1.100.9 10.1.100.10 i > > > > #--------------------# > # Config of R13 # > #--------------------# > beheer at R13# show > protocols { > bgp { > bgp-id: 10.1.1.13 > local-as: "65105" > peer "10.1.1.4" { > local-ip: "10.1.1.13" > as: "65100" > next-hop: 10.1.1.4 > } > export: "re-dist-static" > } > static { > route 0.0.0.0/0 { > next-hop: 172.17.1.2 > } > } > } > policy { > policy-statement "re-dist-static" { > term "announce-st" { > from { > protocol: "static" > } > to { > neighbor: 10.1.1.4..10.1.1.4 > } > then { > accept { > } > } > } > } > } > interfaces { > interface ebr0 { > vif ebr0 { > address 10.1.1.13 { > prefix-length: 24 > broadcast: 10.1.1.255 > } > } > } > interface epair6a { > vif epair6a { > address 172.17.1.1 { > prefix-length: 24 > } > } > } > } > rtrmgr { > config-directory: "/root/chaos/vrd/edwin/R13/boot" > load-file-command: "/root/chaos/vrd/edwin/R13/boot/config.boot" > save-file-command: "/root/chaos/vrd/edwin/R13/boot/config.boot" > } > > [edit] > > > Route information for router R10 : > > beheer at R13> show route table ipv4 unicast final > 0.0.0.0/0 [static(1)/1] > > to 172.17.1.2 via epair6a/epair6a > 10.1.1.0/24 [connected(0)/0] > > via ebr0/ebr0 > 172.17.1.0/24 [connected(0)/0] > > via epair6a/epair6a > > > beheer at R13> show bgp routes > Peer 1: local 10.1.1.13/179 remote 10.1.1.4/179 > beheer at R13> show bgp routes > Status Codes: * valid route, > best route > Origin Codes: i IGP, e EGP, ? incomplete > > Prefix Nexthop Peer AS Path > ------ ------- ---- ------- > *> 0.0.0.0/0 172.17.1.2 0.0.0.0 i > beheer at R13> > > > With best regards, > Edwin > > > > > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100819/b1bb5b87/attachment-0001.html From weaver at ascr.doe.gov Thu Aug 19 12:21:49 2010 From: weaver at ascr.doe.gov (Mike Weaver) Date: Thu, 19 Aug 2010 15:21:49 -0400 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <4C6D763A.9010608@candelatech.com> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> <4C6D763A.9010608@candelatech.com> Message-ID: <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> Ok, standard OS snmp support works fine, but I haven't looked at trying to get any routing-specific data integrated. Not a big deal as I'm only using static routes and PIM-SM. Next question - when trying to commit a firewall rule, I get 1 "102 Command failed No firewall plugin to set the entries" error. I see some mention in the release notes for 1.7 showing (it looks like) support to not compile in the firewall code if you don't want to, but I didn't do that. I see entries in my build log for the fea/firewall* files. Am I missing something? Again, I'm using the 1.8.2-CT version. Thanks, Mike -----Original Message----- From: Ben Greear [mailto:greearb at candelatech.com] Sent: Thursday, August 19, 2010 2:22 PM To: weaver at ascr.doe.gov Cc: Xorp-users at xorp.org Subject: Re: [Xorp-users] SNMP & xorp 1.8.2-CT On 08/19/2010 11:16 AM, Mike Weaver wrote: > Hi, > > I'm a bit confused. The release notes state that xorp SNMP support was > removed in version 1.7, but a whole chapter still exists in the v1.8-CT User > Manual. Since none of the MIBs or scripts or library objects exist on my > 1.8.2 system, I am assuming that the release notes are correct and the User > Manual has yet to catch up. > > Are there plans to (re)support router monitoring via SNMP in future builds? SNMP is well and truly gone from the code. I'll try to scrub the user-manual of it as well. I've no plans to re-add it, but would accept patches if they are not overly intrusive. I suspect one could use standard OS snmp support, but have never tried it. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Thu Aug 19 12:25:13 2010 From: greearb at candelatech.com (Ben Greear) Date: Thu, 19 Aug 2010 12:25:13 -0700 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> <4C6D763A.9010608@candelatech.com> <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> Message-ID: <4C6D8519.3090101@candelatech.com> On 08/19/2010 12:21 PM, Mike Weaver wrote: > Ok, standard OS snmp support works fine, but I haven't looked at trying to > get any routing-specific data integrated. Not a big deal as I'm only using > static routes and PIM-SM. I'm curious to know if you get this working to any degree. > Next question - when trying to commit a firewall rule, I get 1 "102 Command > failed No firewall plugin to set the entries" error. I see some mention in > the release notes for 1.7 showing (it looks like) support to not compile in > the firewall code if you don't want to, but I didn't do that. I see entries > in my build log for the fea/firewall* files. Am I missing something? > Again, I'm using the 1.8.2-CT version. I've never tried the firewall logic in Xorp. What OS and version are you using? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Thu Aug 19 14:04:19 2010 From: greearb at candelatech.com (Ben Greear) Date: Thu, 19 Aug 2010 14:04:19 -0700 Subject: [Xorp-users] Live-CD with Xorp on it. Message-ID: <4C6D9C53.2010304@candelatech.com> I've just updated the xorp.ct web site with some more useful information on the LANforge-LIVE CD (which includes xorp.ct). One thing you can do in this tool is to create multiple routers (OSPF, BGP, multicast, etc) and connect them with virtual network connections. LANforge will generate the xorp config files and start xorp, etc. This may be a useful way to get example xorp config files that can then be tailored for real hardware. http://www.candelatech.com/xorp.ct/livecd.html The Live CD is based on Ubuntu and can also be installed to disk (or virtual machine storage). I'm interested to know how this works out if anyone tries it. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From weaver at ascr.doe.gov Fri Aug 20 03:52:33 2010 From: weaver at ascr.doe.gov (Mike Weaver) Date: Fri, 20 Aug 2010 06:52:33 -0400 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <4C6D8519.3090101@candelatech.com> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> <4C6D763A.9010608@candelatech.com> <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> <4C6D8519.3090101@candelatech.com> Message-ID: <010601cb4055$cc491310$64db3930$@ascr.doe.gov> I'm running on Ubuntu Server 10.04.1 LTS and am reasonably sure I have all the prerequisites installed, the documented ones, anyway and ones that seem to make technical sense. I'll do some digging through the code, but it's been a while since I wore a developer's hat :) I'm thinking of trying it on Fedora also as that's the other main flavor we support and it seems to have more support in the xorp community. Mike -----Original Message----- From: Ben Greear [mailto:greearb at candelatech.com] Sent: Thursday, August 19, 2010 3:25 PM To: weaver at ascr.doe.gov Cc: Xorp-users at xorp.org Subject: Re: [Xorp-users] SNMP & xorp 1.8.2-CT On 08/19/2010 12:21 PM, Mike Weaver wrote: > Ok, standard OS snmp support works fine, but I haven't looked at trying to > get any routing-specific data integrated. Not a big deal as I'm only using > static routes and PIM-SM. I'm curious to know if you get this working to any degree. > Next question - when trying to commit a firewall rule, I get 1 "102 Command > failed No firewall plugin to set the entries" error. I see some mention in > the release notes for 1.7 showing (it looks like) support to not compile in > the firewall code if you don't want to, but I didn't do that. I see entries > in my build log for the fea/firewall* files. Am I missing something? > Again, I'm using the 1.8.2-CT version. I've never tried the firewall logic in Xorp. What OS and version are you using? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Fri Aug 20 09:58:25 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 20 Aug 2010 09:58:25 -0700 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <010601cb4055$cc491310$64db3930$@ascr.doe.gov> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> <4C6D763A.9010608@candelatech.com> <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> <4C6D8519.3090101@candelatech.com> <010601cb4055$cc491310$64db3930$@ascr.doe.gov> Message-ID: <4C6EB431.40004@candelatech.com> On 08/20/2010 03:52 AM, Mike Weaver wrote: > I'm running on Ubuntu Server 10.04.1 LTS and am reasonably sure I have all > the prerequisites installed, the documented ones, anyway and ones that seem > to make technical sense. I'll do some digging through the code, but it's > been a while since I wore a developer's hat :) > > I'm thinking of trying it on Fedora also as that's the other main flavor we > support and it seems to have more support in the xorp community. The firewall stuff is in fea. I'll poke at it today to see if it looks like it should work on Linux. Ben > > Mike > > -----Original Message----- > From: Ben Greear [mailto:greearb at candelatech.com] > Sent: Thursday, August 19, 2010 3:25 PM > To: weaver at ascr.doe.gov > Cc: Xorp-users at xorp.org > Subject: Re: [Xorp-users] SNMP& xorp 1.8.2-CT > > On 08/19/2010 12:21 PM, Mike Weaver wrote: >> Ok, standard OS snmp support works fine, but I haven't looked at trying to >> get any routing-specific data integrated. Not a big deal as I'm only > using >> static routes and PIM-SM. > > I'm curious to know if you get this working to any degree. > >> Next question - when trying to commit a firewall rule, I get 1 "102 > Command >> failed No firewall plugin to set the entries" error. I see some mention > in >> the release notes for 1.7 showing (it looks like) support to not compile > in >> the firewall code if you don't want to, but I didn't do that. I see > entries >> in my build log for the fea/firewall* files. Am I missing something? >> Again, I'm using the 1.8.2-CT version. > > I've never tried the firewall logic in Xorp. What OS and version are you > using? > > Thanks, > Ben > -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Fri Aug 20 12:12:41 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 20 Aug 2010 12:12:41 -0700 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <010601cb4055$cc491310$64db3930$@ascr.doe.gov> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> <4C6D763A.9010608@candelatech.com> <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> <4C6D8519.3090101@candelatech.com> <010601cb4055$cc491310$64db3930$@ascr.doe.gov> Message-ID: <4C6ED3A9.5090100@candelatech.com> On 08/20/2010 03:52 AM, Mike Weaver wrote: > I'm running on Ubuntu Server 10.04.1 LTS and am reasonably sure I have all > the prerequisites installed, the documented ones, anyway and ones that seem > to make technical sense. I'll do some digging through the code, but it's > been a while since I wore a developer's hat :) > > I'm thinking of trying it on Fedora also as that's the other main flavor we > support and it seems to have more support in the xorp community. The conversion to scons broke this. And, the linux headers are busted for C++. Please pull down top-of-tree xorp.ct, rm -fr obj, and build. Watch for a warning about how to fix your linux headers, assuming they are busted on your system as well. I'll see if I can get a fix to the linux headers pushed upstream, but that will take months or years to propagate to all the distributions. All that said, the code obviously hasn't been tested in a long time, so no idea how functional it is. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From weaver at ascr.doe.gov Fri Aug 20 12:21:58 2010 From: weaver at ascr.doe.gov (Mike Weaver) Date: Fri, 20 Aug 2010 15:21:58 -0400 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <4C6ED3A9.5090100@candelatech.com> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> <4C6D763A.9010608@candelatech.com> <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> <4C6D8519.3090101@candelatech.com> <010601cb4055$cc491310$64db3930$@ascr.doe.gov> <4C6ED3A9.5090100@candelatech.com> Message-ID: <000001cb409c$f57eb9f0$e07c2dd0$@ascr.doe.gov> Ok, I'll try that - thanks. Do you know if this still works on FreeBSD? You seem to indicate that it's a Linux thing only. Mike -----Original Message----- From: Ben Greear [mailto:greearb at candelatech.com] Sent: Friday, August 20, 2010 3:13 PM To: weaver at ascr.doe.gov Cc: Xorp-users at xorp.org Subject: Re: [Xorp-users] SNMP & xorp 1.8.2-CT On 08/20/2010 03:52 AM, Mike Weaver wrote: > I'm running on Ubuntu Server 10.04.1 LTS and am reasonably sure I have all > the prerequisites installed, the documented ones, anyway and ones that seem > to make technical sense. I'll do some digging through the code, but it's > been a while since I wore a developer's hat :) > > I'm thinking of trying it on Fedora also as that's the other main flavor we > support and it seems to have more support in the xorp community. The conversion to scons broke this. And, the linux headers are busted for C++. Please pull down top-of-tree xorp.ct, rm -fr obj, and build. Watch for a warning about how to fix your linux headers, assuming they are busted on your system as well. I'll see if I can get a fix to the linux headers pushed upstream, but that will take months or years to propagate to all the distributions. All that said, the code obviously hasn't been tested in a long time, so no idea how functional it is. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From greearb at candelatech.com Fri Aug 20 12:45:07 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 20 Aug 2010 12:45:07 -0700 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <000001cb409c$f57eb9f0$e07c2dd0$@ascr.doe.gov> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> <4C6D763A.9010608@candelatech.com> <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> <4C6D8519.3090101@candelatech.com> <010601cb4055$cc491310$64db3930$@ascr.doe.gov> <4C6ED3A9.5090100@candelatech.com> <000001cb409c$f57eb9f0$e07c2dd0$@ascr.doe.gov> Message-ID: <4C6EDB43.3030401@candelatech.com> On 08/20/2010 12:21 PM, Mike Weaver wrote: > Ok, I'll try that - thanks. Do you know if this still works on FreeBSD? > You seem to indicate that it's a Linux thing only. I've never done more than compile on BSD, but it might work there. Might have to hack on scons for BSD as well..probably somewhat similar to what I did for Linux. I'm curious: Why use xorp for firewalling instead of some third-party thing that manipulates iptables? Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Fri Aug 20 15:25:16 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Sat, 21 Aug 2010 00:25:16 +0200 Subject: [Xorp-users] BGP router is not receiving BGP routes In-Reply-To: References: Message-ID: <243A5F30-BB13-4F3D-AB12-EA25B0F45DE1@spacebugs.nl> On Aug 19, 2010, at 8:36 PM, Aleksandar Cvjetic wrote: > Hello, > > On R4 try to configure a policy matching protocol OSPF routes and apply it as export BGP policy (as you did for static routes on R13). I think that Cisco logic doesn't work here, at least you don't have an option for "network" statement to advertise routes into BGP. Thanks for pointing this out. And Well Cisco logic, doesn't work indeed. After fighting with bgp and policies for a day and a long night, I got it working. I'm quite surprised to find out that only a policy which says: from protocol ospf ,for example isn't going to work. A network statement is required, which tells what prefix needs to be announced. In Junos I would do something like: set term 1 from protocol static ; set term 1 then accept. And 'm done (basically). Now that I begin to understand how it works with Xorp, it provides a very clean way to have full control over what prefix is to be announced by bgp. What I've come up with, at the end is the next policy on R4: policy { policy-statement "bgp-exp" { term "st-bgp" { from { protocol: "ospf4" network4-list: "AS65100-prefixes" } then { accept { } } } } network4-list "AS65100-prefixes" { network 10.1.100.0/24 { modifier: "orlonger" } } And I adjusted to eBGP peers next-hop, so the eBGP has (in Cisco terms now a next-hop-self). The eBGP shouldn't have set a next-hop-self, but in this case It just works, and now I'm going to see if I can make it work with the proper settings for the eBGP peers. For now the routing table on R4 looks good. The default route is being announced by the router R13 into BGP: beheer at R4> show route table ipv4 unicast final 0.0.0.0/0 [ebgp(20)/0] > to 10.1.1.13 via ebr0/ebr0 10.1.1.0/24 [connected(0)/0] > via ebr0/ebr0 10.1.3.0/24 [ospf(110)/2] > to 10.1.100.2 via epair1a/epair1a 10.1.101.0/24 [ebgp(20)/0] > to 10.1.1.1 via ebr0/ebr0 172.17.1.0/24 [ebgp(20)/0] > to 10.1.1.13 via ebr0/ebr0 10.1.100.0/30 [connected(0)/0] > via epair1a/epair1a 10.1.100.4/30 [connected(0)/0] > via epair2a/epair2a 10.1.100.8/30 [ospf(110)/2] > to 10.1.100.6 via epair2a/epair2a 10.1.100.12/30 [ospf(110)/2] > to 10.1.100.2 via epair1a/epair1a Edwin > > Regards, > Alex > > On Thu, Aug 19, 2010 at 7:39 PM, Edwin Schokkenbroek wrote: > > Hello list, > > I'm running Version 1.8-CT (latest build) on FreeBSD 8.0 AMD 64 in Vmware fusion virtual machine. Vmware version is : Version 3.1.1 (282344) > In this setup I'm trying to get BGP working. At this moment I ran into several problems. If someone can point out what Im doing wrong, or what I'm missing it would be much appreciated. > > I've setup two routers : > > > R4 -------- R13 > > > R4 is located in AS 65100 > R13 is located in AS 65105 > > In AS 65100 more routers are located, which all run OSPF (IGP). All the routers are fully meshed (iBGP) > In AS 65105 two routers are located. Only static routing is used. > > R13 Should receive all routes from AS65100 > R13 Should only once a default route to AS65100. > > I've tried to set this up, by converting Cisco configuration to Xorp. Till now I don't get it working. Maybe I messed up some policies. Because when I want to test the policy I receive the following error: > > beheer at R13> test policy re-dist-static 0.0.0.0/0 "-protocol=static" > Error: 102 Command failed PolicyException from line 312 of policy/visitor_test.cc: Can't read uninitialized attribute neighbor > ERROR: Command "/usr/local/xorp/lib/xorp/bin/cli_send_processor_xrl": exited with exit status 1. > > > Besides that error I receive a error when I run the command : show bgp peers: > > [ 2010/08/19 18:38:29.880750 ERROR bgp_print_peers:12960 LIBXORP libxorp/heap.cc:163 pop_obj ] Extract from empty heap 0x0x8025031e0 > Peer 1: local 10.1.1.4/179 remote 10.1.1.1/179 > Peer 2: local 10.1.1.4/179 remote 10.1.1.2/179 > Peer 3: local 10.1.1.4/179 remote 10.1.1.13/179 > Peer 4: local 10.1.100.1/179 remote 10.1.100.2/179 > Peer 5: local 10.1.100.5/179 remote 10.1.100.6/179 > Peer 6: local 10.1.100.5/179 remote 10.1.100.10/179 > beheer at R4> > > > The config of both routers: > #-------------------# > # Config of R4 # > #-------------------# > > beheer at R4# show > protocols { > bgp { > bgp-id: 10.1.100.5 > local-as: "65100" > peer "10.1.100.6" { > local-ip: "10.1.100.5" > as: "65100" > next-hop: 10.1.100.5 > } > peer "10.1.100.2" { > local-ip: "10.1.100.1" > as: "65100" > next-hop: 10.1.100.5 > } > peer "10.1.1.1" { > local-ip: "10.1.1.4" > as: "65101" > next-hop: 10.1.1.1 > } > peer "10.1.1.2" { > local-ip: "10.1.1.4" > as: "65101" > next-hop: 10.1.1.2 > } > peer "10.1.100.10" { > local-ip: "10.1.100.5" > as: "65100" > next-hop: 10.1.100.5 > } > peer "10.1.1.13" { > local-ip: "10.1.1.4" > as: "65105" > next-hop: 10.1.1.13 > } > } > ospf4 { > router-id: 10.1.100.1 > area 0.0.0.0 { > interface epair1a { > vif epair1a { > address 10.1.100.1 { > } > } > } > interface epair2a { > vif epair2a { > address 10.1.100.5 { > } > } > } > interface ebr0 { > vif ebr0 { > address 10.1.1.4 { > passive { > } > } > } > } > } > } > } > interfaces { > interface epair1a { > vif epair1a { > address 10.1.100.1 { > prefix-length: 30 > } > } > } > interface epair2a { > vif epair2a { > address 10.1.100.5 { > prefix-length: 30 > } > } > } > interface ebr0 { > vif ebr0 { > address 10.1.1.4 { > prefix-length: 24 > } > } > } > } > rtrmgr { > config-directory: "/root/chaos/vrd/edwin/R4/boot" > load-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" > save-file-command: "/root/chaos/vrd/edwin/R4/boot/config.boot" > } > > [edit] > > > Routing information for router R4 > > beheer at R4> show route table ipv4 unicast final > 10.1.1.0/24 [connected(0)/0] > > via ebr0/ebr0 > 10.1.3.0/24 [ospf(110)/2] > > to 10.1.100.2 via epair1a/epair1a > 10.1.100.0/30 [connected(0)/0] > > via epair1a/epair1a > 10.1.100.4/30 [connected(0)/0] > > via epair2a/epair2a > 10.1.100.8/30 [ospf(110)/2] > > to 10.1.100.6 via epair2a/epair2a > 10.1.100.12/30 [ospf(110)/2] > > to 10.1.100.2 via epair1a/epair1a > > > beheer at R4> show bgp routes > Status Codes: * valid route, > best route > Origin Codes: i IGP, e EGP, ? incomplete > > Prefix Nexthop Peer AS Path > ------ ------- ---- ------- > * 10.1.3.0/24 10.1.3.12 10.1.100.2 65105 i > *> 10.1.1.0/24 10.1.100.6 10.1.100.6 i > *> 10.1.3.0/24 10.1.100.10 10.1.100.6 i > *> 10.1.100.0/30 10.1.100.6 10.1.100.6 i > *> 10.1.100.12/30 10.1.100.10 10.1.100.6 i > * 10.1.1.0/24 10.1.100.14 10.1.100.10 i > * 10.1.3.0/24 10.1.100.14 10.1.100.10 i > * 10.1.100.0/30 10.1.100.14 10.1.100.10 i > *> 10.1.100.4/30 10.1.100.9 10.1.100.10 i > > > > #--------------------# > # Config of R13 # > #--------------------# > beheer at R13# show > protocols { > bgp { > bgp-id: 10.1.1.13 > local-as: "65105" > peer "10.1.1.4" { > local-ip: "10.1.1.13" > as: "65100" > next-hop: 10.1.1.4 > } > export: "re-dist-static" > } > static { > route 0.0.0.0/0 { > next-hop: 172.17.1.2 > } > } > } > policy { > policy-statement "re-dist-static" { > term "announce-st" { > from { > protocol: "static" > } > to { > neighbor: 10.1.1.4..10.1.1.4 > } > then { > accept { > } > } > } > } > } > interfaces { > interface ebr0 { > vif ebr0 { > address 10.1.1.13 { > prefix-length: 24 > broadcast: 10.1.1.255 > } > } > } > interface epair6a { > vif epair6a { > address 172.17.1.1 { > prefix-length: 24 > } > } > } > } > rtrmgr { > config-directory: "/root/chaos/vrd/edwin/R13/boot" > load-file-command: "/root/chaos/vrd/edwin/R13/boot/config.boot" > save-file-command: "/root/chaos/vrd/edwin/R13/boot/config.boot" > } > > [edit] > > > Route information for router R10 : > > beheer at R13> show route table ipv4 unicast final > 0.0.0.0/0 [static(1)/1] > > to 172.17.1.2 via epair6a/epair6a > 10.1.1.0/24 [connected(0)/0] > > via ebr0/ebr0 > 172.17.1.0/24 [connected(0)/0] > > via epair6a/epair6a > > > beheer at R13> show bgp routes > Peer 1: local 10.1.1.13/179 remote 10.1.1.4/179 > beheer at R13> show bgp routes > Status Codes: * valid route, > best route > Origin Codes: i IGP, e EGP, ? incomplete > > Prefix Nexthop Peer AS Path > ------ ------- ---- ------- > *> 0.0.0.0/0 172.17.1.2 0.0.0.0 i > beheer at R13> > > > With best regards, > Edwin > > > > > > > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > From greearb at candelatech.com Fri Aug 20 15:33:11 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 20 Aug 2010 15:33:11 -0700 Subject: [Xorp-users] BGP router is not receiving BGP routes In-Reply-To: <243A5F30-BB13-4F3D-AB12-EA25B0F45DE1@spacebugs.nl> References: <243A5F30-BB13-4F3D-AB12-EA25B0F45DE1@spacebugs.nl> Message-ID: <4C6F02A7.7000708@candelatech.com> On 08/20/2010 03:25 PM, Edwin Schokkenbroek wrote: > > On Aug 19, 2010, at 8:36 PM, Aleksandar Cvjetic wrote: > >> Hello, >> >> On R4 try to configure a policy matching protocol OSPF routes and apply it as export BGP policy (as you did for static routes on R13). I think that Cisco logic doesn't work here, at least you don't have an option for "network" statement to advertise routes into BGP. > > Thanks for pointing this out. And Well Cisco logic, doesn't work indeed. After fighting with bgp and policies for a day and a long night, I got it working. I'm quite surprised to find out that only a policy which says: from protocol ospf ,for example isn't going to work. A network statement is required, which tells what prefix needs to be announced. In Junos I would do something like: set term 1 from protocol static ; set term 1 then accept. And 'm done (basically). Now that I begin to understand how it works with Xorp, it provides a very clean way to have full control over what prefix is to be announced by bgp. By the way, there were complaints from years ago that xorp bgp has performance issues when synchronizing with large route databases (I think the users were connecting to the full internet BGP routing table, or something like that). I was never able to set up a test to try to debug/optimize this, so if you are able to set up such a thing, I'm interested in knowing the results. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Fri Aug 20 16:01:52 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Sat, 21 Aug 2010 01:01:52 +0200 Subject: [Xorp-users] BGP router is not receiving BGP routes In-Reply-To: <4C6F02A7.7000708@candelatech.com> References: <243A5F30-BB13-4F3D-AB12-EA25B0F45DE1@spacebugs.nl> <4C6F02A7.7000708@candelatech.com> Message-ID: <9BD11841-74C8-4CA5-9BE9-1B4B7DE0CF5F@spacebugs.nl> On Aug 21, 2010, at 12:33 AM, Ben Greear wrote: > On 08/20/2010 03:25 PM, Edwin Schokkenbroek wrote: >> >> On Aug 19, 2010, at 8:36 PM, Aleksandar Cvjetic wrote: >> >>> Hello, >>> >>> On R4 try to configure a policy matching protocol OSPF routes and apply it as export BGP policy (as you did for static routes on R13). I think that Cisco logic doesn't work here, at least you don't have an option for "network" statement to advertise routes into BGP. >> >> Thanks for pointing this out. And Well Cisco logic, doesn't work indeed. After fighting with bgp and policies for a day and a long night, I got it working. I'm quite surprised to find out that only a policy which says: from protocol ospf ,for example isn't going to work. A network statement is required, which tells what prefix needs to be announced. In Junos I would do something like: set term 1 from protocol static ; set term 1 then accept. And 'm done (basically). Now that I begin to understand how it works with Xorp, it provides a very clean way to have full control over what prefix is to be announced by bgp. > > By the way, there were complaints from years ago that xorp bgp has performance issues when > synchronizing with large route databases (I think the users were connecting to the full internet > BGP routing table, or something like that). > > I was never able to set up a test to try to debug/optimize this, so if you > are able to set up such a thing, I'm interested in knowing the results. Should not be a problem. Right now I'm running multiple Xorp instances in jails, which reside in a virtual machine : JID IP Address Hostname Path 1 - local / 2 - R4 / 3 - R10 / 4 - R5 / 5 - R6 / 6 - R13 / 7 - R15 / 8 - R9 / 9 - R11 / 10 - R12 / 11 - R1 / 12 - R2 / 13 - R3 / 14 - R14 / I have a smal amount of prefixes, but with 15 jails running Xorp the machine load and memory usage is not high: last pid: 13948; load averages: 0.01, 0.02, 0.00 up 1+01:36:46 00:54:49 118 processes: 1 running, 117 sleeping CPU: 0.0% user, 0.0% nice, 0.4% system, 0.0% interrupt, 99.6% idle Mem: 288M Active, 56M Inact, 136M Wired, 111M Buf, 499M Free Swap: 256M Total, 256M Free When dealing with full routing tables ... I can image that a couple of these instances can effect performance. What is the best test to do ? Testing in a virtual machine, or testing it on real hardware (or both)? Memory will become a serious issue when loading full BGP routing table(s). Edwin > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > From greearb at candelatech.com Fri Aug 20 16:11:22 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 20 Aug 2010 16:11:22 -0700 Subject: [Xorp-users] BGP router is not receiving BGP routes In-Reply-To: <9BD11841-74C8-4CA5-9BE9-1B4B7DE0CF5F@spacebugs.nl> References: <243A5F30-BB13-4F3D-AB12-EA25B0F45DE1@spacebugs.nl> <4C6F02A7.7000708@candelatech.com> <9BD11841-74C8-4CA5-9BE9-1B4B7DE0CF5F@spacebugs.nl> Message-ID: <4C6F0B9A.8010103@candelatech.com> On 08/20/2010 04:01 PM, Edwin Schokkenbroek wrote: > When dealing with full routing tables ... I can image that a couple of these instances can effect performance. What is the best test to do ? > Testing in a virtual machine, or testing it on real hardware (or both)? Memory will become a serious issue when loading full BGP routing table(s). Well, running on real hardware should get you the best performance out of your hardware, but virtualization is also pretty good these days. As for memory use, etc..I really don't know how much xorp will need/use for lots of bgp prefixes. When you get it set up for performance testing, perhaps we could run xorp under oprofile (if using Linux), or some other tool to profile the code and see where best to optimize things. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Fri Aug 20 16:26:33 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Sat, 21 Aug 2010 01:26:33 +0200 Subject: [Xorp-users] BGP router is not receiving BGP routes In-Reply-To: <4C6F0B9A.8010103@candelatech.com> References: <243A5F30-BB13-4F3D-AB12-EA25B0F45DE1@spacebugs.nl> <4C6F02A7.7000708@candelatech.com> <9BD11841-74C8-4CA5-9BE9-1B4B7DE0CF5F@spacebugs.nl> <4C6F0B9A.8010103@candelatech.com> Message-ID: <26B34688-F304-4E53-8740-4B167CD716B2@spacebugs.nl> On Aug 21, 2010, at 1:11 AM, Ben Greear wrote: > On 08/20/2010 04:01 PM, Edwin Schokkenbroek wrote: > >> When dealing with full routing tables ... I can image that a couple of these instances can effect performance. What is the best test to do ? >> Testing in a virtual machine, or testing it on real hardware (or both)? Memory will become a serious issue when loading full BGP routing table(s). > > Well, running on real hardware should get you the best performance out of your > hardware, but virtualization is also pretty good these days. Yep. Well I can see if I can do both test. > > As for memory use, etc..I really don't know how much xorp will need/use > for lots of bgp prefixes. One way to find it out .. testing :-) > > When you get it set up for performance testing, perhaps we could > run xorp under oprofile (if using Linux), or some other tool to > profile the code and see where best to optimize things. That sounds like a good thing. But I will need help on oprofile, because I never used it. I was planning to transfer my current setup to real hardware. My current setup uses FreeBSD. The reason for using FreeBSD is that jails have little overhead compare to other approaches known to me. Monday I'll ask at work if I can use a server for this. Then I have some real fast hardware to test on :-). If FreeBSD is not an option, I can always test on linux, running just one Xorp instance. And loading full routing table. Edwin > > Thanks, > Ben > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > From greearb at candelatech.com Fri Aug 20 16:37:36 2010 From: greearb at candelatech.com (Ben Greear) Date: Fri, 20 Aug 2010 16:37:36 -0700 Subject: [Xorp-users] BGP router is not receiving BGP routes In-Reply-To: <26B34688-F304-4E53-8740-4B167CD716B2@spacebugs.nl> References: <243A5F30-BB13-4F3D-AB12-EA25B0F45DE1@spacebugs.nl> <4C6F02A7.7000708@candelatech.com> <9BD11841-74C8-4CA5-9BE9-1B4B7DE0CF5F@spacebugs.nl> <4C6F0B9A.8010103@candelatech.com> <26B34688-F304-4E53-8740-4B167CD716B2@spacebugs.nl> Message-ID: <4C6F11C0.4080200@candelatech.com> On 08/20/2010 04:26 PM, Edwin Schokkenbroek wrote: >> When you get it set up for performance testing, perhaps we could >> run xorp under oprofile (if using Linux), or some other tool to >> profile the code and see where best to optimize things. > > That sounds like a good thing. But I will need help on oprofile, because I never used it. > I was planning to transfer my current setup to real hardware. My current setup uses FreeBSD. The reason for using FreeBSD is that jails have little overhead compare to other approaches known to me. Monday I'll ask at work if I can use a server for this. Then I have some real fast hardware to test on :-). If FreeBSD is not an option, I can always test on linux, running just one Xorp instance. And loading full routing table. I can do useful work on Linux, but am mostly worthless on BSD, so I'd definitely prefer Linux. I think for perf testing, using a single xorp instance would make things easiest. Oprofile is a bit ticklish sometimes, but usually isn't too hard. It would be nice to run on fast hardware, but for doing optimization, a slower (or virtual) system should be fine too. On the off chance it's convenient to give out ssh access, I'd enjoy poking at a Linux system able to load the full bgp tables. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From sekhar at copperheadsystems.com Fri Aug 20 21:16:02 2010 From: sekhar at copperheadsystems.com (sekhar at copperheadsystems.com) Date: Fri, 20 Aug 2010 22:16:02 -0600 Subject: [Xorp-users] How to configure IGMP in XORP ROUTER In-Reply-To: References: Message-ID: <876787e4af75d4c93da1c4947b982196.squirrel@mail.copperheadsystems.com> Hi all , Please see the attachment and help me regarding IGMP configuration in XORP ROUTER. Thanks , Sekhar -------------- next part -------------- A non-text attachment was scrubbed... Name: IGMP Topology.doc Type: application/msword Size: 21504 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100820/9871d58e/attachment-0001.doc From weaver at ascr.doe.gov Sun Aug 22 06:23:50 2010 From: weaver at ascr.doe.gov (Mike Weaver) Date: Sun, 22 Aug 2010 09:23:50 -0400 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <4C6EDB43.3030401@candelatech.com> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> <4C6D763A.9010608@candelatech.com> <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> <4C6D8519.3090101@candelatech.com> <010601cb4055$cc491310$64db3930$@ascr.doe.gov> <4C6ED3A9.5090100@candelatech.com> <000001cb409c$f57eb9f0$e07c2dd0$@ascr.doe.gov> <4C6EDB43.3030401@candelatech.com> Message-ID: <20100822092350.155172itnt9v8vks@mail.ascr.doe.gov> I'm much more versed in Linux than BSD anyway, just curious. We're a research organization and trying to scale back both our network infrastructure as well as the use of commercial/proprietary products. We're currently running a Cisco 7206 VXR router, multiple IDS systems (commercial & research) and Websense for content monitoring/blocking. Our lead read about Vyatta providing similar/better performance than Cisco without the hardware & maintenance costs, while also providing firewall (iptables) and content filtering (squidGuard) support. Unfortunately, Quagga doesn't support multicast and I don't have time to see if I make it work with things like pimd. Anyway, xorp looked like a good choice to evaluate and we're generally pretty impressed. When we discuss my evaluation results, we may end up deciding to go with another box or 2 behind the router to handle firewalling & content filtering. It would have been nice to get it all in one box from a complexity & cost standpoint (we're a small organization w/ limited resources). Anyway, thanks for all your work on xorp-CT and your quick assistance to my inquiries! Mike -- Mike Weaver Office of Advanced Scientific Computing Research US Department of Energy T: 301-903-0072 F: 301-903-7774 Quoting Ben Greear : > On 08/20/2010 12:21 PM, Mike Weaver wrote: >> Ok, I'll try that - thanks. Do you know if this still works on FreeBSD? >> You seem to indicate that it's a Linux thing only. > > I've never done more than compile on BSD, but it might work there. > > Might have to hack on scons for BSD as well..probably somewhat similar > to what I did for Linux. > > I'm curious: Why use xorp for firewalling instead of some > third-party thing that manipulates iptables? > > Thanks, > Ben > > > -- > Ben Greear > Candela Technologies Inc http://www.candelatech.com > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From p_latini at hotmail.com Sun Aug 22 08:52:35 2010 From: p_latini at hotmail.com (Patricio Latini) Date: Sun, 22 Aug 2010 12:52:35 -0300 Subject: [Xorp-users] How to configure IGMP in XORP ROUTER In-Reply-To: <876787e4af75d4c93da1c4947b982196.squirrel@mail.copperheadsystems.com> References: <876787e4af75d4c93da1c4947b982196.squirrel@mail.copperheadsystems.com> Message-ID: Sekhar, I have it working in my lab. This would be the configuration that applies to your case. Regards Patricio plumbing { mfea4 { disable: false interface eth0 { vif eth0 { disable: false } } interface eth1 { vif eth1 { disable: false } } } } protocols { igmp { disable: false interface eth0 { vif eth0 { 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 eth1 { vif eth1 { disable: false version: 2 enable-ip-router-alert-option-check: false query-interval: 125 query-last-member-interval: 1 query-response-interval: 10 robust-count: 2 } } } pimsm4 { disable: false interface eth0 { vif eth0 { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } interface eth1 { vif eth1 { disable: false dr-priority: 1 hello-period: 30 hello-triggered-delay: 5 } } static-rps { rp 192.168.11.96 { group-prefix 224.4.4.0/24 { rp-priority: 192 hash-mask-len: 30 } } } } } interfaces { restore-original-config-on-shutdown: false interface eth0 { description: "" disable: false discard: false unreachable: false management: false vif eth0 { disable: false address 192.168.11.96 { prefix-length: 24 disable: false } } } interface eth1 { description: "" disable: false discard: false unreachable: false management: false vif eth1 { disable: false address 192.168.10.96 { prefix-length: 24 disable: false } } } } -----Original Message----- From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On Behalf Of sekhar at copperheadsystems.com Sent: Saturday, August 21, 2010 1:16 AM To: xorp-users at xorp.org Subject: Re: [Xorp-users] How to configure IGMP in XORP ROUTER Hi all , Please see the attachment and help me regarding IGMP configuration in XORP ROUTER. Thanks , Sekhar From greearb at candelatech.com Mon Aug 23 09:38:59 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 23 Aug 2010 09:38:59 -0700 Subject: [Xorp-users] SNMP & xorp 1.8.2-CT In-Reply-To: <20100822092350.155172itnt9v8vks@mail.ascr.doe.gov> References: <00db01cb3fca$ab8c3f70$02a4be50$@ascr.doe.gov> <4C6D763A.9010608@candelatech.com> <00e501cb3fd3$c5835900$508a0b00$@ascr.doe.gov> <4C6D8519.3090101@candelatech.com> <010601cb4055$cc491310$64db3930$@ascr.doe.gov> <4C6ED3A9.5090100@candelatech.com> <000001cb409c$f57eb9f0$e07c2dd0$@ascr.doe.gov> <4C6EDB43.3030401@candelatech.com> <20100822092350.155172itnt9v8vks@mail.ascr.doe.gov> Message-ID: <4C72A423.4070107@candelatech.com> On 08/22/2010 06:23 AM, Mike Weaver wrote: > I'm much more versed in Linux than BSD anyway, just curious. We're a > research organization and trying to scale back both our network > infrastructure as well as the use of commercial/proprietary products. > We're currently running a Cisco 7206 VXR router, multiple IDS systems > (commercial & research) and Websense for content monitoring/blocking. > > Our lead read about Vyatta providing similar/better performance than > Cisco without the hardware & maintenance costs, while also providing > firewall (iptables) and content filtering (squidGuard) support. > Unfortunately, Quagga doesn't support multicast and I don't have time to > see if I make it work with things like pimd. > > Anyway, xorp looked like a good choice to evaluate and we're generally > pretty impressed. When we discuss my evaluation results, we may end up > deciding to go with another box or 2 behind the router to handle > firewalling & content filtering. It would have been nice to get it all > in one box from a complexity & cost standpoint (we're a small > organization w/ limited resources). Even if xorp can't do the firewalling you want (and maybe it can with the patch I posted a few days ago), you could run third-party firewall scripts, or write your own iptables scripts and have that run beside xorp. I don't think either would interfere with the other as long as your firewall rules let appropriate router traffic flow properly. Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com From edwin at spacebugs.nl Mon Aug 23 11:03:40 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Mon, 23 Aug 2010 20:03:40 +0200 Subject: [Xorp-users] BGP router is not receiving BGP routes In-Reply-To: <4C6F11C0.4080200@candelatech.com> References: <243A5F30-BB13-4F3D-AB12-EA25B0F45DE1@spacebugs.nl> <4C6F02A7.7000708@candelatech.com> <9BD11841-74C8-4CA5-9BE9-1B4B7DE0CF5F@spacebugs.nl> <4C6F0B9A.8010103@candelatech.com> <26B34688-F304-4E53-8740-4B167CD716B2@spacebugs.nl> <4C6F11C0.4080200@candelatech.com> Message-ID: <658CE1DD-F71E-43A6-B2F3-79DC4CDD31C3@spacebugs.nl> On Aug 21, 2010, at 1:37 AM, Ben Greear wrote: > On 08/20/2010 04:26 PM, Edwin Schokkenbroek wrote: > >>> When you get it set up for performance testing, perhaps we could >>> run xorp under oprofile (if using Linux), or some other tool to >>> profile the code and see where best to optimize things. >> >> That sounds like a good thing. But I will need help on oprofile, because I never used it. >> I was planning to transfer my current setup to real hardware. My current setup uses FreeBSD. The reason for using FreeBSD is that jails have little overhead compare to other approaches known to me. Monday I'll ask at work if I can use a server for this. Then I have some real fast hardware to test on :-). If FreeBSD is not an option, I can always test on linux, running just one Xorp instance. And loading full routing table. > > I can do useful work on Linux, but am mostly worthless on BSD, so I'd definitely > prefer Linux. > > I think for perf testing, using a single xorp instance would make things easiest. > > Oprofile is a bit ticklish sometimes, but usually isn't too hard. > > It would be nice to run on fast hardware, but for doing optimization, a slower (or virtual) > system should be fine too. On the off chance it's convenient to give out > ssh access, I'd enjoy poking at a Linux system able to load the full bgp tables. I contact you on your private email address if this is ok with you. Cause this will only will produce noise on the mailing list. 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 wubaochuan at seu.edu.cn Tue Aug 24 05:36:28 2010 From: wubaochuan at seu.edu.cn (wubaochuan) Date: Tue, 24 Aug 2010 20:36:28 +0800 Subject: [Xorp-users] Help, BGP seems do not work. Message-ID: <482653499.10783@seu.edu.cn> Dear everyone, I installed XORP on fedora12, and I have turned off firewall of fedora12. Now I have struggled with BGP for several days, but still I don't solve the problem(It seems that BGP do not work), and I do not know what is wrong. I hope someone can tell me where is the problem. Thank you in advance. Figure 1 is the topology: RA: router A. eth0 with IP address 10.0.1.2 eth1 with IP address 10.0.2.1 RB: router B. eth0 with IP address 10.0.2.2 eth1 with IP address 10.0.3.1 RA and RB are in the same AS with AS number 23456. RC: router C. eth0 with IP address 10.0.3.2 eth1 with IP address 10.0.4.1 RD: router D. eth0 with IP address 10.0.4.2 eth1 with IP address 10.0.5.2 RA and RB are in the same AS with AS number 23457. host1 and host2 are hosts, their IP addresses are 10.0.1.1 and 10.0.5.1 respectively. Inside each AS, OSPF is configured. And between RB and RC, BGP is configured. But now, host1 and host2 can not reach each other. 10.0.2.1 10.0.2.2 10.0.3.1 10.0.3.2 10.0.4.1 10.0.4.2 _________ _________ _________ _________ | | | | | | eth0| | | RA |eth1 | RB |eth1 eth0| RC |________| RD | | |_______| |__________| |eth1 | | | | eth0 | | | | | | | | | | | | | | |_________| |_________| |_________| |_________| | 10.0.1.2 10.0.5.2| | eth0 |eth1 | | | | | | _____|___ 10.0.1.1 10.0.5.1 | eth0 | | eth0 ____|___ | host1 | | | | | | host2 | | | | | | | | | |_________| | | |_________| figure 1: My topology. sorry for poor drawing. configure file of RA: interfaces { interface eth0 { vif eth0 { address 10.0.1.2 { prefix-length: 24 } } } interface eth1 { vif eth1 { address 10.0.2.1 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false } } protocols { ospf4 { router-id: 10.0.2.1 area 0.0.0.0 { interface eth1 { vif eth1 { address 10.0.2.1 { } } } } area 0.0.0.0 { interface eth0 { vif eth0 { address 10.0.1.2 { } } } } } } ============================================================================ configure file of RB: interfaces { interface eth0 { vif eth0 { address 10.0.2.2 { prefix-length: 24 } } } interface eth1 { vif eth1 { address 10.0.3.1 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false } } policy{ policy-statement connectedroute{ term connectedexport{ from{ protocol:"connected" } } } policy-statement ospf2bgp{ term ospf2bgp{ from{ protocol:"ospf4" } } } policy-statement bgp2ospf{ term ospf2bgp{ from{ protocol:"bgp" } } } } protocols { ospf4 { router-id: 10.0.2.2 export:"connectedroute" export:"bgp2ospf" area 0.0.0.0 { interface eth0 { vif eth0 { address 10.0.2.2 { } } } } } bgp { bgp-id: 10.0.2.2 local-as: 23456 export:"connectedroute" export:"ospf2bgp" peer 10.0.3.2 { local-ip: 10.0.3.1 as: 23457 next-hop: 10.0.3.1 } } } =============================================================================== configure file of RC: interfaces { interface eth0 { vif eth0 { address 10.0.3.2 { prefix-length: 24 } } } interface eth1 { vif eth1 { address 10.0.4.1 { prefix-length: 24 } } } interface eth2 { vif eth2 { address 10.0.6.1 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false /*enable ipv4 forwarding*/ } } policy{ policy-statement connectedroute{ term connectedexport{ from{ protocol:"connected" } } } policy-statement ospf2bgp{ term ospf2bgp{ from{ protocol:"ospf4" } } } policy-statement bgp2ospf{ term ospf2bgp{ from{ protocol:"bgp" } } } } protocols { ospf4 { router-id: 10.0.4.1 export:"connectedroute" export:"bgp2ospf" area 0.0.0.0 { interface eth1 { vif eth1 { address 10.0.4.1 { } } } } area 0.0.0.0 { interface eth2 { vif eth2 { address 10.0.6.1 { } } } } } bgp { bgp-id: 10.0.3.2 local-as: 23457 /*export: "export-connected"*/ export:"connectedroute" export:"ospf2bgp" peer 10.0.3.1 { local-ip: 10.0.3.2 as: 23456 next-hop: 10.0.3.2 } } } ================================================================== configure file of RD: interfaces { interface eth0 { vif eth0 { address 10.0.4.2 { prefix-length: 24 } } } interface eth1 { vif eth1 { address 10.0.5.2 { prefix-length: 24 } } } } fea { unicast-forwarding4 { disable: false } } protocols { ospf4 { router-id: 10.0.4.2 area 0.0.0.0 { interface eth0 { vif eth0 { address 10.0.4.2 { } } } } area 0.0.0.0 { interface eth1 { vif eth1 { address 10.0.5.2 { } } } } } } ================================================================= Yours Chuan From wubaochuan at seu.edu.cn Tue Aug 24 05:42:08 2010 From: wubaochuan at seu.edu.cn (wubaochuan) Date: Tue, 24 Aug 2010 20:42:08 +0800 Subject: [Xorp-users] Help, BGP seems do not work Message-ID: <482653839.11549@seu.edu.cn> Dear everyone, Sorry for ugly drawing of the figure in the email just sent. The attachment of this email is a PNG image of the figure in the email just sent. Thank you for any help. Yours Chuan -------------- next part -------------- A non-text attachment was scrubbed... Name: AS.png Type: image/png Size: 26089 bytes Desc: not available Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100824/7f230baa/attachment-0001.bin From edwin at spacebugs.nl Tue Aug 24 06:34:03 2010 From: edwin at spacebugs.nl (Edwin Schokkenbroek) Date: Tue, 24 Aug 2010 15:34:03 +0200 Subject: [Xorp-users] Help, BGP seems do not work. In-Reply-To: References: Message-ID: <4C73CA4B.80005@spacebugs.nl> Hello Chuan, It seems you don't have specified which prefixes are allowed to be announced. Add network statements to your policy. See my earlier postings on this list. Hope this helps. With best regards, Edwin xorp-users-request at xorp.org schreef: > Dear everyone, > I installed XORP on fedora12, and I have turned off firewall of > fedora12. Now I have struggled with BGP for several days, but still I > don't solve the problem(It seems that BGP do not work), and I do not > know what is wrong. I hope someone can tell me where is the problem. > Thank you in advance. > > Figure 1 is the topology: > RA: router A. eth0 with IP address 10.0.1.2 > eth1 with IP address 10.0.2.1 > RB: router B. eth0 with IP address 10.0.2.2 > eth1 with IP address 10.0.3.1 > RA and RB are in the same AS with AS number 23456. > > RC: router C. eth0 with IP address 10.0.3.2 > eth1 with IP address 10.0.4.1 > RD: router D. eth0 with IP address 10.0.4.2 > eth1 with IP address 10.0.5.2 > RA and RB are in the same AS with AS number 23457. > > host1 and host2 are hosts, their IP addresses are 10.0.1.1 and > 10.0.5.1 respectively. > > > Inside each AS, OSPF is configured. And between RB and RC, BGP is > configured. > > But now, host1 and host2 can not reach each other. > > > > 10.0.2.1 10.0.2.2 10.0.3.1 10.0.3.2 10.0.4.1 > 10.0.4.2 > _________ _________ > _________ _________ > | | | | > | | eth0| | > | RA |eth1 | RB |eth1 eth0| RC > |________| RD | > | |_______| |__________| > |eth1 | | > | | eth0 | | > | | | | > | | | | > | | | | > |_________| |_________| > |_________| |_________| > | 10.0.1.2 > 10.0.5.2| > | eth0 > |eth1 > | > | > > | > | > > | > | > _____|___ 10.0.1.1 > 10.0.5.1 | eth0 > | | eth0 > ____|___ > | host1 | > | | > | | > | host2 | > | | > | | > | | > | | > |_________| > | | > > |_________| > > figure 1: My topology. sorry for poor drawing. > > > > configure file of RA: > interfaces { > interface eth0 { > vif eth0 { > address 10.0.1.2 { > prefix-length: 24 > } > } > } > interface eth1 { > vif eth1 { > address 10.0.2.1 { > prefix-length: 24 > } > } > } > } > > > > > fea { > unicast-forwarding4 { > disable: false > } > } > > > > protocols { > ospf4 { > router-id: 10.0.2.1 > area 0.0.0.0 { > interface eth1 { > vif eth1 { > address 10.0.2.1 { > } > } > } > } > > area 0.0.0.0 { > interface eth0 { > vif eth0 { > address 10.0.1.2 { > } > } > } > } > } > } > ============================================================================ > > configure file of RB: > interfaces { > interface eth0 { > vif eth0 { > address 10.0.2.2 { > prefix-length: 24 > } > } > } > interface eth1 { > vif eth1 { > address 10.0.3.1 { > prefix-length: 24 > } > } > } > } > > fea { > unicast-forwarding4 { > disable: false > } > } > > policy{ > > policy-statement connectedroute{ > term connectedexport{ > from{ > protocol:"connected" > } > } > } > > policy-statement ospf2bgp{ > term ospf2bgp{ > from{ > protocol:"ospf4" > } > } > } > policy-statement bgp2ospf{ > term ospf2bgp{ > from{ > protocol:"bgp" > } > } > } > > } > protocols { > ospf4 { > router-id: 10.0.2.2 > > export:"connectedroute" > export:"bgp2ospf" > area 0.0.0.0 { > interface eth0 { > vif eth0 { > address 10.0.2.2 { > } > } > } > } > } > bgp { > bgp-id: 10.0.2.2 > local-as: 23456 > export:"connectedroute" > export:"ospf2bgp" > peer 10.0.3.2 { > local-ip: 10.0.3.1 > as: 23457 > next-hop: 10.0.3.1 > } > } > } > > =============================================================================== > configure file of RC: > > interfaces { > interface eth0 { > vif eth0 { > address 10.0.3.2 { > prefix-length: 24 > } > } > } > interface eth1 { > vif eth1 { > address 10.0.4.1 { > prefix-length: 24 > } > } > } > interface eth2 { > vif eth2 { > address 10.0.6.1 { > prefix-length: 24 > } > } > } > } > > > > > fea { > unicast-forwarding4 { > disable: false /*enable ipv4 forwarding*/ > } > } > > policy{ > policy-statement connectedroute{ > term connectedexport{ > from{ > protocol:"connected" > } > } > } > > policy-statement ospf2bgp{ > term ospf2bgp{ > from{ > protocol:"ospf4" > } > } > } > policy-statement bgp2ospf{ > term ospf2bgp{ > from{ > protocol:"bgp" > } > } > } > } > > protocols { > ospf4 { > router-id: 10.0.4.1 > export:"connectedroute" > export:"bgp2ospf" > area 0.0.0.0 { > interface eth1 { > vif eth1 { > address 10.0.4.1 { > } > } > } > } > area 0.0.0.0 { > interface eth2 { > vif eth2 { > address 10.0.6.1 { > } > } > } > } > } > bgp { > bgp-id: 10.0.3.2 > local-as: 23457 > /*export: "export-connected"*/ > export:"connectedroute" > export:"ospf2bgp" > peer 10.0.3.1 { > local-ip: 10.0.3.2 > as: 23456 > next-hop: 10.0.3.2 > } > } > } > > > ================================================================== > configure file of RD: > > interfaces { > interface eth0 { > vif eth0 { > address 10.0.4.2 { > prefix-length: 24 > } > } > } > interface eth1 { > vif eth1 { > address 10.0.5.2 { > prefix-length: 24 > } > } > } > } > > fea { > unicast-forwarding4 { > disable: false > } > } > > protocols { > ospf4 { > router-id: 10.0.4.2 > area 0.0.0.0 { > interface eth0 { > vif eth0 { > address 10.0.4.2 { > } > } > } > } > > area 0.0.0.0 { > interface eth1 { > vif eth1 { > address 10.0.5.2 { > } > } > } > } > } > } > > ================================================================= > > Yours > Chuan > > > > From greearb at candelatech.com Tue Aug 24 16:17:42 2010 From: greearb at candelatech.com (Ben Greear) Date: Tue, 24 Aug 2010 16:17:42 -0700 Subject: [Xorp-users] Fwd: Using GPU to do packet forwarding Message-ID: <4C745316.7010200@candelatech.com> Not really related to xorp, but these guys are getting massive routing throughput on commodity hardware! -------- Original Message -------- Subject: Using GPU to do packet forwarding Date: Tue, 24 Aug 2010 15:15:07 -0700 From: Stephen Hemminger Organization: Vyatta To: David Miller , Eric Dumazet , netdev at vger.kernel.org Interesting paper: http://www.ndsl.kaist.edu/~kyoungsoo/papers/packetshader.pdf One section of general consideration is the expense of the current skb scheme. At 10G, they measure 60% of the CPU is used doing skb alloc/free; see paper for the alternative of using a huge packet buffer. Also, they managed to shrink skb to 8 bytes! -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From wubaochuan at seu.edu.cn Tue Aug 24 17:27:05 2010 From: wubaochuan at seu.edu.cn (wubaochuan) Date: Wed, 25 Aug 2010 08:27:05 +0800 Subject: [Xorp-users] Help, BGP seems do not work. In-Reply-To: <482676482.10744@seu.edu.cn> References: <482676482.10744@seu.edu.cn> Message-ID: <482696146.04304@seu.edu.cn> Hello Edwin, Thank you for your help, I will try. Yours Chuan xorp-users-request at xorp.org wrote: > 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. Help, BGP seems do not work. (Edwin Schokkenbroek) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 24 Aug 2010 15:34:03 +0200 > From: Edwin Schokkenbroek > Subject: [Xorp-users] Help, BGP seems do not work. > To: xorp-users at xorp.org > Message-ID: <4C73CA4B.80005 at spacebugs.nl> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hello Chuan, > > It seems you don't have specified which prefixes are allowed to be > announced. Add network statements to your policy. See my earlier > postings on this list. > Hope this helps. > > With best regards, > > Edwin > > > > xorp-users-request at xorp.org schreef: > >> Dear everyone, >> I installed XORP on fedora12, and I have turned off firewall of >> fedora12. Now I have struggled with BGP for several days, but still I >> don't solve the problem(It seems that BGP do not work), and I do not >> know what is wrong. I hope someone can tell me where is the problem. >> Thank you in advance. >> >> Figure 1 is the topology: >> RA: router A. eth0 with IP address 10.0.1.2 >> eth1 with IP address 10.0.2.1 >> RB: router B. eth0 with IP address 10.0.2.2 >> eth1 with IP address 10.0.3.1 >> RA and RB are in the same AS with AS number 23456. >> >> RC: router C. eth0 with IP address 10.0.3.2 >> eth1 with IP address 10.0.4.1 >> RD: router D. eth0 with IP address 10.0.4.2 >> eth1 with IP address 10.0.5.2 >> RA and RB are in the same AS with AS number 23457. >> >> host1 and host2 are hosts, their IP addresses are 10.0.1.1 and >> 10.0.5.1 respectively. >> >> >> Inside each AS, OSPF is configured. And between RB and RC, BGP is >> configured. >> >> But now, host1 and host2 can not reach each other. >> >> >> >> 10.0.2.1 10.0.2.2 10.0.3.1 10.0.3.2 10.0.4.1 >> 10.0.4.2 >> _________ _________ >> _________ _________ >> | | | | >> | | eth0| | >> | RA |eth1 | RB |eth1 eth0| RC >> |________| RD | >> | |_______| |__________| >> |eth1 | | >> | | eth0 | | >> | | | | >> | | | | >> | | | | >> |_________| |_________| >> |_________| |_________| >> | 10.0.1.2 >> 10.0.5.2| >> | eth0 >> |eth1 >> | >> | >> >> | >> | >> >> | >> | >> _____|___ 10.0.1.1 >> 10.0.5.1 | eth0 >> | | eth0 >> ____|___ >> | host1 | >> | | >> | | >> | host2 | >> | | >> | | >> | | >> | | >> |_________| >> | | >> >> |_________| >> >> figure 1: My topology. sorry for poor drawing. >> >> >> >> configure file of RA: >> interfaces { >> interface eth0 { >> vif eth0 { >> address 10.0.1.2 { >> prefix-length: 24 >> } >> } >> } >> interface eth1 { >> vif eth1 { >> address 10.0.2.1 { >> prefix-length: 24 >> } >> } >> } >> } >> >> >> >> >> fea { >> unicast-forwarding4 { >> disable: false >> } >> } >> >> >> >> protocols { >> ospf4 { >> router-id: 10.0.2.1 >> area 0.0.0.0 { >> interface eth1 { >> vif eth1 { >> address 10.0.2.1 { >> } >> } >> } >> } >> >> area 0.0.0.0 { >> interface eth0 { >> vif eth0 { >> address 10.0.1.2 { >> } >> } >> } >> } >> } >> } >> ============================================================================ >> >> configure file of RB: >> interfaces { >> interface eth0 { >> vif eth0 { >> address 10.0.2.2 { >> prefix-length: 24 >> } >> } >> } >> interface eth1 { >> vif eth1 { >> address 10.0.3.1 { >> prefix-length: 24 >> } >> } >> } >> } >> >> fea { >> unicast-forwarding4 { >> disable: false >> } >> } >> >> policy{ >> >> policy-statement connectedroute{ >> term connectedexport{ >> from{ >> protocol:"connected" >> } >> } >> } >> >> policy-statement ospf2bgp{ >> term ospf2bgp{ >> from{ >> protocol:"ospf4" >> } >> } >> } >> policy-statement bgp2ospf{ >> term ospf2bgp{ >> from{ >> protocol:"bgp" >> } >> } >> } >> >> } >> protocols { >> ospf4 { >> router-id: 10.0.2.2 >> >> export:"connectedroute" >> export:"bgp2ospf" >> area 0.0.0.0 { >> interface eth0 { >> vif eth0 { >> address 10.0.2.2 { >> } >> } >> } >> } >> } >> bgp { >> bgp-id: 10.0.2.2 >> local-as: 23456 >> export:"connectedroute" >> export:"ospf2bgp" >> peer 10.0.3.2 { >> local-ip: 10.0.3.1 >> as: 23457 >> next-hop: 10.0.3.1 >> } >> } >> } >> >> =============================================================================== >> configure file of RC: >> >> interfaces { >> interface eth0 { >> vif eth0 { >> address 10.0.3.2 { >> prefix-length: 24 >> } >> } >> } >> interface eth1 { >> vif eth1 { >> address 10.0.4.1 { >> prefix-length: 24 >> } >> } >> } >> interface eth2 { >> vif eth2 { >> address 10.0.6.1 { >> prefix-length: 24 >> } >> } >> } >> } >> >> >> >> >> fea { >> unicast-forwarding4 { >> disable: false /*enable ipv4 forwarding*/ >> } >> } >> >> policy{ >> policy-statement connectedroute{ >> term connectedexport{ >> from{ >> protocol:"connected" >> } >> } >> } >> >> policy-statement ospf2bgp{ >> term ospf2bgp{ >> from{ >> protocol:"ospf4" >> } >> } >> } >> policy-statement bgp2ospf{ >> term ospf2bgp{ >> from{ >> protocol:"bgp" >> } >> } >> } >> } >> >> protocols { >> ospf4 { >> router-id: 10.0.4.1 >> export:"connectedroute" >> export:"bgp2ospf" >> area 0.0.0.0 { >> interface eth1 { >> vif eth1 { >> address 10.0.4.1 { >> } >> } >> } >> } >> area 0.0.0.0 { >> interface eth2 { >> vif eth2 { >> address 10.0.6.1 { >> } >> } >> } >> } >> } >> bgp { >> bgp-id: 10.0.3.2 >> local-as: 23457 >> /*export: "export-connected"*/ >> export:"connectedroute" >> export:"ospf2bgp" >> peer 10.0.3.1 { >> local-ip: 10.0.3.2 >> as: 23456 >> next-hop: 10.0.3.2 >> } >> } >> } >> >> >> ================================================================== >> configure file of RD: >> >> interfaces { >> interface eth0 { >> vif eth0 { >> address 10.0.4.2 { >> prefix-length: 24 >> } >> } >> } >> interface eth1 { >> vif eth1 { >> address 10.0.5.2 { >> prefix-length: 24 >> } >> } >> } >> } >> >> fea { >> unicast-forwarding4 { >> disable: false >> } >> } >> >> protocols { >> ospf4 { >> router-id: 10.0.4.2 >> area 0.0.0.0 { >> interface eth0 { >> vif eth0 { >> address 10.0.4.2 { >> } >> } >> } >> } >> >> area 0.0.0.0 { >> interface eth1 { >> vif eth1 { >> address 10.0.5.2 { >> } >> } >> } >> } >> } >> } >> >> ================================================================= >> >> Yours >> Chuan >> >> >> >> >> > > > > ------------------------------ > > _______________________________________________ > Xorp-users mailing list > Xorp-users at xorp.org > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > > > End of Xorp-users Digest, Vol 53, Issue 24 > ****************************************** > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100825/4c004f63/attachment.html From coolria at 126.com Thu Aug 26 19:29:33 2010 From: coolria at 126.com (yang) Date: Fri, 27 Aug 2010 10:29:33 +0800 (CST) Subject: [Xorp-users] About using click as FEA in another machine Message-ID: <1e03945.1ff6.12ab160ee55.Coremail.coolria@126.com> I want to use click as FEA in computer A, use xorp in computer B, I wonder if B could control A's forwarding table. That means click and xorp are in two different computers. can xorp could do this?how to config? thanks in advance!!!!! (sorry for my poor English :( ) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100827/9487091d/attachment.html From marc.mueller at broadbandnetworks.ch Fri Aug 27 04:19:23 2010 From: marc.mueller at broadbandnetworks.ch (=?iso-8859-1?Q?Marc_M=FCller?=) Date: Fri, 27 Aug 2010 13:19:23 +0200 Subject: [Xorp-users] IGMP messages ignored Message-ID: Hi list, I want to force XORP to accept any IGMP control message on a given interface regardless of the requesters IP address. Unfortunately XORP doesn't process the request if its source IP address doesn't match the kernel routing table. Rp_filter is disabled for all interfaces. How can I override this behavior? According to the 1.6 release notes, XORP used to handle this differently: "- Ignore control messages if the source address is not directly connected." Thanks for any help Marc From danielcamara at gmail.com Mon Aug 30 02:58:21 2010 From: danielcamara at gmail.com (Daniel Camara) Date: Mon, 30 Aug 2010 11:58:21 +0200 Subject: [Xorp-users] Problems with PIM-SSM In-Reply-To: References: Message-ID: Hi, ?I new using XORP, and I am with a small problem, probably is something very stupid like a configuration or a routing missing, but I really can not see it :(. ? I have a simple scenario with two linux machines, neighbor ones in the same network, connected by a cable. This is a small part of a bigger scenario. However I cannot manage to make a simple Multicast PIM-SSM data traffic to be received in clients of these two machines. The scenario is as follows: +-----------+ ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?? +----------+ | machine1?|---eth02---------------------eth0---| machine2 | +-----------+192.168.14.1 ? ?? 192.168.14.53 +----------+ The two machines are connected directly by a cable and they can ping each other. However when I start a multicast traffic, in any of them, I can not see the data arriving in the client. I am using the same commands as described in http://www.columbia.edu/~alan/igmp/#SSM. The line of the data source is: root at machine1# iperf -u -c 232.5.6.7 -p 8910 -T 10 -b 1 -i 5 -t 1200 The line used at the client is (code get from http://www.columbia.edu/~alan/igmp/rtpqual.c): root at machine1# ./rtpqual 192.168.14.1 at 232.5.6.7 8910 root at machine2# ./rtpqual 192.168.14.1 at 232.5.6.7 8910 I tried to put the server in both machines, the odd thing is that when I start the server at the machine 2? the client in the same machine sees and receives the data traffic, the client in the other machine don't. When I start? the iperf in the machine 1, none of the clients sees the traffic, not even the one in the same machine.? Other thing that I perceived is that when I start the traffic in the machine 2, the XORP in machine 1 receives the data packets, even before the register of the client. The inverse is not true, when I start the server in Machine 1 the XORP instance in machine 2 does not receive anything. To be honest I really don't understand why this happens.? Shouldn't the traffic of PIM-SSM stop at the first router, at least until some client in another machine requests for the traffic? Well, in this case the first router is the one in the same machine of the server, isn't it?? I will add the logs and configurations of the machines below to try to give you a better view of what is going on. But, just to summarize, the main questions are: ?1.? Why the membership requests, from machine 1, does not arrive ?2.? Why, even when the membership request arrives, the data does not ?3.? Why, when the server is in machine 2 the client is able to receive the data from the local server, but not when the server in machine 1, and even stranger, why when I put the server in machine 1, not even its local client is able to register ?4.? Why when I add the server at machine 2, machine 1 is aware of the traffic and when I put the server in machine 1, machine 2 is not aware of the traffic, what was supposed to be the correct? ?5. As far as I know the PIM-SSM does not requires a Rendezvous? Point (RP) but when? I remove it? a warning message appears? saying that the traffic? over the 232.5.6.7 address has no RP, why this happens?? Will I always need a RP? Isn't the communication direct, since it has the Group and Server? ? Just now I perceived the size of the e-mail. I am? Sorry for this but I tried to add as much information as possible. At least when I am trying to help some one I normally think, the more information the better. ? Thanks in advance. ? Best regards.... ??? Daniel Camara ---------------------------------------------------------------------------- XORP LOGS: ---------- Server in machine 1: ---------------------------------------- // machine1 XORP log - Server and Client (...) [ 2010/08/30 10:00:38 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.14.53 to 224.0.0.22 on vif eth2 // here we see that the membership report for the request from machine 2 arrives but no data arrives to the client [ 2010/08/30 10:00:38 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (192.168.14.1, 232.5.6.7) on vif eth2 [ 2010/08/30 10:00:38 TRACE xorp_pimsm4 PIM ] Add membership for (192.168.14.1, 232.5.6.7) on vif eth2 [ 2010/08/30 10:00:39 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.14.53 to 224.0.0.22 on vif eth2 (...) // even the delete membership arrives for the client in machine2, but no membership arrived for the client in the same machine [ 2010/08/30 10:00:55 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (192.168.14.1, 232.5.6.7) on vif eth2 [ 2010/08/30 10:00:55 TRACE xorp_pimsm4 PIM ] Delete membership for (192.168.14.1, 232.5.6.7) on vif eth2 //-------------------------------------------------- // machine2 XORP log - Just client for this scenario (...) [ 2010/08/30 10:02:18 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.14.53 to 224.0.0.22 on vif eth0 // the route membership for the client in the machine 2 [ 2010/08/30 10:02:18 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (192.168.14.1, 232.5.6.7) on vif eth0 [ 2010/08/30 10:02:18 TRACE xorp_pimsm4 PIM ] Add membership for (192.168.14.1, 232.5.6.7) on vif eth0 (...) [ 2010/08/30 10:02:35 TRACE xorp_pimsm4 PIM ] Delete membership for (192.168.14.1, 232.5.6.7) on vif eth0 ----------------------------------- // SECOND CASE, server in machine 2 //--------------------------------- // // machine1 XORP log (...) [ 2010/08/30 09:43:34 TRACE xorp_pimsm4 PIM ] RX PIM_REGISTER from 192.168.14.53 to 192.168.14.1 on vif eth2 [ 2010/08/30 09:43:34 TRACE xorp_pimsm4 PIM ] Add MFC entry: (192.168.14.53, 232.5.6.7) iif = 2 olist = ... olist_disable_wrongvif = OOO [ 2010/08/30 09:43:34 TRACE xorp_pimsm4 PIM ] RX NOCACHE signal from MFEA_4: vif_index = 0 src = 192.168.14.53 dst = 232.5.6.7 [ 2010/08/30 09:43:34 TRACE xorp_pimsm4 PIM ] Add dataflow monitor: source = 192.168.14.53 group = 232.5.6.7 threshold_interval_sec = 210 threshold_interval_usec = 0 threshold_packets = 0 threshold_bytes = 0 is_threshold_in_packets = 1 is_threshold_in_bytes = 0 is_geq_upcall = 0 is_leq_upcall = 1 (...) ?// membership for the client in machine 2 [ 2010/08/30 10:13:19 TRACE xorp_pimsm4 PIM ] TX PIM_HELLO from 192.168.14.1 to 224.0.0.13 on vif eth2 // start membership [ 2010/08/30 09:43:46 TRACE xorp_pimsm4 PIM ] Add membership for (192.168.14.53, 232.5.6.7) on vif eth2 [ 2010/08/30 09:43:46 TRACE xorp_pimsm4 PIM ] Add MFC entry: (192.168.14.53, 232.5.6.7) iif = 0 olist = ... olist_disable_wrongvif = OOO [ 2010/08/30 09:43:46 TRACE xorp_pimsm4 PIM ] RX PIM_REGISTER from 192.168.14.53 to 192.168.14.1 on vif eth2 [ 2010/08/30 09:43:46 TRACE xorp_pimsm4 PIM ] RX WRONGVIF signal from MFEA_4: vif_index = 2 src = 192.168.14.53 dst = 232.5.6.7 (...) [ 2010/08/30 09:43:50 TRACE xorp_pimsm4 PIM ] Add dataflow monitor: source = 192.168.14.53 group = 232.5.6.7 threshold_interval_sec = 210 threshold_interval_usec = 0 threshold_packets = 0 threshold_bytes = 0 is_threshold_in_packets = 1 is_threshold_in_bytes = 0 is_geq_upcall = 0 is_leq_upcall = 1 (...) // delete membership for client in machine 2 [ 2010/08/30 09:44:28 TRACE xorp_igmp MLD6IGMP ] Notify routing delete membership for (192.168.14.53, 232.5.6.7) on vif eth2 [ 2010/08/30 09:44:28 TRACE xorp_pimsm4 PIM ] Delete membership for (192.168.14.53, 232.5.6.7) on vif eth2 //--------------------------------- // machine2 XORP log - Server in this case (...) [ 2010/08/30 10:15:13 TRACE xorp_pimsm4 PIM ] Add dataflow monitor: source = 192.168.14.53 group = 232.5.6.7 threshold_interval_sec = 210 threshold_interval_usec = 0 threshold_packets = 0 threshold_bytes = 0 is_threshold_in_packets = 1 is_threshold_in_bytes = 0 is_geq_upcall = 0 is_leq_upcall = 1 (...) // adding membership [ 2010/08/30 10:15:17 TRACE xorp_igmp MLD6IGMP ] Notify routing add membership for (192.168.14.53, 232.5.6.7) on vif eth0 [ 2010/08/30 10:15:17 TRACE xorp_pimsm4 PIM ] Add membership for (192.168.14.53, 232.5.6.7) on vif eth0 (...) // deleting membership [ 2010/08/30 10:15:31 TRACE xorp_pimsm4 PIM ] Delete membership for (192.168.14.53, 232.5.6.7) on vif eth0 ------------------------------ The Machines configuration: ------------------------------ - The routing configuration is as follows: root at machine1# route -n Kernel IP routing table Destination???? Gateway???????? Genmask???????? Flags Metric Ref??? Use Iface 239.0.0.1?????? 0.0.0.0???????? 255.255.255.255 UH??? 0????? 0??????? 0 eth2 224.0.0.161???? 0.0.0.0???????? 255.255.255.255 UH??? 0????? 0??????? 0 eth0 10.0.1.0??????? 0.0.0.0???????? 255.255.255.0?? U???? 0????? 0??????? 0 nasmesh0 192.168.14.0??? 0.0.0.0???????? 255.255.255.0?? U???? 0????? 0??????? 0 eth2 192.168.12.0??? 0.0.0.0???????? 255.255.255.0?? U???? 0????? 0??????? 0 eth0 169.254.0.0???? 0.0.0.0???????? 255.255.0.0???? U???? 1000?? 0??????? 0 eth0 0.0.0.0???????? 192.168.12.100? 0.0.0.0???????? UG??? 0????? 0??????? 0 eth0 root at machine2# route -n Kernel IP routing table Destination???? Gateway???????? Genmask???????? Flags Metric Ref??? Use Iface 192.168.14.0??? 0.0.0.0???????? 255.255.255.0?? U???? 1????? 0??????? 0 eth0 169.254.0.0???? 0.0.0.0???????? 255.255.0.0???? U???? 1000?? 0??????? 0 eth0 0.0.0.0???????? 192.168.14.1??? 0.0.0.0???????? UG??? 0????? 0??????? 0 eth0 - The configurations of the interfaces are as follows: root at machine1# ifconfig eth0????? Link encap:Ethernet? HWaddr 00:1C:23:2B:A8:3C ????????? inet addr:z`? Bcast:192.168.12.255? Mask:255.255.255.0 ????????? UP BROADCAST RUNNING MULTICAST? MTU:1500? Metric:1 ????????? RX packets:136925059 errors:0 dropped:0 overruns:0 frame:0 ????????? TX packets:68475707 errors:0 dropped:0 overruns:0 carrier:0 ????????? collisions:0 txqueuelen:1000 ????????? RX bytes:1378720974 (1.2 GB)? TX bytes:371923242 (354.6 MB) ????????? Interrupt:17 eth2????? Link encap:Ethernet? HWaddr 00:18:4D:6E:D1:3D ????????? inet addr:192.168.14.1? Bcast:192.168.14.255? Mask:255.255.255.0 ????????? UP BROADCAST RUNNING MULTICAST? MTU:1500? Metric:1 ????????? RX packets:6552371 errors:0 dropped:0 overruns:0 frame:0 ????????? TX packets:3509 errors:2 dropped:0 overruns:0 carrier:4 ????????? collisions:0 txqueuelen:1000 ????????? RX bytes:2895093950 (2.6 GB)? TX bytes:248299 (242.4 KB) ????????? Interrupt:18 Base address:0x2000 (...) nasmesh0? Link encap:UNSPEC? HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 ????????? inet addr:10.0.1.3? Bcast:10.0.1.255? Mask:255.255.255.0 ????????? UP BROADCAST RUNNING NOARP MULTICAST? MTU:1500? Metric:1 ????????? RX packets:15 errors:0 dropped:0 overruns:0 frame:0 ????????? TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 ????????? collisions:0 txqueuelen:100 ????????? RX bytes:772 (772.0 b)? TX bytes:1700 (1.6 KB) pimreg??? Link encap:UNSPEC? HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 ????????? UP RUNNING NOARP? MTU:1472? Metric:1 ????????? RX packets:1 errors:0 dropped:0 overruns:0 frame:0 ????????? TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 ????????? collisions:0 txqueuelen:0 ????????? RX bytes:1498 (1.4 KB)? TX bytes:0 (0.0 b) root at machine2# ifconfig eth0????? Link encap:Ethernet? HWaddr 00:1c:23:5a:0a:eb ????????? inet addr:192.168.14.53? Bcast:192.168.14.255? Mask:255.255.255.0 ????????? inet6 addr: fe80::21c:23ff:fe5a:aeb/64 Scope:Link ????????? UP BROADCAST RUNNING MULTICAST? MTU:1500? Metric:1 ????????? RX packets:1486231 errors:0 dropped:0 overruns:0 frame:0 ????????? TX packets:13125988 errors:0 dropped:0 overruns:0 carrier:0 ????????? collisions:0 txqueuelen:1000 ????????? RX bytes:2071741977 (2.0 GB)? TX bytes:539869744 (539.8 MB) ????????? Interrupt:17 (...) pimreg??? Link encap:UNSPEC? HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 ????????? UP RUNNING NOARP? MTU:1472? Metric:1 ????????? RX packets:0 errors:0 dropped:0 overruns:0 frame:0 ????????? TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 ????????? collisions:0 txqueuelen:0 ????????? RX bytes:0 (0.0 B)? TX bytes:0 (0.0 B) - The operation system used are: root at machine1# uname -a Linux smell-laptop 2.6.20 #2 SMP Fri May 7 18:02:41 CEST 2010 i686 GNU/Linux root at machine2# uname -a Linux marconi 2.6.29.4 #2 SMP PREEMPT Mon Jun 28 18:28:42 CEST 2010 i686 GNU/Linux ------------------ XORP configuration ------------------ The configuration files are as follows: // Machine1 /* $XORP: multicastExample1.boot */ interfaces { ??? interface eth2 { ??? vif eth2 { ??? ??? address 192.168.14.1 { ??? ??? prefix-length: 24 ??? ??? } ??? } ??? } ??? interface nasmesh0 { ??? vif nasmesh0 { ??? ??? address 10.0.1.3 { ??? ??? prefix-length: 24 ??? ??? } ??? } ??? } } fea { ??? unicast-forwarding4 { ??? disable: false ??? } } plumbing { ??? mfea4 { ??? interface eth2 { ??? ??? vif eth2 { ??? ??? disable: false ??? ??? } ??? } ??? interface nasmesh0 { ??? ??? vif nasmesh0 { ??? ??? disable: false ??? ??? } ??? } ??? interface register_vif { ??? ??? vif register_vif { ??? ??? /* Note: this vif should be always enabled */ ??? ??? disable: false ??? ??? } ??? } /* ??? traceoptions { ??? ??? flag all { ??? ??? disable: false ??? ??? } ??? } */ ??? } } protocols { ??? igmp { ??? interface eth2 { ??? ??? vif eth2 { ??? ??? version: 3 ??? ??? disable: false ??? ??? } ??? } ??? interface nasmesh0 { ??? ??? vif nasmesh0 { ??? ??? version: 3 ??? ??? disable: false ??? ??? } ??? } ??? traceoptions { ??? ??? flag all { ??? ??? disable: false ??? ??? } ??? } ??? } } protocols { ??? pimsm4 { ??? interface eth2 { ??? ??? vif eth2 { ??? ??? disable: false ??? ??? } ??? } ??? interface nasmesh0 { ??? ??? vif nasmesh0 { ??? ??? disable: false ??? ??? } ??? } ??? interface register_vif { ??? ??? vif register_vif { ??? ??? /* Note: this vif should be always enabled */ ??? ??? disable: false ??? ??? } ??? } ??? /* Note: static-rps and bootstrap should not be mixed */ /*??? static-rps { ??? ??? rp 10.0.1.1 { ??? ??? group-prefix 239.0.0.0/8 { ??? ??? } ??? ??? group-prefix 232.0.0.0/8 { ??? ??? } ??? ??? } ??? } */ ??? static-rps { ??? ??? rp 192.168.14.1 { ??? ??? group-prefix 232.0.0.0/8 { ??? ??? } ??? ??? } ??? } ??? switch-to-spt-threshold { ??? ??? /* approx. 1K bytes/s (10Kbps) threshold */ ??? ??? disable: false ??? ??? interval: 100 ??? ??? bytes: 102400 ??? } ??? traceoptions { ??? ??? flag all { ??? ??? disable: false ??? ??? } ??? } ??? } } protocols { ??? fib2mrib { ??? disable: false ??? } } -------------------- // machine 2 /* $XORP: multicastExample1.boot */ interfaces { ??? interface eth0 { ??? vif eth0 { ??? ??? address 192.168.14.53 { ??? ??? prefix-length: 24 ??? ??? } ??? } ??? } } fea { ??? unicast-forwarding4 { ??? disable: false ??? } } plumbing { ??? mfea4 { ??? interface eth0 { ??? ??? vif eth0 { ??? ??? disable: false ??? ??? } ??? } ??? interface register_vif { ??? ??? vif register_vif { ??? ??? /* Note: this vif should be always enabled */ ??? ??? disable: false ??? ??? } ??? } /* ??? traceoptions { ??? ??? flag all { ??? ??? disable: false ??? ??? } ??? } */ ??? } } protocols { igmp { interface eth0 { vif eth0 { version: 3 disable: false } } traceoptions { flag all { disable: false } } } } protocols { pimsm4 { interface eth0 { vif eth0 { disable: false } } interface register_vif { vif register_vif { /* Note: this vif should be always enabled */ disable: false } } /* Note: static-rps and bootstrap should not be mixed */ /* static-rps { rp 10.0.1.1 { group-prefix 239.0.0.0/8 { } group-prefix 232.0.0.0/8 { } } } */ static-rps { rp 192.168.14.1 { group-prefix 232.0.0.0/8 { } } } switch-to-spt-threshold { /* approx. 1K bytes/s (10Kbps) threshold */ disable: false interval: 100 bytes: 102400 } traceoptions { flag all { disable: false } } } } protocols { fib2mrib { disable: false } } From diego360xen at gmail.com Mon Aug 30 12:13:50 2010 From: diego360xen at gmail.com (=?ISO-8859-1?Q?Diego_Augusto_Pinzon_Carre=F1o?=) Date: Mon, 30 Aug 2010 14:13:50 -0500 Subject: [Xorp-users] hi Ben Message-ID: i just test your live -Cd base on ubuntu that come xorp pre-install , on a virtualbox 3.2.4 seems a problem with find the interfaces. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100830/8273960b/attachment.html From greearb at candelatech.com Mon Aug 30 12:17:43 2010 From: greearb at candelatech.com (Ben Greear) Date: Mon, 30 Aug 2010 12:17:43 -0700 Subject: [Xorp-users] hi Ben In-Reply-To: References: Message-ID: <4C7C03D7.6070101@candelatech.com> On 08/30/2010 12:13 PM, Diego Augusto Pinzon Carre?o wrote: > i just test your live -Cd base on ubuntu that come xorp pre-install , > on a virtualbox 3.2.4 seems a problem with find the interfaces. Can you provide some more info, perhaps: ifconfig -a lspci 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 danielcamara at gmail.com Tue Aug 31 02:50:30 2010 From: danielcamara at gmail.com (Daniel Camara) Date: Tue, 31 Aug 2010 11:50:30 +0200 Subject: [Xorp-users] Problems with PIM-SSM In-Reply-To: <011501cb48d5$f4cf4790$de6dd6b0$@etri.re.kr> References: <011501cb48d5$f4cf4790$de6dd6b0$@etri.re.kr> Message-ID: Hi S. K. Jo, In fact the routes, for the real machines, are defined. Machine1 has a route to saying that all nodes for the network 192.168.14.0 should go through the interface eth2, that is directly connected to machine2. By its turn, machine1 is the default router for machine2. But you are right I didn't add them in the xorp configuration. However, I just did that and it didn't work. The result is the same. What is bothering me is that when I start a multicast traffic in the machine1, not even the xorp in that machine perceives the traffic or even acknowledges the request from the client. When I start in machine 2, the data does not arrive to the client but at least machine1 it perceives that there is a traffic coming from the machine2 and a request from a client at machine2. One thing that I found odd is that when I ask to see the pim routing information it shows the next routing to be the same node in machine1 and in machine2 it shows the next hop to be machine1, what I think should be the right thing to be. root at machine1> show pim mrib DestPrefix NextHopRouter VifName VifIndex MetricPref Metric 192.168.14.0/24 192.168.14.1 eth2 0 0 0 // I added in the machine1 config protocols { static { route 192.168.14.0/24 { next-hop: 192.168.14.53 } mrib-route 192.168.14.0/24 { next-hop: 192.168.14.53 } } } // added to machine2 config protocols { static { route 0.0.0.0/0 { next-hop: 192.168.14.1 } mrib-route 192.168.14.0/24 { next-hop: 192.168.14.1 } } } A ND, thanks for the document it helped a lot :). Best regards... Daniel 2010/8/31 ??? > I'm not sure exactly what problem is. > > > > However, based on what I had experienced, static route should be configured > between Machine #1 and #2. > > > > Can you let me know exact network configuration and setting info? > > > > Please refer attached document. Though it was written by Korean, you can > understand for configuration. > > > > I hope it would work for you. > > > > S. K. Jo > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100831/f7d766d4/attachment.html