OAI 核心网

### OAI Core Network Setup and Configuration #### Understanding the Requirements To configure an OAI (OpenAirInterface) core network, it is essential to understand that this involves setting up a non-containerized environment where three separate instances of the core network run on one virtual machine within server A while connecting to three independent base stations running on another virtual machine located on host B. This setup allows for simulating multiple independent networks using ueransim as the user equipment simulator. The configuration process can be complex due to dependencies such as kernel compatibility which significantly impacts stability and performance[^4]. #### Machine Network Configuration For establishing connections between Server A and Host B via direct Ethernet cables, specific IP addressing schemes must be adhered to ensure proper communication without conflicts or routing issues. Typically, each pair of connected interfaces should belong to different subnets unless explicitly stated otherwise by design requirements[^1]. In cases like these described here, maintaining consistent subnetting practices across all links helps avoid potential complications during deployment. #### UERANSIM Configuration UERANSIM configurations are tailored towards emulating UE behavior accurately when interacting with various types of gNodeBs under test conditions. Configuring UERANSIM requires precise adjustments according to documentation provided alongside source code repositories[^3], ensuring seamless integration into existing setups involving real-world hardware elements. #### Routing Between Core Networks and Hosts Properly configuring routes ensures packets traverse from any given endpoint through intermediary devices until reaching their destination correctly. For scenarios outlined previously regarding simultaneous operation of multiple cores/base-stations pairs over dedicated physical paths, static route entries might prove beneficial in directing traffic efficiently among involved parties[^2]. ```bash ip route add 192.168.10.0/24 dev eth0 ``` This command adds a static route entry pointing toward `eth0` interface leading outwards onto specified target LAN segment (`192.168.10.0/24`) assuming appropriate substitutions made based upon actual topology details present at runtime. #### Kernel Compatibility Consideration Since OAI has strict demands concerning underlying operating system kernels used throughout its lifecycle stages—from initial installation till final operational readiness—it becomes imperative always verify whether currently installed versions meet minimum supported standards before proceeding further down development pathways.