On Fri, 31 Oct 2014 18:28:28 -0700, Freddie Cash wrote:
> On Oct 31, 2014 12:12 PM, "John-Mark Gurney" wrote:
> >
> > Can any one think of a good reason not to enable IPDIVERT sockets in
> > the ipfw module?
Yes, two. Nowadays people are just as or perhaps mo
On Oct 31, 2014 12:12 PM, "John-Mark Gurney" wrote:
>
> Can any one think of a good reason not to enable IPDIVERT sockets in
> the ipfw module?
>
> And possibly enabling default to accept? That way you don't have to
> go to the console when you load the ipfw mo
John-Mark Gurney wrote this message on Fri, Oct 31, 2014 at 12:12 -0700:
> Can any one think of a good reason not to enable IPDIVERT sockets in
> the ipfw module?
sorry, ignore this... didn't realize ipdivert was loadable as a
separate module, ipdivert...
--
John-
Can any one think of a good reason not to enable IPDIVERT sockets in
the ipfw module?
And possibly enabling default to accept? That way you don't have to
go to the console when you load the ipfw module because you forgot to
auto add the accept all rule? :)
something like:
//depot/pro
hi, there!
I would like to add IPDIVERT option to GENERIC kernels on all
platforms and to CFLAGS for ipfw module.
This will allow using natd out of box.
I'll commit this change by the end of this week if there will be no objections.
Regards,
68.0.99
>
> I have a win2k server at 192.168.0.1
>
> I want to route telnet service on .99 to .3
> that means if you telnet from .1 to .99 the laptop answers on 3
>
> This feature requires ipfw/natd and I have made a kernel for this (IPFIREWALL,
> IPDIVERT)
>
> I d
telnet from .1 to .99 the laptop answers on 3
This feature requires ipfw/natd and I have made a kernel for this (IPFIREWALL,
IPDIVERT)
I don´t know how to continue, i tried this on the bsd server:
/sbin/ipfw -f flush
/sbin/ipfw add divert natd all from any to any via ed0
/sbin/ipfw add pass all from
kernel
> with all those options just to make sure it's not just me.
>
> -Alfred
>
> > > Let me apologize in advance for this shoddyish bug report.
> > >
> > > In a recent -stable (since the new ipfw fixes) if you build
> > > a kernel with
ce for this shoddyish bug report.
> >
> > In a recent -stable (since the new ipfw fixes) if you build
> > a kernel with options:
> >
> > IPFIREWALL
> > IPFIREWALL_VERBOSE
> > IPFIREWALL_DEFAULT_TO_ACCEPT
> > IPDIVERT
> > BRIDGE
> > DUMMYNET
&g
the new ipfw fixes) if you build
> a kernel with options:
>
> IPFIREWALL
> IPFIREWALL_VERBOSE
> IPFIREWALL_DEFAULT_TO_ACCEPT
> IPDIVERT
> BRIDGE
> DUMMYNET
>
> You wind up with a kernel that doesn't grok the ipfw 'via' keyword.
>
> Basicall
Let me apologize in advance for this shoddyish bug report.
In a recent -stable (since the new ipfw fixes) if you build
a kernel with options:
IPFIREWALL
IPFIREWALL_VERBOSE
IPFIREWALL_DEFAULT_TO_ACCEPT
IPDIVERT
BRIDGE
DUMMYNET
You wind up with a kernel that doesn't grok the ipfw 'vi
11 matches
Mail list logo