All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal@plouf.fr.eu.org>
To: Tobias Andresen <tobiasarp@gmx.de>
Cc: netfilter@vger.kernel.org
Subject: Re: NTP forwarding
Date: Sun, 06 Mar 2016 21:42:25 +0100	[thread overview]
Message-ID: <56DC9631.7010702@plouf.fr.eu.org> (raw)
In-Reply-To: <56DAEA15.409@gmx.de>

Tobias Andresen a écrit :
> 
> i have following network structure:
> 
> 
>      NTP-Server (62.214.6.29)
>                |
>                |
>                |
>       (eth0: 10.0.0.95)
>         Embedded board
>     (eth1: 192.168.31.95)
>                |
>                |
>                |
>         Ethernet-Switch
>          |        |    |
>          |        |    |
>         PC1       |   PC3 (192.168.31.98)
> (192.168.31.96)  |
>                   |
>                  PC2
> (192.168.31.97)
> 
> 
> The 3 PCs shall be able to connect to the NTP server (62.214.6.29)
> to update their time but i cannot figure out how to configure the 
> iptables rules
> on the embedded board to achieve this.

Why do you think you need iptables rules ? Isn't plain routing enough ?

> I have tried to forward port 123 but it does not work.

This statement does not contain any useful information. It does not
describe what you did and what happened.

  reply	other threads:[~2016-03-06 20:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-05 14:15 NTP forwarding Tobias Andresen
2016-03-06 20:42 ` Pascal Hambourg [this message]
2016-03-06 21:16   ` Tobias Andresen
2016-03-06 21:40     ` Pascal Hambourg
2016-03-07  7:24       ` Tobias Andresen
2016-03-07 19:33         ` Pascal Hambourg
2016-03-07  3:49     ` Remzi AKYÜZ
2016-03-07  7:26       ` Tobias Andresen
2016-03-07  9:24         ` Vigneswaran R
2016-03-07 10:05         ` Remzi AKYÜZ
2016-03-08 11:54 ` Karol Babioch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56DC9631.7010702@plouf.fr.eu.org \
    --to=pascal@plouf.fr.eu.org \
    --cc=netfilter@vger.kernel.org \
    --cc=tobiasarp@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.