Uap2105 » History » Revision 25
« Previous |
Revision 25/26
(diff)
| Next »
tsaitgaist, 02/25/2016 09:29 AM
add UAP3 and UAP4 information
The Huawei UAP2105 is a UMTS femtocell.
Support¶
This product has been EOL/deprecated:- UAP2105 (2011-12-20)
- UAP2105C01 (2011-12-20)
- UAP2105C01 V300R011 (2011-12-20)
- UAP2105C01 V300R011 (2011-12-30)
- UAP2105C01 V300R012 (2012-06-19)
Hardware¶
main board (QWG1SUAP VER C), front:- CPU (ARM based + integrated UMTS base station baseband): HiSilicon SD6121RBC
- 1Gb DDR2 RAM: Samsung K4T1G164QE-HCE6
- 10/100 Base-T transformer: Wurth Electronics Midcom 7112-35-H
- 10/100 Base-T transceiver: Broadcom BCM5241
- AND-gate: Fairchild 74LCX08
- 3V voltage monitor: Maxim MAX708S
- low dropout regulator: Texas Instruments TPS73701
- step down DC-DC convert: Texas Instruments TPS54331
- 256Mb NOR flash: Spansion S29GL256N10TFI01
- 16-bit transceiver: NXP LVT16245B
- EPD TVS Diode Array: Semtech SLVU2.8-4
- low dropout regulator: Texas Instruments TPS73701
- base station transmitter: Maxim MAX2599
- base station receiver: Maxim MAX2547
- GSM baseband: Texas Instruments T303IFZPH
- 16Mb CMOS flash: Spansion S29NS016J0LBJW00
- CPU?: Texas Instruments D6928BB
connectors¶
debug connector:signal/state | pin | pin | signal/state |
---|---|---|---|
low | 1 | 2 | pulse |
TX?/high | 3 | 4 | GND |
RX?/high | 5 | 6 | low |
low | 7 | 8 | low |
TCK?/low | 9 | 10 | pulse |
GND | 11 | 12 | GND |
high | 13 | 14 | high |
GND | 15 | 16 | GND |
TDI?/high | 17 | 18 | pulse |
TRST?/low | 19 | 20 | TDO?/low |
high | 21 | 22 | TMS?/high |
low | 23 | 24 | low |
low | 25 | 26 | low |
DEBUG |
state | pin | pin | signal | mode |
---|---|---|---|---|
high | 1 | 2 | GND | WDGEN |
low | 3 | 4 | GND | BOOTMODE |
high | 5 | 6 | GND | JTAGMODE0 |
high | 7 | 8 | GND | JTAGMODE1 |
high | 9 | 10 | GND | RUNMODE |
MODE |
UAP1¶
The operator where it was bought from is Vodafone Greece.
The board date is 1023.
UAP2¶
The operator where it was bought from is Vodafone Spain.
The board date is 1201.
This board has more shielding cans.
UAP3¶
This femtocell was baught directly in china and is not operator branded.
The board date is 1215.
This femtocell even has a power button on the case.
Rooting¶
How to root this device and intercept communication has been shown in August 2015 at the in Femtoland 350 Yuan for Invaluable Fun presentation (slides, video).
This issue has been analysed and fixed by the vendor.
All femtocells should use the a permanent static IP address 172.16.1.1.
The default web interface password is the femtocells serial (8 characters, starting with B?)
UAP1¶
firmware version: QWGM3SUAP4 V300R011C00 SPC173
ports¶
debug port:- UART not found on pins described in slides (all modes)
- no UART identified using JTAGulator (all modes)
- JTAG not found on pins described in slides (all modes)
- no JTAG identified using JTAGulator, using id code and bypass scans (all modes)
boot¶
boot process (all modes):- red and blue LEDs on for 7 s
- ethernet link on
- red and blue LEDs on for 9 s
- ethernet link off
- red and blue LEDs on for 2 s
- ethernet link on
- red and blue LEDs on for 12 s
- red LED on for 23 s
- red and blue LEDs on for 2 s
- LEDs off for 0.1 s
- red and blue LEDs on for 5 s
- red LED on
network¶
network ports:- the first time the link is on, only UDP port 17185 on fixed IP 172.16.1.1 is open, apparently providing wdbrpc service:
sudo nmap -n -Pn -p21,23,80,17185,6000,6006,7547 -sT -sU 172.16.1.1 Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-22 20:47 CET Nmap scan report for 172.16.1.1 Host is up (0.0030s latency). PORT STATE SERVICE VERSION ... 17185/udp open wdbrpc?
- the second time the link is on, all ports are blocked/filtered:
sudo nmap -n -A -Pn -p21,23,80,17185,6000,6006,7547 -sT -sU 172.16.1.1 Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-22 20:53 CET Nmap scan report for 172.16.1.1 Host is up (0.0019s latency). PORT STATE SERVICE VERSION 21/tcp closed ftp 23/tcp closed telnet 80/tcp filtered http 6000/tcp filtered X11 6006/tcp filtered X11:6 7547/tcp filtered unknown 17185/tcp closed unknown
UAP2¶
firmware version: QWGM3SUAP4 V300R011C02 SPC182
ports¶
debug port:- UART not found on pins described in slides (all modes)
- JTAG not found on pins described in slides (all modes)
- no JTAG identified using JTAGulator, using id code scan (all modes)
boot¶
boot process (all modes):- red and blue LEDs on for 7 s
- ethernet link on
- red and blue LEDs on for 14 s
- ethernet link off
- red and blue LEDs on for 2 s
- ethernet link on
- red and blue LEDs on for 1 s
- ethernet link off
- red and blue LEDs on for 2 s
- ethernet link on
- red and blue LEDs on for 8 s
- red and blue LEDs on for 25 s
- red and blue LEDs on for 2 s
- LEDs off for 0.5 s
- red and blue LEDs on for 3 s
- 6x LEDs off for 2 s
- 6x red and blue LEDs on for 2 s
- red LED on
network¶
network ports:- the first time the link is on no ports are open on IP 172.16.1.1 (compared to UAP1 for wdbrpc service):
- the second time the link is on, only TCP port 80 is open an there is an HTTP service
Starting Nmap 6.40 ( http://nmap.org ) at 2015-11-25 21:56 CET Nmap scan report for 172.16.1.1 Host is up (0.0014s latency). PORT STATE SERVICE VERSION ... 80/tcp open http [[GoAhead]]-Webs httpd |_http-methods: No Allow or Public header in OPTIONS response (status code 400) | http-title: User Login |_Requested resource was http://172.16.1.1/index.htm ...
The IPsec server certificate is checked.
UAP3¶
firmware version: QWGM3SUAP11 V300R011C02 SPC183
network¶
This get the IPsec gateway information from the SIM card.
The IPsec server certificate is checked.
UAP4¶
This is the femtocell from the presentation speakers, which they got from a Russian operator.
network¶
It uses the SIM only the get key material for the IPsec tunnel.
The IPsec gateway and HMS server are configured on the web interface.
The IPsec server certificate is not checked.
Once connect to the IPsec gateway, it will connect to the HMS.
The HMS needs to push the HNB-GW configuration using CWMP (own implementation, the femto CWMP client is very case sensitive and openCWMP did not work here).
Various parameters needs to be pushed.
Once everything is configured the ADMIN_STATE can be set to TRUE to enable broadcasting.
Updated by tsaitgaist about 8 years ago · 25 revisions