added to all that, Buechler's book is surly talking about 'updates' …. just apply  ;)

You should re-install pfSense completely.
The reason you see the main page only is that you are logged in with a restricted username/password combination which doesn't give you access to all areas, only traffic shaper.
Are you able to download a backup config from it?

What type of hardware are you running this on?

how did you manage to get to 2.2.2 ? the latest stable release = 2.2.4

Good to hear you got it going. For the record, you ought not be able to ping the outside interface from inside the LAN anyway, at least not with the default firewall rules. The fact that your two internal hosts can't ping one another despite being on the same LAN is odd, but if it isn't causing you any problem then I guess it's all good.

@jimp:

Your screenshot does not show where you set the suggested variable. Also, settings in loader.conf.local only apply at boot time, so after altering the file you must reboot the firewall.

I have set in the loader.conf and restarted the firewall. but the set value does not appear when i typed the command sysctl vm.

boot11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111.png
boot11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111.png_thumb

Mixed USB 1 & 2 ….

This device (PC ?) dates from what year ??

For what its worth, I was able to crack open the case, pull out the CF, install 'netgate-2.2-RELEASE-4g-i386-nanobsd.m1n1wall.img' to the CF and it successfully boots into 2.2 (free bsd 10.1).  So the question becomes, why won't the auto upgrade work and what the heck is stopping the device from booting after.

Is there a list of URL's and ports that need to be unblocked to allow upgrades/package installations ?

Depending on what they're using to filter you, could you not simply ask them to whitelist *.psense.org?

i write from Italy. I had the same problem on Win 7 64 bit / Chrome 64 bit. I have solved in this very simple way. Uninstalled Chrome completely (iobit uninstaller free). Reinstalled, logged in the chrome account for the favorites (in which i have the favorite for web interface). Logged in pfsense. All good. In other PC (generally i have ubuntu 64 or some free unix, windows is only on the pc that have programs not virtualizable for windows) I had no problem. When i had the problem, the metallic theme was not affected. Only ng_theme was affected.

Did you download the correct ISO for your hardware? (aka: AMD64 and not i386)

Ok, I bit the bullet and tried to upgrade from 2.2.2 to 2.2.4: same result  :-\

They're not down, not building at the moment. Haven't really been any changes. Should be back later this week if not later today.

Hi silfen,
I don't know if you already solved this, but we have a similar configuration, but virtualized.
And yes, we use VLANs to segment different traffics (operation LAN, WAN or different WANS, clients LANs). You must use a VLAN tagged dot1q cappable switch.

Then you can use just one port as minimun to interconnect pfSense with the switch and configure that port on the switch as VLAN tagged port with all VLANs available 1-4096. On the pfSense you set that interface as VLAN, and then you can create many VLANs as you want and assign as virtual interfaces on pfSense. You can create then each VLAN for each customer + internal traffic, management, WAN, etc. VLANs for internal purpouse.
In that way you isolate each customer from each other not just at layer 3 IP/routing network range, but layer 2 MAC address.
You can even have the ESX Ethernet port configured as VLAN tagged and assign each VM to each VLAN number.
We have a testing VM (windows or linux) too that we can switch to any VLAN number to test anything as we were connected at the same customer LAN.

For the WAN public IPs, you can create Virtual IPs on the pfSense to NAT by ports or 1:1 to the interal IPs or even you can create a VLAN with the some Public IPs if the customer require a public IP at their VM.

Regards
JP

Not really. Even the most crappy 20 years old COM ports had 115200bps. Why the hell would be USB limited to 57600?

@tokamak:

@s1nemesis1s:

Sorry Guys,
I might be in a little over my head. I have not done much networking stuff for over a decade, this was supposed to help spark it and help me learn again.

My dell switch is set to grab an address of 192.168.1.200. - I can plug in a unmanaged switch to rule this thing out - I just used this one because I was intending on learning as much as possible.

My uverse gateway has an address of 192.168.1.254

I set the Pfsense box to 192.168.1.50 /24

The uvese box of course is a gateway device which hands out DHCP address and serves up WIFI.

I am pretty sure I need to put the pfsense box on its on subnet but I am not sure what is best, and how I will get the uverse box to actually forward to the pfsense box if I put it on a different subnet. I have read several threads on uverse boxes and how you have to config them for pfsense, in that you have to set up some sort of stacked router or forwarding. Again, any and all help is appreciated - I will post whatever info you guys want - I am just stuck…and am trying to figure this out with little experience or luck,

Hey bud,

I can relate, I too have a Uverse (NVG599) beast and I am working on getting pfsense working with it. So here is how I got mine to work, wired LAN only, with intermittent issues I am still working out:

You need to put Uverse in FULL Bridge/Passthrough mode with ONLY the Pfsense box connected to it.

ATT-Uverse router–---pfsense box----switch----connected devices of house

To put uverse in full bridge/pass through go here - https://goo.gl/dkvy5f (& OR) http://www.dslreports.com/faq/17734

This will get the wired LAN working, at least it did for me, I have a TP-Link TL-WDN4800 in my pfsense box and I'm trying to get Wifi AND Wired through my one pfsense box.

Your best bet is to NOT have Wifi served up by the UVerse router since in order for pfsense to work you must put that uverse box into full bridge/pass through.

Your best bet, the one I'm leaning to now, is have a separate Wifi device hanging off of your switch behind your pfsense box.

In my recent searches I'm finding out from folks smarter than me that Uverse wants to know EVERYTHING that passes through your home network!!!!!

ATT Uverse does not like to be put in the corner...

Meaning that Uverse routes all traffic through their NVG, DNS, etc and if you try to bypass their systems they packet shape, throttle and will do their damnedest to make your experience miserable. (paraphrasing on official networking terms since smarter people explained it better than I can write it.)

An example I have well documented on my home Uverse with DD-WRT/OpenVPN: (different vpn providers tested & on different home computers too.)

My Uverse is 45 down 8 up - runs close to that on my Uverse NVG599 (all traffic through my vanilla home uverse equipment)

OpenVPN running (UDP or TCP any and all ports, servers around the world, does not matter) 7mbps down & 7mbps up

OpenVPN running SSL or SSH 43mbps down & 8mbps up

A quick google search will reveal a lot of other folks experiencing similar issues...

A ray of hope potentially for us Uverse users - pfsense forum user -  icemanncsu - also has Uverse and somehow connect his pfsense box directly to his uverse fibre termination point and bypassed his Uverse NVG altogether.

But his link explaining his step by step on how he did that is down. I've PM'd him hoping he can share his step by step on here.

Hello! I used http://www.dslreports.com/faq/17734 and it totally worked! I left my wireless intact for a guest network that is on a different subnet. Thank you! What is with the packages though? HVAP did not work correctly for the web part, kept getting errors and it would not let YouTube play….
Also what is with squid, I don't play a ton of games but it blocks GTA 5...

I need to do more reading, but without the packages everyone raves about...hmm..I guess I need to look at all of it as learning :)

@doktornotor:

….. I would get rid of the garbage and never ever consider Linksys products again.

I'm using several 'Linkys' (Cisco now ?) devices, re flashed with DDWRT.
Some of theme are running nearly a decade now.

root@WRT54GL:~# uptime 07:55:12 up 100 days, 22:12, load average: 0.00, 0.01, 0.00

Ok, no draft N support, but they handle the job for me.

As 'stupid' AP's, they do fine. I love the setup : "shut everything down" and up it goes ;)

Btw: DD-WRT: with some 'ebtables' rules I can re-enforce "Client Isolation", a must-have on public (wifi) networks.

Interesting fault between an X-cable and a straight-thru.  I will make myself a cross over and see how autoselect behaves on my WAN connection.  In my case, setting my WAN to default (which does properly auto negotiate) vs autoselect (erratic operation) makes a difference on my WAN for some very odd reason.