u/jimbo_rr

While troubleshooting a network issue for packets appearing to be duplicated (only once, not a continual flood), I did a trace from a nearby system and have output unlike anything I've seen before.

Localhost#traceroute 192.168.10.20

 Traceroute to 192.168.10.20 ,30 hops max 0 byte packets:

1  192.168.255.252     &lt;1  ms    &lt;1  ms    &lt;1  ms
2  192.168.10.20       3   ms    &lt;1  ms    2   ms
3  192.168.10.20       &lt;1  ms    4   ms    &lt;1  ms
4  0.0.0.0            *        [192.168.10.20    ] reports:  &lt;1  ms   [192.168.10.20    ] reports:  &lt;1  ms
5  192.168.10.20       2   ms    *         &lt;1  ms
6  192.168.10.20       &lt;1  ms    2   ms    *
7  192.168.10.20       &lt;1  ms    &lt;1  ms    2   ms
8  0.0.0.0            *        [192.168.10.20    ] reports:  &lt;1  ms   [192.168.10.20    ] reports:  &lt;1  ms
9  192.168.10.20       2   ms    *         &lt;1  ms
10 192.168.10.20       &lt;1  ms    2   ms    *
11 192.168.10.20       &lt;1  ms    &lt;1  ms    2   ms
12 0.0.0.0            *        [192.168.10.20    ] reports:  &lt;1  ms   [192.168.10.20    ] reports:  &lt;1  ms
13 192.168.10.20       2   ms    *         &lt;1  ms
14 192.168.10.20       &lt;1  ms    2   ms    *
15 192.168.10.20       &lt;1  ms    &lt;1  ms    2   ms
16 0.0.0.0            *        [192.168.10.20    ] reports:  &lt;1  ms   [192.168.10.20    ] reports:  1   ms
17 192.168.10.20       2   ms    *         1   ms
18 192.168.10.20       &lt;1  ms    &lt;1  ms    *
19 192.168.10.20       &lt;1  ms    &lt;1  ms    2   ms
20 0.0.0.0            *        [192.168.10.20    ] reports:  &lt;1  ms   [192.168.10.20    ] reports:  &lt;1  ms
21 192.168.10.20       2   ms    *         &lt;1  ms
22 192.168.10.20       &lt;1  ms    2   ms    *
23 192.168.10.20       &lt;1  ms    &lt;1  ms    2   ms
24 0.0.0.0            *        [192.168.10.20    ] reports:  &lt;1  ms   [192.168.10.20    ] reports:  &lt;1  ms
25 192.168.10.20       2   ms    *         &lt;1  ms
26 192.168.10.20       &lt;1  ms    2   ms    *
27 192.168.10.20       &lt;1  ms    &lt;1  ms    2   ms
28 0.0.0.0            *        [192.168.10.20    ] reports:  &lt;1  ms   [192.168.10.20    ] reports:  &lt;1  ms
29 192.168.10.20       2   ms    *         &lt;1  ms
30 192.168.10.20       &lt;1  ms    2   ms    *


Hop Count = 30 Last TTL = 30 Test attempt = 90 Test Success = 69

I checked several other systems directly attached to this same switch and got similar results. However, doing a trace to a system connected to a downstream switch connected to the problem switch seemed just fine:

Localhost#traceroute 192.168.10.120

 Traceroute to 192.168.10.120 ,30 hops max 0 byte packets:

1  192.168.255.252     &lt;1  ms    &lt;1  ms    &lt;1  ms
2  192.168.10.120      2   ms    1   ms    4   ms


Hop Count = 2 Last TTL = 2 Test attempt = 6 Test Success = 6

Vlan involved is trunked between the two switches, an IP Route on the upstream switch routes the traffic to the problem switch.

The connected systems are all various servers, and connections to these all seem to be operating just fine otherwise. I only noticed this because the 10.20 system is my DHCP server (for multiple subnets) and it suddenly started seeing duplicate DHCP requests coming in, and was sending duplicate replies as a result. This wasn't causing any problems so I didn't investigate until I saw my logs were growing faster than normal.

Has anyone come across a trace similar to the above, and if so, what was the cause? I'm not a network dummy, but this is a new one for me.

I’ve been working on cars all my adult life, not professionally, but this one has me stumped for such a simple part. Kia made this way more difficult than it should have been, see pics.

There are two tabs to release these nozzles, the one I can see is easy enough to press with a screwdriver, the hidden one at the bottom (nearest windshield) is basically inaccessible. I went as far as to purchase a kiwi pliers but I couldn’t get it into that small opening. There is no hole in the metal on that side to reach anything in, only access is from the top.

Short of finding a set of pliers that can reach the two clips (ideal solution) the only other option I seem to have is to try breaking apart the existing nozzle to remove it. Less destructive would be trying to drill a hole in the right spot on the back side to get a screwdriver in from that side to release the other tab, but that’s still a hack I’d rather avoid.

Odd Traceroute