Re: NATd error Message

2004-03-25 Thread Kevin D. Kinsey, DaleCo, S.P.
JP wrote:

--- "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]>
wrote:
 

JP wrote:

   

Hey Gang--

I recompiled my kernel to include support for
 

firewall
   

and such.  



 

OK, we kinda know what you mean.  So I'll kinda
give you an answer.  You kinda did something
wrong ;-)
Seriously, exactly what did you add to your kernel
config?
   

After creating my rules file, fwrules and
rebooting this is the error I am getting:
natdnatd: Unable to create divert socket.  Protocol
not supported
Can someone explain whats wrong?

Thanks



 

I'm guessing that either you didn't add

   options IPDIVERT

  to your kernel, or your didn't do
gateway_enable="yes" in /etc/rc.conf.
If the latter is the case, try issuing

   #sysctl net.inet.ip.forwarding=1

  and then try natd.

HTH,

Kevin Kinsey
DaleCo, S.P.
   

*grin*  I added the following to my kernel:

options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=100
options IPDIVERT
 

And, did you see the second part of my
message, you top-poster, you ? ;-)
KDK

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: NATd error Message

2004-03-25 Thread JP
*grin*  I added the following to my kernel:

options IPFIREWALL
options IPFIREWALL_VERBOSE
options IPFIREWALL_VERBOSE_LIMIT=100
options IPDIVERT

--- "Kevin D. Kinsey, DaleCo, S.P." <[EMAIL PROTECTED]>
wrote:
> JP wrote:
> 
> >Hey Gang--
> >
> >I recompiled my kernel to include support for
> firewall
> >and such.  
> >
> >
> >  
> >
> 
> OK, we kinda know what you mean.  So I'll kinda
> give you an answer.  You kinda did something
> wrong ;-)
> 
> Seriously, exactly what did you add to your kernel
> config?
> 
> >
> >After creating my rules file, fwrules and
> >rebooting this is the error I am getting:
> >
> >natdnatd: Unable to create divert socket.  Protocol
> >not supported
> >
> >Can someone explain whats wrong?
> >
> >Thanks
> >
> >  
> >
> 
> I'm guessing that either you didn't add
> 
> options IPDIVERT
> 
>to your kernel, or your didn't do
> gateway_enable="yes" in /etc/rc.conf.
> 
> If the latter is the case, try issuing
> 
> #sysctl net.inet.ip.forwarding=1
> 
>and then try natd.
> 
> HTH,
> 
> Kevin Kinsey
> DaleCo, S.P.


__
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: NATd error Message

2004-03-25 Thread Kevin D. Kinsey, DaleCo, S.P.
JP wrote:

Hey Gang--

I recompiled my kernel to include support for firewall
and such.  

 

OK, we kinda know what you mean.  So I'll kinda
give you an answer.  You kinda did something
wrong ;-)
Seriously, exactly what did you add to your kernel
config?
After creating my rules file, fwrules and
rebooting this is the error I am getting:
natdnatd: Unable to create divert socket.  Protocol
not supported
Can someone explain whats wrong?

Thanks

 

I'm guessing that either you didn't add

   options IPDIVERT

  to your kernel, or your didn't do
gateway_enable="yes" in /etc/rc.conf.
If the latter is the case, try issuing

   #sysctl net.inet.ip.forwarding=1

  and then try natd.

HTH,

Kevin Kinsey
DaleCo, S.P.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


NATd error Message

2004-03-25 Thread JP
Hey Gang--

I recompiled my kernel to include support for firewall
and such.  After creating my rules file, fwrules and
rebooting this is the error I am getting:

natdnatd: Unable to create divert socket.  Protocol
not supported

Can someone explain whats wrong?

Thanks

__
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"