|Summary:||Ntpd does not work with non-fixed interfaces|
|Product:||[Retired] Red Hat Linux||Reporter:||Jos Vos <jos>|
|Component:||ntp||Assignee:||Harald Hoyer <harald>|
|Status:||CLOSED WONTFIX||QA Contact:||Brian Brock <bbrock>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2002-12-05 10:12:32 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Jos Vos 2002-12-05 10:12:26 UTC
Description of Problem: Ntpd seems to look only once, at startup time, to the local addresses for binding purposes. This means that you run into trouble with for example ADSL/cable/dial-up PPP interfaces and with VPN tunnels, of which the interface and address is available after ntpd startup. NTP packets will then be generated using a wrong source address (e.g., this might be a private address), which might not work, either because of routing issues or by firewall blocks. Version-Release number of selected component (if applicable): 4.1.1a-9 (applies to all versions I know). Steps to Reproduce: 1. Set up a system with an 192.168.x.y address. 2. Do not enable masquerading. 3. Start ntpd. 4. Make a PPP connection with a default route. 5. Let ntpd talk to a public NTP server. Actual Results: Packets will be sent out with a 192.168.x.y address. Expected Results: Packats are sent out with the external PPP address.
Comment 1 Harald Hoyer 2002-12-05 10:19:31 UTC
how about /sbin/service ntp restart in /etc/ppp/ip-up.local ?? I will not fix this. Please mail this "Request for Extension" to firstname.lastname@example.org, thx.