Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #2010
| From | Ivan Shmakov <oneingray@gmail.com> |
|---|---|
| Newsgroups | comp.protocols.time.ntp, comp.os.linux.networking |
| Subject | Re: IPv6 and ip6tables |
| Date | 2013-03-11 21:13 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <87vc8xod1j.fsf@violet.siamics.net> (permalink) |
| References | <dc9f63ef-02b6-47aa-8182-ad92d9443922@googlegroups.com> |
Cross-posted to 2 groups.
>>>>> Xavier Robin <geckolimo@gmail.com> writes: [Cross-posting to news:comp.os.linux.networking.] > Has anyone some experience serving NTP over IPv6 through an ip6tables > firewall here? > Despite the fact that I opened port 123 (both UPD and TCP), as soon > as I set the INPUT policy to DROP, NTP becomes unreachable. Is it > using a different port on ipv6 or something like this? The server is > fully reachable when the INPUT policy is ACCEPT. It is also > reachable over ipv4 with the same iptables rule (and DROP policy). I've never seen an issue with such a setup. The only difference is that my firewall has also a -j ACCEPT rule for --dport 123 in the FORWARD chain. I don't know if it's related, though. [...] > xavier@arthur:~$ sudo ip6tables -L > [sudo] password for xavier: > Chain INPUT (policy DROP) > target prot opt source destination > ACCEPT all anywhere anywhere Is there really such an all-permitting rule? > ACCEPT all anywhere anywhere ctstate RELATED,ESTABLISHED > ACCEPT tcp anywhere anywhere tcp dpt:(some ports...) > ACCEPT udp anywhere anywhere udp dpt:ntp > ACCEPT tcp anywhere anywhere tcp dpt:ntp [...] -- FSF associate member #7257
Back to comp.os.linux.networking | Previous | Next — Next in thread | Find similar | Unroll thread
Re: IPv6 and ip6tables Ivan Shmakov <oneingray@gmail.com> - 2013-03-11 21:13 +0000
Re: IPv6 and ip6tables geckolimo@gmail.com - 2013-03-12 08:51 -0700
Re: IPv6 and ip6tables Ivan Shmakov <oneingray@gmail.com> - 2013-03-12 16:14 +0000
csiph-web