Sorry, it's the next morning. Actually, I was bragging. What I have is
more of a debugging output. If I'm not watching when it happens, it's
gone (buried). But I'd be glad to watch when you get home, if we set it
up in
advance.
Here's what I get from a wide scan in my office. Notice that
"Time Warner Cable" is listed first as ID 51. That's us, GENI.
Seems to be wrong in the database. Is that WiMAX_DB.bin?
If I edit WiMAX_DB.bin, how do I make it take effect?
Notice that ID51 has a different RSSI from the other 3. I think
that Clear, Sprint and Comcast are all carried on the same signal,
while we - GENI - are a separate BS and signal altogether.
The wimax interface on node1-110 (below) is an Intel 6250 Centrino,
which I think uses the same driver as you have for the 5150.
Tony
native at node1-110:~$ wimaxcu dconnect
Network Disconnected.
native at node1-110:~$ wimaxcu scan wide
WARNING: Wide scan may take upto 2 minutes...
NSP : Time Warner Cable 4G
ID : 51
Signal : Very Good
RSSI : -60 dBm
CINR : 24 dB
Network Type: Home Network
Activated.
NSP : CLEAR
ID : 2
Signal : Very Good
RSSI : -59 dBm
CINR : 25 dB
Network Type: Home Network
Activated.
NSP : SPRINT
ID : 47
Signal : Very Good
RSSI : -59 dBm
CINR : 25 dB
Network Type: Home Network
Activated.
NSP : Comcast
ID : 48
Signal : Very Good
RSSI : -59 dBm
CINR : 25 dB
Network Type: Home Network
Activated.
native at node1-110:~$
On 1/17/2011 8:46 PM, Ward, David - 0663 - MITLL wrote:
> Tony --
>
> I've been trying to get this working at home ... which is Porter
> Square in Cambridge ;-) Want to see if anything showed up in your
> logs about 20 minutes ago?
>
> I did a manual scan to see if I could find GENI, but wimaxcu is only
> showing me the commercial networks (CLEAR, Time Warner, Comcast,
> Sprint). In any case I've only ever tried telling it to connect to
> network 2 (CLEAR). But who knows...
>
> What WiMAX adapter are you trying to use to connect to GENI?
>
> Does anyone living in the Boston area have an Intel WiMAX/WiFi Link
> 5150 working under Linux? If so ... we should chat. :)
>
> David
>
>
> On 01/17/2011 06:11 PM, Tony Michel wrote:
>> Well, this is probably a long shot. I'm in Boston, too, at FreshPond
>> in Cambridge. I'm working on the GENI WiMAX network (see
>> http://www.geni.net/) and trying to get a pretty recent build of
>> WiMAX up on the net. We have the advantage that we have a base
>> station and I can watch the logs as I try to connect. I can even dig
>> in a little bit but we do not have source code for the BS and in any
>> case I don't want to "void the warranty." I remember David Ward's
>> last cry for help on this list. It happened at about the time that I
>> was seeing a rogue station trying to access GENI. We control access
>> by accepting only certain MAC addresses and I didn't grant access to
>> the rogue. It seems unlikely that If David was attempting to access
>> us at FreshPond, from a site at Lincoln Labs, that we would hear him,
>> but, who knows? If you want to schedule a time when I should watch
>> the logs, send me some email at axm at bbn.com. Maybe you're the rogue!
>>
>> But, why I'm really writing is that with my Dell Inspiron 1012,
>> loaded with Ubuntu 10.10 and the current WiMAX Tools and WiMAX
>> service daemon shows symptoms similar to David's. I can find the
>> base signal with wimaxcu scan but I don't see any sign of my mobile
>> signal in BS logs. How should I start tracking this? It seems like
>> a config problem...as if I'm not sending on the right frequency
>> (which happens to be 2590MHz - well away from the local ClearWire
>> signals). We have a legitimate FCC experimental license.
>>
>> I also have a Sprint EVO 4G (rooted and jimmied) and a Beceem USB
>> dongle. Both the EVO and Beceem connect and work just fine.
>>
>> Tony
>>
>>
>> On 01/16/2011 10:31 PM, Ward, David - 0663 - MITLL wrote:
>>> Hi Inaky,
>>>
>>> I tried responding to this a long time ago, but it seems that my
>>> message was too large with the logs and it never made it to the
>>> mailing list. I'm sending it again, but this time I've gzipped the
>>> logs and attached them. I was out of town a lot recently with the
>>> holidays, but I really would like to get this working and appreciate
>>> any time you can spare to help me with this.
>>>
>>> >So the tip of the source in git has a few patches (attached) which I'd
>>> >would like to ask you to try. They are probably not the cure, but I
>>> want
>>> >to rule out that was the issue.
>>>
>>> I updated wimax-network-service to the latest version from git,
>>> which included your patches. However the connection still failed;
>>> see the console output inlined below, and the attached logs. Which
>>> Linux distribution you were able to get the 5150 working under?
>>>
>>> >When I had this applied, I was able to connect here in Portland
>>> with my
>>> >5150. I need to run another test in the other test machine I have
>>> where
>>> >the 5150 is fully connected (both the USB and PCI devices) to see if
>>> >there are any changes in that, but I don't know if I'll be able to get
>>> >that machine before Thanksgiving.
>>>
>>> I suspect that my system is fully connected, since both the i2400m
>>> and i2400m_usb modules are being loaded. Can you test this on a
>>> fully connected machine if you haven't already?
>>>
>>> Thanks again!
>>>
>>> David
>>>
>>>
>>>
>>> ----- console -----
>>>
>>> $ sudo wimaxd -i wmx0 # issued at 16:03:00
>>>
>>> $ wimaxcu ron # issued at 16:04:00
>>> SW Radio is turned ON.
>>>
>>> $ wimaxcu scan # issued at 16:05:00
>>> Network found.
>>> NSP : Time Warner Cable 4G
>>> ID : 51
>>> Signal : Excellent
>>> RSSI : -46 dBm
>>> CINR : 32 dB
>>> Network Type: Home Network
>>> Activated
>>>
>>> Network found.
>>> NSP : Comcast
>>> ID : 48
>>> Signal : Excellent
>>> RSSI : -46 dBm
>>> CINR : 32 dB
>>> Network Type: Home Network
>>> Activated
>>>
>>> Network found.
>>> NSP : SPRINT
>>> ID : 47
>>> Signal : Excellent
>>> RSSI : -46 dBm
>>> CINR : 32 dB
>>> Network Type: Home Network
>>> Activated
>>>
>>> Network found.
>>> NSP : CLEAR
>>> ID : 2
>>> Signal : Excellent
>>> RSSI : -46 dBm
>>> CINR : 32 dB
>>> Network Type: Home Network
>>> Activated
>>>
>>> $ wimaxcu connect network 2 # issued at 16:06:00
>>> Connecting to CLEAR Network...
>>> Connection Fail: time out
>>>
>>
>>
>
>
