[ABANDON] osmo-bsc[master]: prevent ARFCN+BSIC collisions in config

2018-05-09 Thread Neels Hofmeyr
Neels Hofmeyr has abandoned this change. Change subject: prevent ARFCN+BSIC collisions in config .. Abandoned -- To view, visit https://gerrit.osmocom.org/7814 To unsubscribe, visit https://gerrit.osmocom.org/settings

osmo-bsc[master]: prevent ARFCN+BSIC collisions in config

2018-04-16 Thread Neels Hofmeyr
Patch Set 1: Code-Review-1 so, it's not that simple. Practically, one would want to be able to re-use the same ARFCN+BSIC even within the same BSC. When resolving an ARFCN+BSIC, the source BTS is the third part of information that needs to provide a unique match. i.e. each BTS has neighbors

osmo-bsc[master]: prevent ARFCN+BSIC collisions in config

2018-04-15 Thread Neels Hofmeyr
Patch Set 1: ah, didn't realize this already depends on the neighbor_ident API -- To view, visit https://gerrit.osmocom.org/7814 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ia7c38188ccbad5d8b7398e3e5220015e62c08c8b Gerrit-PatchSet: 1

[PATCH] osmo-bsc[master]: prevent ARFCN+BSIC collisions in config

2018-04-15 Thread Neels Hofmeyr
Review at https://gerrit.osmocom.org/7814 prevent ARFCN+BSIC collisions in config If multiple BTS are configured with identical ARFCN+BSIC, handover cannot possibly work. Add warn_on_arfcn_bsic_collisions() and when collisions are detected: - exit right away on program startup. - warn on vty