BBMD and FD behaviour #1078

Thanks for the answer Steve

The router is a Linux PC with two ethernet ports. Forwarding and iptables.

I did run wireshark on both computers running the bacserv BBMD (1.2 and 2.2) and I see the
whois coming from 2.3 show up on 1.2 but not broadcasted to the whole 1.X network
so I never receive any I-am from my bacnet device on 1.3.

So I can confirm that the broadcast is forwarded to the subnets in the BDT but what I am unsure of is if it should be broadcasted on each subnet.

I will have to admit that I am misunderstanding something but...

I tried using your DemoBBMD with same result. But I could get a positive result registering YABE as a foreign device on the same subnet and then got an I-am from my Bacnet device after restart. I think this is good enough for making my device work correctly as a foreign device and that is good enough for now.

Just to follow up with a short conclusion.
I turned off the BBMD on 1.2 and compiled my device on 1.3 with BBMD=client. That works like charm and it registers as a foreign device with the timetolive period.
But I need to register YABE (2.3) as a BDT on the BBMD (2.2) for my device to show up in YABE. AFAIK that is wrong behaviour but this is good enough for the time being.

Finally it works. I had not set the BDT. BACNET_BDT_ADDR_n so the BDT was not filled in correctly and my other BBMD was in One-Hop mode.

Nice! I had tried to create a bin/bacbbmd-bdt.sh example for you to try using different PORT numbers, but had trouble making the unique set of tables for each of the N BBMD servers I was creating. Entry BACNET_BDT_ADDR_1 and BACNET_BDT_PORT_1 is filled by the device itself, and entry BACNET_BDT_ADDR_2 and BACNET_BDT_PORT_2 etc are filled with the other BBMD servers. I also needed to keep 47809 free for having the example bvlc.sh client tools that would Foreign Device Register into 47808 and run at 47809. The first couple of tries flooded my network with BBMD broadcast loops.