Maybe I answered my own question, but I guess I can NAT all traffic
and then only redirect those ports that need it. I was afraid the the
server that ipfilter is running on won't be able to respond to requests
to it. Such as:
rdr bge0 0.0.0.0/0 port 47111 -> 172.23.66.58 port 47111 tcp
rdr bge0 0.0.0.0/0 port 40385 -> 172.23.66.57 port 40385 tcp
#
map bge0 0.0.0.0/0 -> 172.27.0.58/32
Thanks again for the help,
Karl
Karl Fosburg wrote:
Hi Larry,
I reset everything this morning and it is working using the ftp proxy.
I'm not sure how stable this will be, but it seems to be working and I
will continue to test. Unfortunately, this has crashed my solaris
server twice now - hard down... no console messages even.
I may be wrong in my thinking (which many people
will agree with), but I think that the ftp proxy is working because the
application information passing through it doesn't match any expected
strings and is passing it on a packet for packet basis, just
transforming the source IP address and following the redirect. This is
really all I am looking to do - a straight NAT, but only on one port.
Is there a better way to do this?
Thanks,
Karl
Laurence Moore wrote:
On Thu, 11 Nov 2004, [EMAIL PROTECTED] wrote:
Ah... indeed it had been a long day when I composed my email. Yes, it was supposed to be 47111, not 74111! (dyslexia strikes again) I will take a look at it tomorrow morning first thing.
Thought that might be the case.
Either way, what are the built in proxies available in ipfilter? Obviously, ftp...
The inbuilt proxies for 4.1.3 are ftp, h323, ipsec, irc, netbios, pptp,
real-audio, remote-comand & sun-rpc-bind.
You can find them by performing the following command in the source
directory for IP Filter after you have built the code,
ls ip_*_pxy*
Otherwise look in the netinet directory of the IP Filter source.
You will also find them included in ip_proxy.c.
Cheers,
Larry.
|
