Bug #2669
openosm-msc doesn't clean up BSC state
0%
Description
If a BSC has ever sent a BSSMAP RESET to OsmoMSC we acknowledge this with a RESET-ACK. But then it appears we keep its state indefinitely and want to perform a MSC-originated RESET procedure in return. If the BSC never gets back, this process appears to continue indefinitely.
This is bad, as it means that anyone ever sending/spoofing a single "BSSMAP RESET" to OsmoMSC will be able to turn it into an "amplification attack" with OsmoMSC sending BSSMAP RESET in return.
In order to avoid this, we should probably do both of:
- stop re-transmitting the BSSMAP RESET after some point and simply forget about the BSCs
- introduce a "locked down" mode in which we don't accept BSSMAP from any random source out there, but only explicitly configured BSCs (in the VTY)
Updated by laforge over 6 years ago
- Category changed from A interface (AoIP) to A interface (general)
Updated by dexter almost 6 years ago
See also #2397 As soon as we start collecting LACs we can also collect information about when the BSC appeared first and when the last activity was. This allows us to perform a regular garbage collection.
Updated by dexter almost 6 years ago
Another idea: Once we can maintain the lists using the VTY, we could also have an VTY option that disables the BSC-Auto-Learning completely if necessary.