Custom query (1016 matches)


Show under each result:

Results (130 - 132 of 1016)

Ticket Resolution Summary Owner Reporter
#1249 not broken nat64 in terminal room Clemens Schrimpe mcr@…
I'm trying to live on the NAT64.
(Founda  few bugs in the rest of the Internet)

I'm in the terminal room this morning.
I'm not getting to (IPv4 only):

% ping
PING (64:ff9b::de5:bc3b)) 56 data bytes
... no reply.

% ping
PING (2404:6800:4003:80d::2004)) 56 data bytes
64 bytes from (2404:6800:4003:80d::2004): icmp_seq=1 ttl=54 time=31.4 ms
64 bytes from (2404:6800:4003:80d::2004): icmp_seq=2 ttl=54 time=31.8 ms

My dual-stack home desktop:
% ping
PING (2607:f0b0:f:2::247)) 56 data bytes
64 bytes from (2607:f0b0:f:2::247): icmp_seq=1 ttl=46 time=367 ms

details for me.
I will live on this network for awhile until I find I need github :-)
Oh, that's now.

dooku-[~](system) mcr 10138 %ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::a11:96ff:fe01:81e0  prefixlen 64  scopeid 0x20<link>
        inet6 2001:67c:370:1998:ac32:98c6:bc97:67a6  prefixlen 64  scopeid 0x0<global>
        inet6 2001:67c:370:1998:a11:96ff:fe01:81e0  prefixlen 64  scopeid 0x0<global>
        ether 08:11:96:01:81:e0  txqueuelen 1000  (Ethernet)
        RX packets 14359628  bytes 4726467908 (4.4 GiB)
        RX errors 0  dropped 64  overruns 0  frame 0
        TX packets 2683303  bytes 898675406 (857.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

dooku-[~](system) mcr 10139 %iwconfig wlan0
wlan0     IEEE 802.11  ESSID:"ietf-nat64"
          Mode:Managed  Frequency:5.24 GHz  Access Point: 38:90:A5:F6:30:2C
          Bit Rate=12 Mb/s   Tx-Power=15 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=68/70  Signal level=-42 dBm
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:10   Missed beacon:0

#1064 pending my wireless card goes "wheefee" when I poke it in the tummy s5d0f1i4k1j2o7p5@… anonymous

I took a video of my wireless card responding to a poke in the tummy. what can you do about this problem?

#1221 fixed multi-second ping times in Viscount panda@… kaduk@…

I'm in Viscount for the DOTS session, and have been seeing poor network performance in interactive usage, quantified by ping responses exceeding 3 seconds.

Note: See TracQuery for help on using queries.