mirror of
https://github.com/XeonSquared/OC-Copper.git
synced 2024-11-23 01:48:06 +11:00
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.
This commit is contained in:
parent
8e8b3f650d
commit
9df9823a4f
@ -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:
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user