Custom query (937 matches)
Results (121 - 123 of 937)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #877 | fixed | new reply feature | ||
| Description |
trac has changed... if you want to reply to me you'll need to use the reply button ---> and you'll have to scroll to the bottom to find the reply box. Comments now appears to be internal. sigh |
|||
| #302 | wontfix | network woes? | ||
| 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 |
|||
| #519 | worksforme | network teardown time; Jabber connectivity | ||
| Description |
(a) When will the IETF network be torn down? In particular, when will the in-room networking (at the Hyatt), wired and wireless, be switched back to the Hyatt's bandwidth and (v4 only, presumably NATted) IP address space. (b) I tried to Jabber this, per the meeting network web page, but I'm getting a reply that noc@jabber.ietf.org isn't available for messaging. --Steve Bellovin, https://www.cs.columbia.edu/~smb |
|||
Note: See TracQuery for help on using queries.
