Cannot Forward Port range in PFSense 2.0

DeMiNe0 · Dec 24, 2009, 4:20 AM

When I press CTRL+T, it looks to be stuck on "extracting +CONTENTS" If i do CTRL+T again, I get
"load 0.00 cmd : bsdtar 1440 [piperd] 503.47r 630u 0.60s 0% 2320k"

jimp · Dec 24, 2009, 5:06 AM

Hmm, you'd think it would throw an error rather than just stalling

Is this a full install or nanobsd?

DeMiNe0 · Dec 24, 2009, 5:19 AM

This is a full install.

I just did another reinstall of pfsense 2.0, and instead of installing the git package, I went and ran "playback git master". It looks like it ran, but I noticed an error at the end. It scrolled past too fast for me to see. So I'm not sure if I have the latest version yet.

jimp · Dec 24, 2009, 4:17 PM

I guess that depends on the error, really.

It may be better to wait and just upgrade to the next snapshot that comes out (or which has probably come out overnight)

DeMiNe0 · Dec 24, 2009, 4:52 PM

Sounds like a plan. THe snapshot should of come out by now. I'll give that one a shot.

DeMiNe0 · Dec 24, 2009, 6:54 PM

I used the auto updater to update to the latest snapshot, and everything seems to be working fine.

_igor_ · Dec 25, 2009, 11:11 AM

I did that and it worked so like a charm. The only thing I noticed was this:

===> Signaling PHP and Lighty restart…

Warning: Invalid argument supplied for foreach() in /usr/local/sbin/pfSsh.php(334) : eval()'d code on line 261
===> Checkout complete.

Your system is now sync'd and PHP and Lighty will be restarted in 5 seconds.

pfSense shell: Terminated

jimp · Dec 25, 2009, 2:17 PM

igor,

I think that was a bug in a previous snapshot which was fixed since then. I saw that once but haven't seen it again on subsequent gitsync runs.

xbipin · Dec 27, 2009, 3:11 PM

i have port forwarded to lan clients and rules present under wan firewall rules but systemlog keeps reporting this so is it the same thing to with the port forward or something else?

inetd[377]: 28184/udp: unknown service

jimp · Dec 27, 2009, 3:25 PM

That would probably be from NAT reflection.

Try with NAT reflection disabled, if the message goes away and then comes back when you turn NAT reflection on again, it may be worthy of opening a bug report.

xbipin · Dec 28, 2009, 7:05 AM

with nat reflection disabled, the message seems to have gone

cmb · Dec 29, 2009, 1:23 AM

That "unknown service" message was a consequence of a reflection bug that was fixed yesterday.

xbipin · Dec 29, 2009, 6:03 AM

ill test it with the 28th december snapshot