> Date: Tue, 17 Jan 2012 15:27:35 -0500
> From: wimax at topquark.net
> To: dcbw at redhat.com
> CC: tass2001 at hotmail.com; wimax at linuxwimax.org
> Subject: Re: Idle Mode Timer?
>
> On Mon, Jan 16, 2012 at 07:41:53PM -0500, Paul Donohue wrote:
> > On Mon, Jan 16, 2012 at 04:03:00PM -0600, Dan Williams wrote:
> > > Note that if you don't remove the "welcome." part you may never get past
> > > the VLAN landing page too; you'll be in a loop where it always says "we
> > > have an important message for you" and you can't ever get to the actual
> > > internet.
> > I have been having problems for quite some time where if I establish my wimax connection in an area with very weak signal or while I'm moving in a car or train, I often get stuck in the "We have an important message for you" loop, but can get out of it by turning my radio off and back on a few times (I don't have this problem if I turn the radio on in an area with strong signal - I'm guessing some handshake or authentication packet getting lost or delayed triggers this?) ... I'll have to do some testing to see if that is still the case now that I've changed realms...
>
> Just got that message again while connecting with weak signal even with the other realm ... guess that didn't help:
>
> $ wimaxcu status connect
> Connected.
> Network Info:
> ID : 2
> Name : CLEAR
> Realm : clearwire-wmx.net
> Signal : Poor
> RSSI : -86 dBm
> CINR : 2 dB
> Activated: No
> Network Type : Home network
> Connection Time: 00:04:23
>
With a CINR of 2dB it's plausible that your data isn't actually being passed to the network and/or you're actually completely disconnected.?WiMAX_DB.bin has some URIs to Clearwire tech support and?subscription pages - maybe the daemon is trying to redirect you to one of them and the page is cached by your browser as the VLAN page ("We have an Important message for you...")?instead? On a side note, anytime I've had issues with connectivity I issue the following commands:>> wimaxcu roff; sudo kill -9 `head -n 1 /var/run/wimax.wmx0.pid`; sudo /usr/bin/wimaxd -b -i wmx0; wimaxcu ronAnd life is peachy once again :)
