Project

General

Profile

Configuring the ipaccess nano3G » History » Version 3

neels, 02/08/2017 01:15 PM

1 2 neels
{{>toc}}
2 1 neels
3 2 neels
h1. Configuring the ip.access nano3G
4
5
h2. IP address
6
7
The ip.access nano3G will obtain an IP address from the DHCP server in your network.
8
You can look it up there or watch wireshark filtering on 'BOOTP' while the nano3G starts up.
9
For this text, let's assume the IP address it obtained is 192.168.0.124.
10
11
h2. Initial Config
12
13
Once off, configure:
14
15
* the MCC + MNC,
16
* the UARFCN (i.e. the frequencies to transceive on) and
17
* the LAC and RAC.
18
19
You can do this on the _dmi_ console reachable by telnet:
20
21
<pre>
22
telnet 192.168.0.124 8090
23
dmi>
24
</pre>
25
26
On the dmi, enter commands like these:
27
28
<pre>
29
# PLMN Id == MCC + MNC
30
set mcc="901"
31
set mnc="98"
32
33
# [uarfcnDownlink, 1900 MHz band], [scramblingCode], [dummyCellId]
34
set rfParamsCandidateList=({9800, 401, 1})
35
36
# [lac], [rac]
37
set lacRacCandidateList=({10422, (99)})
38
</pre>
39
40
These settings persist across nano3G power down.
41
42
h2. Starting Operation
43
44
Every time you boot the nano3G, you need to
45
46
* set the IP address the nano3G will find the HNB-GW at.
47
* 2061 = set cell parameters
48
* 1216 = unlock ap
49
* activate HNB-GW connection
50
* set csg to open access so that any IMSI can register
51
52
Enter the _dmi_...
53
<pre>
54
telnet 192.168.0.124 8090
55
dmi>
56
</pre>
57
58
...and issue commands like:
59
60
<pre>
61
set hnbGwAddress="192.168.0.132" 
62
action 2061
63
action 1216
64
action establishPermanentHnbGwConnection
65
set csgAccessMode=CSG_ACCESS_MODE_OPEN_ACCESS
66
</pre>
67
68
h2. SSH Access
69
70
The nano3G come with a root password of 'newsys':
71
<pre>
72
ssh root@192.168.0.124
73
password: newsys
74
</pre>
75
76
h2. Logging
77
78
When logged in via SSH, you can view the live logging here:
79
<pre>
80
ls /tmp/iapclogs/trace_*.log
81
</pre>
82
83
h2. Closed Mode
84
85
You can also set csgAccessMode to closed and allow only specific IMSIs:
86
87
<pre>
88
# IMSI, 1:allowed/2:not allowed, phone number (only for "Closed Access")
89
set accessControlList = ({"001010123456015",  1, "81084"},{"001010123456025", 2, "81025"})
90
</pre>
91
92
(The phone number is actually not relevant)
93
94
h1. Peculiarities and Tips
95
96
h2. UE Register
97
98
The nano3G apparently passes the same identity received from the UE through to
99
the HNBAP UE Register Request message. This means that when the UE sends a
100
TMSI, the UE Register Request received by osmo-hnbgw contains no IMSI.
101
102
In this scenario, the problem is that Paging apparently does not work.
103
So even though we have working code that allows HNBAP registration with
104
a TMSI, that means that you can't reach the UE from the CN.
105
106
For completeness sake, the VTY configuration option for this _which you
107
actually don't really want to enable_ is:
108
109
<pre>
110
hnbgw
111
 iuh
112
  hnbap-allow-tmsi 0
113
</pre>
114
115
Legacy workaround: connect the phone to a different network between retries (being
116
rejected suffices). That causes the UE to discard its TMSI and then use the IMSI
117
for the next registration.
118
119
A closed csgAccess with explicit IMSIs could help here to enforce that a UE
120
indeed sends its IMSI to the nano3G and hence Paging should work (to be verified).
121
See also #1924.
122 3 neels
123
h2. id-Reset
124
125
The nano3G seems to *not* send an id-Reset message upon connecting to the HNB-GW.
126
127
h2. Location Update failure due to timeout
128
129
If a UE seems to connect successfully at first but fails by timeout because the final
130
"TMSI Reallocation Complete" message is missing, this might be due to misconfiguration:
131
the CN is sending the wrong LAC or the PLMN-ID (NCC/MNC) is configured wrongly.
132
133
This might be confusing in the sense that a complete LU worked once but not after that;
134
GMM Attach may be successful; Security Mode Commands succeed; and so forth.
135
Still the solution might be simply to fix the mobile network code in the osmo-cscn.cfg.
Add picture from clipboard (Maximum size: 48.8 MB)