Linux

I need to configure an NTP daemon on a "bridge-PC" connected on 2 LANs. It is expected to read the correct time on a time server on the first LAN and behave as a server for the second LAN.
Can I do both the things with ntpd?
In other words, is ntpd able to work as client and server at the same time?
I've configured ntp.conf with the external NTP server address on the first LAN, and inserted ./ntdp in the rc.local. The daemon runs correctly, it reads and updates its time, but the other PCs in the second LAN (the "internal"one) do not recognize the "bridge-PC" as an NTP server (even if they are able to ping it).

What should be going wrong?

Thanks,
M.

Yes. This is a fairly common configuration.

On your 'bridge-PC" you need to configure ntpd to allow the ntp clients on the second lan to get their information from it. Typically this is done by adding a line such as

Code:

restrict 192.168.0.0 mask 255.255.255.0 nomodify notrap

The ntp clients on the second lan should be configured to point to the "bridge-PC"

Code:

server bridge-PC

Thanks! I suppose that line should be added in the ntp.conf, isn't it?
Should I add anything to rc.conf?

Just add to ntp.conf