Hi:
I'm using cookfire RC1 and have been playing with port forwarding to my
internal web server. I have noticed that forwarding works fine if I open all
protocols on the "Users Traffic Filter" page on the web configuration tool.
However, if I restrict ports it doesn't port forward properly anymore. I'm
leaving www port open on tcp (as well as smtp,pop,imap,https) and all ports
on udp. Why is this? I don't really know what ports I should leave open to
allow port forwarding to work, since it's not obvious to me (a relative
dummy) why this is happening in the first place. I wonder if anyone else can
reproduce this and whether this is a "bug" or whether I'm doing something
wrong. If I wanted to leave all the ports open I could just use a dumb NAT
router like coyote or freesco or edge, so I would appreciate any input.
In addition, I've always felt that one of the advantages to the single disk
floppy router-firewall was robustness following power failures. I have a UPS
on my firewall computer but I'm afraid a long outage might result in corrupt
filesystems, as opposed to a floppy router running from a ramdisk. Can
cookfire run from reiserfs to minimize the chance of unrecoverable
filesystem damage? I suppose I could set up a UPS shutdown daemon if I could
find the right serial cable for my UPS, which might not be a bad idea in any
case.
Thanks to all,
John
