Hi Michael,
Am Mo, 23.03.2009, 13:38, schrieb Michael Gernoth:
On Mon, Mar 23, 2009 at 09:13:00AM +0100, Holger Adams
wrote:
Output of 'bsc_hack'
<1000> input/misdn.c:123 alen =6, dev(0) channel(3) sapi(0) tei(1)
<1000> input/misdn.c:126 <= len = 15, prim(0x3008) id(0x30100):
DL_DATA_IND
<1000> input/misdn.c:151 RX: 0c 12 01 90 0f 00 3c
<1000> input/misdn.c:123 alen =6, dev(0) channel(3) sapi(0) tei(1)
<1000> input/misdn.c:126 <= len = 20, prim(0x3008) id(0x30100):
DL_DATA_IND
<1000> input/misdn.c:151 RX: 0c 12 01 88 12 06 00 fa 00 00 00 00
<1000> input/misdn.c:123 alen =6, dev(0) channel(3) sapi(0) tei(1)
<1000> input/misdn.c:126 <= len = 15, prim(0x3008) id(0x30100):
DL_DATA_IND
<1000> input/misdn.c:151 RX: 0c 12 01 90 0f 00 3c
(...)
Question to Michael Gernoth:
Is this the situation you had with your "new" PC?
Yes, this is the ouput I'm getting on the working PC. Can you see the
network when you let bsc_hack run for two minutes and then restart it?
That's how it is working for me.
Yes, I can see the network now (as you said, I had to wait a few minutes)
Do you also get scary mISDN-errors in the dmesg
output?
Nope, no mISDN errors in my dmesg (but a lot of
"ph_data_indication"-messages).
Best Regards,
Holger