Custom query (1019 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (196 - 198 of 1019)

Ticket Resolution Summary Owner Reporter
#300 fixed IETF-hotel.1x is flaky in Peony wireless79@… anonymous
Description
I keep losing association. 
IETF.1x not available. 

#301 fixed atrfumi's missing iphone xzhao@… anonymous
Description

my registration id is: 7910157842.

Joel,

thank you for your kindness.

MAC address is 7c:c5:37:13:93:fe

but, I called my phone several times, and found that it was powered-off or out-of-area.

Anyway, I really appreciate it.

On 2010/11/09, at 13:41, joel.jaeggli@… wrote:

Hey, if you don't find it tell us your registration id number and we'll see if we can find the mac address and see if it's still on the network and where.


From: 79attendees-bounces@… 79attendees-bounces@… On Behalf Of ext Arifumi Matsumoto Sent: Monday, November 08, 2010 20:20 To: Ole Jacobsen Cc: 79attendees@… Subject: Re: [79attendees] I dropped iphone4

Thanks, I'll check it.

On 2010/11/09, at 13:13, Ole Jacobsen wrote:

This might be the "iPod" that the Secretariat has, check with them.

Ole

Ole J. Jacobsen Editor and Publisher, The Internet Protocol Journal Cisco Systems Tel: +1 408-527-8972 Mobile: +1 415-370-4628 E-mail: ole@… URL: http://www.cisco.com/ipj

On Tue, 9 Nov 2010, Arifumi Matsumoto wrote:

All,

Yesterday maybe after technical plenary, I dropped a black small pouch with iPhone4 in it. My iPhone4 is also black, of course.

If you find one, please let me know about it.

# I realized those smart-phones are too smart to lose. # It stores too much of my personal information like # account info for each applications/sites. # Too much pain. _ 79attendees mailing list 79attendees@… https://www.ietf.org/mailman/listinfo/79attendees

_ 79attendees mailing list 79attendees@… https://www.ietf.org/mailman/listinfo/79attendees

#302 wontfix network woes? wireless79@… anonymous
Description
This is fro the hotel lobby, using the ietf-a.1x SSID.  Others are using
the hotel.1x or ietf.1x SSIDs nearby and having the same issues.

PING 130.129.96.1 (130.129.96.1): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
64 bytes from 130.129.96.1: icmp_seq=3 ttl=64 time=152.454 ms
Request timeout for icmp_seq 4
64 bytes from 130.129.96.1: icmp_seq=5 ttl=64 time=40.961 ms
64 bytes from 130.129.96.1: icmp_seq=6 ttl=64 time=238.270 ms
64 bytes from 130.129.96.1: icmp_seq=7 ttl=64 time=138.817 ms
64 bytes from 130.129.96.1: icmp_seq=8 ttl=64 time=46.625 ms
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
64 bytes from 130.129.96.1: icmp_seq=11 ttl=64 time=3.523 ms
64 bytes from 130.129.96.1: icmp_seq=12 ttl=64 time=6.342 ms
64 bytes from 130.129.96.1: icmp_seq=13 ttl=64 time=4.255 ms
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
64 bytes from 130.129.96.1: icmp_seq=18 ttl=64 time=4.334 ms
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
64 bytes from 130.129.96.1: icmp_seq=22 ttl=64 time=1.508 ms
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
64 bytes from 130.129.96.1: icmp_seq=25 ttl=64 time=101.299 ms
64 bytes from 130.129.96.1: icmp_seq=26 ttl=64 time=6.347 ms
64 bytes from 130.129.96.1: icmp_seq=27 ttl=64 time=228.147 ms
64 bytes from 130.129.96.1: icmp_seq=28 ttl=64 time=143.442 ms
64 bytes from 130.129.96.1: icmp_seq=29 ttl=64 time=35.190 ms
Request timeout for icmp_seq 30
64 bytes from 130.129.96.1: icmp_seq=31 ttl=64 time=87.742 ms
64 bytes from 130.129.96.1: icmp_seq=32 ttl=64 time=2.928 ms
^C
--- 130.129.96.1 ping statistics ---
34 packets transmitted, 17 packets received, 50.0% packet loss
round-trip min/avg/max/stddev = 1.508/73.070/238.270/78.342 ms

Note: See TracQuery for help on using queries.