why is nexthop ip print reversed with the ping command?

Question

This question hit me today while I'm quite used to see it reversed, but actually, why is the nexthop ip noted reversed in the ping command ?

PING 10.8.0.8 (10.8.0.8) 56(84) bytes of data.
From 10.8.0.1 icmp_seq=1 Redirect Host(New nexthop: 8.0.8.10)
From 10.8.0.1 icmp_seq=2 Redirect Host(New nexthop: 8.0.8.10)
From 10.8.0.1 icmp_seq=3 Redirect Host(New nexthop: 8.0.8.10)
From 10.8.0.1 icmp_seq=4 Redirect Host(New nexthop: 8.0.8.10)

(10.8.0.8 is usually accessed via 10.8.0.1, but is not powered on thus the ping fails... but the question is about the "8.0.8.10" reversed)

You'll have to ask whoever runs the server at 10.8.0.1. – Michael Hampton Aug 15 '20 at 14:54 — Michael Hampton, Aug 15 '20 at 14:54
I guess I'll have to ask myself then... can you detail ? – hl037_ Aug 17 '20 at 11:25 — hl037_, Aug 17 '20 at 11:25

score 4 · Accepted Answer · answered Feb 02 '21 at 20:08

4

This seems to be a bug in iputils with Ubuntu.

https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1892108

answered Feb 02 '21 at 20:08

zille

56
2

Seems to be there in upstream as well, where it got fixed: https://github.com/iputils/iputils/commit/e2e9a2dd4639924614bdbee43907a49134e8da19 – Steve Dee Mar 05 '22 at 12:17

why is nexthop ip print reversed with the ping command?

1 Answers1