Project

General

Profile

Configuring the ipaccess nano3G » History » Version 21

neels, 12/07/2017 03:01 PM

1 2 neels
{{>toc}}
2 1 neels
3 2 neels
h1. Configuring the ip.access nano3G
4
5
h2. IP address
6
7 21 neels
The ip.access nano3G will obtain an IP address from the DHCP server in your network. Ways to find out:
8
9
* Run @abisip-find@ (currently in the osmo-bsc.git repository), which should find the nano3G (despite no Abis interface being present). Find the @abisip-find@ output matching the MAC address printed on the sticker next to the power jack.
10
* Watch wireshark, filtering on 'BOOTP' while the nano3G starts up.
11
* Look it up in your DHCP server's list of leases.
12
13 2 neels
For this text, let's assume the IP address it obtained is 192.168.0.124.
14
15
h2. Initial Config
16
17
Once off, configure:
18
19
* the MCC + MNC,
20
* the UARFCN (i.e. the frequencies to transceive on) and
21
* the LAC and RAC.
22
23
You can do this on the _dmi_ console reachable by telnet:
24
25
<pre>
26
telnet 192.168.0.124 8090
27
dmi>
28
</pre>
29
30
On the dmi, enter commands like these:
31
32
<pre>
33
# PLMN Id == MCC + MNC
34
set mcc="901"
35
set mnc="98"
36
37
# [uarfcnDownlink, 1900 MHz band], [scramblingCode], [dummyCellId]
38
set rfParamsCandidateList=({9800, 401, 1})
39
40
# [lac], [rac]
41
set lacRacCandidateList=({10422, (99)})
42
</pre>
43
44
These settings persist across nano3G power down.
45
46
h2. Starting Operation
47
48
Every time you boot the nano3G, you need to
49
50
* set the IP address the nano3G will find the HNB-GW at.
51
* 2061 = set cell parameters
52
* 1216 = unlock ap
53
* activate HNB-GW connection
54
* set csg to open access so that any IMSI can register
55
56
Enter the _dmi_...
57
<pre>
58
telnet 192.168.0.124 8090
59
dmi>
60
</pre>
61
62
...and issue commands like:
63
64
<pre>
65
set hnbGwAddress="192.168.0.132" 
66
action 2061
67
action 1216
68
action establishPermanentHnbGwConnection
69
set csgAccessMode=CSG_ACCESS_MODE_OPEN_ACCESS
70
</pre>
71
72
h2. SSH Access
73
74
The nano3G come with a root password of 'newsys':
75
<pre>
76
ssh root@192.168.0.124
77
password: newsys
78
</pre>
79
80 9 roox
In case you are using a recent version of the OpenSSH-client you'll get the following error message while trying to connect:
81
_Unable to negotiate with 192.168.0.124 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1_
82
83
Starting with OpenSSH version 7.0 support for the 1024-bit diffie-hellman-group1-sha1 key exchange was disabled by default at run-time.
84
Use the following to connect to your nano3G in this case.
85
<pre>
86
ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 root@192.168.0.124
87
</pre>
88
89 10 roox
h2. NTP
90
91
Be sure that the nano3G is able to resolve the DNS record _0.ipaccess.pool.ntp.org_ and can connect the the corresponding NTP servers.
92
Without syncronized NTP the nano3G does not bring up the TRX and it even do not try to connect to the hnbGw.
93 9 roox
94 20 neels
A workaround is to edit the @/etc/hosts@ file on the nano3G (via SSH) and add an entry to resolve 0.ipaccess.pool.ntp.org to your local NTP server's IP address (which requires re-mounting the root file system in read-write mode...).
95 19 neels
96 2 neels
h2. Logging
97
98
When logged in via SSH, you can view the live logging here:
99
<pre>
100
ls /tmp/iapclogs/trace_*.log
101
</pre>
102
103
h2. Closed Mode
104
105
You can also set csgAccessMode to closed and allow only specific IMSIs:
106
107
<pre>
108 6 neels
set csgAccessMode=CSG_ACCESS_MODE_CLOSED_ACCESS
109 2 neels
# IMSI, 1:allowed/2:not allowed, phone number (only for "Closed Access")
110
set accessControlList = ({"001010123456015",  1, "81084"},{"001010123456025", 2, "81025"})
111
</pre>
112
113
(The phone number is actually not relevant)
114
115
h1. Peculiarities and Tips
116
117 12 neels
h2. Exiting the dmi while keeping it alive
118
119
When you exit the dmi telnet by hitting Ctrl-C, it will not be available anymore until you reboot the nano3G.
120
Every connection attempt will then end in
121
122
<pre>
123
dmi> Connection closed by foreign host.
124
</pre>
125
126 13 neels
However, if you end your session by the telnet escape character and quitting, the dmi remains open for further connections. Usually that means: hit Ctrl-] (Ctrl and closing square brace) and then enter 'quit':
127 12 neels
128
<pre>
129
dmi> ^]
130
telnet> quit
131
</pre>
132
133 2 neels
h2. UE Register
134
135
The nano3G apparently passes the same identity received from the UE through to
136
the HNBAP UE Register Request message. This means that when the UE sends a
137
TMSI, the UE Register Request received by osmo-hnbgw contains no IMSI.
138
139 7 neels
In this scenario, the problem is that Paging apparently does not (always) work.
140 1 neels
So even though we have working code that allows HNBAP registration with
141 7 neels
a TMSI, that means that you can't (always) reach the UE from the CN.
142
This is not always the case, sometimes the nano3G can well page UEs that have
143
registered by TMSI. Vague idea: it may be that it needs to have seen the IMSI
144
once after power-cycling, e.g. after a closed-mode registration, and then
145
TMSI registration will not harm Paging. (TODO: clarify this)
146 2 neels
147 7 neels
The VTY configuration option to allow TMSI-only attaching to HNBGW, which
148
possibly helps to shorten your dev cycle but may harm paging, is:
149 2 neels
150
<pre>
151
hnbgw
152
 iuh
153 7 neels
  hnbap-allow-tmsi 1
154 2 neels
</pre>
155 1 neels
156 2 neels
Legacy workaround: connect the phone to a different network between retries (being
157
rejected suffices). That causes the UE to discard its TMSI and then use the IMSI
158
for the next registration.
159
160 18 neels
A [[Configuring the ipaccess nano3G#Closed-Mode|closed csgAccess]] with explicit IMSIs could help here to enforce that a UE
161 7 neels
indeed sends its IMSI to the nano3G and hence Paging should work.
162 3 neels
See also #1924.
163
164
h2. id-Reset
165
166
The nano3G seems to *not* send an id-Reset message upon connecting to the HNB-GW.
167
168
h2. Location Update failure due to timeout
169
170
If a UE seems to connect successfully at first but fails by timeout because the final
171
"TMSI Reallocation Complete" message is missing, this might be due to misconfiguration:
172
the CN is sending the wrong LAC or the PLMN-ID (NCC/MNC) is configured wrongly.
173
174
This might be confusing in the sense that a complete LU worked once but not after that;
175
GMM Attach may be successful; Security Mode Commands succeed; and so forth.
176 8 neels
Still the solution might be simply to fix the mobile network code in the osmo-msc.cfg.
177 4 neels
178
h2. RAB Assignment needs IuUP ACK Initialization
179
180
IuCS uses UP encapsulated in RTP. The UP starts off by sending an Initialization, replied
181
upon by an ACK Initialization.
182
183
The nano3G seems to not reply with an ACK when it receives an IuUP Initialization frame.
184
Thus it is not possible to merely echo its own RTP packets back to itself; instead, the
185
first RTP frame received from the nano3G (that is an IuUP Initialization) can be changed
186
to an ACK Initialization by writing 0xe4 to the first payload byte. Sending this back to
187
the nano3G then results in successful RAB Assignment.
188
189
(With the SysmoCell5000, echoing its own Initialization back to itself results in an ACK
190 1 neels
being sent, which we can also echo back to itself, so mere echoing works there.)
191 11 neels
192 14 neels
A hack to make the nano3G work is currently on the "3G master" (the vlr_3G branch),
193
because it does not seem to harm other femto cells: the commit's summary is
194
"mgcp: hack RAB success from nano3G: patch first RTP payload", see "cgit":http://git.osmocom.org/openbsc/log/?h=vlr_3G.
195 15 neels
196
See also #1712#note-21 and the following two comments.
Add picture from clipboard (Maximum size: 48.8 MB)