gbproxy2: Re-introduce handling of NS_AFF_CAUSE_FAILURE
We need to figure out what exactly to do in situatoins where NS is reporting failures of the underlying netowkr to us, and test those situations.
When a complete NSE becomes unavailable gbproxy should notify the other
The current code blocks every PtP-BVC (belonging to that BSS) on all SGSNs if
a BSS goes down.
The BSS-side should not be blocked unless no more SGSN connections are
present. We could also remove all BSS nse and wait for those to reconnect.
This is not yet implemented.
gbproxy: Don't free NSE/BVC0 if SGSN NSE goes down
SGSN NSEs are static and should not be removed. Instead remove all
BVC0 can't be blocked and will be reset after the NSE becomes available
again. It might be cleaner to remove BVC0 on NS failure and create it
again, but that change is a bit more complicated.
Fixes ttcn3 test after commit f96cac5077 broke them.
- % Done changed from 0 to 50