Hi, I have a nanobts config file:
! OpenBSC configuration saved from vty ! password foo ! line vty no login ! network network country code 1 mobile network code 1 short name SomeNet long name SomeNet timer t3101 10 timer t3113 60 auth policy closed
bts 0 type nanobts ip.access unit_id 0 0 band GSM1800 location_area_code 1 training_sequence_code 7 base_station_id_code 63 ms max power 40
trx 0 rf_locked 0 arfcn 514 timeslot 0 phys_chan_config CCCH+SDCCH4 timeslot 1 phys_chan_config SDCCH8 timeslot 2 phys_chan_config TCH/F timeslot 3 phys_chan_config TCH/F timeslot 4 phys_chan_config TCH/F timeslot 5 phys_chan_config TCH/F
bsc_hack reports:
DB: Database initialized. DB: Database prepared. <000d> input/ipaccess.c:535 accept()ed new OML link from 192.168.1.85 <0005> bsc_init.c:735 bootstrapping OML for BTS 0
The light on the nanoBTS flashes green but does not go solid green / or start transmitting a signal.
Any ideas?
Thanks, Stuart
On Friday 09 April 2010 20:26:05 Stuart Baggs wrote:
DB: Database initialized. DB: Database prepared. <000d> input/ipaccess.c:535 accept()ed new OML link from 192.168.1.85 <0005> bsc_init.c:735 bootstrapping OML for BTS 0
The light on the nanoBTS flashes green but does not go solid green / or start transmitting a signal.
Any ideas?
Yes,
you have a rugby sized BTS, you didn't check the mailing list archives prior to posting and you didn't include relevant information. :)
Please look at the mail from Nordin that was sent on Tuesday and see if you suffer from the same problem? The thread also contains the information we are looking for.
Hi, whoops missed that one! Yes its a rugby sized GSM/GPRS bts. Looked through the posts not sure what information has been requested but if you let me know I can give the group all the info.
Thanks
On 9 Apr 2010, at 19:30, Holger Freyther wrote:
On Friday 09 April 2010 20:26:05 Stuart Baggs wrote:
DB: Database initialized. DB: Database prepared. <000d> input/ipaccess.c:535 accept()ed new OML link from 192.168.1.85 <0005> bsc_init.c:735 bootstrapping OML for BTS 0
The light on the nanoBTS flashes green but does not go solid green / or start transmitting a signal.
Any ideas?
Yes,
you have a rugby sized BTS, you didn't check the mailing list archives prior to posting and you didn't include relevant information. :)
Please look at the mail from Nordin that was sent on Tuesday and see if you suffer from the same problem? The thread also contains the information we are looking for.
On Friday 09 April 2010 20:34:54 Stuart Baggs wrote:
Hi, whoops missed that one! Yes its a rugby sized GSM/GPRS bts. Looked through the posts not sure what information has been requested but if you let me know I can give the group all the info.
A recent commit, e.g. we speculate it might have been the merge of the first bits of the GPRS conf branch, broke support for the rugby sized nanoBTS. What we would need would be a pcap file of a working startup and one of a non- working startup. The other bit would be to use the power of git bisect to figure out the commit that actually broke it.
OK, I will do this for the group. Could you let me know how to downgrade my openBSC to a version which supports the rugby nanoBTS? Would I also need to downgrade libosmocore?
Thanks for your help.
On 9 Apr 2010, at 19:43, Holger Freyther wrote:
On Friday 09 April 2010 20:34:54 Stuart Baggs wrote:
Hi, whoops missed that one! Yes its a rugby sized GSM/GPRS bts. Looked through the posts not sure what information has been requested but if you let me know I can give the group all the info.
A recent commit, e.g. we speculate it might have been the merge of the first bits of the GPRS conf branch, broke support for the rugby sized nanoBTS. What we would need would be a pcap file of a working startup and one of a non- working startup. The other bit would be to use the power of git bisect to figure out the commit that actually broke it.
On Friday 09 April 2010 20:48:17 Stuart Baggs wrote:
OK, I will do this for the group. Could you let me know how to downgrade my openBSC to a version which supports the rugby nanoBTS? Would I also need to downgrade libosmocore?
Yes, you would need to downgrade libosmocore too. Well I think the best way would be to search for a small git tutorial. When I would have the time to track it down I would do..
$ git bisect start -- openbsc/ $ git bisect bad HEAD $ git bisect good 0.9.0
$ cd openbsc/; make (and if I have link errors or such I would downgrade libosmocore too... I would downgrade by checking out the releases).
That's weird because I was running the GPRS branch on a rugby sized nanoBTS. It initially didn't work because of the NM_ATT_IPACC_RLC_CFG_3 attribute but this one is now commented out.
Note that some nanoBTS require fixes that are only in my pending branch ... (but that's a pre-lisbosmocore branch, I haven't rebased it yet).
I don't have the setup ready to test right now, but I'll give it a shot tomorrow ...
Sylvain
On Friday 09 April 2010 22:53:44 Sylvain Munaut wrote:
That's weird because I was running the GPRS branch on a rugby sized nanoBTS. It initially didn't work because of the NM_ATT_IPACC_RLC_CFG_3 attribute but this one is now commented out.
Note that some nanoBTS require fixes that are only in my pending branch ... (but that's a pre-lisbosmocore branch, I haven't rebased it yet).
Do you need some help to merge patches of your branch?
That's weird because I was running the GPRS branch on a rugby sized nanoBTS. It initially didn't work because of the NM_ATT_IPACC_RLC_CFG_3 attribute but this one is now commented out.
Note that some nanoBTS require fixes that are only in my pending branch ... (but that's a pre-lisbosmocore branch, I haven't rebased it yet).
Do you need some help to merge patches of your branch?
They rebased automatically quite fine. I didn't push the rebased version yet because I didn't get a chance to test it yet.
I think Harald wanted to see if they didn't affect proper operation on the EDGE units and BS-11. Since I don't have any of those, I can't test myself.
Sylvain
Still wont get past the green flashing light on 0.9.0 :s
On 9 Apr 2010, at 22:16, Sylvain Munaut wrote:
That's weird because I was running the GPRS branch on a rugby sized nanoBTS. It initially didn't work because of the NM_ATT_IPACC_RLC_CFG_3 attribute but this one is now commented out.
Note that some nanoBTS require fixes that are only in my pending branch ... (but that's a pre-lisbosmocore branch, I haven't rebased it yet).
Do you need some help to merge patches of your branch?
They rebased automatically quite fine. I didn't push the rebased version yet because I didn't get a chance to test it yet.
I think Harald wanted to see if they didn't affect proper operation on the EDGE units and BS-11. Since I don't have any of those, I can't test myself.
Sylvain
On Sat, Apr 10, 2010 at 02:59:57AM +0100, Stuart Baggs wrote:
Still wont get past the green flashing light on 0.9.0 :s
please create a pcap file of the full BTS boot with tcpdump or wireshark, also please post a debug log file of openbsc (start bsc_hack with -d DINP:DNM:DRSL,0:0:0)
Hi guys, ok first things first. Here if the debug log of openbsc startup:
root@gateway:~/openbsc/openbsc/src# ./bsc_hack -d DINP:DNM:DRSL,0:0:0 DB: Database initialized. DB: Database prepared. <000d> input/ipaccess.c:535 accept()ed new OML link from 192.168.1.85 <000d> input/ipaccess.c:235 Identified BTS 0/0/0 <0005> bsc_init.c:735 bootstrapping OML for BTS 0 <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=GPRS NSE(f0) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=GPRS CELL(f1) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,01,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) Sending OPSTART <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) Software Activated Report <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=GPRS NSE(f0) INST=(00,ff,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1753 Set BTS Attr (bts=0) <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) Sending OPSTART <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) Software Activated Report <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 31 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 31 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=GPRS NSE(f0) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:519 OC=GPRS NSE(f0) INST=(00,ff,ff) Software Activated Report <0005> abis_nm.c:519 OC=GPRS CELL(f1) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,01,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:519 OC=GPRS CELL(f1) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,01,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:519 OC=GPRS CELL(f1) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,01,ff) Software Activated Report <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) Sending OPSTART <0005> abis_nm.c:2824 ip.access RSL CONNECT IP=0.0.0.0 PORT=3003 STREAM=0x00 <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=0) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=1) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=2) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=3) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=4) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=5) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=6) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=7) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) Sending OPSTART <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) IPACCESS(0xe1): RSL CONNECT ACK IP=192.168.1.50 PORT=3003 STREAM=0x00 <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) Software Activated Report <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:1770 Set TRX Attr (bts=0,trx=0) <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) Sending OPSTART <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=OK(ff) ADM=Unlocked <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) Sending OPSTART
On 10 Apr 2010, at 10:51, Harald Welte wrote:
On Sat, Apr 10, 2010 at 02:59:57AM +0100, Stuart Baggs wrote:
Still wont get past the green flashing light on 0.9.0 :s
please create a pcap file of the full BTS boot with tcpdump or wireshark, also please post a debug log file of openbsc (start bsc_hack with -d DINP:DNM:DRSL,0:0:0)
--
- Harald Welte laforge@gnumonks.org http://laforge.gnumonks.org/
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
root@gateway:~/openbsc/openbsc/src# tcpdump port 3002 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:11:21.797321 IP 192.168.1.85.52667 > 192.168.1.50.3002: Flags [S], seq 409659731, win 16000, options [mss 1460], length 0 11:11:21.797361 IP 192.168.1.50.3002 > 192.168.1.85.52667: Flags [R.], seq 0, ack 409659732, win 0, length 0 11:11:41.779406 IP 192.168.1.85.56146 > 192.168.1.50.3002: Flags [S], seq 2599547005, win 16000, options [mss 1460], length 0 11:11:41.779451 IP 192.168.1.50.3002 > 192.168.1.85.56146: Flags [R.], seq 0, ack 2599547006, win 0, length 0 11:11:58.442678 IP 192.168.1.85.7245 > 192.168.1.50.3002: Flags [S], seq 2917588595, win 16000, options [mss 1460], length 0 11:11:58.442699 IP 192.168.1.50.3002 > 192.168.1.85.7245: Flags [R.], seq 0, ack 2917588596, win 0, length 0 11:12:22.500586 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [S], seq 1562623206, win 16000, options [mss 1460], length 0 11:12:22.500633 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [S.], seq 2967578324, ack 1562623207, win 5840, options [mss 1460], length 0 11:12:22.501011 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], ack 1, win 16000, length 0 11:12:22.501352 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1:21, ack 1, win 5840, length 20 11:12:22.502339 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 1:5, ack 21, win 15980, length 4 11:12:22.502360 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 5, win 5840, length 0 11:12:22.502441 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 21:25, ack 5, win 5840, length 4 11:12:22.504934 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 5:131, ack 25, win 15996, length 126 11:12:22.543240 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 131, win 5840, length 0 11:12:22.543776 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [P.], seq 131:449, ack 25, win 16000, length 318 11:12:22.543786 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 449, win 6432, length 0 11:12:24.509645 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 449:598, ack 25, win 16000, length 149 11:12:24.509669 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 598, win 7504, length 0 11:12:24.509937 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 25:174, ack 598, win 7504, length 149 11:12:24.701164 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], ack 174, win 16000, length 0 11:12:24.701173 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 174:194, ack 598, win 7504, length 20 11:12:24.708748 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 598:610, ack 194, win 16000, length 12 11:12:24.747239 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 610, win 7504, length 0 11:12:24.747864 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [P.], seq 610:941, ack 194, win 16000, length 331 11:12:24.747873 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 941, win 8576, length 0 11:12:24.747964 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 194:206, ack 941, win 8576, length 12 11:12:24.752873 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 941:953, ack 206, win 16000, length 12 11:12:24.752881 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 206:544, ack 953, win 8576, length 338 11:12:24.771674 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 953:965, ack 544, win 16000, length 12 11:12:24.811238 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 965, win 8576, length 0 11:12:24.811952 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [P.], seq 965:1840, ack 544, win 16000, length 875 11:12:24.811961 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 1840, win 10500, length 0 11:12:24.812034 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 544:612, ack 1840, win 10500, length 68 11:12:24.819174 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 1840:1911, ack 612, win 16000, length 71 11:12:24.819184 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 612:1533, ack 1911, win 10500, length 921 11:12:24.888002 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 1911:1925, ack 1533, win 16000, length 14 11:12:24.927238 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 1925, win 10500, length 0 11:12:24.927849 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [P.], seq 1925:2119, ack 1533, win 16000, length 194 11:12:24.927857 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2119, win 12250, length 0 11:12:24.954213 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2119:2137, ack 1533, win 16000, length 18 11:12:24.954260 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2137, win 12250, length 0 11:12:24.955859 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2137:2153, ack 1533, win 16000, length 16 11:12:24.955907 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2153, win 12250, length 0 11:12:24.955948 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1533:1547, ack 2153, win 12250, length 14 11:12:24.958282 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2153:2171, ack 1547, win 16000, length 18 11:12:24.958292 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1547:1590, ack 2171, win 12250, length 43 11:12:24.961987 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2171:2189, ack 1590, win 16000, length 18 11:12:24.961996 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1590:1632, ack 2189, win 12250, length 42 11:12:24.966291 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2189:2207, ack 1632, win 16000, length 18 11:12:24.966301 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1632:1674, ack 2207, win 12250, length 42 11:12:24.970734 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2207:2225, ack 1674, win 16000, length 18 11:12:24.970743 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1674:1716, ack 2225, win 12250, length 42 11:12:24.975263 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2225:2243, ack 1716, win 16000, length 18 11:12:24.975275 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1716:1758, ack 2243, win 12250, length 42 11:12:24.979554 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2243:2261, ack 1758, win 16000, length 18 11:12:24.979564 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1758:1800, ack 2261, win 12250, length 42 11:12:24.983848 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2261:2279, ack 1800, win 16000, length 18 11:12:24.983858 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1800:1842, ack 2279, win 12250, length 42 11:12:24.987368 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2279:2297, ack 1842, win 16000, length 18 11:12:24.987378 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1842:1884, ack 2297, win 12250, length 42 11:12:25.021388 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2297:2311, ack 1884, win 16000, length 14 11:12:25.021398 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1884:1926, ack 2311, win 12250, length 42 11:12:25.025685 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2311:2331, ack 1926, win 16000, length 20 11:12:25.063239 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2331, win 12250, length 0 11:12:25.063852 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [P.], seq 2331:2811, ack 1926, win 16000, length 480 11:12:25.063861 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2811, win 14000, length 0 11:12:25.064378 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2811:2827, ack 1926, win 16000, length 16 11:12:25.064418 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2827, win 14000, length 0 11:12:25.067884 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2827:2843, ack 1926, win 16000, length 16 11:12:25.067931 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2843, win 14000, length 0 11:12:25.071663 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2843:2859, ack 1926, win 16000, length 16 11:12:25.071711 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2859, win 14000, length 0 11:12:25.074964 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2859:2875, ack 1926, win 16000, length 16 11:12:25.075005 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2875, win 14000, length 0 11:12:25.088318 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2875:2893, ack 1926, win 16000, length 18 11:12:25.088366 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2893, win 14000, length 0 11:12:25.089840 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2893:2909, ack 1926, win 16000, length 16 11:12:25.089881 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2909, win 14000, length 0 11:12:25.089917 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1926:1945, ack 2909, win 14000, length 19 11:12:25.129885 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2909:2928, ack 1945, win 16000, length 19 11:12:25.129895 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1945:1971, ack 2928, win 14000, length 26 11:12:25.150016 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2928:2942, ack 1971, win 16000, length 14 11:12:25.187238 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2942, win 14000, length 0 11:12:25.187693 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [P.], seq 2942:2973, ack 1971, win 16000, length 31 11:12:25.187737 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2973, win 14000, length 0 11:12:25.187756 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1971:1983, ack 2973, win 14000, length 12 11:12:25.190336 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2973:2985, ack 1983, win 16000, length 12 11:12:25.227238 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2985, win 14000, length 0 11:12:45.196404 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], seq 2985:2989, ack 1983, win 16000, length 4 11:12:45.196458 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [.], ack 2989, win 14000, length 0 11:12:45.196624 IP 192.168.1.50.3002 > 192.168.1.85.3661: Flags [P.], seq 1983:1987, ack 2989, win 14000, length 4 11:12:45.395830 IP 192.168.1.85.3661 > 192.168.1.50.3002: Flags [.], ack 1987, win 16000, length 0
On 10 Apr 2010, at 11:09, Stuart Baggs wrote:
Hi guys, ok first things first. Here if the debug log of openbsc startup:
root@gateway:~/openbsc/openbsc/src# ./bsc_hack -d DINP:DNM:DRSL,0:0:0 DB: Database initialized. DB: Database prepared. <000d> input/ipaccess.c:535 accept()ed new OML link from 192.168.1.85 <000d> input/ipaccess.c:235 Identified BTS 0/0/0 <0005> bsc_init.c:735 bootstrapping OML for BTS 0 <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=GPRS NSE(f0) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=GPRS CELL(f1) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,01,ff) STATE CHG: OP_STATE=Disabled AVAIL=Not installed(07) ADM=Locked <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) STATE CHG: OP_STATE=Enabled AVAIL=OK(ff) <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) Sending OPSTART <0005> abis_nm.c:519 OC=SITE MANAGER(00) INST=(ff,ff,ff) Software Activated Report <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=GPRS NSE(f0) INST=(00,ff,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1753 Set BTS Attr (bts=0) <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) Sending OPSTART <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) Software Activated Report <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 31 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 31 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=GPRS NSE(f0) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:519 OC=GPRS NSE(f0) INST=(00,ff,ff) Software Activated Report <0005> abis_nm.c:519 OC=GPRS CELL(f1) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,00,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,01,ff) SW Activate Request: <0005> abis_nm.c:839 Software Activate Request, ACKing and Activating <0005> abis_nm.c:854 Found SW config: 42 12 00 08 31 32 30 61 30 30 32 00 13 00 0a 76 32 30 39 62 32 34 64 30 00 <0005> abis_nm.c:519 OC=BTS(01) INST=(00,ff,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:519 OC=GPRS CELL(f1) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,01,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:519 OC=GPRS CELL(f1) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:519 OC=GPRS NSVC(f2) INST=(00,01,ff) Software Activated Report <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) Sending OPSTART <0005> abis_nm.c:2824 ip.access RSL CONNECT IP=0.0.0.0 PORT=3003 STREAM=0x00 <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=0) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=1) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=2) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=3) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=4) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=5) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=6) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) Sending OPSTART <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1928 Set Chan Attr (bts=0,trx=0,ts=7) <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) Sending OPSTART <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:519 OC=BASEBAND TRANSCEIVER(04) INST=(00,00,ff) IPACCESS(0xe1): RSL CONNECT ACK IP=192.168.1.50 PORT=3003 STREAM=0x00 <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) SET CHANNEL ATTRIBUTE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,00) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,01) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,02) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,03) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,04) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,05) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,06) Software Activated Report <0005> abis_nm.c:519 OC=CHANNEL(03) INST=(00,00,07) Software Activated Report <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Off line(03) <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) Software Activated Report <0005> abis_nm.c:1770 Set TRX Attr (bts=0,trx=0) <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) Sending OPSTART <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=OK(ff) ADM=Unlocked <0005> abis_nm.c:519 OC=RADIO CARRIER(02) INST=(00,00,ff) Sending OPSTART
On 10 Apr 2010, at 10:51, Harald Welte wrote:
On Sat, Apr 10, 2010 at 02:59:57AM +0100, Stuart Baggs wrote:
Still wont get past the green flashing light on 0.9.0 :s
please create a pcap file of the full BTS boot with tcpdump or wireshark, also please post a debug log file of openbsc (start bsc_hack with -d DINP:DNM:DRSL,0:0:0)
--
- Harald Welte laforge@gnumonks.org http://laforge.gnumonks.org/
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
I can reproduce your problem on a GSM900 nanoBTS, but I don't really have any idea why that happens.
Using ipaccess-telnet and using moi::states to look at the debug console of the nanoBTS, I can see:
----- MOI States ----- [ Site] (Null:255), Enabled, [ BTS:0] (Unlocked), Disabled, <Dependency> [ BBTRX:0-0] (Unlocked), Disabled, <Dependency>> [ Channel:0-0-0] (Locked), Disabled, <Dependency>> [ Channel:0-0-1] (Locked), Disabled, <Dependency>> [ Channel:0-0-2] (Locked), Disabled, <Dependency>> [ Channel:0-0-3] (Locked), Disabled, <Dependency>> [ Channel:0-0-4] (Locked), Disabled, <Dependency>> [ Channel:0-0-5] (Locked), Disabled, <Dependency>> [ Channel:0-0-6] (Locked), Disabled, <Dependency>> [ Channel:0-0-7] (Locked), Disabled, <Dependency>> [ Carrier:0-0] (Unlocked), Disabled, > [ GPRS NSE:0] (Locked), Disabled, <Dependency> [ GPRS Cell:0-0] (Unlocked), Disabled, <Dependency>> [ GPRS NSVC:0-0] (Locked), Disabled, > [ GPRS NSVC:0-1] (Locked), Disabled, >
The problem is the radio carrier. It is Disabled, without having any dependency on other objects. Sending OPSTART even twice does not change its state.
If the Radio Carrier would get into Enabled state, the Channels would all get rid of their Dependency problem.
I would like to know how to downgrade my openbsc to get this BTS online (just for testing). I tried to use the git commands from Holger, but no luck so far.
$ git bisect start -- openbsc/ $ git bisect bad HEAD $ git bisect good 0.9.0
$ cd openbsc/; make (and if I have link errors or such I would downgrade libosmocore too... I would downgrade by checking out the releases).
Is there anyway I can get this BTS setup and working in the short term?
Thanks, Stuart
On 10 Apr 2010, at 11:49, Harald Welte wrote:
I can reproduce your problem on a GSM900 nanoBTS, but I don't really have any idea why that happens.
Using ipaccess-telnet and using moi::states to look at the debug console of the nanoBTS, I can see:
----- MOI States ----- [ Site] (Null:255), Enabled, [ BTS:0] (Unlocked), Disabled, <Dependency> [ BBTRX:0-0] (Unlocked), Disabled, <Dependency>> [ Channel:0-0-0] (Locked), Disabled, <Dependency>> [ Channel:0-0-1] (Locked), Disabled, <Dependency>> [ Channel:0-0-2] (Locked), Disabled, <Dependency>> [ Channel:0-0-3] (Locked), Disabled, <Dependency>> [ Channel:0-0-4] (Locked), Disabled, <Dependency>> [ Channel:0-0-5] (Locked), Disabled, <Dependency>> [ Channel:0-0-6] (Locked), Disabled, <Dependency>> [ Channel:0-0-7] (Locked), Disabled, <Dependency>> [ Carrier:0-0] (Unlocked), Disabled, > [ GPRS NSE:0] (Locked), Disabled, <Dependency> [ GPRS Cell:0-0] (Unlocked), Disabled, <Dependency>> [ GPRS NSVC:0-0] (Locked), Disabled, > [ GPRS NSVC:0-1] (Locked), Disabled, >
The problem is the radio carrier. It is Disabled, without having any dependency on other objects. Sending OPSTART even twice does not change its state.
If the Radio Carrier would get into Enabled state, the Channels would all get rid of their Dependency problem.
--
- Harald Welte laforge@gnumonks.org http://laforge.gnumonks.org/
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
On Saturday 10 April 2010 13:02:17 Stuart Baggs wrote:
I would like to know how to downgrade my openbsc to get this BTS online (just for testing). I tried to use the git commands from Holger, but no luck so far.
$ git bisect start -- openbsc/ $ git bisect bad HEAD $ git bisect good 0.9.0
$ cd openbsc/; make (and if I have link errors or such I would downgrade libosmocore too... I would downgrade by checking out the releases).
Is there anyway I can get this BTS setup and working in the short term?
Well, I'm a bit confused. You mentioned that 0.9.0 is not working and now you mention you don't know how to checkout a given version of git? The original message I wrote had two parts:
1.) Consult a git tutorial of your choice 2.) If you want to debug this, use git bisect (you copied this bit).
Let us assume you want to reset your current branch to an older version you can use the git reset (man git-reset) utility.
$ git reset --hard TAG|HASH
TAG can be a tag, e.g. 0.9.0 HASH can be a sha1 hash of a git commit..
but the above is no replacement for consulting a git tutorial, and of course if you got back to an older release you might need to install an older version of libosmocore as well.
Ok I entered git reset --hard 0.9.0 but when I issue a fresh "git pull" I get this error:
root@gateway:~/openbsc# git pull You are not currently on a branch, so I cannot use any 'branch.<branchname>.merge' in your configuration file. Please specify which branch you want to merge on the command line and try again (e.g. 'git pull <repository> <refspec>'). See git-pull(1) for details.
Is there a tar.gz file of the 0.9.0 version of openbts? I am really keen to get involved in the project but I simply cannot understand how GIT works and no mattter how many tutorials I read it is still clear as mud.
I really would appreciate some instructions on how to get a fresh version of OpenBSC to work with my rugby sized nanoBTS.
Thanks for your help.
On 10 Apr 2010, at 12:26, Holger Freyther wrote:
git reset --hard
On Saturday 10 April 2010 13:34:39 Stuart Baggs wrote:
Ok I entered git reset --hard 0.9.0 but when I issue a fresh "git pull" I get this error:
root@gateway:~/openbsc# git pull You are not currently on a branch, so I cannot use any 'branch.<branchname>.merge' in your configuration file. Please specify which branch you want to merge on the command line and try again (e.g. 'git pull <repository> <refspec>'). See git-pull(1) for details.
Is there a tar.gz file of the 0.9.0 version of openbts? I am really keen to get involved in the project but I simply cannot understand how GIT works and no mattter how many tutorials I read it is still clear as mud.
Hi Stuart,
git can be hard to understand at first but with a basic cheat sheet and just using a handful commands you should be just fine.
What most likely happened for you is you typed some of the bisect commands I wrote without actually knowing what they will do and what you will have to do. What git bisect does is it go away from your default branch to a unnamed temporary branch to jump in the history...
Now when you type "git pull" it is first fetching objects from the default remote (origin) and then tries to merge with the remote branch that you are tracking... The problem is you are currently not on a branch (as the command tells you) and so it refuses to merge.
All you want to type is "git bisect reset" to go back to before you started the bisect. which brings you back to the master branch..
Thank you for all your help. I have managed to get OML sync now from a nanoBTS and the network is up. The problem now is that even though I have added my IMSI to the sqlite3 DB, it still give an auth REJECT.
Not sure what database name openBSC used by default (or if sqlite even supports multiple databases). Does anyone know how I can get ths to auth based on the entries I have put into sqlite.
Thanks, Stuart
On 10 Apr 2010, at 14:09, Holger Freyther wrote:
On Saturday 10 April 2010 13:34:39 Stuart Baggs wrote:
Ok I entered git reset --hard 0.9.0 but when I issue a fresh "git pull" I get this error:
root@gateway:~/openbsc# git pull You are not currently on a branch, so I cannot use any 'branch.<branchname>.merge' in your configuration file. Please specify which branch you want to merge on the command line and try again (e.g. 'git pull <repository> <refspec>'). See git-pull(1) for details.
Is there a tar.gz file of the 0.9.0 version of openbts? I am really keen to get involved in the project but I simply cannot understand how GIT works and no mattter how many tutorials I read it is still clear as mud.
Hi Stuart,
git can be hard to understand at first but with a basic cheat sheet and just using a handful commands you should be just fine.
What most likely happened for you is you typed some of the bisect commands I wrote without actually knowing what they will do and what you will have to do. What git bisect does is it go away from your default branch to a unnamed temporary branch to jump in the history...
Now when you type "git pull" it is first fetching objects from the default remote (origin) and then tries to merge with the remote branch that you are tracking... The problem is you are currently not on a branch (as the command tells you) and so it refuses to merge.
All you want to type is "git bisect reset" to go back to before you started the bisect. which brings you back to the master branch..
Hi guys, is there a list somwhere which matches versions of openbsc with the required version of libosmocore?
Thanks, Stuart
On 10 Apr 2010, at 12:26, Holger Freyther wrote:
On Saturday 10 April 2010 13:02:17 Stuart Baggs wrote:
I would like to know how to downgrade my openbsc to get this BTS online (just for testing). I tried to use the git commands from Holger, but no luck so far.
$ git bisect start -- openbsc/ $ git bisect bad HEAD $ git bisect good 0.9.0
$ cd openbsc/; make (and if I have link errors or such I would downgrade libosmocore too... I would downgrade by checking out the releases).
Is there anyway I can get this BTS setup and working in the short term?
Well, I'm a bit confused. You mentioned that 0.9.0 is not working and now you mention you don't know how to checkout a given version of git? The original message I wrote had two parts:
1.) Consult a git tutorial of your choice 2.) If you want to debug this, use git bisect (you copied this bit).
Let us assume you want to reset your current branch to an older version you can use the git reset (man git-reset) utility.
$ git reset --hard TAG|HASH
TAG can be a tag, e.g. 0.9.0 HASH can be a sha1 hash of a git commit..
but the above is no replacement for consulting a git tutorial, and of course if you got back to an older release you might need to install an older version of libosmocore as well.
Reverting commit f5284ae1cf8babc1567b33f469e20a66a73fcd9e
--- ipa: Reduce the throttling of the IPA msges
This code used to be a sleep, it was changed to be a timer by Andreas but this timer does not seem to have any use. When doing the sw load this timer is increasing the upload time dramatically, reduce it to make it work faster. ---
fixes the problem for me.
Sylvain
On Saturday 10 April 2010 23:47:05 Sylvain Munaut wrote:
Reverting commit f5284ae1cf8babc1567b33f469e20a66a73fcd9e
Okay, feel free to push it to the repository. I will make it configurable as I want to have a way lower timeout for the software load.
I was hoping someone would know _why_ this has _any_ impact at all ...
Some timing problem. In older versions we used a usleep, then Andreas switched it to a timer and then I reduced the timeout to have a faster firmware loading... we can probably only speculate why we need to wait a bit more... or maybe we are hiding a bug in our bootstrap where we would need to wait for an ack before we can continue..
Hi Sylvain,
thanks for debugging this.
On Sat, Apr 10, 2010 at 11:24:11PM +0200, Sylvain Munaut wrote:
Reverting commit f5284ae1cf8babc1567b33f469e20a66a73fcd9e
ipa: Reduce the throttling of the IPA msges This code used to be a sleep, it was changed to be a timer by Andreas but this timer does not seem to have any use. When doing the sw load this timer is increasing the upload time dramatically, reduce it to make it work faster.
fixes the problem for me.
That makes complete sense. In fact, the reason why that throttling was in place ('does not seem to have any use') was exactly to make the initialization work at all. Initially I was working with a GSM900 unit, and the initialization never worked without those sleeps.
This probably means that we're still doing something wrong with regard to the object state transitions. I never really understood why 12.21 has to be so horribly complex with all those objects and their dependencies, as well as administrative, operational and a third stage. It sounds like a stupid exercise in object oriented data model serving nothing but the purpose of advertising the perceived marvels of object orientation :(
I for my part think reverting the patch is the way to go, until somebody has debugged this issue. Is that ok with you, zecke?
Regards, Harald
On Sunday 11 April 2010 07:43:26 Harald Welte wrote:
I for my part think reverting the patch is the way to go, until somebody has debugged this issue. Is that ok with you, zecke?
Yeah, I already mentioned that I'm perfectly fine with that. I have a GSM900 nanoBTS at home and I will figure out what is going on on this one and will attempt to land such a patch again without breaking the GSM900 this time.
holger
I am also getting problems with SMS buffering until the handset restarts or the bsc_hack program restarts. No segmentation faults though. I am running 0.9.0 with DSC1800 nanoBTS GPRS (Rugby Ball).
sms are distributed only on location updates or when forced in the telnet CLI.
On Sun, Apr 11, 2010 at 1:04 PM, Stuart Baggs stuart@bluewave.im wrote:
I am also getting problems with SMS buffering until the handset restarts or the bsc_hack program restarts. No segmentation faults though. I am running 0.9.0 with DSC1800 nanoBTS GPRS (Rugby Ball).
Sylvain Munaut schrieb:
That's weird because I was running the GPRS branch on a rugby sized nanoBTS. It initially didn't work because of the NM_ATT_IPACC_RLC_CFG_3 attribute but this one is now commented out.
Note that some nanoBTS require fixes that are only in my pending branch ... (but that's a pre-lisbosmocore branch, I haven't rebased it yet).
Do you need some help to merge patches of your branch?
They rebased automatically quite fine. I didn't push the rebased version yet because I didn't get a chance to test it yet.
I think Harald wanted to see if they didn't affect proper operation on the EDGE units and BS-11. Since I don't have any of those, I can't test myself.
I now can confirm that the sylvain/pending branch works with the following BTS:
nanoBTS 139 (DCS1800 rugby sized) nanoBTS 165AU (DCS1800 EDGE version) BS11
Sylvain
On Tuesday 13 April 2010 12:46:51 Konrad Meier wrote:
I now can confirm that the sylvain/pending branch works with the following BTS:
nanoBTS 139 (DCS1800 rugby sized) nanoBTS 165AU (DCS1800 EDGE version) BS11
I can add a DCS900 nanoBTS EDGE to the mix. I think Sylvain should land his branch.
Sylvain
-
Harald Welte -
Holger Freyther -
Konrad Meier -
Stuart Baggs -
Sylvain Munaut