Yes, "That did the trick" means problem solved ;)

The short cut to the answer is here: http://forum.pfsense.org/index.php/board,23.0.html
ONE line above YOUR question is the answer you were looking for ;D It's a sticky since 2006..

Ok, switching to RELENG_2_0, ditching master for now.
I have to sync my (live) pfsense box also (means somewhat downgrading) with this code to get a sane setup.

Thanks for the fast answer ^^

Ah, how simple. Thank you, that was exactly what I needed.

Piplfox-  13.10.1.0/8 is a routable public address and shouldn't be used on LAN unless your the user of that subnet…  It has the possibility of causing you problems.

http://www.noah.org/wiki/Private_LAN_IP_addresses

Heres a screenshot of the rule on my test box...  I use a nonstandard port on my production boxes...

as pointed out already...  You should have no port forwarding turned on for this rule.

WanRule.JPG
WanRule.JPG_thumb

Nice!!! good deal there sir. That would of course make my life much simpler…instead of mocking up a lab and having to do all the leg work to redo 254 Ip's, hundreds of Port & IP Aliases, rules and such...were going to try this this weekend before we try to do a full rebuild :) you rock man and thanks a TON for the advice.... :P

You said: The issue is when I try to set the gateway for the WAN interface using the webGUI "add gateway"

I do not understand that part.

As soon as a WAN interface is set up (Interface => Assign) and it's UP (Status=> Interfaces) it will be listed in Status => Gateway.

I'm not able to add a gateway using Interfaces => WAN - WAN is a gateway.

Btw: I have only one WAN interface, do you have more then one ?

Looks like it's having trouble reading files from the drive, files that should be there in any working installation.

I would suspect that your hdd/cf/whatever storage you have is failing.

Thanks!

If I can do anyhing to help I'd be happy to be of any assistance.

Use the port 465 and it works :)

@jimp:

Should work fine. Once we post images for 2.0.1 they are sized to 1000's instead of 1024 so they'll fit again.

Okay, that sound's nice. I will change the image until 2.0.1 will be released. its working like a charm right now :-)

Hi !

@packets:

…. Maybe this is a bug on RC.

Maybe it's time to shift to Release  ;)

@jimp:

It's been fixed in the repo already.

Code is available on github.

Thanks for the fast reply.
I was pretty sure that the missing ? was fixed already, I just couldn't find my way to  github.

Not sure anyone is actively working on that. someone on the forum had some graphing working. not sure anyone submitted patches.

Looked once, didn't find it. Found it the second time… Thanks :)
(For anyone else: http://doc.pfsense.org/index.php/Remote_Config_Backup )

thanks for the reply jimp  ;D

Good news then :-)

If you set nonstandard port while using https, then you should use that same port, but you'll need to use http

and as marcelloc said assigning interfaces on console is the key to revert gui to http

You are correct of course, that would be the best way to do it.
(in my defense, I wrote the first post at 3:00am local time  ;D )