> I've seen some conversation about portfw vs autofw and downloaded Nigels
> redir 0.7 last night. I noticed that redir only does TCP packets. I'm
> wanting to run Myth games, and I'm pretty sure that those use UDP
> packets, so I don't think that solution will work for me. Eventually,
> I'm sure I'm going to have a whole list of ports that I'll just want
> delivered to this ip or that behind the firewall, and I'm sure it'll be
> mixed traffic (TCP and UDP). What is the solution of choice?
I personally use ipportfw. It sets up the forwarding rules, and
terminates, so it's ideal for an rc script (I choose rc.local
myself). No programs eating up memory. Here's the help for it:
As you can see, it does tcp and udp. I forward tcp port 1000 of my
firewall box to 23(telnet) on the box I actually use. The rule for
that is rather simple.
ipportwf -A -t 208.144.137.28/1000 -R 192.168.1.3/23
I don't know for certain about port range capabilities, but others
have talked about doing it. (I.E. forwarding box 1000-2000 ->
dest. machine ports 1-1000).
One important item of note. ipportfw seems to only work from
*outside* the firewall in, so it may be unsuitable for http(assuming
you want to access the same pages from inside the firewall as
outside). However, for things such as ftp and telnet, it's worked
like a charm
-----------------------------------------------------------------------
Usage: /sbin/ipportfw -A -[t|u] l.l.l.l/lport -R a.a.a.a/rport add entry
/sbin/ipportfw -D -[t|u] l.l.l.l/lport delete entry
/sbin/ipportfw -C clear table
/sbin/ipportfw -L list table
l.l.l.l is the local interface receiving packets to be forwarded.
a.a.a.a is the remote address.
lport is the port being redirected.
rport is the port being redirected to.
------------------------------------------------------------------
--
Innocent Bystander([EMAIL PROTECTED]). Finger me for PGP Key
bait: [EMAIL PROTECTED],[EMAIL PROTECTED],admin@localhost
