Read this post before asking questions on the mailing lists.
Mailing list usage
- openair5g-user: mailing list to post questions on the usage of openairinterface5g repository. This mailing list must not contain questions related to development of OAI. This mailing list is meant for users of OAI.
- openair5g-devel: mailing list to post questions on the development of openairinterface5g repository. This mailing list is meant only for developers of openairinterface.
- openaircn-user: mailing list to post questions on the usage of openair-cn repository. This mailing list must not contain questions related to development of OAI. This mailing list is meant only for users of openair-cn repository
- openaircn-devel: mailing list to post questions on the development of openair-cn repository. This mailing list is meant only for developers of openair-cn.
- Please post your networking configuartion of eNB/EPC/UE/RRH using the output of
ifconfig -a
androute -n
General
- Do no post same issue in multiple mailing lists and create spam for everyeone The community has limited time/resources to help you. Read this carefully to ensure you get the correct response.
- Please report your branch/commit ID, linux kernel version, and what cpu type, etc in your post
- Search the Mailing List Archives if the problem was not already treated. Try to look at the linux installation, kernel logs to find out the problem. If you describe the problem clearly, then someone can answer you with a clear solution.
- Try to locate whether the problem is within openairinterface5g or openair-cn repository. Avoid sending email to multiple mailing lists.
- In some cases, it might be that problem of usage is related to both openairinterface5g and openair-CN. Only in these exceptional cases, you should send email to both the mailing lists.
- Make sure the subject describes the problems clearly. Avoid sending new/different problems on the old thread.
- Do not post questions on usage of OAI in developer mailing list or vice versa.
- Look in the list of know bugs and at the issues on gitlab
- We make lot of frequent updates to develop/master branch. Please try both the branches (latest updates by pulling from gitlab server) before posting on the mailing list.
- When posting a logfile, we need complete log file as an attachment and not inserted as inline text withing email
Questions related to basic installation of OAI (core + optional packages)
- Look at the logfiles that are generated after installation for errors
- Send these log files along with information on your machine (VM, Ubuntu 14.04?) and x86 CPU type
Questions related to compilation of OAI (oaisim + lte-softmodem)
- Look at the logfiles that are generated after installation for errors. In most cases, it is related to Linux issues.
- What command did you use for compilation?
- Send these log files along with information on your machine (VM, Ubuntu 14.04?) and x86 CPU type
Questions related to oaisim/lte-softmodem execution
- Look at the logfiles that are generated after installation for errors
- What command was used for compilation?
- What command was used for execution and in what order? In case of lte-softmodem, what is your physical setup (USRP/ExpressMimo/XXX, antennas/direct connection/attenuators/XXX, UE is phone/dongle/OAI based)?
- Send these log files (compilation + execution) along with information on your machine (VM, Ubuntu 14.04?) and x86 CPU type
- Send the config files which were changed for your setup
- If HSS database was changed, send the image of the database
- 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
- tags prior to v1.0.0 are not maintained anymore.
- Follow the guidelines above to post questions on the usage of openair-cn.
- It will be far more easier for us to inspect a scenario if you capture a pcap trace of relevant messages.
Please provide:
- Repetition of General section above: Please report your branch/commit ID, linux kernel version, in your post.
- A PCAP trace. (In general S1-C, S11, S6a, S5, SX-ab, S1-U traffic should be captured).
- Configuration files if relevant.
- Network functions logs if relevant.