Re: ntpd could not parse "pool.ntp.org"

2005-08-17 Thread C. Bensend
{blah} machines has the IP 192.168.1.20 for example) can t exit to Internet >>> >>> >>> You have 192.168.1.x in that last sentence but 192.169.1.x up >>> above. >>> I assume you mean: >>> >>> 192.168.1.2

Re: ntpd could not parse "pool.ntp.org"

2005-08-17 Thread Nick Ryan
ame.rl0 files. hostname.rl0 inet 192.168.1.3 255.255.255.0 NONE hostname.rl1 inet 192.168.0.9 255.255.255.0 NONE > Can you also confirm the subnet mask on your adsl router's 192.168.0.1 > address ( it'll probably be something like 255.255.255.0) Yes I can confirm you the subne

Re: ntpd could not parse "pool.ntp.org"

2005-08-17 Thread Mike Henker
r /etc/mygate file. 192.168.0.1 > Can you confirm the contents of your /etc/hostname.rl1 and > /etc/hostname.rl0 files. hostname.rl0 inet 192.168.1.3 255.255.255.0 NONE hostname.rl1 inet 192.168.0.9 255.255.255.0 NONE > Can you also confirm the subnet mask on your adsl router'

Re: ntpd could not parse "pool.ntp.org"

2005-08-17 Thread Mike Henker
; Can you confirm the contents of your /etc/mygate file. 192.168.0.1 > Can you confirm the contents of your /etc/hostname.rl1 and > /etc/hostname.rl0 files. hostname.rl0 inet 192.168.1.3 255.255.255.0 NONE hostname.rl1 inet 192.168.0.9 255.255.255.0 NONE > Can you also conf

Re: ntpd could not parse "pool.ntp.org"

2005-08-17 Thread Mike Henker
tents of your /etc/hostname.rl1 and > /etc/hostname.rl0 files. hostname.rl0 inet 192.168.1.3 255.255.255.0 NONE hostname.rl1 inet 192.168.0.9 255.255.255.0 NONE > Can you also confirm the subnet mask on your adsl router's 192.168.0.1 > address ( it'll pr

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<-- > Pl

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 nslo

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 name

Re: ntpd could not parse "pool.ntp.org"

2005-08-16 Thread Nick Ryan
e.rl1 inet 192.168.0.9 255.255.255.0 NONE > Can you also confirm the subnet mask on your adsl router's 192.168.0.1 > address ( it'll probably be something like 255.255.255.0) Yes I can confirm you the subnet mask is 255.255.255.0 From the firewall with these setting I can ping 1

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 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
and > /etc/hostname.rl0 files. hostname.rl0 inet 192.168.1.3 255.255.255.0 NONE hostname.rl1 inet 192.168.0.9 255.255.255.0 NONE > Can you also confirm the subnet mask on your adsl router's 192.168.0.1 > address ( it'll probably be something like 255.255.255.0) Yes I can c

Re: ntpd could not parse "pool.ntp.org"

2005-08-16 Thread Mike Henker
confirm you the subnet mask is 255.255.255.0 From the firewall with these setting I can ping 192.168.0.1 but cannot ping for example http://www.google.com Just something that has been bugging me: are you trying to ping "http://www.google.com"; or "www.google.com". It's

Re: ntpd could not parse "pool.ntp.org"

2005-08-16 Thread Nick
27;s 192.168.0.1 > address ( it'll probably be something like 255.255.255.0) Yes I can confirm you the subnet mask is 255.255.255.0 From the firewall with these setting I can ping 192.168.0.1 but cannot ping for example http://

Re: ntpd could not parse "pool.ntp.org"

2005-08-16 Thread Arnaud Bergeron
all with these setting I can ping 192.168.0.1 but cannot > ping for example http://www.google.com Just something that has been bugging me: are you trying to ping "http://www.google.com"; or "www.google.com". It's just because the frist one will never work. > &

Re: ntpd could not parse "pool.ntp.org"

2005-08-16 Thread Mike Henker
an confirm you the subnet mask is 255.255.255.0 From the firewall with these setting I can ping 192.168.0.1 but cannot ping for example http://www.google.com If it can help the past message that appears the past days saying: ntpd could not parse "pool.ntp.org" doesnt appear now

Re: ntpd could not parse "pool.ntp.org"

2005-08-16 Thread Nick
It's definitely a DNS issue, although it should be working as your resolv.conf file looks good. Can you check a few things please? Can you put your /etc/resolv.conf file back to the one with the ISP's dns servers in it first. 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 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 gatewa

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.

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

[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

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 a

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 yo

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 Mike Henker
er <[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. Salutes, Mike

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 "

ntpd could not parse "pool.ntp.org"

2005-08-14 Thread Mike Henker
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. Salutes, Mike