Works with version commit 18b2b5531da1f436da50f73f44d9b3fb25522ed0 - 2015-12-17 01:10:43.
Note: I used this version since there were test errors in the JUnit tests in the latest one (commit 4a445c93356d8558988f270c3e7a97a85df28eef)

Excellent. I fetched the infiniteautomation project several days ago when there was no difference between the two forks. But it seems that the problem has been fixed in the meantime (at least if the commit-messages are correct). I will grab the latest version and try again.

Thanks!

I used the latest version (af736e9fa7d37736e69c4d29f9442d20c60f548b - 2015-12-10 18:47:09) taken from https://github.com/mlohbihler/BACnet4J which is version 3.2.2.

I had exactly the same issue, running the library on linux with multiple network interfaces. I investigated "a bit" and found out that the library works until commit 519d464e686a1d551093e11316a2f314a60f02c3 (2015-10-14 16:56:50). This was the commit where BBMD-support was added.
The problem is, that in the class IpNetwork during initialization phase the DatagramSocket is always bound to a specific interface (using it's address). In previous versions a wildcast-binding was supported. Unfortunately, the specific binding causes problems on some implementations when trying to receive broadcast messages, as stated in the JavaDoc of DatagramSocket (see class-level description of http://docs.oracle.com/javase/7/docs/api/java/net/DatagramSocket.html).
I tried several versions of the JVM (oracle and openjdk) - without success. It seems to be an issue on operation-system level.

ATM, I have a quick and dirty workaround for me, maybe breaking BBMD-support or other features and which prevents me releasing new versions of libraries which use this library as base. It would be nice to have a "certified" fix for this.