- Bird-users - Mailing Lists

more understanding of the bird hang on ifdown/ifup
by Florian Lohoff 20 Jun '07

20 Jun '07

Hi, i debugged further and build a version with debugging symbols and put an assert into the code where we detect the out of sequence netlink message. My understanding is that we do an krt_if_scan on a regular basis - Now we go through the notification chain and end up sending another netlink message before krt_if_scan pulled all netlink messages. nl_get_reply gets an out-of-sequence netlink message and drops it although nl_get_scan would need it for an end-of-messages marker. Thus returning from our notification chain nl_get_scan ends up polling for the next message which already got removed via nl_send_route -> nl_exchange -> nl_get_reply as an out-of-sequence. As the netlink FD is blocking we deadlock here. One solution i see would be to convert all nl_get_scan users to first poll ALL messages before starting to process them which could mean a lot of memory usage especially on full routing BGP where we need to poll all routes first. Another solution would be to make some generic polling/callback based approach, or probably replacing the netlink.c with an API wrapper around libnl (http://people.suug.ch/~tgr/libnl/) (gdb) bt #0 0xb7e3e947 in raise () from /lib/tls/libc.so.6 #1 0xb7e400c9 in abort () from /lib/tls/libc.so.6 #2 0xb7e3805f in __assert_fail () from /lib/tls/libc.so.6 #3 0x08078a09 in nl_get_reply () at netlink.c:135 #4 0x08078b0d in nl_exchange (pkt=0xbfe3f2b4) at netlink.c:193 #5 0x08079562 in nl_send_route (p=0x80905a0, e=0x809921c, new=0) at netlink.c:542 #6 0x080795d2 in krt_set_notify (p=0x80905a0, n=0x80981c4, new=0x0, old=0x809921c) at netlink.c:561 #7 0x0807614e in krt_notify (P=0x80905a0, net=0x80981c4, new=0x0, old=0x809921c, attrs=0x0) at krt.c:698 #8 0x08049910 in do_rte_announce (a=0x8095e40, net=0x80981c4, new=0x80991cc, old=0x809921c, tmpa=0x0, class=4100) at /home/flo/p/root/bird-1.0.11/./nest/rt-table.c:227 #9 0x08049521 in rte_announce (tab=0x808f4b0, net=0x80981c4, new=0x80991cc, old=0x809921c, tmpa=0x0) at /home/flo/p/root/bird-1.0.11/./nest/rt-table.c:261 #10 0x08049b94 in rte_recalculate (table=0x808f4b0, net=0x80981c4, p=0x80906c8, new=0x80991cc, tmpa=0x0) at /home/flo/p/root/bird-1.0.11/./nest/rt-table.c:368 #11 0x08049ff1 in rte_update (table=0x808f4b0, net=0x80981c4, p=0x80906c8, new=0x80991cc) at /home/flo/p/root/bird-1.0.11/./nest/rt-table.c:514 #12 0x0804fd41 in dev_ifa_notify (p=0x80906c8, c=1, ad=0x8095c80) at /home/flo/p/root/bird-1.0.11/./nest/rt-dev.c:69 #13 0x0804e962 in ifa_send_notify (p=0x80906c8, c=1, a=0x8095c80) at /home/flo/p/root/bird-1.0.11/./nest/iface.c:148 #14 0x0804e87e in ifa_notify_change (c=1, a=0x8095c80) at /home/flo/p/root/bird-1.0.11/./nest/iface.c:159 #15 0x0804ea7d in if_notify_change (c=1, i=0x8095b38) at /home/flo/p/root/bird-1.0.11/./nest/iface.c:211 #16 0x0804ed24 in if_update (new=0xbfe3f5ec) at /home/flo/p/root/bird-1.0.11/./nest/iface.c:280 #17 0x08078f5c in nl_parse_link (h=0x80919b8, scan=1) at netlink.c:334 #18 0x080792a1 in krt_if_scan (p=0x8090778) at netlink.c:445 #19 0x08074fd5 in kif_scan (t=0x8095af8) at krt.c:94 #20 0x08075004 in kif_force_scan () at krt.c:102 #21 0x08076018 in krt_scan (t=0x8095a48) at krt.c:655 #22 0x08073005 in tm_shot () at io.c:298 #23 0x08074886 in io_loop () at io.c:1126 #24 0x080774ef in main (argc=Cannot access memory at address 0x67ec ) at main.c:462 -- Florian Lohoff flo(a)rfc822.org +49-171-2280134 Those who would give up a little freedom to get a little security shall soon have neither - Benjamin Franklin

1 0

RE: BIRD <-> Quagga Compatiblity
by Vonlanthen, Elmar 30 May '07

30 May '07

Hello Ondrej and Joseph Thanks for your quick answers. I have tried with both patches (but not with both together). When I apply the topology.c-patch, everything is working. Quagga accepts the routes! But when I apply the iface.c-patch bird doesn't send any packets anymore. Maybe you can find anything in the bird logfile. Anyway, for me is it a reasonable solution. Thanks for your help and have a nice day. Best regards Elmar > -----Original Message----- > From: Sörös József [mailto:soros.jozsef@multip.hu] > Sent: Sunday, May 27, 2007 8:13 AM > To: Ondrej Filip; Vonlanthen, Elmar > Cc: bird-users(a)network.cz > Subject: Re: BIRD <-> Quagga Compatiblity > > Once upon a time I suggested the correction below in > nest/iface.c to get > bird handle interfaces > with unnumbered and addresses correctly. It worked. > > --- iface.c 2004-02-10 09:41:09.000000000 +0100 > +++ nest/iface.c 2004-02-10 02:58:51.000000000 +0100 > @@ -407,9 +407,13 @@ > > WALK_LIST(a, i->addrs) > { > - if (!(a->flags & IA_SECONDARY) && (!b || a->scope > b->scope)) > - b = a; > - a->flags &= ~IA_PRIMARY; > + if (!(a->flags & IA_SECONDARY) > + && !(a->flags & IA_UNNUMBERED) > + && (!b || a->scope > b->scope)) > + { > + b = a; > + a->flags &= ~IA_PRIMARY; > + } > } > res = (b != i->addr); > i->addr = b; > > Joseph > > Sörös József > Multip Kft. > E-Mail: soros.jozsef(a)multip.hu > Mobil: +36309403985 > ----- Original Message ----- > > > From: "Ondrej Filip" <feela(a)network.cz> > To: "Vonlanthen, Elmar" > <Elmar.Vonlanthen(a)united-security-providers.ch> > Cc: <bird-users(a)network.cz> > Sent: Saturday, May 26, 2007 5:09 PM > Subject: Re: BIRD <-> Quagga Compatiblity > > > > Vonlanthen, Elmar wrote: > >> Hello > > > > Hello! > > > >> > >> At the moment, I do some tests with BIRD. We would like to > replace our > >> currently used routing daemon Quagga with this piece of software. > >> > >> My first impressions are very good. There are lot of > features, which are > >> missing in Quagga. And the design is much better. > >> > >> I do some tests with OSPF in the following configuration: > >> > >> 172.16.101.0/24 -- router/gw 1 -- 10.254.1.4 --- P-t-P --- > 10.254.4.1 -- > >> router/gw 4 -- 172.16.104.0/24 > >> > > > > There are two problems I notice: > > > > 1) Bird thinks that the P-t-P interfaces are unnumbered. I > am not sure > > whether this is correct. Could you please send me: "show interfaces" > > and "show ospf interface" ? > > > > 2) I guess that Quagga has a bug in routing table calculation if the > > network contains unnumbered P-t-P interfaces. We can me a > workaround: > > Bird will send the interface as numbered. > > > > I prepared a quick and dirty solution (and I didn't test > it!). Try to > > apply the attached patch. It is definitely wrong way, but > it may solve > > your case. Let me know, if this helps. > > > > Ondrej > > > >> The complete setup is much more complicated. The Point-to-Point > >> Connection is made between two GRE Interfaces with > multicast enabled. > >> The GRE interfaces have a tunnel over an Ipsec transport > connection. > >> There are 4 Tunnels between these two routers (two "wan" > links for each > >> site), but only tunnel linkA to linkA is up (like above). > >> The gre tunnel ist working. Both routing daemons can talk together. > >> > >> On both routers/gateways I can switch between Quagga and Bird. > >> The OS on the routers is Debian Woody with Kernel 2.4.32. > >> > >> My first test results: > >> > >> Quagga - Quagga: Working fine (our currently productive setup). > >> Bird - Bird: Working fine. > >> > >> Quagga - Bird: > >> > >> It is not working! But im not sure if the problem ist > Quagga or Bird. > >> Bird gets the routes from Quagga, but Quagga doesn't take > the routes > >> from Bird. But Bird is sending the packet with the routing > information. > >> > >> I have the following message in the quagga-ospfd logfile: > >> 2007/05/25 08:12:05 OSPF: Route[External]: Calculate > AS-external-LSA to > >> 172.16.104.0/24 > >> 2007/05/25 08:12:05 OSPF: Route[External]: Can't find > originating ASBR > >> route > >> > >> With quagga - quagga (which is working) I have the > following log entry: > >> 2007/05/25 08:06:08 OSPF: Route[External]: Calculate > AS-external-LSA to > >> 172.16.104.0/24 > >> 2007/05/25 08:06:08 OSPF: Route[External]: AS-external-LSA > is MAXAGE > >> 2007/05/25 08:06:08 OSPF: > LSA[Type5,id(172.16.104.0),ar(172.16.104.1)]: > >> MaxAge LSA remover scheduled. > >> > >> The Quagga router of router 4 is listed in router 1 as > border-router. If > >> I replace the routing daemon in router 4 with Bird, it > will not appear > >> again as border-router. > >> > >> Another strange thing is, that in the LSA Update packets > from 10.254.4.1 > >> to 224.0.0.5, with Quagga I have the following data: > >> Type: PTP > >> Router ID: 172.16.101.1 (-> the difference!) > >> Link Data: 10.254.4.1 > >> Link Type: 1 -Point-to-point connection to another router > >> > >> In Bird the data looks like this: > >> Type: PTP > >> Router ID: 172.16.101.1 > >> Link Data: 0.0.0.60 (-> the difference!) > >> Link Type: 1 -Point-to-point connection to another router > >> > >> Is the link data field only informational? > >> > >> Unfortunately it is necessary for us, that the > communication between > >> Bird and Quagga is working until everything is migrated to Bird. > >> > >> As attachement you will find tcpdump output, quagga log > files and the > >> configuration files. > >> > >> Please, let me know if there are some informations missing. > >> > >> Thanks in advance. > >> > >> Best regards > >> Elmar > >> > >> P.S. Sorry for my bad english :-( > > > > > > > -------------------------------------------------------------- > ------------------ > > > > --- topology.c.good 2005-02-20 19:58:01.000000000 +0100 > > +++ topology.c 2007-05-26 17:00:26.000000000 +0200 > > @@ -81,11 +81,13 @@ > > ln->id = neigh->rid; > > ln->metric = ifa->cost; > > ln->notos = 0; > > +#if 0 > > if (ifa->iface->flags && IA_UNNUMBERED) > > { > > ln->data = ifa->iface->index; > > } > > else > > +#endif > > { > > ln->data = ipa_to_u32(ifa->iface->addr->ip); > > } > > > >

2 2

some other daemon to handle ipv6 dynamic routing
by Martin Kraus 29 May '07

29 May '07

Hi, just a quick question. Is it possible to use some routing daemon next to bird(which does ipv4 dynamic routing) which would handle ipv6 addresses? I'm looking for something simple to use inside our network to get packets to the 6to4 gateway. thanks for suggestions Martin Kraus -- printk(KERN_EMERG "This is not a software problem!\n"); linux-2.6.19/arch/x86_64/kernel/mce.c

1 0

BIRD <-> Quagga Compatiblity
by Vonlanthen, Elmar 26 May '07

26 May '07

Hello At the moment, I do some tests with BIRD. We would like to replace our currently used routing daemon Quagga with this piece of software. My first impressions are very good. There are lot of features, which are missing in Quagga. And the design is much better. I do some tests with OSPF in the following configuration: 172.16.101.0/24 -- router/gw 1 -- 10.254.1.4 --- P-t-P --- 10.254.4.1 -- router/gw 4 -- 172.16.104.0/24 The complete setup is much more complicated. The Point-to-Point Connection is made between two GRE Interfaces with multicast enabled. The GRE interfaces have a tunnel over an Ipsec transport connection. There are 4 Tunnels between these two routers (two "wan" links for each site), but only tunnel linkA to linkA is up (like above). The gre tunnel ist working. Both routing daemons can talk together. On both routers/gateways I can switch between Quagga and Bird. The OS on the routers is Debian Woody with Kernel 2.4.32. My first test results: Quagga - Quagga: Working fine (our currently productive setup). Bird - Bird: Working fine. Quagga - Bird: It is not working! But im not sure if the problem ist Quagga or Bird. Bird gets the routes from Quagga, but Quagga doesn't take the routes from Bird. But Bird is sending the packet with the routing information. I have the following message in the quagga-ospfd logfile: 2007/05/25 08:12:05 OSPF: Route[External]: Calculate AS-external-LSA to 172.16.104.0/24 2007/05/25 08:12:05 OSPF: Route[External]: Can't find originating ASBR route With quagga - quagga (which is working) I have the following log entry: 2007/05/25 08:06:08 OSPF: Route[External]: Calculate AS-external-LSA to 172.16.104.0/24 2007/05/25 08:06:08 OSPF: Route[External]: AS-external-LSA is MAXAGE 2007/05/25 08:06:08 OSPF: LSA[Type5,id(172.16.104.0),ar(172.16.104.1)]: MaxAge LSA remover scheduled. The Quagga router of router 4 is listed in router 1 as border-router. If I replace the routing daemon in router 4 with Bird, it will not appear again as border-router. Another strange thing is, that in the LSA Update packets from 10.254.4.1 to 224.0.0.5, with Quagga I have the following data: Type: PTP Router ID: 172.16.101.1 (-> the difference!) Link Data: 10.254.4.1 Link Type: 1 -Point-to-point connection to another router In Bird the data looks like this: Type: PTP Router ID: 172.16.101.1 Link Data: 0.0.0.60 (-> the difference!) Link Type: 1 -Point-to-point connection to another router Is the link data field only informational? Unfortunately it is necessary for us, that the communication between Bird and Quagga is working until everything is migrated to Bird. As attachement you will find tcpdump output, quagga log files and the configuration files. Please, let me know if there are some informations missing. Thanks in advance. Best regards Elmar P.S. Sorry for my bad english :-(

2 1

BGP routes persist in kernel
by Aaron Wirtz 05 Jan '07

05 Jan '07

I have a test setup involving 2 machines running BIRD, communicating routes via BGP. When trying to integrate to the Linux kernel routing table, I am having some problems. While BIRD is running, it adds BGP-learned routes to the kernel route table properly (also properly preferring the local device route 10.0.1.0/24 over the BGP-learned route 10.0.1.0/24). But when BIRD shuts down, it removes the device route 10.0.1.0/24 from the kernel table, then installs the BGP route 10.0.1.0/24 instead, and leaves the other BGP-learned routes in the kernel instead of cleaning them. I have attached the configuration and debugging output showing this problem. Maybe there is something obvious I am overlooking? -Aaron Config: router id 62.168.0.1; protocol device { debug all; scan time 10; } protocol direct { debug all; } protocol kernel { debug all; persist no; kernel table 254; learn; scan time 10; import all; export all; } protocol bgp { debug all; import all; export all; local as 123; neighbor 10.0.1.126 as 5; } Log: Lines marked "joda#" are commands I typed in the shell. Lines marked "bird>" are commands I typed to birdc. Lines marked "bird:" are debug output from bird. All other lines are the immediate output of a command I typed. joda# cat /proc/version Linux version 2.6.15-27-amd64-generic (buildd@king) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 SMP PREEMPT Fri Dec 8 17:50:54 UTC 2006 joda# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 10.0.1.1 0.0.0.0 UG 0 0 0 eth0 joda# bird -d bird: device1: Initializing bird: direct1: Initializing bird: kernel1: Initializing bird: bgp1: Initializing bird: device1: Starting bird: device1: Scanning interfaces bird: device1: State changed to feed bird: direct1: Starting bird: direct1: State changed to feed bird: kernel1: Starting bird: kernel1: State changed to feed bird: bgp1: Starting bird: bgp1: State changed to start bird: device1: State changed to up bird: direct1 < primary address 127.0.0.0/8 on interface lo added bird: direct1 > added [best] 127.0.0.0/8 dev lo bird: direct1 < primary address 10.0.1.0/24 on interface eth0 added bird: direct1 > added [best] 10.0.1.0/24 dev eth0 bird: direct1: State changed to up bird: kernel1: Connected to table master bird: kernel1 < added 10.0.1.0/24 dev eth0 bird: kernel1 < added 127.0.0.0/8 dev lo bird: kernel1: State changed to up bird: bgp1: Connect delayed by 5 seconds bird: kernel1: Scanning routing table bird: kernel1: 0.0.0.0/0: [alien] created bird: kernel1: Pruning table master bird: kernel1: Pruning inherited routes bird: kernel1 > added [best] 0.0.0.0/0 via 10.0.1.1 on eth0 bird: kernel1 < added 0.0.0.0/0 via 10.0.1.1 on eth0 joda# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 10.0.1.1 0.0.0.0 UG 0 0 0 eth0 joda# birdc BIRD 1.0.11 ready. bird> show route 0.0.0.0/0 via 10.0.1.1 on eth0 [kernel1 12:34] (10) 10.0.1.0/24 dev eth0 [direct1 12:34] (240) 127.0.0.0/8 dev lo [direct1 12:34] (240) bird: bgp1: Connecting to 10.0.1.126 from local address 10.0.1.10 bird: device1: Scanning interfaces bird: kernel1: Scanning routing table bird: kernel1: 0.0.0.0/0: [alien] seen bird: kernel1: Pruning table master bird: kernel1: Pruning inherited routes bird: bgp1: Incoming connection from 10.0.1.126 port 33378 bird: bgp1: Sending OPEN(ver=4,as=123,hold=240,id=3ea80001) bird: bgp1: Got OPEN(as=5,hold=240,id=3ea80002) bird: bgp1: Connection collision, giving up the other connection bird: bgp1: Sending KEEPALIVE bird: bgp1: Got KEEPALIVE bird: bgp1: State changed to feed bird: bgp1: Connected to table master bird: bgp1 < added 0.0.0.0/0 via 10.0.1.1 on eth0 bird: bgp1: Sending UPDATE bird: bgp1 < added 10.0.1.0/24 dev eth0 bird: bgp1: Sending UPDATE bird: bgp1 < out of scope 127.0.0.0/8 dev lo bird: bgp1: State changed to up bird: bgp1: Got UPDATE bird: bgp1 > added 10.0.1.0/24 via 10.0.1.126 on eth0 bird: bgp1: Got UPDATE bird: bgp1 > added [best] 10.1.2.0/24 via 10.0.1.126 on eth0 bird: kernel1 < added 10.1.2.0/24 via 10.0.1.126 on eth0 bird: bgp1 < rejected by protocol 10.1.2.0/24 via 10.0.1.126 on eth0 bird: bgp1: Got UPDATE bird: bgp1 > added [best] 10.0.7.0/24 via 10.0.1.126 on eth0 bird: kernel1 < added 10.0.7.0/24 via 10.0.1.126 on eth0 bird: bgp1 < rejected by protocol 10.0.7.0/24 via 10.0.1.126 on eth0 bird: bgp1: Got UPDATE bird: bgp1 > added [best] 10.9.8.0/24 via 10.0.1.126 on eth0 bird: kernel1 < added 10.9.8.0/24 via 10.0.1.126 on eth0 bird: bgp1 < rejected by protocol 10.9.8.0/24 via 10.0.1.126 on eth0 joda# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.7.0 10.0.1.126 255.255.255.0 UG 0 0 0 eth0 10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 10.9.8.0 10.0.1.126 255.255.255.0 UG 0 0 0 eth0 10.1.2.0 10.0.1.126 255.255.255.0 UG 0 0 0 eth0 0.0.0.0 10.0.1.1 0.0.0.0 UG 0 0 0 eth0 bird> show route 0.0.0.0/0 via 10.0.1.1 on eth0 [kernel1 12:34] (10) 10.0.1.0/24 dev eth0 [direct1 12:34] (240) via 10.0.1.126 on eth0 [bgp1 12:34] (100) [AS5i] 10.1.2.0/24 via 10.0.1.126 on eth0 [bgp1 12:34] (100) [AS5i] 10.0.7.0/24 via 10.0.1.126 on eth0 [bgp1 12:34] (100) [AS5i] 10.9.8.0/24 via 10.0.1.126 on eth0 [bgp1 12:34] (100) [AS5i] 127.0.0.0/8 dev lo [direct1 12:34] (240) bird: device1: Scanning interfaces bird: kernel1: Scanning routing table bird: kernel1: 10.0.7.0/24: seen bird: kernel1: 10.9.8.0/24: seen bird: kernel1: 10.1.2.0/24: seen bird: kernel1: 0.0.0.0/0: [alien] seen bird: kernel1: Pruning table master bird: kernel1: Pruning inherited routes joda# killall bird bird: Shutting down bird: device1: Unconfigured bird: device1: Shutting down bird: direct1 < primary address 127.0.0.0/8 on interface lo removed bird: kernel1 < removed 127.0.0.0/8 dev lo bird: bgp1 < removed 127.0.0.0/8 dev lo bird: bgp1: Sending UPDATE bird: direct1 > removed [sole] 127.0.0.0/8 dev lo bird: direct1 < primary address 10.0.1.0/24 on interface eth0 removed bird: kernel1 < replaced 10.0.1.0/24 via 10.0.1.126 on eth0 bird: bgp1 < rejected by protocol 10.0.1.0/24 via 10.0.1.126 on eth0 bird: bgp1 < removed 10.0.1.0/24 dev eth0 bird: bgp1: Sending UPDATE bird: direct1 > removed [replaced] 10.0.1.0/24 dev eth0 bird: bgp1: Neighbor lost bird: bgp1: State changed to flush bird: bgp1: Sending NOTIFICATION(code=6.0) bird: device1: State changed to flush bird: direct1: Unconfigured bird: direct1: Shutting down bird: direct1: State changed to flush bird: kernel1: Unconfigured bird: kernel1: Shutting down bird: kernel1: Flushing kernel routes bird: kernel1: State changed to flush bird: bgp1: Unconfigured bird: kernel1 > removed [sole] 0.0.0.0/0 via 10.0.1.1 on eth0 bird: bgp1 > removed [sole] 10.0.1.0/24 via 10.0.1.126 on eth0 bird: bgp1 > removed [sole] 10.1.2.0/24 via 10.0.1.126 on eth0 bird: bgp1 > removed [sole] 10.0.7.0/24 via 10.0.1.126 on eth0 bird: bgp1 > removed [sole] 10.9.8.0/24 via 10.0.1.126 on eth0 bird: bgp1: State changed to down bird: device1: State changed to down bird: direct1: State changed to down bird: kernel1: State changed to down bird: System shutdown completed joda# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.7.0 10.0.1.126 255.255.255.0 UG 0 0 0 eth0 10.0.1.0 10.0.1.126 255.255.255.0 UG 0 0 0 eth0 10.9.8.0 10.0.1.126 255.255.255.0 UG 0 0 0 eth0 10.1.2.0 10.0.1.126 255.255.255.0 UG 0 0 0 eth0 0.0.0.0 10.0.1.1 0.0.0.0 UG 0 0 0 eth0 P.S. Also, BIRD did not seem to use the proper kernel routing table by default. I had to manually specify "kernel table 254" in the config.

1 0

BGP MD5 password on bird and equivalent of "show ip bgp sum" ?
by Xavier Beaudouin 24 Sep '06

24 Sep '06

Hi there. I have finaly getting the way to make bird to work on freebsd... Was the --enable-ipv6 that made me crazy.... So I am thinking to manage on move from OpenBGPD to bird... Seems that bird is the most fastest alternative to OpenBGPd (same time to get the full view on a PIII 886 machine than OpenBGPd, so this is good), and seems to have small fingerprint about RAM usage. A big question is : - how to set a MD5 password on a BGP session ? This is more and more needed on public IXes. Is there any plan for that ? in brief support for RFC 2385. Another question is how to get a summary of routes announced by a peer like the Cisco command : show ip bgp sum This is really usefull when trying to figure how many routes is getting announced. Thanks for your support. /Xavier

1 0

Re: Bird na MIPSu
by losako＠seznam.cz 19 Sep '06

19 Sep '06

Hi, output from remote debugging is following: This GDB was configured as "--host=i686-pc-linux-gnu --target=mips-linux-uclibc"... (gdb) set solib-search-path /usr/local/gcc333/lexra-nnop-v5/mips-linux/lib (gdb) target remote 192.168.5.22:4444 Remote debugging using 192.168.5.22:4444 warning: Remote failure reply: E01 0x2aaa8ff4 in ?? () (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x2ab36c1c in realloc () from /usr/local/gcc333/lexra-nnop-v5/mips-linux-uclibc/lib/libc.so.0 (gdb) backtrace #0 0x2ab36c1c in realloc () from /usr/local/gcc333/lexra-nnop-v5/mips-linux-uclibc/lib/libc.so.0 #1 0x0043aaa0 in lp_allocz (m=0x0, size=12) at mempool.c:175 #2 0x00431d7c in cf_lex_init (is_cli=0) at cf-lex.l:359 #3 0x004321b0 in config_parse (c=0x100033d0) at conf.c:108 #4 0x00438790 in unix_read_config (cp=0x7fff7df0, name=0x4498bc "/etc/bird.conf") at main.c:100 #5 0x004387f8 in read_config () at main.c:108 #6 0x004395c8 in main (argc=268448720, argv=0x0) at main.c:428 (gdb) Thanks for your help, Best regards Pavel > ------------ Původní zpráva ------------ > Od: Martin Mares <mj(a)ucw.cz> > Předmět: Re: Bird na MIPSu > Datum: 19.9.2006 14:09:21 > ---------------------------------------- > Hello! > > > zkousel jsem rozchodit bird-1.0.11 na zarizeni s RTL8186 (uClibc SDK mohu > > poskytnout) , bohuzel po zkompilovani a spusteni je program ihned ukoncen. > > Please post to bird-users in English. > > > Vypis z strace: > > strace doesn't tell much, could you please run gdb on the binary? > > Have a nice fortnight > -- > Martin `MJ' Mares <mj(a)ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ > Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth > "Snow falling on Perl. White noise covering line noise. Hides all the bugs too." > -- J. Putnam > > >

1 0

Bird na MIPSu
by losako＠seznam.cz 14 Sep '06

14 Sep '06

Dobry den, zkousel jsem rozchodit bird-1.0.11 na zarizeni s RTL8186 (uClibc SDK mohu poskytnout) , bohuzel po zkompilovani a spusteni je program ihned ukoncen. Pavel Vypis z strace: execve("/bin/bird", ["bird"], [/* 5 vars */]) = 0 svr4_syscall() = -1 ERRNO_4090 (Unknown error 4090) readlink("/lib/ld-uClibc.so.0", "ld-uClibc-0.9.26.so", 1024) = 19 open("/lib/libc.so.0", O_RDONLY) = 3 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, 0, 0) = 0do_page_fault() #2: sending SIGSEGV to bird for illegal write access to x2aaaf0000000000 (epc == 2ab1e14c, ra == 0043aaa0) 0 read(3,\177ELF\1\2\1\0\0\0\0\0\0\0\0\0\0\3\0\10\0\0\0\1\0\0\270"..., 4096) = 4096 old_mmap(NULL, 704512, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2aaee000 old_mmap(0x2aaee000, 415588, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0x2aaee000 old_mmap(0x2ab93000, 6328, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x65000) = 0x2ab93000 old_mmap(0x2ab95000, 17144, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2ab95000 close(3) = 0 munmap(0x2aaaf000, 4096) = 0 ioctl(0, TIOCNXCL, {B115200 opost isig icanon echo ...}) = 0 ioctl(1, TIOCNXCL, {B115200 opost isig icanon echo ...}) = 0 socket(PF_FILE, SOCK_DGRAM, 0) = 3 connect(3, {sa_family=AF_FILE, path="/dev/log"}, 10) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 4 connect(4, {sa_family=AF_FILE, path="/var/run/bird.ctl"}, 19) = -1 ENOENT (No such file or directory) close(4) = 0 brk(0x100040dc) = 0x100040dc brk(0x10005000) = 0x10005000 time(NULL) = 946685888 open("/etc/bird.conf", O_RDONLY) = 4 brk(0x10009000) = 0x10009000 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ Process 514 detached

1 0

Re: Moderate this list...
by Martin Mares 23 Aug '06

23 Aug '06

Hello! > I agree with that. Please limit postings to list members. I will wait a couple of days to see if anybody objects and then I will set the limit. Have a nice fortnight -- Martin `MJ' Mares <mj(a)ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth System going down at 5 pm to install scheduler bug.

3 3

Re: NEW
by Ladislav Lhotka 18 Aug '06

18 Aug '06

Hey, is getting reports about spam any different from getting spam itself? Please stop this. Lada Manage píše v Pá 18. 08. 2006 v 10:18 -0200: > Spam detection software, running on the system "trubka.network.cz", has > identified this incoming email as possible spam. The original message > has been attached to this so you can view it (if it isn't spam) or label > similar future email. If you have any questions, see > the administrator of that system for details. > > Content preview: Shower Type GiftsMost Popular Wished ForMost GiftedTop > ListsBaby someones List: ListGift Idea Registry This Price Under Teens > Girl Recipient Thumb Occasion Shower Type GiftsMost Popular Wished > ForMost GiftedTop ListsBaby someones List: ListGift Idea Registry This > item not eligible for Amazon Prime but over million other items are. > Join today. Already member Sign in. Get less Have sell A.com users save > Amazon. Learn how. NEW LIST more. larger image Share own customer images > currently Details Shipping: Currently can shipped only within U.S. > APO/FPO shipments [...] > > Content analysis details: (7.1 points, 5.0 required) > > pts rule name description > ---- ---------------------- -------------------------------------------------- > 2.0 DATE_IN_FUTURE_03_06 Date: is 3 to 6 hours after Received: date > 0.0 HTML_MESSAGE BODY: HTML included in message > 3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100% > [score: 1.0000] > 0.2 DNS_FROM_RFC_ABUSE RBL: Envelope sender in abuse.rfc-ignorant.org > 1.5 RCVD_IN_SORBS_WEB RBL: SORBS: sender is a abuseable web server > [194.150.99.136 listed in dnsbl.sorbs.net] > > The original message was not completely plain text, and may be unsafe to > open with some email clients; in particular, it may contain a virus, > or confirm that your address can receive spam. If you wish to view > it, it may be safer to save it to a file and open it with an editor. > -- Ladislav Lhotka, CESNET PGP key id: E74E8C0C

1 0