View Full Version : Bacnet/ip over internet
Burnt-Out
12-11-2008, 07:27 AM
Is there any way to run bacnet over Internet, I hear that nat addressing breaks it down
amigo
12-11-2008, 09:28 AM
look up BBMD functionality in BACnet.
Most high level bacnet controllers have this feature but it needs to be enabled. Each internet segment/subnet of your network requires one device to act as the BBMD.
The BBMDs talk to each other by encapsulating BACnet packets in standard TCP format, that is why they can cross internet routers. Once the other BBMD gets the packet it unbundles it to a standard BACnet packet and passes it to the BACnet device that resides on its segment.
justjohnson
12-11-2008, 11:32 AM
As long as the BBMDs have external IP addresses that can be seen from the internet it's not a problem. The current Bacnet/IP standard does not address NAT so if your devices sit on an internal IP with a router doing port forwarding from a common external IP then the messages will get lost.
Webbyz
12-11-2008, 01:29 PM
Agreed with both previous posts. We have tried this and it will not work behind a firewall. You need to have a BBMD on both sides with a real world WAN IP address. You can get away with inter-corporate WAN bridging if you have a VPN but you need higher level Cisco Routers to take care of this. The issue is just when you start crossing subnets things get lost in the shuffle.
AutoPilot
12-11-2008, 02:31 PM
On a firewall you have to allow UDP/IP on port 47808.
Most IT people freak out on opening ports.
But after the they check into the BACnet protocol and the reserved BAC0 (47808) port they slowly begin to come around.
It's totally safe.
Webbyz
12-11-2008, 02:36 PM
This is a long document but check it out and it does a good job at explining the quirks... http://www.bacnet.org/Bibliography/ES-7-99/IPPART1.HTM
Burnt-Out
12-12-2008, 08:22 AM
On a firewall you have to allow UDP/IP on port 47808.
Most IT people freak out on opening ports.
But after the they check into the BACnet protocol and the reserved BAC0 (47808) port they slowly begin to come around.
It's totally safe.
I think theirs more to it that just opening up 47808, I have done this and I can connect to the device, however whenever I tried to view any points the link breaks down.
I do have a BBMD, however they are behind firewalls.
So basically my question is what do 2 BBMD's need to see each other, just 47808?
Thanks for the info, Im sifting through it now
Burnt-Out
12-12-2008, 08:30 AM
This is a long document but check it out and it does a good job at explining the quirks... http://www.bacnet.org/Bibliography/ES-7-99/IPPART1.HTM
That is a good document!, Thanks Webby
If refers to a sourcforge application http://sourceforge.net/projects/bfr
Has anyone here used it?
AutoPilot
12-12-2008, 03:32 PM
What software are you using?
I run several remote sites with Andover, Delta, and Tridium.
I've never had any problems with BBMD.
I take that back... Sometimes a JACE can be fussy about the network connections.
Burnt-Out
12-12-2008, 04:24 PM
Summit
jeffk91467
12-14-2008, 02:41 AM
I think theirs more to it that just opening up 47808, I have done this and I can connect to the device, however whenever I tried to view any points the link breaks down.
I do have a BBMD, however they are behind firewalls.
So basically my question is what do 2 BBMD's need to see each other, just 47808?
Try this as a workaround:
Router #1
Internal IP 192.168.1.10
External IP 45.125.100.101
Router #2
Internal IP 192.168.5.15
External IP 67.101.45.100
In your BBMD tables, use the External addresses. So router #1 will have the IP address of 67.101.45.100 to find router #2. Router #2 will have the IP address of 45.125.100.101 to find router #1.
Set Router #1's NAT firewall's to port forward traffic on 47808 to the internal Bacnet router's address of 192.168.1.10.
Set Router #2's NAT firewall's to port forward traffic on 47808 to the internal Bacnet router's address of 192.168.5.15.
This should get your Bacnet traffic to work.
Thanks for the info guys. These posts will help some of the guys at my office.:D
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.