On 10/15/05, Bill Marquette <[EMAIL PROTECTED]> wrote:
Thank you for your reply.
I am trying to run p3scan on pfsense, but it needs a redirection done with ipfw... When I am trying to add the rule, I have the following error:
# ipfw add fwd 127.0.0.1:8110 tcp from 10.0.0.0/24 to any 110
ipfw: getsockopt(IP_FW_ADD): Invalid argument
When I am loading ipfw module, I see the following in dmesg:
ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging disabled
Does this mean that I cannot do forwarding with this ipfw?
TIA
Tom
Not sure I follow with the "redirection" part. But if I understand
correctly, yes we can use both ipfw and pf in conjunction for
different tasks. This is how our shaper code used to work - define
the queues in PF and assign the traffic in IPFW. Our ultimate goal is
to get IPFW out of the core system altogether and we had done that
until we found some nasty bugs in CP due to it (just stuff that'll
take a little longer to work around).
I am trying to run p3scan on pfsense, but it needs a redirection done with ipfw... When I am trying to add the rule, I have the following error:
# ipfw add fwd 127.0.0.1:8110 tcp from 10.0.0.0/24 to any 110
ipfw: getsockopt(IP_FW_ADD): Invalid argument
When I am loading ipfw module, I see the following in dmesg:
ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging disabled
Does this mean that I cannot do forwarding with this ipfw?
TIA
Tom
