/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
Jon Etkins <[EMAIL PROTECTED]> wrote:
>
> When I issue an ipfwadm -I (or -O or -F) -l command, the output freezes
> whenever it gets to an entry that references my internal network
> (192.168.0.0/24).
That makes sense. It wants to lookup that IP address, and if your local
name server and/or host file doesn't have an entry, it'll take a while
for the nameservers to figure that out.
> Appending the -n parameter, to force it to show numeric addresses
> only, cures the delay
I find that I always use the -n parameter, because I hate to wait. :)
> It this working as designed? It doesn't seem right to me.
Why doesn't it seem right? How does the ipchains program know if the
address referred to is supposed to be a network address or a host
address? It just blindly looks it up.
You *should* have all local network addresses resolved locally, anyway.
Why bother the internet with reverse-lookups for YOUR local network IP's?
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Nothing takes the taste out of peanut
sometimes known as David DeSimone || butter quite like unrequited love."
http://www.dallas.net/~fox/ || -- Charlie Brown
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
