Rather than running in an endless loop (useful for manual tets),
terminate each UE_CT after sending 50 packets. Also adjust the ramping
and timeouts in a way that it manages to terminate ahead of the guard
timeout.
Change-Id: I7f40f5c59d399d528072986d067b5014fbd085c4
Let's start a number of per-UE/TLLI component on each BVC, and generate
some uplink traffic with random-payload 512-byte LLC frames. The
FRNET(SGSN) side simply ignores all of those by means of a
CreateCallback.
Change-Id: I1b25b4a650d831bb07e9623b76e6c3dcdd71ac88
The existing BSSGP Code assumed that the TLLIs were always known "a
priori" by the test case. With the newly-introduced create_cb,
the user can provide a function to handle any incoming messages for an
unknown TLLL. The default handler behaves like before: fail +
terminate.
Change-Id: Ice0e145f5a6518ff79547dd851042b7965f38e00
We don't want the number of NSE and the number of BVC to be a
compile-time choice, but rather something dynamic at rutime. This
allows configuration files to define those details.
Change-Id: I55b44481b5322deaf78619c1689462d716ddfcec
This is something we need to simulate more complex scenarios,
particularly in the context of frame relay.
Change-Id: If1220852785853f8a5d8de183d5053ddd6ccb958
Add frame relay testcase for BSS and SGSN side.
The test cases require hdlc interfaces (based on
dadhi with super channels and no lmi).
Change-Id: I95d64dc26a8d2ff02d6cf2bfcd22a97e5481f957
Harald Welte