Welcome to the BACnet Firewall Router¶
If you would like to participate in its development, please join the developers mailing list and use the Trac to create tickets and monitor the project development. There is also a Google+ page that you can add to your circles and have release notifications show up in your stream.
For an overview of the current project activity, there is a Trello board, feel free to become a member and share what you are doing with the rest of the BFR community.
Welcome aboard!
Getting Started¶
This section is a walk through of the process of building and installing the application, downloading the sample code and communicating with a test device.
Configuration¶
This section is a walk through of the process of building and installing the application, downloading the sample code and communicating with a test device.
Developers¶
This documentation is intended for BFR developers.
Missing Features¶
- Missing link layer; ARCNET - Most enterprise networks are composed of a collection of Ethernet and/or IP LAN’s. so the focus of the project has been on those two technologies. There are relatively few ARCNET cards with Linux drivers, so ARCNET support has been a low priority
- Missing link layer; MS/TP - almost all PC’s come with a serial port, but it is very difficult to manage the timing issues with MS/TP communications with many operating systems. The floppy-boot Linux environment, particularly where the BFR is the only application running, should have no problems keeping track of the necessary timers.
- Missing link layer; PTP - Enterprise networks are typically static, with dial-up connections becoming less popular as full-time, high speed connections become available. PTP does not have the same timing requirements that are involved in MS/TP networks and the PTP protocol is relatively simple, so adding support for PTP should not be difficult.
- Half-routers - Similar to PTP support, there are standard procedures for processing I-Could-Be-Router-To-Network, Establish-Connection-To-Network, and other similar network layer messages that are appropriate for networks that are not “always on”, the BFR application does not currently follow these procedures.