On 10/16/05, Tommaso Di Donato <[EMAIL PROTECTED]> wrote: > On 10/15/05, Bill Marquette <[EMAIL PROTECTED]> wrote: > > > > 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). > > 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?
Module probably isn't loaded (it's only loaded if CP is in use I believe). Any reason you wouldn't just create a port forward for this? Seems like what you want to do is forward any traffic from 10.0.0.0/24 destined to port 110 anywhere to localhost on port 8110 (transparent pop3 server? interesting). This can be done easily in our GUI, just use a port forward (it was renamed from "Inbound NAT" to try and remind people it can be used in either direction). --Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
