bfr BACnet IP configuration over vpn

[Jesse Jämsén]

Hi,

I have setup where I have 2 interfaces on pc, 192.168.235.2 (vpn tun adapter) and 10.20.0.128 (local ethernet port)

Broadcasting seems to be working nicely but when devices respond to Who-is they send response directly to my vpn client (192.168.235.12).

How can I configure BFR to forward messages instead of devices responding directly?

Here is my current configuration:

<bfr></bfr>

 <UDP address="10.20.0.128/24" server="lan" />

 <BBMD client="lan" server="bbmd1" foreign="y" />

     <Router>
            <Adapter client="bbmd1" net="0" />
    </Router>

<bfr></bfr>

-Jesse

[Joel Bender]

Jesse,

The configuration you have has only one network, so it's not acting like a router.  When a device receives a Who-Is request it can respond with a broadcast I-Am (the "old school" way of responding) or with a unicast I-Am (the "new school" as an attempt to keep broadcast traffic to a minimum, especially important on large networks).  I'm assuming that your VPN client is registering as a foreign device to your BBMD, so they are on the same BACnet network.

To use the BFR as a router and split your topology into two BACnet networks like this:

<bfr>
    <udp server="udp1" address="10.20.0.128/24">
    <bip client="udp1" server="bip1"></bip></udp></bfr>

<udp server="udp2" address="192.168.235.2/24">
    <bip client="udp2" server="bip2"></bip></udp>

<router>
        <adapter net="1" client="bip1">
        <adapter net="2" client="bip2">
    </adapter></adapter></router>

When your VPN client at 192.168.235.12 sends out a global broadcast message it will be received by the BFR on BACnet network 2 then forwarded to BACnet network 1 with the SNET/SLEN/SADR filled in to say the message had been routed. When the I-Am message is sent, it will be sent to the router saying in effect "please forward this to device" rather than directly back. Note that these are just BIP elements, they don't have to be a BBMD because it won't be using foreign device registration or forwarding broadcasts to peer BBMDs.

Thank you for your interest in the BFR!

Joel

[Joel Bender]

Jesse,

I hope you can pick out the correct pieces for the XML that was included inline in the message. The version that was sent back to me has been horribly mangled and I'm not sure if an XML document that is attached will fair any better! Maybe the problem is the SourceForge mail relay, if you have more problems like this we can continue the conversation at my work address jjb5{at}cornell.edu.

Joel

---

From: Joel Bender joelbender@users.sourceforge.net
Sent: Tuesday, September 3, 2019 1:03 AM
To: [bfr:discussion] 404247@discussion.bfr.p.re.sourceforge.net
Subject: [bfr:discussion] Re: bfr BACnet IP configuration over vpn

Jesse,

The configuration you have has only one network, so it's not acting like a router. When a device receives a Who-Is request it can respond with a broadcast I-Am (the "old school" way of responding) or with a unicast I-Am (the "new school" as an attempt to keep broadcast traffic to a minimum, especially important on large networks). I'm assuming that your VPN client is registering as a foreign device to your BBMD, so they are on the same BACnet network.

To use the BFR as a router and split your topology into two BACnet networks like this:

<bfr>
<udp address="10.20.0.128/24" server="udp1">
<bip client="udp1" server="bip1"></bip></udp></bfr>

<udp address="192.168.235.2/24" server="udp2">
<bip client="udp2" server="bip2"></bip></udp>

<router>
<adapter net="1" client="bip1">
<adapter net="2" client="bip2">
</adapter></adapter></router>

When your VPN client at 192.168.235.12 sends out a global broadcast message it will be received by the BFR on BACnet network 2 then forwarded to BACnet network 1 with the SNET/SLEN/SADR filled in to say the message had been routed. When the I-Am message is sent, it will be sent to the router saying in effect "please forward this to device" rather than directly back. Note that these are just BIP elements, they don't have to be a BBMD because it won't be using foreign device registration or forwarding broadcasts to peer BBMDs.

Thank you for your interest in the BFR!

Joel

---

bfr BACnet IP configuration over vpnhttps://sourceforge.net/p/bfr/discussion/404247/thread/53678d4bb6/?limit=25#6ec6/a2e3

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/bfr/discussion/404247/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Jesse Jämsén]

Hi, I see thank you very much.

I have been using foreign device registeration since the vpn I'm using is tun type so broadcast messages sent by my vpn client won't go trough 192.168.235.0/24 network.
So should I change 192.168.235.2/24 BIP into BBMD and do foreign device registeration to that interface instead?
or am I missing something else?

-Jesse

[Joel Bender]

Jesse,

Yes, you are exactly correct, turn one into a BBMD for foreign device registration. The interface you pick will be the "home" network for the foreign device and everything else will go through the BFR as a BACnet router.

Joel

---

From: "Jesse J?ms?n" jesek@users.sourceforge.net
Sent: Tuesday, September 3, 2019 1:48 AM
To: [bfr:discussion] 404247@discussion.bfr.p.re.sourceforge.net
Subject: [bfr:discussion] bfr BACnet IP configuration over vpn

Hi, I see thank you very much.

I have been using foreign device registeration since the vpn I'm using is tun type so broadcast messages sent by my vpn client won't go trough 192.168.235.0/24 network.
So should I change 192.168.235.2/24 BIP into BBMD and do foreign device registeration to that interface instead?
or am I missing something else?

-Jesse

---

bfr BACnet IP configuration over vpnhttps://sourceforge.net/p/bfr/discussion/404247/thread/53678d4bb6/?limit=25#1266

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/bfr/discussion/404247/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/