Skip to content

Adding possibility of specifying listening interface #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
feriniguez wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Adding possibility of specifying listening interface #64

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3f02c61
adding listen interface to startup.sh
feriniguez Jun 29, 2023
c86701d
Update README.md listeniface var
feriniguez Jun 29, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,6 +167,17 @@ As an example, using `docker-compose.yaml`, that would be look like this if you
...
```

## Listening Interface

In case the docker 'host' network is used, it is possible to select the interface in which the ntp service wil be
listening by setting up the variable `LISTENIFACE` and the interface name in `docker-compose.yaml` file:

```yaml
...
environment:
- LISTENIFACE=eth1
...
```

## Testing your NTP Container

Expand Down
3 changes: 3 additions & 0 deletions assets/startup.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,9 @@ done
# final bits for the config file
{
echo
if [ ! -z ${LISTENIFACE+x} ]
echo "binddevice $LISTENIFACE"
fi
echo "driftfile /var/lib/chrony/chrony.drift"
echo "makestep 0.1 3"
if [ "${NOCLIENTLOG}" = true ]; then
Expand Down