[Bug 9146] New: ntpd uses wrong IP address in reply to query

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=9146

            Bug ID: 9146
           Summary: ntpd uses wrong IP address in reply to query
           Product: Busybox
           Version: 1.24.x
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Networking
          Assignee: unassigned at busybox.net
          Reporter: stijn+busybox at linux-ipv6.be
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

Created attachment 6591
  --> https://bugs.busybox.net/attachment.cgi?id=6591&action=edit
busybox config

When sending NTP queries to a secondary IP addresses of a device running
busybox ntpd, the replies are sent from the primary IP address. This happens
for both IPv4 and IPv6.

Interface addresses:
15: eth0.54 at eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
    link/ether 04:18:d6:31:38:b3 brd ff:ff:ff:ff:ff:ff
    inet 192.168.54.254/24 brd 192.168.54.255 scope global eth0.54
       valid_lft forever preferred_lft forever
    inet 192.168.54.1/24 brd 192.168.54.255 scope global secondary eth0.54
       valid_lft forever preferred_lft forever
    inet6 [hidden]/64 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::1/64 scope link nodad
       valid_lft forever preferred_lft forever
    inet6 fe80::618:d6ff:fe31:38b3/64 scope link
       valid_lft forever preferred_lft forever

IPv4 tcpdump:
11:15:22.468631 IP 192.168.54.121.123 > 192.168.54.1.123: NTPv4, Client, length
48
11:15:22.469272 IP 192.168.54.254.123 > 192.168.54.121.123: NTPv4, Server,
length 48
11:15:24.468616 IP 192.168.54.121.123 > 192.168.54.1.123: NTPv4, Client, length
48
11:15:24.469014 IP 192.168.54.254.123 > 192.168.54.121.123: NTPv4, Server,
length 48
11:15:26.468606 IP 192.168.54.121.123 > 192.168.54.1.123: NTPv4, Client, length
48
11:15:26.468999 IP 192.168.54.254.123 > 192.168.54.121.123: NTPv4, Server,
length 48
11:15:28.468622 IP 192.168.54.121.123 > 192.168.54.1.123: NTPv4, Client, length
48
11:15:28.469010 IP 192.168.54.254.123 > 192.168.54.121.123: NTPv4, Server,
length 48

Result on the client:
 8 Aug 11:15:30 ntpdate[13088]: no server suitable for synchronization found

IPv6 tcpdump:
11:17:48.020528 IP6 fe80::be5f:f4ff:fe67:1f9a.123 >
fe80::618:d6ff:fe31:38b3.123: NTPv4, Client, length 48
11:17:48.021053 IP6 fe80::1.123 > fe80::be5f:f4ff:fe67:1f9a.123: NTPv4, Server,
length 48
11:17:50.020552 IP6 fe80::be5f:f4ff:fe67:1f9a.123 >
fe80::618:d6ff:fe31:38b3.123: NTPv4, Client, length 48
11:17:50.020989 IP6 fe80::1.123 > fe80::be5f:f4ff:fe67:1f9a.123: NTPv4, Server,
length 48
11:17:52.020525 IP6 fe80::be5f:f4ff:fe67:1f9a.123 >
fe80::618:d6ff:fe31:38b3.123: NTPv4, Client, length 48
11:17:52.020963 IP6 fe80::1.123 > fe80::be5f:f4ff:fe67:1f9a.123: NTPv4, Server,
length 48
11:17:54.020563 IP6 fe80::be5f:f4ff:fe67:1f9a.123 >
fe80::618:d6ff:fe31:38b3.123: NTPv4, Client, length 48
11:17:54.021004 IP6 fe80::1.123 > fe80::be5f:f4ff:fe67:1f9a.123: NTPv4, Server,
length 48

Result on the client:
 8 Aug 11:17:56 ntpdate[13099]: no server suitable for synchronization found

-- 
You are receiving this mail because:
You are on the CC list for the bug.