| ... | @@ -39,5 +39,13 @@ The community has limited time/resources to help you. Read this carefully to ens |
... | @@ -39,5 +39,13 @@ The community has limited time/resources to help you. Read this carefully to ens |
|
|
1. Upload the wireshark trace (eNB and EPC) on a dropbox/google drive capturing the traffic on ALL interfaces. Do not send wireshark trace as an attachment to the mailing list. **If these files are too big (which should not be the case), do not send them on the mailing list**, but upload them on google drive/dropbox folder and send everyone the link. Refrain from sending huge attachments to the mailing list.
|
|
1. Upload the wireshark trace (eNB and EPC) on a dropbox/google drive capturing the traffic on ALL interfaces. Do not send wireshark trace as an attachment to the mailing list. **If these files are too big (which should not be the case), do not send them on the mailing list**, but upload them on google drive/dropbox folder and send everyone the link. Refrain from sending huge attachments to the mailing list.
|
|
|
|
|
|
|
|
## Questions related to openair-cn
|
|
## Questions related to openair-cn
|
|
|
1. Follow the guidelines above to post questions on the usage of openair-cn
|
|
0. tags prior to v1.0.0 are not maintained anymore.
|
|
|
|
1. Follow the guidelines above to post questions on the usage of openair-cn.
|
|
|
|
2. It will be far more easier for us to inspect a scenario if you capture a pcap trace of relevant messages.
|
|
|
|
Please provide:
|
|
|
|
1) a PCAP trace. (In general S1-C, S11, S6a, S5, SX-ab, S1-U traffic should be captured).
|
|
|
|
2) configuration files if relevant.
|
|
|
|
3) network functions logs if relevant.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
