Some time in the recent past Lowell Gilbert scribbled:
> Josh Brooks <[EMAIL PROTECTED]> writes:
>
>> > Have you tried something like:
>> >
>> > add 01000 fwd 10.10.10.10,5050 tcp from any to 10.10.10.10 50
>>
>>
>> When I do this, I get:
>>
>> ipfw: getsockopt(IP_FW_ADD): Invalid argumentipfw:
>>
Josh Brooks <[EMAIL PROTECTED]> writes:
> > Have you tried something like:
> >
> > add 01000 fwd 10.10.10.10,5050 tcp from any to 10.10.10.10 50
>
>
> When I do this, I get:
>
> ipfw: getsockopt(IP_FW_ADD): Invalid argumentipfw: getsockopt(IP_FW_ADD):
> Invalid argument
>
>
> Any ideas ? Is
> Have you tried something like:
>
> add 01000 fwd 10.10.10.10,5050 tcp from any to 10.10.10.10 50
When I do this, I get:
ipfw: getsockopt(IP_FW_ADD): Invalid argumentipfw: getsockopt(IP_FW_ADD):
Invalid argument
Any ideas ? Is there any reason why port forwarding with ipfw is special
and
>
> Hello,
>
> I want to perform a very simple act:
>
> All traffic going to 10.10.10.10 port 50
> should go to
> 10.10.10.10 port 5050
>
> That's it. The trick is, I am _not_ interested in running NAT. This is
> not some cable modem or laptop splitting my DSL service - this is a
> rackmoun
Hello,
I want to perform a very simple act:
All traffic going to 10.10.10.10 port 50
should go to
10.10.10.10 port 5050
That's it. The trick is, I am _not_ interested in running NAT. This is
not some cable modem or laptop splitting my DSL service - this is a
rackmount firewall on a re
