TABLE OF CONTENTS

• Settings for the eNodeB
• Settings for the UE
• Tower Router Configuration
  • Alternative DHCP Method
  • DHCP router configuration
• Monitoring

Settings for the eNodeB

Go through normal eNodeB setup from the Baicells manual.  Then make sure these settings are made:

Save everything and reboot.

Settings for the UE

Log into UE, upgrade to BCE-ODU-1.0.12 and leave everything at default except the following:

Set the customer router to:

IP address: 192.168.254.254/24

Default GW: 192.168.254.254

DNS1: 192.168.254.1

DNS2: 8.8.8.8

Then set the DMZ to pint to the customer router:

Tower Router Configuration

The tower router that the eNodeB connects to will need an IP address on the interface facing the eNodeB and a DHCP server.  Once a UE pulls an IP, this becomes the customer's IP for all purposed because the DMZ settings on the UE will forward everything except https to the customer's router behind the UE.  Management of the UE will still be by https on its WAN IP.  Once the UE pulls an address, make that address static in the router and notate it by the customer's name for future reference.

Alternative DHCP Method

You can integrate this setup with Radius/Billing by using authenticated DHCP and radius.  

DHCP router configuration

• Set DHCP to use User Manager for DHCP server leases:

/ ip dhcp-server set dhcp1 use-radius=yes

• Add radius client to consult User Manager for DHCP service.

/ radius add service=dhcp address=y.y.y.y secret=123456

Where 'secret' is equal to Radius Server's router secret. 'y.y.y.y' is the Radius Server address.

In the radius server, use the UE's MAC addresses for user name and password.  The Radius Server could then do user accounting, turn customers on and off, etc.

Monitoring

You can now monitor/manage via https your UE's here: