On Sep 16, 2007, at 11:53 AM, Jan Hoevers wrote: > Koos van den Hout wrote on 12-9-2007 19:32: >> And maybe we could name home routers which work and don't work for >> a pool >> ntp server. That could save some future participants some headaches. > > I'm using pfSense on a Soekris 4801. It works at least reasonable, but > I've cranked up the NAT state table from the default 10,000 to 100,000 > slots. So far I've seen > 17,000 slots in use during a 410 kbit/sec > pool > burst. > > Of course a stateless setup would be better, but I haven't figured > that > out yet. At least these figures give an idea of what's going on. A > consumer grade NAT router with 1000 or 4000 slots won't handle this.
Certainly true, at least if the router insists upon persisting state for each of these NTP queries. It's not a great idea to use NAT in the path to an NTP server; it just adds load and latency which have a negative effect upon the quality of the time service being provided. People who want to provide contribute time services to the pool should make every effort to only use machines which have statically assigned public IPs which are not behind a NAT firewall/router. -- -Chuck _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
