IPv6 in rawhide

Jay Cliburn jacliburn at bellsouth.net
Sat Jul 22 18:05:01 UTC 2006


Before I go much further in investigating this, I'd like to ask if 
anyone has successfully used IPv6 under rawhide?

I can ssh over IPv6 between FC5 and Centos 4.3 boxes, but any attempt to 
ssh using v6 to or from a rawhide machine doesn't work.  I haven't 
gotten any details yet, other than an odd packet in an ethereal capture 
that I executed on an FC4 machine while trying to connect IPv6 from a 
rawhide machine to the FC4 machine.  The frames shown below represent 
the TCP 3-way handshake for the session, but the last frame seems to 
indicate that the ssh client is ACKing a frame it hasn't yet seen.  wtf?

No.     Time        Source                Destination           Protocol 
Info
       4 6.335103    fec0::250:8dff:feef:9069 fec0::250:8dff:fed3:7b0d 
TCP      4
5702 > ssh [SYN] Seq=0 Len=0 MSS=1440 TSV=770378 TSER=0 WS=7

Frame 4 (94 bytes on wire, 94 bytes captured)
Ethernet II, Src: AbitComp_ef:90:69 (00:50:8d:ef:90:69), Dst: 
AbitComp_d3:7b:0d
(00:50:8d:d3:7b:0d)
Internet Protocol Version 6
Transmission Control Protocol, Src Port: 45702 (45702), Dst Port: ssh 
(22), Seq:
  0, Len: 0
     Source port: 45702 (45702)
     Destination port: ssh (22)
     Sequence number: 0    (relative sequence number)
     Header length: 40 bytes
     Flags: 0x0002 (SYN)
     Window size: 737280 (scaled)
     Checksum: 0x3ece [correct]
     Options: (20 bytes)
========================================================================
========================================================================
No.     Time        Source                Destination           Protocol 
Info
       5 6.335131    fec0::250:8dff:fed3:7b0d fec0::250:8dff:feef:9069 
TCP      s
sh > 45702 [SYN, ACK] Seq=0 Ack=1 Win=22848 Len=0 MSS=1440 TSV=136555 
TSER=77037
8 WS=2

Frame 5 (94 bytes on wire, 94 bytes captured)
Ethernet II, Src: AbitComp_d3:7b:0d (00:50:8d:d3:7b:0d), Dst: 
AbitComp_ef:90:69
(00:50:8d:ef:90:69)
Internet Protocol Version 6
Transmission Control Protocol, Src Port: ssh (22), Dst Port: 45702 
(45702), Seq:
  0, Ack: 1, Len: 0
     Source port: ssh (22)
     Destination port: 45702 (45702)
     Sequence number: 0    (relative sequence number)
     Acknowledgement number: 1    (relative ack number)
     Header length: 40 bytes
     Flags: 0x0012 (SYN, ACK)
     Window size: 22848 (scaled)
     Checksum: 0x3517 [correct]
     Options: (20 bytes)
========================================================================
========================================================================
No.     Time        Source                Destination           Protocol 
Info
       6 9.330977    fec0::250:8dff:feef:9069 fec0::250:8dff:fed3:7b0d 
TCP      [
TCP ACKed lost segment] 45702 > ssh [SYN] Seq=0 Len=0 MSS=1440 
TSV=771128 TSER=0
  WS=7

Frame 6 (94 bytes on wire, 94 bytes captured)
Ethernet II, Src: AbitComp_ef:90:69 (00:50:8d:ef:90:69), Dst: 
AbitComp_d3:7b:0d
(00:50:8d:d3:7b:0d)
Internet Protocol Version 6
Transmission Control Protocol, Src Port: 45702 (45702), Dst Port: ssh 
(22), Seq:
  0, Len: 0
     Source port: 45702 (45702)
     Destination port: ssh (22)
     Sequence number: 0    (relative sequence number)
     Header length: 40 bytes
     Flags: 0x0002 (SYN)
     Window size: 737280 (scaled)
     Checksum: 0x3be0 [correct]
     Options: (20 bytes)
     SEQ/ACK analysis
         TCP Analysis Flags
             This frame ACKs a segment we have not seen (lost?)




More information about the test mailing list