Custom query (1019 matches)

Begin forwarded message:

> From: Bob Hinden <bob.hinden@gmail.com>
> Subject: Poor WLAN (FREE) in my room this morning
> Date: November 6, 2012 7:53:03 AM EST
> To: Jim Martin <jim@daedelus.com>
> Cc: Bob Hinden <bob.hinden@gmail.com>
> 
> I was seeing very poor wireless in my room this morning.  Switched to wired and was fine.
> 
> Here is the ping output and info about my wireless setup.
> 
> Thanks,
> Bob
> 
>  Interfaces:
> en0:
>  Card Type:	AirPort Extreme  (0x14E4, 0xEF)
>  Firmware Version:	Broadcom BCM43xx 1.0 (5.106.198.19.22)
>  MAC Address:	b8:f6:b1:1c:45:9f
>  Locale:	FCC
>  Country Code:	US
>  Supported PHY Modes:	802.11 a/b/g/n
>  Supported Channels:	1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 149, 153, 157, 161, 165
>  Wake On Wireless:	Supported
>  AirDrop:	Supported
>  Status:	Connected
>  Current Network Information:
> Free:
>  PHY Mode:	802.11b
>  BSSID:	00:0d:bd:1f:c4:8c
>  Channel:	3
>  Country Code:	US
>  Network Type:	Infrastructure
>  Security:	None
>  Signal / Noise:	-81 dBm / -79 dBm
>  Transmit Rate:	11
>  Other Local Wi-Fi Networks:
> ATT448:
>  PHY Mode:	802.11n
>  BSSID:	40:b7:f3:da:df:c0
>  Channel:	6
>  Network Type:	Infrastructure
>  Security:	WPA2 Personal
>  Signal / Noise:	-86 dBm / -92 dBm
> DaedelusOnTheRoad:
>  PHY Mode:	802.11n
>  BSSID:	00:1f:f3:07:e9:bf
>  Channel:	10
>  Country Code:	US
>  Network Type:	Infrastructure
>  Security:	WPA2 Personal
>  Signal / Noise:	-88 dBm / -92 dBm
> Free:
>  PHY Mode:	802.11b
>  BSSID:	00:0a:f4:e2:4f:5b
>  Channel:	1
>  Network Type:	Infrastructure
>  Security:	None
>  Signal / Noise:	-79 dBm / -92 dBm
> Free:
>  PHY Mode:	802.11b
>  BSSID:	00:0d:bd:6f:ae:5d
>  Channel:	1
>  Network Type:	Infrastructure
>  Security:	None
>  Signal / Noise:	-76 dBm / -92 dBm
> MESH GROUP2:
>  PHY Mode:	802.11a
>  BSSID:	02:0b:6b:02:77:3e
>  Channel:	165
>  Network Type:	Computer-to-Computer
>  Security:	None
>  Signal / Noise:	-89 dBm / -92 dBm
> MiFi4620L Jetpack 7898 Secure:
>  PHY Mode:	802.11g
>  BSSID:	00:15:ff:1a:78:98
>  Channel:	1
>  Country Code:	US
>  Network Type:	Infrastructure
>  Security:	WPA2 Personal
>  Signal / Noise:	-69 dBm / -92 dBm
> jexpress:
>  PHY Mode:	802.11g
>  BSSID:	00:1e:52:f7:c4:97
>  Channel:	11
>  Network Type:	Infrastructure
>  Security:	WPA2 Personal
>  Signal / Noise:	-41 dBm / -92 dBm
> sailing:
>  PHY Mode:	802.11n
>  BSSID:	20:c9:d0:22:96:3e
>  Channel:	149,+1
>  Country Code:	US
>  Network Type:	Infrastructure
>  Security:	WPA2 Personal
>  Signal / Noise:	-84 dBm / -92 dBm
> sailing:
>  PHY Mode:	802.11n
>  BSSID:	20:c9:d0:22:96:3d
>  Channel:	1
>  Country Code:	US
>  Network Type:	Infrastructure
>  Security:	WPA2 Personal
>  Signal / Noise:	-72 dBm / -92 dBm
> 
> 
> dhcp-4619:~ hinden$ ping6 www.google.com
> PING6(56=40+8+8 bytes) 2001:df8::64:9078:45f5:ef90:86c0 --> 2607:f8b0:400a:801::1011
> 16 bytes from 2607:f8b0:400a:801::1011, icmp_seq=0 hlim=53 time=3008.581 ms
> 16 bytes from 2607:f8b0:400a:801::1011, icmp_seq=1 hlim=53 time=3892.837 ms
> 16 bytes from 2607:f8b0:400a:801::1011, icmp_seq=3 hlim=53 time=2905.942 ms
> 16 bytes from 2607:f8b0:400a:801::1011, icmp_seq=4 hlim=53 time=2265.994 ms
> ^C
> --- www.google.com ping6 statistics ---
> 13 packets transmitted, 4 packets received, 69.2% packet loss
> round-trip min/avg/max/std-dev = 2265.994/3018.339/3892.837/579.547 ms
> 
> dhcp-4619:~ hinden$ ping www.google.com
> PING www.google.com (173.194.33.51): 56 data bytes
> Request timeout for icmp_seq 0
> Request timeout for icmp_seq 1
> Request timeout for icmp_seq 2
> Request timeout for icmp_seq 3
> Request timeout for icmp_seq 4
> Request timeout for icmp_seq 5
> 64 bytes from 173.194.33.51: icmp_seq=6 ttl=53 time=206.502 ms
> Request timeout for icmp_seq 7
> Request timeout for icmp_seq 8
> Request timeout for icmp_seq 9
> Request timeout for icmp_seq 10
> Request timeout for icmp_seq 11
> Request timeout for icmp_seq 12
> Request timeout for icmp_seq 13
> Request timeout for icmp_seq 14
> Request timeout for icmp_seq 15
> Request timeout for icmp_seq 16
> Request timeout for icmp_seq 17
> Request timeout for icmp_seq 18
> Request timeout for icmp_seq 19
> 
> 

signature.asc​

Hi,

I'd like to forward to you the WG Chair's beer evening information which
was sent out on the wgchairs list earlier today:

Best,

	Henrik

-------- Original Message --------
Subject: Re: WG Chairs' Beer Evening in Maastreicht
Date: Wed, 28 Jul 2010 02:06:58 -0700
From: Stig Venaas <stig@venaas.com>
To: Jari Arkko <jari.arkko@piuha.net>
CC: WG Chairs <wgchairs@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>

Jari Arkko wrote:
> Wojciech,
>> Sorry for missing a previous mail, but what day/evening has been chosen?
>>   
> 
> Traditionally, we do this Wednesday night. IIRC Wednesday was mentioned 
> earlier in the thread, so I'm hoping this is true for this IETF as well. 
> I can make it on Wednesday, at least :-)

I would suggest we do it at the usual time, which I guess is right after
the plenary tonight.

Several of us have now been to

Cafe 't Pothuiske, Het Bat 1, http://www.pothuiske.nl/

and it looks like a good place to go. Only issue is that tonight they
seem to only have cold food like sandwiches.

The place is by the west river bank, just a little bit south of where
the social was.

They have been warned that a large crowd is likely to show up tonight.

Stig

Begin forwarded message:

> From: Melinda Shore <melinda.shore@gmail.com>
> Date: March 28, 2012 12:35:15 AM EDT
> To: wgchairs@ietf.org
> Subject: Remote participation
> 
> So far this meeting has been somewhat less remote-friendly than usual.
> Some of it can be attributed to crappy audio and it's not clear to me
> whether and/or to what extent that's under the control of the IETF,
> but while some chairs have done an excellent job keeping tabs on remote
> participants through the Jabber rooms (thank you, Paul Hoffman, for
> doing a great job with ipsecme despite funky audio) so far I've found
> that the majority are checking Jabber rooms as an afterthought, if at
> all (granted, probably a sampling problem).  The week isn't half over
> yet, so there's a chance to get things back on track and be attentive
> to your remote participants - make sure that audio is working, that
> they've got an opportunity to provide feedback/input, and that someone
> in the meeting room is checking the Jabber room regularly to see
> if there are issues.
> 
> Melinda