dude this is really clickity clickity there is nothing special to do in pfsense to allow for remote webgui access.  It by default listens on all ports, you just have to enable wan rule to allow it. You sure your not trying to redirect http to https?  Please post your firewall rules, your gui settings and your not behind a nat right??  You don't have any sort of vpn client access setup on pfsense do you?  Your not trying to route traffic through a vpn or anything. The only thing required to enable remote webgui access is firewall rule on the wan to allow access to the port..  I currently show 53 and 80 open.. If your trying to redirect 80 to 443 its not showing open. Please post the output of sockstat..  And your gui setup section – its just listed as http right??

This was already discussed before - https://forum.pfsense.org/index.php?topic=55454.0 If you looking for a central management feature, there's not one (yet).

I run a cron job to backup my config.xml to a local ftp server. Example below: #!/bin/sh cd /conf cat <<end |="" ftp="" 'ftp:="" login:password@ftp.server.com="" backup'<br="">put ./config.xml END To restore, just run a manual ftp session to the backup server and pull down the last good config, removing the package info as jimp suggests.</end>

Well why don't just fix your asymmetric routing.. Simple enough to do with a transit network. Why don't you draw your network - drawing is worth a 1000 words as they say.

Please file a bug about the spamd thing before it gets forgotten… This is insane. Found ~3 GiB worth of crap here after a couple of test installs. https://redmine.pfsense.org/issues/5231 https://github.com/pfsense/pfsense-packages/pull/1086

Found it, Modem Card was in slot 1 and for access to the sim card it has to be in slot 2 i didn't read the manual  :-[

@johnpoz: I don't see why you couldn't just create your manual outbound nats to distribute your lan space across your public IP space. If you can do ipv6 - do that, now every client could have their own public IP and you have no need to nat anything. There is a feature in pfSense to add an address pool on the wan side and various methods for distributing this to LAN (via NAT), round robin sounds like a good option.  But how that works (or doesn't work) with ipv6 I do not know. Ipv6 is fine for computer clients, but some consoles, like the Xbox 360 doesn't do ipv6. Currently 17 people join with 360s, some other older consols include the Wii (7 people), PS3 (29 people). Haven't checked them for ipv6 support. @dreamslacker: @heper: why'd you want 200 public ip's ? 600 users can run on far less then 16gb of ram. Some games will not allow you to host more than a certain number of servers on a single IP. E.g. Battlenet (Warcraft 3) has a limit of 6 game hosts per IP last I tried. If this is a big event, or a publicized event with hosted streaming servers, I'd be far more concerned about DDoS attacks on the main line(s) than whether pfSense can hold up to the load from the clients. A decent Core-i quad core with 8GB of ram will probably be more than sufficient just for the load. Repelling DDoS is another issue on its own. That's old-school Battle.net, the new one has no IP limitations (according to a battle.net forum).

State of… hmmm, what? The widget uses: $dev_state = trim(exec("smartctl -H /dev/$dev | awk -F: '/^SMART overall-health self-assessment test result/ {print $2;exit} smartctl -H is notoriously unreliable/useless (not exactly the widget fault).

The interfaces assign prompt should only be triggered if you remove an interface. If it run if, when the config file is parsed, it has references to interfaces that are no longer present in the system. This is a problem, as you say, for newer 4g devices that appear as USB Ethernet devices. Using MAC addresses is often not a viable solution. They can be spoofed but more importantly they often do not correctly provide a MAC to the OS and use a randomly generated one leading to much confusion! Some 4G devices can be reconfigured to use a PPP interface which has no problem with disappearing hardware. You could add the usb ethernet type to the list of interfaces that are not parsed at boot (VLANs, QinQ etc).  Hard to say quite how that might affect things if you have other interfaces though. Steve

1/ But it didn't work is not a useful problem description. 2/ Perhaps it would work better with actually maintained, uptodate pfSense version. The permission name is here: https://github.com/pfsense/pfsense/blob/RELENG_2_1/usr/local/www/status_rrd_graph.php#L36 - traffic shaping certainly has nothing to do with this.

memtest Not to say it couldn't be a bug, but it would need to be an issue with FreeBSD, which would be highly unlikely to only affect you. In case you haven't done this, my rule of thumb is before I use a system, I give it 2-3 days of burn-ins. Almost a week before I actually start using my machines.

@Derelict: Draw your network.  It'll probably be obvious if you do that. Thats the problem…  Both networks are very simple...  Flat networks, only one switch, both have identically configured pfSense routers. My hard-wired machine has the ip: 10.1.2.100.  My laptop (wireless) has the IP 10.1.2.101.  Desktop can access the NAS, laptop can't.  If I attach the laptop to the switch, and even use the same IP it works. This is why I think it's my Wireless AP, but there's nothing special there either.  It's a Rucks Wireless 7363, nothing strangely configured.  I have another AP here that I can swap out and test.

@doktornotor: You won't expose anything in the first place unless you allow UDP/123 access on WAN. Consider it to be an option flaw if the WAN selection does not establish the necessary rules.

Glad that it works. ;)

Ok, so I left PFSense connected to my ISP router all night. Today I go check on it and its working. Most likely it was PFSense taking 2 centuries to update the routing table. Thank you to everyone with their tips even though we didn't achieve the intended result :)