Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Sep 2007 08:33:02 -0700 (PDT)
From:      Joe <josepha48@yahoo.com>
To:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   natd / ipfw services on internal interface
Message-ID:  <114394.51652.qm@web34611.mail.mud.yahoo.com>

next in thread | raw e-mail | index | archive | help
I figured out what the problem was.  I had compiled my dhcp server with USE=
_SOCKETS and am NOT running in a jail.

After a lot of searching the bug reports I came across an old bug that said=
 that USE_SOCKETS was added for jailed dhcp servers, because they do not ha=
ve access to bpf.  It also said that compiling USE_SOCKETS into a non jaile=
d dhcp server will have unpredictable results.

I found out that the server will behave badly like it is being sent through=
 nat out our the wrong port.  =20

&gt; You should specify more information about your setup, but generally yo=
u=20
&gt; should be able to just insert a rule like &quot;ipfw add xxx allow ip =
from=20
&gt; mynet/mask to mynet/mask&quot;, where &quot;xxx&quot; is the rule-numb=
er BEFORE your=20
&gt; natd redirection rule-number and mynet/mask describes your internal ne=
twork.=0A=0A=0A       =0A__________________________________________________=
__________________________________=0AMoody friends. Drama queens. Your life=
? Nope! - their life, your story. Play Sims Stories at Yahoo! Games.=0Ahttp=
://sims.yahoo.com/  



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?114394.51652.qm>