Re: IETF58 - Network Status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Randall,

> I have been consistently unable to maintain a connection for more 
> than a very few minutes, usually not even long enough to establish a 
> VPN tunnel and fetch one message.  The 802.11 coverage comes and 
> goes; the APs seem to vanish and I see nothing for a while, 
> eventually the network comes back but only briefly.  This has been 

I can partly confirm your observations, since
I often see my driver reporting a signal strength of 0 for seconds.
The connection is somehow unstable as my log also reports
(NSIS meeting this morning, actually not crowded)
Nov 13 10:41:01  kernel: eth1: New link status: AP In Range (0005)
Nov 13 10:41:03  kernel: eth1: New link status: AP Changed (0003)
Nov 13 10:41:25  kernel: eth1: New link status: AP Out of Range (0004)
Nov 13 10:41:26  kernel: eth1: New link status: AP In Range (0005)
Nov 13 10:42:58  kernel: eth1: New link status: AP Changed (0003)
Nov 13 10:45:18  kernel: eth1: New link status: AP Out of Range (0004)
Nov 13 10:45:18  kernel: eth1: New link status: AP In Range (0005)
Nov 13 10:45:18  kernel: eth1: New link status: AP Changed (0003)
Nov 13 10:45:23  kernel: eth1: New link status: AP Out of Range (0004)
Nov 13 10:45:24  kernel: eth1: New link status: AP In Range (0005)
Nov 13 10:45:54  kernel: eth1: New link status: AP Changed (0003)
Nov 13 10:46:28  kernel: eth1: New link status: AP Out of Range (0004)
Nov 13 10:46:28  kernel: eth1: New link status: AP In Range (0005)
... and so on...
however, it seems also to depend on the cards firmware and driver,
so other people may have no problems at all...
Inspite all the problems, it works well enough to get things actually done.

> the case in every session I've attended, as well as tonight's 
> plenary.  It doesn't seem to matter if the room is crowded or empty, 
> or where I sit.
> 
> I have attempted to only select the 'ietf58' network, but often the 
> network vanishes and there are no networks visible; other times the 
> only visible "network" is an ad-hoc calling itself 'ietf58'.

I wasn't often successful to reattach to APs after my card was
"hi-jacked" to ad-hoc cards announcing ietf58. Setting the 
essid again to the same value seems to do trick, however,
often I see signals of strength 0 (maybe the card is confused then..).
Furthermore, it happens often that I don't get an IPv6 address
directly after activating the card (maybe the RA doesn't get through).

Cheers,
 Roland


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]