As soon as the payment clears and the account is active on https://portal.pfsense.org/members/ you can reach the book.

If the pfSense team is in on this one , you could make a "recovery-xonfig.xml" in the script , and on boot check if it exists. If it exists : use that one (and delete it after boot) , else use normal config.xml. And then just a : reload in xx minutes entry in the menu - making the revovery-config.xml , and the at now+xx (reboot) And a reload cancel , that deletes the revovery-config.xml , and kills the at job I don't know the "inners" of pfsense , and don't know if it goes "crazy" if the config.xml gets replaced , but i'm sure the team could make this in a short time. /Bingo

Good recommendation, will try. I suspect it will be faster, as I did get about 3-5mb faster when I swapped out the AC adapter for the on-board N adapter. This led me to believe that it had something to do with that NIC and that it was somehow tied to the MAC of that NIC. I was wondering if there was somewhere in pfSense that I could find that it's blocked or throttled by the MAC/IP. I'll grab a cable and test though…just to see. Thanks, Randy

mattyd, thanks for all the help. I changed my LAN to use 172.xx.xx.xx ip and that resolved the issue. You were right the fact that both the VPN and LAN were using 10.x.x.x IPs was the problem. Much appreciated.

But is it possible to do a reverse ssh tunnel to be able to manage the firewall rather than using openvpn?

Hi Techies, Please help me here. Thank you for time in advance.

Thanks for the feedback. Yes, the upstream switch is VLAN capable and I have no management access to it.  I've used VLAN in the past on another network but that was on Cisco switches and internal to the network (no firewall involvement).  Looks like I need to play with the interfaces area of pfsense a little to develop a feel for it.

have you viewed some of these?: https://doc.pfsense.org/index.php/How_can_I_monitor_bandwidth_usage

I219_V should be supported by anything 2.3 or newer though: https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_3/sys/dev/e1000/if_em.c#L189 So if yours is not recognised it's not that NIC or it's some new variant with a different PCI device ID. pciconf -lv will show that though. #define E1000_DEV_ID_PCH_SPT_I219_V 0x1570 /* Sunrise Point PCH */ Steve

Okay, I found what was screwing me up… Whilst thinking about something completely different, I realised I had Squid Proxy Server running in pfSense. Turning off Squid fixed the issue, I'll have to try and reconfigure that for VLANs later when I have more time.

OK, I believe I am at the last state of building the iso. Please help what's wrong, I am getting this error.. _====>> Compressing kernel Cloning everything to /usr/MYPRODUCT/tmp/stage-dir staging area…mv: rename /usr/MYPRODUCT/tmp/stage-dir/usr/local/sbin/pfSense-upgrade to /usr/MYPRODUCT/tmp/stage-dir/usr/local/sbin/MYPRODUCT-upgrade: No such file or directory mtree: /usr/MYPRODUCT/tmp/stage-dir/var: No such file or directory ====>> Copying metadata for package rc ====>> Creating core package rc pkg: Unable to access file /usr/MYPRODUCT/tmp/stage-dir/etc/rc:No such file or directory ====>> ERROR: Execution of 'pkg create -o /usr/MYPRODUCT/tmp/MYPRODUCT_master_amd64-core/.real_20170704-0418/All -p /tmp/rc.fBwqdvV/rc_plist -r /usr/MYPRODUCT/tmp/stage-dir -m /tmp/rc.fBwqdvV/rc_metadir' failed (rc = 70) ====>> Removing immutable flags from /tmp/rc.fBwqdvV ====>> Removing recursively /tmp/rc.fBwqdvV #################################### Something went wrong, check errors! ####################################_

Ah there we go, it was just the firewall rules. Didn't seem to need any special outbound rules in pfsense or anything special with openwrt. I just used these rules below and all is well.First one is a bit redundant, but I'll leave it since it doesn't hurt. Thanks for the help! EDIT: I just realized, since they can both access each other, I wonder if they will compete for DHCP… more testing to do. EDIT2: I have multiple access points across the house(wired), and they are all connected to pfsense, so my laptop will get a 192.168.1.x ip. I move towards the area with the wrt1200ac(which has the same name/login as the other ap/s) and the laptop's ip changes to a 192.168.2.x ip and everything works seamlessly. I go back to the other side and the ip changes back to  192.168.1.x with pretty much no interruptions. I'm surprised it works so well. So far I have not see any other type of DHCP competition for the wired computers or anything like that. [image: capture3.PNG_thumb] [image: capture3.PNG]