Actually I neglected to mention I also have this rule:

# Allow all traffic from internal lan
$fwcmd add allow all from 192.168.0.0/16 to any

This should take care of ANY traffic from my internal lan, including DNS requests from my machines to the nameservers, no?


From: Simon1 <[EMAIL PROTECTED]>
To: C KH <[EMAIL PROTECTED]>
CC: <[EMAIL PROTECTED]>
Subject: Re: Can't connect to DNS servers -- Firewall prob?
Date: Tue, 29 Oct 2002 13:57:08 -0500 (EST)

Make sure your box has permission to connect /to/ these systems. The rules
below allow the DNS servers to send things *to* your box, but don't allow
your box to send things TO those servers. You need to give
your box the ability to send the request /out/ to them in the first place.

The hostname hangup is due to it trying to resolve the domain. Once you
get the DNS resolving that problem will disappear.


> I have explicitly added these rules to my /etc/rc.firewall:
>
> $fwcmd add allow udp from 66.135.144.2 53 to $oip
> $fwcmd add allow udp from 66.135.128.68 53 to $oip
> $fwcmd add allow tcp from 66.135.144.2 53 to $oip
> $fwcmd add allow tcp from 66.135.128.68 53 to $oip
>
> (where $oip is my external IP address).
>
> Another possibly related thing is that on bootup, my server hangs
> indefinitely as the initializing "hostname" part. I need to hard break it
> with CTRL+C to continue bootup.

_________________________________________________________________
Get faster connections -- switch to MSN Internet Access! http://resourcecenter.msn.com/access/plans/default.asp


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Reply via email to