0

I have a network appliance based on Busybox (on a Zynq device), and it has two NICs. One network has access to the internet, while the other is private. Both have DHCP, so both are reporting gateways, even though the private network doesn't have Internet access. For some reason, traffic for things like ntpd, rdate, and ping is being routed to the private network. We need to get NTP working, but the Busybox ntpd doesn't have a -I option. We've tried deleting the gateway (route del default eth1, IIRC) from the NIC for the private network, but that results in making the device completely inaccessible.

At a minimum, I need to figure out how to just get NTP to work. More generally, it would be nice (but not critical at the moment) to figure out how to set up a default route for all outgoing traffic to go to the public network if it doesn't match the IP range of the private one. Any help will be most appreciated.

3
  • 1
    If the private LAN has no access to the internet, why does the private DHCP server publish a default route? The fix could be to get the private DHCP server to stop publishing that route.
    – Jim L.
    May 10 '19 at 17:09
  • Another way of achieving what @JimL. suggested would be to configure your DHCP client not to ask for the default route on the internal interface. Post the output of ip route (in the non-working state) to help us understand your configuration.
    – Paul Gear
    May 10 '19 at 23:17
  • I agree, you should fix the misconfigured DHCP server. May 10 '19 at 23:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.