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 PROTECTED]>
To:     Mike Henker <[EMAIL PROTECTED]>
References:     <[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]> 
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>



Mike,

There's a few things to do and  I thought I'd get in early before you 
got answers like read the man pages...

It looks like your openbsd box isn't doing DNS lookups. You'll need to 
correct this by editing /etc/resolv.conf to have your adsl 
router in it - eg:

lookup file bind
nameserver 192.168.0.1

This'll sort your ntp problem out as it'll now lookup pool.ntp.org 
properly. Test DNS lookups by either using:
lynx news.bbc.co.uk OR
nslookup news.bbs.co.uk

If these fail, start troubleshooting - it could be that the nameserver 
needs to be the IP of your ISP's DNS servers - these can usually be 
found on their support website.

Next to get your packets routing properly you'll need to either:

Add a route on your adsl router to point the 192.168.1.0 255.255.255.0 
network to the 192.168.0.3 interface on your openbsd box. (recommended)
OR:
use your openbsd box to nat the 192.168.1.0/24 network to its external 
IP of 192.168.0.3 by adding in a couple of lines like:

EXT_IF="rl1"
nat on $EXT_IF from !($EXT_IF) to any -> ($EXT_IF)

Have a look in man pf.conf for details (it's under the Translation 
section). "tcpdump -ni pflog0" and "tcpdump -ni rl1" will help 
troubleshoot network issues on the openbsd box.

Make sure that the /etc/mygate file on your openbsd box has one line in 
it that says:
192.168.0.1
This'll make sure that all packets get diverted to your router.

The problem I think you've got is that your adsl router is receiving 
packets from your wifes PC but doesn't know where that subnet is to send 
packets back. It needs a static route adding in. I'm also assuming your 
adsl router is doing the main network address translation which I'm 
pretty certain is correct as your adsl router has a 192.168.0.1 internal 
IP address.

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.)


Cheers - Nick



Mike Henker wrote:

> 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 home and want to put a firewall between the router 
> and the lan I have at home.
>
> The gateway (on the router is 192.168.0.1)
> The OpenBSD firewall I installed has 2 nerwork cards
> - 192.168.0.3
> - 192.169.1.9
>
> Like the man afterboot says I enabled in /etc/sysctl.conf:
>
>            net.inet.ip.forwarding=1
>
> But seems not to work, because the machines in the intranet (my wife 
> machines has the IP 192.168.1.20 for example) can t exit to Internet
>
> For to verify network interface configuration like the man afterboot 
> says i did ifconfig -a for to see if the network interfaces are 
> properly configured I paste the info:
>
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33224
>    inet 127.0.0.1 netmask 0xff000000
>    inet6 ::1 prefixlen 128
>    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6
> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>    address: 00:50:ba:be:09:35
>    media: Ethernet autoselect (100base TX full-duplex)
>    status: active
>    inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
>    inet6 fe80::250:baff:febe:935%rl0 prefixlen 64 scopeid 0x1
> rl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>    address: 00:60:67:75:ae:e7
>    media: Ethernet autoselect (10baseT)
>    status: active
>    inet 192.168.0.9 netmask 0xffffff00 broadcast 192.168.0.255
>    inet6 fe80::260:67ff:fe75:aee7%rl1 prefixlen 64 scopeid 0x2
> pf log0: flags=0<> mtu 33224
> pf sync0: flags=0<> mtu 2020
> enc0: flags=0<> mtu 1536
>
> I m lost after that point, because I think the network cards are ok 
> plus I enabled in /etc/sysctl.conf: net.inet.ip.forwarding=1
>
> Thanks,
> Mike
>
> ____________________________________________________________________________ 
>
> Chris Kuethe escribis:
>
>> On 8/14/05, Mike Henker <[EMAIL PROTECTED]> wrote:
>>
>>> Hi Chris, exactly what s the name of the file where I must to look?
>>>
>>> Salutes,
>>> Mike
>>
>>
>>
>> /etc/ntp.conf
>>
>> as an aside, you do have working name resolution on that machine,
>> right? can you ping things by name? does "lynx
>> http://www.openbsd.org/"; work?
>>
>> CK

Reply via email to