Configuring the ipaccess nano3G » History » Revision 3
Revision 2 (neels, 02/08/2017 01:14 PM) → Revision 3/39 (neels, 02/08/2017 01:15 PM)
{{>toc}}
h1. Configuring the ip.access nano3G
h2. IP address
The ip.access nano3G will obtain an IP address from the DHCP server in your network.
You can look it up there or watch wireshark filtering on 'BOOTP' while the nano3G starts up.
For this text, let's assume the IP address it obtained is 192.168.0.124.
h2. Initial Config
Once off, configure:
* the MCC + MNC,
* the UARFCN (i.e. the frequencies to transceive on) and
* the LAC and RAC.
You can do this on the _dmi_ console reachable by telnet:
<pre>
telnet 192.168.0.124 8090
dmi>
</pre>
On the dmi, enter commands like these:
<pre>
# PLMN Id == MCC + MNC
set mcc="901"
set mnc="98"
# [uarfcnDownlink, 1900 MHz band], [scramblingCode], [dummyCellId]
set rfParamsCandidateList=({9800, 401, 1})
# [lac], [rac]
set lacRacCandidateList=({10422, (99)})
</pre>
These settings persist across nano3G power down.
h2. Starting Operation
Every time you boot the nano3G, you need to
* set the IP address the nano3G will find the HNB-GW at.
* 2061 = set cell parameters
* 1216 = unlock ap
* activate HNB-GW connection
* set csg to open access so that any IMSI can register
Enter the _dmi_...
<pre>
telnet 192.168.0.124 8090
dmi>
</pre>
...and issue commands like:
<pre>
set hnbGwAddress="192.168.0.132"
action 2061
action 1216
action establishPermanentHnbGwConnection
set csgAccessMode=CSG_ACCESS_MODE_OPEN_ACCESS
</pre>
h2. SSH Access
The nano3G come with a root password of 'newsys':
<pre>
ssh root@192.168.0.124
password: newsys
</pre>
h2. Logging
When logged in via SSH, you can view the live logging here:
<pre>
ls /tmp/iapclogs/trace_*.log
</pre>
h2. Closed Mode
You can also set csgAccessMode to closed and allow only specific IMSIs:
<pre>
# IMSI, 1:allowed/2:not allowed, phone number (only for "Closed Access")
set accessControlList = ({"001010123456015", 1, "81084"},{"001010123456025", 2, "81025"})
</pre>
(The phone number is actually not relevant)
h1. Peculiarities and Tips
h2. UE Register
The nano3G apparently passes the same identity received from the UE through to
the HNBAP UE Register Request message. This means that when the UE sends a
TMSI, the UE Register Request received by osmo-hnbgw contains no IMSI.
In this scenario, the problem is that Paging apparently does not work.
So even though we have working code that allows HNBAP registration with
a TMSI, that means that you can't reach the UE from the CN.
For completeness sake, the VTY configuration option for this _which you
actually don't really want to enable_ is:
<pre>
hnbgw
iuh
hnbap-allow-tmsi 0
</pre>
Legacy workaround: connect the phone to a different network between retries (being
rejected suffices). That causes the UE to discard its TMSI and then use the IMSI
for the next registration.
A closed csgAccess with explicit IMSIs could help here to enforce that a UE
indeed sends its IMSI to the nano3G and hence Paging should work (to be verified).
See also #1924.
h2. id-Reset
The nano3G seems to *not* send an id-Reset message upon connecting to the HNB-GW.
h2. Location Update failure due to timeout
If a UE seems to connect successfully at first but fails by timeout because the final
"TMSI Reallocation Complete" message is missing, this might be due to misconfiguration:
the CN is sending the wrong LAC or the PLMN-ID (NCC/MNC) is configured wrongly.
This might be confusing in the sense that a complete LU worked once but not after that;
GMM Attach may be successful; Security Mode Commands succeed; and so forth.
Still the solution might be simply to fix the mobile network code in the osmo-cscn.cfg.
