Re: ntpd could not parse pool.ntp.org

2005-08-17 Thread Mike Henker
Before try the solution of Nick I tried what you said: - There is a typo in one of the nameserver ip's posted here. 194.22_5_.52.4 does not exist. Yes correct, are 194.224.52.6 and 194.224.52.4 --8-- nameserver 194.224.52.4 nameserver 192.94.163.152 --8-- Please try to do a nslookup

Re: ntpd could not parse pool.ntp.org

2005-08-17 Thread Steve Williams
Mike Henker wrote: Before try the solution of Nick I tried what you said: - There is a typo in one of the nameserver ip's posted here. 194.22_5_.52.4 does not exist. Yes correct, are 194.224.52.6 and 194.224.52.4 --8-- nameserver 194.224.52.4 nameserver 192.94.163.152 --8-- Please try

Re: ntpd could not parse pool.ntp.org

2005-08-17 Thread Mike Henker
Forget the last message I can add to the router the static address and also allow to specify a gateway. I ll do what you said Nick: 192.168.1.0 netmask 255.255.255.0 gateway 192.168.0.9 Salutes, Mike Nick Ryan escribis: The static route you'll need to add will be for your internal lan eg:

Re: ntpd could not parse pool.ntp.org

2005-08-17 Thread Nick Ryan
Congratulations!! I don't know what else we can try with getting dns lookups to work on your openbsd box. We've: Checked /etc/resolv.conf --this should have been the likely cause Checked /etc/hostname.rl1 and rl0 --subnets are ok Checked /etc/mygate --this is the adsl router IP Checked

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Mike Henker
Hi Nick Greg I was testing all the steps but the problem (and remember I m a newbie and perhaps I m wrong) I think is because the firewall can t see Internet (exactly the rl1 card with ip 192.168.0.9). I tried differents options in resolv.conf 1) The one you said (192.168.0.1 is the gateway

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Mike Henker
Ok Nick, ckecking all what you said step by step: Can you put your /etc/resolv.conf file back to the one with the ISP's dns servers in it first. Changed to: lookup file bind name server 194.224.52.6 name server 194.224.52.4 Can you confirm if you've got pf enabled or not and if you do can

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Arnaud Bergeron
On 8/16/05, Mike Henker [EMAIL PROTECTED] wrote: Ok Nick, ckecking all what you said step by step: Can you put your /etc/resolv.conf file back to the one with the ISP's dns servers in it first. Changed to: lookup file bind name server 194.224.52.6 name server 194.224.52.4 Can

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Nick
That all looks fine. Ping isn't really a great test of network connectivity outside of your own lan anymore. Most sites tend to block ping nowadays as a matter of course. What you can do is usually ping your ISP's router and you can find this from a traceroute www.google.com command - the

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Mike Henker
Just something that has been bugging me: are you trying to ping http://www.google.com; or www.google.com. Arnaud I ping always www.google.com or www.openbsd.org and the answer is always the same: ping: unknown host: www.google.com I wrote the http:// for to ilustrate better Im trying to

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Mike Henker
Answering all the points: Just type nslookup www.google.com and see what response you get. connection timed out; no servers could be reached One of google's IPs is 66.102.7.99 if you want to test a traceroute. Traceroute works fine with google's IPs (66.102.7.99) but if I do a traceroute

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Diana Eichert
ok, so pinging the IP number works AOK. as a root equivalent run pfctl -vsall and post the results, yes I know you said PF was disabled. have you deleted the /etc/resolv.conf file and recreted it with only the info you need? g.day

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Mike Henker
Hi Diana, and welcome to the Firewall Nightmare... as a root equivalent run pfctl -vsall and post the results, yes I know you said PF was disabled. Nothing appears have you deleted the /etc/resolv.conf file and recreted it with only the info you need? Yes I did it some days ago.

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Nick Ryan
The static route you'll need to add will be for your internal lan eg: 192.168.1.0 netmask 255.255.255.0 gateway 192.168.0.9 This'll tell your adsl router that to get to the 192.168.1. network it needs to go through the 192.168.0.9 interface of your openbsd box. Note this is outside interface IP

Re: ntpd could not parse pool.ntp.org

2005-08-16 Thread Tobias Ulmer
Hmmm imho the dns problem should be solved before routing :) - Mikes internet connection is up and running. He confirmed he can traceroute one of googles ips from the openbsd box. - There is a typo in one of the nameserver ip's posted here. 194.22_5_.52.4 does not exist. - These are the

Re: ntpd could not parse pool.ntp.org

2005-08-15 Thread Mike Henker
I checked the file you said and is correct. I think the problem is what you said because if I do a ping and a messages appears saying ping: unknow host http://www.openbsd.org; Perhaps giving the maximun info will understand better what I want to do. I installed OpenBSD 3.7 I have a router at

[Fwd: Re: ntpd could not parse pool.ntp.org]

2005-08-15 Thread Nick
I forgot to say: You'll need to configure your wife's PC to have a default gateway of 192.169.1.9 and use a dns server of 192.168.0.1 Cheers. Original Message Subject:Re: ntpd could not parse pool.ntp.org Date: Mon, 15 Aug 2005 13:36:09 +0100 From: Nick [EMAIL

Re: ntpd could not parse pool.ntp.org

2005-08-15 Thread Mike Henker
You re right, Im sorry I wrote an error instead of 192.169.1.x I mean 192.168.1.x I know what I want to do, the problem is I don t know how to configurate the firewall: For to ilustrate better the structure is: Router-OpenBSDFirewall-Hub-Intranet Lan (with some machines connected) Looking

Re: [Fwd: Re: ntpd could not parse pool.ntp.org]

2005-08-15 Thread Greg Thomas
On 8/15/05, Nick [EMAIL PROTECTED] wrote: OpenBSD has a steep learning curve but it's a great system once you've learnt a bit. (The mailing list can be a bit vicious though.) Whether OpenBSD has a steep learning curve or not is irrelevant as this issue is almost a pure networking one. It

Re: ntpd could not parse pool.ntp.org

2005-08-14 Thread Chris Kuethe
Show us your config file. My guess is you have a line that says pool.ntp.org l in there, when the correct syntax is servers pool.ntp.org On 8/14/05, Mike Henker [EMAIL PROTECTED] wrote: Hi, a message appears all the time saying: ntpd could not parse pool.ntp.org I dont know the reason why it

Re: ntpd could not parse pool.ntp.org

2005-08-14 Thread Mike Henker
Hi Chris, exactly what s the name of the file where I must to look? Salutes, Mike Chris Kuethe escribis: Show us your config file. My guess is you have a line that says pool.ntp.org l in there, when the correct syntax is servers pool.ntp.org On 8/14/05, Mike Henker [EMAIL PROTECTED] wrote:

Re: ntpd could not parse pool.ntp.org

2005-08-14 Thread Tobias Ulmer
Mike Henker schrieb: Hi Chris, exactly what s the name of the file where I must to look? Salutes, Mike /etc/ntpd.conf Tobias

Re: ntpd could not parse pool.ntp.org

2005-08-14 Thread Lars Hansson
On Sun, 14 Aug 2005 10:51:05 +0200 Mike Henker [EMAIL PROTECTED] wrote: Hi, a message appears all the time saying: ntpd could not parse pool.ntp.org I dont know the reason why it appears and how to solve this doubt. Unless you have changed the configuration yourself I would say it's a