From 9df9823a4fe7e0505e0520e6321d670e1ac40255 Mon Sep 17 00:00:00 2001 From: 20kdc Date: Mon, 20 Mar 2017 16:20:52 +0000 Subject: [PATCH] Clarify possibilities of interaction between broadcast packets and hierarchial gateways. The implementation in the oc/ subfolder of a hierarchial gateway goes with the "allow subnets to cause higher-level broadcasts, and allow higher levels to cause subnet broadcasts, but don't let messages leak" solution That is, the default if hierarchial gateways have no special handling for broadcast addresses. --- protocol.1 | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/protocol.1 b/protocol.1 index 34b9d56..fb8db4a 100644 --- a/protocol.1 +++ b/protocol.1 @@ -17,8 +17,13 @@ If it's on the child side, reject if it's prefixed with "<", If it's on the parent side, reject unless prefixed with hostname .. "/", otherwise remove that. + (Optionally, if the name is "*", bypass this rule completely. + This is not recommended, though, as this allows sending a "complete broadcast packet" via "[some amount of <]*".) + If it's on the child side, reject unless prefixed with "<", otherwise remove that. + (Optionally, if the name is "<*", reject anyway. + This is a measure which you may or may not wish to take - if the above 'complete broadcast' possibility has been implemented, then it is a must.) For the packet's general routing: