Modify

Opened 7 years ago

Last modified 4 years ago

#9820 new defect

Ping6 doesn't display source addresses correctly

Reported by: jch@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version: Backfire 10.03.1 RC5
Keywords: Cc:

Description

I just had a router that stopped routing. No problem, let's find out its link-local IPv6 address and log in to that:

64 bytes from ff02::1: seq=2 ttl=64 time=0.998 ms
64 bytes from ff02::1: seq=2 ttl=64 time=3.614 ms (DUP!)
64 bytes from ff02::1: seq=2 ttl=64 time=4.763 ms (DUP!)

For some reason, ping6 doesn't display the link-local address that's used as the source of the echo reply, but instead displays the multicast address that was used as destination of the echo request.

Packet traces indicate that, as expected, the link-local address is used as the source:

21:54:16.107233 IP6 fe80::218:f3ff:fe98:e534 > ff02::1: ICMP6, echo request, seq 5, length 64
21:54:16.110341 IP6 fe80::218:f3ff:fea9:914e > fe80::218:f3ff:fe98:e534: ICMP6, echo reply, seq 5, length 64
21:54:16.111209 IP6 fe80::418:84ff:fe24:8055 > fe80::218:f3ff:fe98:e534: ICMP6, echo reply, seq 5, length 64

--jch

Attachments (0)

Change History (2)

comment:1 in reply to: ↑ description Changed 5 years ago by anonymous

Replying to jch@…:

I just had a router that stopped routing. No problem, let's find out its link-local IPv6 address and log in to that:

64 bytes from ff02::1: seq=2 ttl=64 time=0.998 ms
64 bytes from ff02::1: seq=2 ttl=64 time=3.614 ms (DUP!)
64 bytes from ff02::1: seq=2 ttl=64 time=4.763 ms (DUP!)

For some reason, ping6 doesn't display the link-local address that's used as the source of the echo reply, but instead displays the multicast address that was used as destination of the echo request.

Packet traces indicate that, as expected, the link-local address is used as the source:

21:54:16.107233 IP6 fe80::218:f3ff:fe98:e534 > ff02::1: ICMP6, echo request, seq 5, length 64
21:54:16.110341 IP6 fe80::218:f3ff:fea9:914e > fe80::218:f3ff:fe98:e534: ICMP6, echo reply, seq 5, length 64
21:54:16.111209 IP6 fe80::418:84ff:fe24:8055 > fe80::218:f3ff:fe98:e534: ICMP6, echo reply, seq 5, length 64

--jch

Bug still affecting Attitude Adjustment. Very frustrating.

comment:2 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.