Hello,
I bougth one ip.access nano3G in ebay, it seem to have a custom firmware for an operator that does not work in my country I want to know how to reflash it with the correct firmware to run openbsc. Can anybody help me?
Best regards and a lot of thanks in advance.
Good day, Ernesto
it seem to have a custom firmware for an operator that does not work in
my country
How have you found that out? What actions have you taken? Have you performed a factory reset?
If you expand on the description of your problem, then it will be much easier for someone here to help you.
With best wishes, Mykola
A lot of thanks Mykola, I tried to: - Find the nano3G ip address, I found it and create a rule in my dhcp server to assign a fixed ip address. - Ping the nano3G: 0% packet loss. - Scan all TCP ports with nmap: there is no open port - Capture all network traffic from nano3Gwith tcpdump: it connect to a T-mobile to perform a isakmp handshake without any result, also get the date and time from some ntp servers. - Perform a factory reset but I think that this action just restore the custom operator firmware, at this step the nano3g also connect to ip.access servers and download some crl certificates, then also try the isakmp handshake with T-mobile server.
Best regards
2018-07-25 9:41 GMT+02:00 Mykola Shchetinin mykola@razormaker.com:
Good day, Ernesto
it seem to have a custom firmware for an operator that does not work in
my country
How have you found that out? What actions have you taken? Have you performed a factory reset?
If you expand on the description of your problem, then it will be much easier for someone here to help you.
With best wishes, Mykola
Have you tried connecting to the commissioning web page of the FAP right after performing the factory reset? (You need to connect to it directly via Ethernet)
It is somewhat described in the section 5 of this document: https://fccid.io/QGGIPA237C/User-Manual/User-manual-1470788
I use this process when configuring the FAP. (After that it pulls the configuration from my ACS server)
If that doesn’t work, then I hope somebody other will help you :)
Hello.
I have the same problem.
For me I don't have the webadmin password. I think we won't the nanobts proprietary software for reset it.
Thanks.
Le mer. 25 juil. 2018 à 11:17, Mykola Shchetinin mykola@razormaker.com a écrit :
Have you tried connecting to the commissioning web page of the FAP right after performing the factory reset? (You need to connect to it directly via Ethernet)
It is somewhat described in the section 5 of this document: https://fccid.io/QGGIPA237C/User-Manual/User-manual-1470788
I use this process when configuring the FAP. (After that it pulls the configuration from my ACS server)
If that doesn’t work, then I hope somebody other will help you :)
Hello Mykola,
I tried it, It shown a login/password screen: https://i.imgur.com/G2TgoHS.png unfortunately I don't know it.
Best regards
2018-07-25 11:17 GMT+02:00 Mykola Shchetinin mykola@razormaker.com:
Have you tried connecting to the commissioning web page of the FAP right after performing the factory reset? (You need to connect to it directly via Ethernet)
It is somewhat described in the section 5 of this document: https://fccid.io/QGGIPA237C/User-Manual/User-manual-1470788
I use this process when configuring the FAP. (After that it pulls the configuration from my ACS server)
If that doesn’t work, then I hope somebody other will help you :)
Hello
I think the password this not the same by nanobts. All nanobts have their password.
Le mer. 25 juil. 2018 à 18:37, Ernesto Sanchez xload.es@gmail.com a écrit :
Hello Mykola,
I tried it, It shown a login/password screen: https://i.imgur.com/G2TgoHS.png unfortunately I don't know it.
Best regards
2018-07-25 11:17 GMT+02:00 Mykola Shchetinin mykola@razormaker.com:
Have you tried connecting to the commissioning web page of the FAP right after performing the factory reset? (You need to connect to it directly via Ethernet)
It is somewhat described in the section 5 of this document: https://fccid.io/QGGIPA237C/User-Manual/User-manual-1470788
I use this process when configuring the FAP. (After that it pulls the configuration from my ACS server)
If that doesn’t work, then I hope somebody other will help you :)
I don't know if there is a generic login/password or it's a custom pair for each device.
Best regards.
2018-07-25 18:38 GMT+02:00 Choukou Moun choukoumoun@gmail.com:
Hello
I think the password this not the same by nanobts. All nanobts have their password.
Le mer. 25 juil. 2018 à 18:37, Ernesto Sanchez xload.es@gmail.com a écrit :
Hello Mykola,
I tried it, It shown a login/password screen: https://i.imgur.com/G2TgoHS.png unfortunately I don't know it.
Best regards
2018-07-25 11:17 GMT+02:00 Mykola Shchetinin mykola@razormaker.com:
Have you tried connecting to the commissioning web page of the FAP right after performing the factory reset? (You need to connect to it directly via Ethernet)
It is somewhat described in the section 5 of this document: https://fccid.io/QGGIPA237C/User-Manual/User-manual-1470788
I use this process when configuring the FAP. (After that it pulls the configuration from my ACS server)
If that doesn’t work, then I hope somebody other will help you :)
Hi all,
the nano3G come with various firmwares, and it is not trivial to get them to act as hNodeB ready to connect to osmo-hnbgw. It is highly unlikely that you will find on the market a nano3G that is usable for osmocom as-is.
Sysmocom has nano3G on offer that are ready to connect to osmo-hnbgw, but we obviously cannot legally distribute the firmware. So this has to end in: sorry folks, you will likely not have any fun with your nano3G :(
~N
Hi Neels, a lot of thanks, I think that is not a good idea work in an open proyect with proprietary hardware, and proprietary firmware... The result is: I don't own my hardware, I paid for hardware that I can not use, I can understand pay a fee for the "new" license but no more than this.
BTW: how much cost the nano3G that sysmocom offers? You can write me if you can not the the price in public.
We are still working :)
2018-07-25 16:47 GMT+02:00 Neels Hofmeyr nhofmeyr@sysmocom.de:
Hi all,
the nano3G come with various firmwares, and it is not trivial to get them to act as hNodeB ready to connect to osmo-hnbgw. It is highly unlikely that you will find on the market a nano3G that is usable for osmocom as-is.
Sysmocom has nano3G on offer that are ready to connect to osmo-hnbgw, but we obviously cannot legally distribute the firmware. So this has to end in: sorry folks, you will likely not have any fun with your nano3G :(
~N
On Wed, Jul 25, 2018 at 05:08:35PM +0200, Ernesto Sanchez wrote:
Hi Neels, a lot of thanks, I think that is not a good idea work in an open proyect with proprietary hardware, and proprietary firmware... The result is: I don't own my hardware, I paid for hardware that I can not use, I can understand pay a fee for the "new" license but no more than this.
Sorry, but preaching Open Source to Osmocom is quite misplaced. Small companies across the world have made considerable investment in effort and money to get 3G support into the Open, and besides sysmocom offering the much more expensive SysmoCell5000 series, it's a major highlight that the much cheaper nano3G was also made to work with Osmocom, specifically to allow remotely affordable Open Source 3G hacking. Sysmocom also gave away quite a few of them for free during the Accelerate3G5 project. I see it as a major achievement to whip all of this up while being a (small) company that is still able to pay wages and taxes. So please, hold your horses there, seriously.
One key item that is not in Open Source yet is the RNC. If we then add an SDR implementation for a UMTS transceiver, we could do completely without proprietarily licensed hardware.
Open Source lives by contribution, so you are more than welcome to bring in your part and implement these (or fund someone to do so).
Feel free to browse http://sysmocom.de and/or enquire at sales@sysmocom.de about 3G hardware to go with Osmocom. I'm a developer, not familiar with the sales details. Or maybe you can persuade ip.access to hand out Free firmware?
~N