Thanks :)

192.168.1.1/24 is the default LAN IP. The 2D13 defaults to:

LAN IP 192.168.1.1
DHCP server on LAN giving out addresses to whoever plugs in.
Allow all on LAN rule
DHCP client on WAN asking the [ISP|upstream router] for an IP address.

Reset to factory defaults Plug the laptop into the LAN port - it should get an IP address Browse to 192.168.1.1 Login admin/pfsense Follow the bouncing ball through the setup wizard.

(It looks right but why TF doesn't it work?!!?!?)

Because the pfSense LAN IP is not a gateway from pfSense to anywhere. A "gateway" in network terms is an IP address on another box, that gets you closer to other destination subnets.
If you set it to yourself, then packets can go into a bit of an infinite spin, and exhuast their TTL.
When you have other private subnets behind LAN, you could, in principle, have pfSense LAN gateway set to the other router on LAN that gets you to those "back-end" subnets. But pfSense does not need that to be done.
I think the real problem that blows it all up is selecting LAN gateway as "default gateway" (or when pfSense kindly does that for you without you realising).
In any case, on pfSense never set a gateway on a LAN-style interface.

I tried it. Didn't work. My wan interface should be my bridged adapter right at the virtual box network settings?
Our ISP originally gave us  a static ip, wouldn't that be a problem if i set my wan to dhcp?

@alieas:

except I don't know how to do a fresh install so I guess I'll have to learn that first.

You can use the serial memstick from Netgate for that (http://firmware.netgate.com/firmware/memstick/) but it shouldn't be necessary.

@alieas:

I'm thinking the SSD might be setup in the same dual-boot partitions as the CF.  I guess I would go about that through the console to see if a boot option comes up?

It's not setup that way. If it were, it would be running NanoBSD, not a full install.

@dorrell:

I am new to KVM and PFSense.  How do I install this in KVM?  If I extract it, the file has a .raw extension, not an .img extension which is used under KVM.

Hi,

File extensions don't matter in Linux. Just use this as your KVM hard disk image and you're good to go. Let me know how this works for you. Just make sure to set the proper devices when configuring your virtual disks and network interfaces i.e. virtio.

Thanks,
bert

Nice.  :)
If you read through that upgrade guide you'll also see it lists a separate firmware for the LCD module so I imagine that generating some/all of those messages. It may be a standard part for which other firmware is available, have a close look at the LCD module.

The administration guide for the box talks about some lan-bypass features. If it has those on some NICs then that can make them appear un-available. Often it is possible to disable that in the BIOS or via jumpers on the board.

Steve

o_O

Is it really that simple? I'm going to try this tonight when I can create some downtime. Thanks!

What is the model of the card?

You may need to use a 2.1.1 snapshot.

I'm having the same exact issue with the same type of hardware : Poweredge 2950. Did you ever manage to get it working?

Thanks,

@doktornotor:

Yeah, it is solved. As said, do NOT use the broken package. Or get help from whoever has produced it.

broken package ??

where to get the right package? and how? thanks

I Steve,

I revert my config and now I'm ok. I don't wanna investigate further.

My WAN address is public and I'm behind another router with another public ip address. During this period of crash I asked to my provider to change the configuration of their router to act like a "firewall". Now I'm going back hoping that my brand new machin will work like the old one…

config seems perfectly ok... cross your fingers....

I hope not to bother you anymore but sound possible....

Thank you very much for your support.

Enrico

In that how-to robi does not use a physical NIC for the host-only adapter. The only difference I can see is that he simply sets the pfSense interface to use the existing 192.168.56.X subnet created by VBox. I can't really see why that would make any difference but you could try that anyway.

Steve

Nope I mean just re-install the client export package.
Go to System: Packages: Installed Packages: and click the button next to the OpenVPN Client Export Utility labeled 'pkg' with an arrow symbol (presumably supposed to look like the recycling arrows or a reload arrow). The mouse-over hint tells you what it does.
That's assuming you have installed that package in the first place of course!  ;)

Steve

FYI: http://redmine.pfsense.org/issues/972

I figured it out! I created an Alias called InternetforVLANs for all VLAN traffic that require internet. After that I then created a rule to allow Any IPv4 traffic from InternetforVLANs to any destination. I have attached screenshots for those who may have a similar issue.

Alias.png
Alias.png_thumb
FirewallRule.png
FirewallRule.png_thumb

Uhm. Can I know how to set pfsense on router mode? thanks! I can't get my WAN work with my static wan IP.

"it was not uncommon that a specific gateway was way overcrowded "

Exactly why I asked if his address space had changed - I have seen this sort of issue as well, where if you were on different address space you were fine, get unlucky and get other and speeds were crap ;)