- Bird-users - Mailing Lists

None
by None 13 Jun '26

13 Jun '26

There are a number of special directives which can be included within an action: `ECHO' copies yytext to the scanner's output. `BEGIN' followed by the name of a start condition places the scanner in the corresponding start condition (see below). `REJECT' directs the scanner to proceed on to the "second best" rule which matched the input (or a prefix of the input). The rule is chosen as described above in *Note Matching::, and `yytext' and `yyleng' set up appropriately. It may either be one which matched as much text as the originally chosen rule but came later in the `flex' input file, or one which matched less text. For example, the following will both count the words in the input and call the routine `special()' whenever `frob' is seen: int word_count = 0; %% frob special(); REJECT; [^ \t\n]+ ++word_count; Without the `REJECT', any occurrences of `frob' in the input would not be counted as words, since the scanner normally executes only one action per token. Multiple uses of `REJECT' are allowed, each one finding the next best choice to the currently active rule. For example, when the following scanner scans the token `abcd', it will write `abcdabcaba' to the output: .... `flex' scans your rule actions to determine whether you use the `REJECT' or `yymore()' features. The `REJECT' and `yymore' options are available to override its decision as to whether you use the options, either by setting them (e.g., `%option reject)' to indicate the feature is indeed used, or unsetting them to indicate it actually is not used (e.g., `%option noyymore)'. Another indication is: flex -s -Cf -B -8 -ocf-lex.c -Pcf_ cf-lex.l flex: REJECT cannot be used with -f or -F make: *** [cf-lex.c] Error 1 You can't use -Cf because flex think you are using REJECT in your scanner. > > Sure, it is not elegant and it might cause bugs in the future (currently, I do > not see any real bug), but your rename is not elegant either. No, but it is the equivalent of renaming a variable from an ideal name to a less ideal name, not a big deal.

1 0

None
by None 13 Jun '26

13 Jun '26

> > I ask because I would like to configure some(if not everything) from our > app with its own CLI/GUI. People usually generate config file and than load it to BIRD. BIRD has quite smart reconfiguration so it is able to see the differences. Ondrej > > Jocke

1 0

None
by None 13 Jun '26

13 Jun '26

interfaces. Suppose the following configuration for router A, # ifconfig eth0 10.1.1.1 netmask 255.255.255.0 broadcast 10.1.1.255 # ifconfig eth1 10.2.2.2 netmask 255.255.255.0 broadcast 10.2.2.255 # ifconfig eth0:0 10.10.10.1 netmask 255.255.255.0 broadcast 10.10.10.255 and a similar one for another router B, # ifconfig eth0 10.1.1.42 netmask 255.255.255.0 broadcast 10.1.1.255 # ifconfig eth1 10.3.3.42 netmask 255.255.255.0 broadcast 10.3.3.255 # ifconfig eth0:0 10.10.10.42 netmask 255.255.255.0 broadcast 10.10.10.255 and then for each say we set up OSPF on eth0:0 such as protocol ospf { ... area 0.0.0.0 { interface "eth0:0" { cost 10; stub no; hello 10; ... type nonbroadcast; strict nonbroadcast yes; authentication none; neighbors { 10.10.10.42 eligible; }; }; interface "eth1" { cost 10; stub yes; ... }; }; } If we check the configuration for ospf, we don't see interface eth0:0 at all: # birdc BIRD 1.0.4 ready. bird> show ospf interface ospf1: Interface "eth1": Area: 0.0.0.0 (0) Type: broadcast ... and note the signifigant absence of eth0:0. So apparently we can't route over alias interfaces? Is there any technical reason for this? I'd really like to be able to because I have a number of routers with different subnets hanging off of them, and some routers beneath those subnets. But I can only route over one particular subnet per interface, the one assigned to the physical interface. Thanks! 'james -- James A. Crippen <james(a)unlambda.com> ,-./-. Anchorage, Alaska, Lambda Unlimited: Recursion 'R' Us | |/ | USA, 61.2069 N, 149.766 W, Y = \f.(\x.f(xx)) (\x.f(xx)) | |\ | Earth, Sol System, Y(F) = F(Y(F)) \_,-_/ Milky Way.

1 0

Re: CentOS 7 repo not work
by Maria Matejka 13 Jun '26

13 Jun '26

Hi Zhang Xun, the reason was that my scripting missed some renaming, and therefore the exception for createrepo, which must run with `--compatibility` for centos 7, was not hit. After re-running `createrepo` and reuploading, it looks fixed on my side. Please note that CentOS 7 may get discontinued without notice when we find out that our tooling breaks beyond repair. Iŧ's hard to keep the build machinery running for a discontinued distro. Thank you for your report! Maria On Sat, Jun 13, 2026 at 10:33:43PM +0800, zx--- via Bird-users wrote: > Hi there, > > Some of my servers are still using CentOS 7 and I'm following https://bird.nic.cz/get-bird/ to install bird, but it looks like CentOS 7 repo is broken? > > [root@localhost ~]# yum-config-manager --add-repo https://pkg.labs.nic.cz/rpm/bird/centos/7/x86_64/bird.repo > Loaded plugins: elrepo, fastestmirror > adding repo from: https://pkg.labs.nic.cz/rpm/bird/centos/7/x86_64/bird.repo > grabbing file https://pkg.labs.nic.cz/rpm/bird/centos/7/x86_64/bird.repo to /etc/yum.repos.d/bird.repo > repo saved to /etc/yum.repos.d/bird.repo > [root@localhost ~]# yum update > Loaded plugins: elrepo, fastestmirror > Determining fastest mirrors > base | 3.6 kB 00:00:00 > bird | 1.5 kB 00:00:00 > epel | 4.3 kB 00:00:00 > extras | 2.9 kB 00:00:00 > updates | 2.9 kB 00:00:00 > bird/primary | 11 kB 00:00:02 > > > One of the configured repositories failed (Unknown), > and yum doesn't have enough cached data to continue. At this point the only > safe thing yum can do is fail. There are a few ways to work "fix" this: > > 1. Contact the upstream for the repository and get them to fix the problem. > > 2. Reconfigure the baseurl/etc. for the repository, to point to a working > upstream. This is most often useful if you are using a newer > distribution release than is supported by the repository (and the > packages for the previous distribution release still work). > > 3. Run the command with the repository temporarily disabled > yum --disablerepo=<repoid> ... > > 4. Disable the repository permanently, so yum won't use it by default. Yum > will then just ignore the repository until you permanently enable it > again or use --enablerepo for temporary usage: > > yum-config-manager --disable <repoid> > or > subscription-manager repos --disable=<repoid> > > 5. Configure the failing repository to be skipped, if it is unavailable. > Note that yum will try to contact the repo. when it runs most commands, > so will have to try and fail each time (and thus. yum will be be much > slower). If it is a very temporary problem though, this is often a nice > compromise: > > yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true > > Parsing primary.xml error: Start tag expected, '<' not found > > [root@localhost ~]# cat /etc/os-release > NAME="CentOS Linux" > VERSION="7 (Core)" > ID="centos" > ID_LIKE="rhel fedora" > VERSION_ID="7" > PRETTY_NAME="CentOS Linux 7 (Core)" > ANSI_COLOR="0;31" > CPE_NAME="cpe:/o:centos:centos:7" > HOME_URL="https://www.centos.org/" > BUG_REPORT_URL="https://bugs.centos.org/" > > CENTOS_MANTISBT_PROJECT="CentOS-7" > CENTOS_MANTISBT_PROJECT_VERSION="7" > REDHAT_SUPPORT_PRODUCT="centos" > REDHAT_SUPPORT_PRODUCT_VERSION="7" > > > > > Zhang Xun > -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.

1 0

Releases on bird.network.cz no longer updated
by Leon Grasmeijer 11 Jun '26

11 Jun '26

Hi there, Are https://bird.network.cz/?download and ftp://bird.network.cz/pub/bird/ no longer being updated? I see there are some versions missing that have been announced and are present on https://bird.nic.cz/get-bird/. Kind regards, Leon

2 1

Crash with `Assertion 'BIT32_TEST(cur->used_bits, idx)' failed at lib/islab.c:678` on 3.3.1
by Matt Corallo 10 Jun '26

10 Jun '26

Sadly I don't have a useful coredump since I was running against a package that I don't have symbols for. Matt

2 1

BIRD 3.3.1, 3.2.2, 3.1.7, 2.19.1, 2.18.2, 2.17.5 released
by Maria Matejka 09 Jun '26

09 Jun '26

Dear BIRD users, we're, as promised, releasing patch versions for all the supported branches. Downloads are possible at <https://bird.nic.cz/get-bird/> and in our upstream repositories. There are some security-relevant fixes this time with a varying degree of relevance. We have fixed a lot of BGP in BIRD 3, most notably several nasty bugs in graceful restart behavior, labelled NLRI parsing and other MPLS stuff. (There are still more MPLS bugs pending in BIRD 3.) We have fixed several flowspec parser flaws in all versions, which were there for years. We have fixed the no-refeed bug of BMP in BIRD 3, and also a cornercase off-by-one in all versions. We have fixed a bunch of corner case OSPF bugs. We have fixed a bunch of race conditions in internal reading the routing tables. We have also fixed the infamous remote code execution bug happening when the path mask feature is used on a gargantuan AS Path (in all versions). There are some outstanding bugs (in all versions) reported, and we've prioritized expediting this release which is already quite beefy, over doing it all at once. If your bug report has been reported as fixed, we would love if you confirmed that from your side. If not, it will most probably get fixed in the next patch release. Officially supported versions are now: - 3.3.x and 2.19.x until 6 months after 3.4.0 and 2.20.0 get released - 3.2.x and 2.18.x until end of November 2026 - LTS 3.1.x and 2.17.x tracking Debian Trixie Also, on commercial note, we offer BIRD Support, so that you can get help with configuration, priority access to critical bug information and fixes, and better influence the overall development directions. It's the users paying for these services, who keep the development running. More on that at our website: <https://bird.nic.cz/commercial-services/> Happy routing! Maria and the BIRD Team -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.

1 0

bird: Assertion 'birdloop_inside(sl->loop)' failed at lib/event.c:161
by Lexi Winter 09 Jun '26

09 Jun '26

hello, running BIRD 3.2.1 on OpenBSD/arm64 7.9, i changed the router-id in bird.conf, then ran 'birdc reload', and bird crashed: Jun 9 07:02:56 ragweed bird: Reconfiguring Jun 9 07:02:56 ragweed bird: Restarting protocol core4 Jun 9 07:02:56 ragweed bird: Restarting protocol core6 Jun 9 07:02:56 ragweed bird: Assertion 'birdloop_inside(sl->loop)' failed at lib/event.c:161 after restarting bird, it appears to be working fine. unfortunately, the generated core file does not seem to be very useful: (lldb) thread list Process 0 stopped * thread #1: tid = 0, 0x00000011e2b302d4 libc.so.103.0`_thread_sys_setsockopt at -:3, stop reason = signal SIGABRT (lldb) bt * thread #1, stop reason = signal SIGABRT * frame #0: 0x00000011e2b302d4 libc.so.103.0`_thread_sys_setsockopt at -:3 frame #1: 0x0000000d19648050 bird`sk_join_group at sysio.h:101:7 (lldb) i can provide the bird executable and core file privately if that's any use.

2 1

Races in birdc causing daemon to crash on low spec routers
by Yifei Sun 03 Jun '26

03 Jun '26

Hello all, I'm hitting crash in BIRD 3.3.0 on several routers. The machines are running - NixOS x86_64-linux 7.0.10 - 2-5 BGP IPv4/IPv6 peers per affected host - prometheus-bird-exporter 1.4.5, scraping every 30s prometheus-bird-exporter runs `show protocols all` over /run/bird/bird.ctl every ~30s, and on hosts with active BGP churn that crashes bird inside bgp_show_proto_info(). systemd restarts it, the next scrape kills it again, and NRestarts climbs ~120/hr... toompea and timah took 14 and 13 cores in their last ~20 minutes of uptime, highline took 4 over a slower span. The other seven routers (butte, cradle, baldy, kongo, lantau, roraima, rysy) run the same build and exporter with no cores (most likely because these machines are only getting default routes). The crash needs concurrent BGP state changes. For example: ```console $ colmena exec --verbose --on @router -- 'sudo coredumpctl list || true' timah | highline | kongo | toompea | butte | cradle | baldy | rysy | lantau | roraima | rysy | No coredumps found. rysy | Succeeded toompea | TIME PID UID GID SIG COREFILE EXE SIZE toompea | Thu 2026-05-28 15:41:25 UTC 1185401 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 98.9M toompea | Thu 2026-05-28 15:41:53 UTC 1265107 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 100.3M toompea | Thu 2026-05-28 15:42:22 UTC 1265317 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 100.9M toompea | Thu 2026-05-28 15:42:54 UTC 1265529 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 106.1M toompea | Thu 2026-05-28 15:43:23 UTC 1265740 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 101.8M toompea | Thu 2026-05-28 15:43:54 UTC 1265952 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 105.9M toompea | Thu 2026-05-28 15:44:22 UTC 1266165 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 90.2M toompea | Thu 2026-05-28 15:44:53 UTC 1266380 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 100.6M toompea | Thu 2026-05-28 19:45:24 UTC 1266590 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 102.9M toompea | Thu 2026-05-28 19:45:53 UTC 1355754 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 88.6M toompea | Thu 2026-05-28 19:46:22 UTC 1355959 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 87.4M toompea | Thu 2026-05-28 19:46:53 UTC 1356167 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 100.8M toompea | Thu 2026-05-28 19:47:22 UTC 1356371 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 88.8M toompea | Thu 2026-05-28 19:47:54 UTC 1356389 993 991 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 104.8M toompea | Succeeded butte | No coredumps found. butte | Succeeded timah | TIME PID UID GID SIG COREFILE EXE SIZE timah | Thu 2026-05-28 15:36:51 UTC 1268745 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 96.9M timah | Thu 2026-05-28 15:37:17 UTC 1268960 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 98.6M timah | Thu 2026-05-28 15:37:52 UTC 1268974 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 95.9M timah | Thu 2026-05-28 15:38:18 UTC 1269382 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 89.2M timah | Thu 2026-05-28 15:38:53 UTC 1269397 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 95.4M timah | Thu 2026-05-28 19:39:27 UTC 1269828 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 131.6M timah | Thu 2026-05-28 19:39:48 UTC 1359330 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 76.2M timah | Thu 2026-05-28 19:40:20 UTC 1359346 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 99.8M timah | Thu 2026-05-28 19:40:49 UTC 1359574 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 94.1M timah | Thu 2026-05-28 19:41:20 UTC 1359832 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 98.9M timah | Thu 2026-05-28 19:41:51 UTC 1360097 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 93.9M timah | Thu 2026-05-28 19:42:22 UTC 1360320 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 88.9M timah | Thu 2026-05-28 19:42:48 UTC 1360526 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 78.8M timah | Succeeded highline | TIME PID UID GID SIG COREFILE EXE SIZE highline | Thu 2026-05-28 11:34:31 UTC 1203740 999 999 SIGSEGV present /nix/store/afhrc47kar31rwmvbj0qrymm6xcpglvk-bird-3.3.0/bin/bird 99.4M highline | Thu 2026-05-28 11:37:02 UTC 1204447 999 999 SIGSEGV present /nix/store/afhrc47kar31rwmvbj0qrymm6xcpglvk-bird-3.3.0/bin/bird 81.9M highline | Thu 2026-05-28 11:40:00 UTC 1205349 999 999 SIGSEGV present /nix/store/afhrc47kar31rwmvbj0qrymm6xcpglvk-bird-3.3.0/bin/bird 108.9M highline | Thu 2026-05-28 12:15:56 UTC 1220240 999 999 SIGSEGV present /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird 80.3M highline | Succeeded baldy | No coredumps found. baldy | Succeeded kongo | No coredumps found. kongo | Succeeded roraima | No coredumps found. roraima | Succeeded lantau | No coredumps found. lantau | Succeeded cradle | No coredumps found. cradle | Succeeded | All done! ``` ```console $ sudo coredumpctl info PID: 1356389 (bird) UID: 993 (bird) GID: 991 (bird) Signal: 11 (SEGV) Timestamp: Thu 2026-05-28 19:47:42 UTC (1h 37min ago) Command Line: /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird -c /etc/bird/bird.conf Executable: /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird Control Group: /system.slice/bird.service Unit: bird.service Slice: system.slice Boot ID: fd4c001e44dc44e1a05cbc5d60440ecb Machine ID: 77293224076f4ff7845c2358cb35a4c0 Hostname: toompea Storage: /var/lib/systemd/coredump/core.bird.993.fd4c001e44dc44e1a05cbc5d60440ecb.1356389.1779997662000000.zst (present) Size on Disk: 104.8M Message: Process 1356389 (bird) of user 993 dumped core. Module /nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird without build-id. Module libz.so.1 without build-id. Module libssh.so.4 without build-id. Stack trace of thread 1356389: #0 0x000059d538758d08 bgp_show_proto_info.lto_priv.0 (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0xdcd08) #1 0x000059d538706fb2 proto_cmd_show (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x8afb2) #2 0x000059d5387077c1 proto_apply_cmd.isra.0 (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x8b7c1) #3 0x000059d5386a2de8 cf_parse.isra.0 (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x26de8) #4 0x000059d5386ac462 cli_parse (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x30462) #5 0x000059d5386f96e5 cli_command (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x7d6e5) #6 0x000059d5386f9980 cli_event.lto_priv.0 (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x7d980) #7 0x000059d5386dff35 ev_run_list_limited (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x63f35) #8 0x000059d538693c8c main (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x17c8c) #9 0x00007ae37602b285 __libc_start_call_main (libc.so.6 + 0x2b285) #10 0x00007ae37602b338 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2b338) #11 0x000059d538694885 _start (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x18885) Stack trace of thread 1356391: #0 0x00007ae3760a6922 __syscall_cancel_arch (libc.so.6 + 0xa6922) #1 0x00007ae37609a00c __internal_syscall_cancel (libc.so.6 + 0x9a00c) #2 0x00007ae37609a084 __syscall_cancel (libc.so.6 + 0x9a084) #3 0x00007ae37611778e __poll (libc.so.6 + 0x11778e) #4 0x000059d5387b3bfe bird_thread_main.lto_priv.0 (/nix/store/230z9nyndgbn265mqlbyvf20z5wdciwy-bird-3.3.0/bin/bird + 0x137bfe) #5 0x00007ae37609dd53 start_thread (libc.so.6 + 0x9dd53) #6 0x00007ae37612563c __clone3 (libc.so.6 + 0x12563c) ELF object binary architecture: AMD x86-64 ``` I temporarily worked around this by removing the prefix count showed when invoking `birdc show proto all`. But I’m not sure if this type of patches are acceptable for upstreaming (please see reasoning in the commit message in the patch): https://raw.githubusercontent.com/stepbrobd/inc/refs/heads/master/pkgs/bird… Best, Yifei

1 3

Fw: [oss-security] BIRD/BIRD2: stack buffer overflow in BGP AS_PATH mask matching, CVE pending
by Bruce Duncan 03 Jun '26

03 Jun '26

Hi, Long time lurker, first time poster. FYI, since I didn't see anything about this, I thought operators might want to be aware that a "vulnerability" has been disclosed on the oss-security list today, and this might cause managers/auditors to ask you probing questions. Hope that's helpful to someone. Bruce The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.

2 1