It happens sometimes while pasting URL in forum. Just remove the extra ftp://  :)

Sounds like the crux of that thread is: if you want long lasting SSD's, buy Intel.  (But I think some of us were already of that opinion.)

I wonder what their little SLC SSD's do with that kind of testing.

This is because you are using a 64 bit installer on a 32 bit machine try to download the right installer and see if that works I had the same issue recently

To rule that out I think you should format the drive and start over.

Steve

Thanks for the additional information.

@derwood:

I have a /30 from Time Warner.

As previously suggested in VirtualBox I would bridge the physical NIC available for connection to the modem and an emulated interface available to the pfSense. That emulated interface will become the pfSense WAN interface and be assigned your public static IP. Thus pfSense will talk with your modem over the software bridge in VirtualBox and the "eth1" physical NIC.

It seems as though maybe the Hyper-V isn't initializing the NICs properly.

Ifconfig de0 down
Ifconfig de0 up
Ifconfig de1 down
Ifconfig de1 up

Now I'm able to ping the pfSense box and access the web interface.

I was having the same problem and I ended plunging the hard drive to my PC and flashing: pfSense-2.0.1-RELEASE-4g-i386-nanobsd_vga.img to the disk using win32diskimager.

Every time I've seen that specific symptom with Time Warner it's been because they screwed up the static IP config on their end in some fashion (happens way more than one would think). That's assuming it's the business class static IP service, and you have the correct default gateway and have it marked as default under System>Routing.

So basically since I tried to reimage, I've been screwed.  I boot with an extra drive that has Ubuntu server on it (along with the images I'm trying to apply to my flash IDE drive), but when I start the copy (using dd), it ultimately hangs my OS with a slew of DMA errors being spewed to the terminal.  The dd command I'm running looks like so:

sudo dd if=pfSense…img of=/dev/sda

Where /dev/sda is the IDE flash drive and /dev/sdb is my Ubuntu server disk.

I'm honestly at a loss.  I think this IDE flash drive might just be total crap.  It's an Emphase 2Gb IDE flash drive, not sure if anyone's had any experience with them.  Any suggestions for where I can find a slim IDE or sata flash drive for this sort of application that doesn't totally suck?

The Linksys WRT54GL was the ideal platform for OpenWRT/DD-WRT etc a few years ago but these days it's looking a bit weak. The Netgear WNR3500L, that you already have, is far far more powerful:
480MHz CPU, 128MB RAM, 128MB ROM.

Choose one of the firmwares linked to above, say this one, configure captive portal on it. ??.??. Profit!  ;)

Steve

@stephenw10:

What's wrong with using 2.1 snapshots, which are based on 8.3?

Whilst 2.1 Snapshots are okay for testing and possibly for production if the day is right when no major glitches arise, I have found it hangs quite often when testing configs for routing public IPs - something not explained well either in the wiki or in the book and needs some experimentation.

@stephenw10:

See: http://devwiki.pfsense.org/UsingProjectEvilOnpfSense

Thanks, I saw it was a bit dated what with the old sze of 64MB that is now 128MB and whether the loader.conf.local would entries would still be needed - will check it out though.

I thought the release 2.0.2 might have some nice fixes now - any build from repo instructions?

@stephenw10:

@apmuthu:

Are there any unofficial public Wikis on pfSense that are maintained well?

I've never seen one.

Thanks for the info - a nice candidate for a wiki to substitute for the missing links in the current one and experimentations not in the book as well! Trawling the forum is quite cumbersome. Managing Spam and malicious activity on the Wiki is tiresome indeed.

@cmb - your book is well laid out and nicely cross referenced. Thankyou.

The memstick installer img uses the older FreeBSD Slice naming convention and had me stumped quite a while. Instead of mounting it withmount /dev/md0s1a /mnt/pfsensewe need to mount it with```
mount /dev/md0a /dev/pfsense

Thank You for the responses.

The pfsense appliance has 4 LAN ports available and it will be connected to three 42-port VLAN capable switches. Is it best to design it as a router on a stick, or to connect each VLAN to a pfsense LAN port?

yeah I was hoping to have 2.1 out as well, but I've had to deploy 2.1 BETA from the snapshots to my customers for now. Even though it's beta, still more than reliable enough to deploy in a simple network situation. :)

Michael Johnson
Novacore Systems
http://www.novacoresystems.com

I have reread this thread and noticed a change in the network shared by Cisco and ISP facing router: 192.168.2.0/24 became 192.168.2.0/30 (unless you made a typo). Depending on the IP addresses assigned when you did the switchover you may have created an invalid configuration. For example, suppose the Cisco had 192.168.2.100 and the simple router 19.2.168.2.1. Perhaps you replaced the simple router by pfSense with the interface connected to the Cisco assigned 192.168.2.1/30 then you have an invalid configuration because the Cisco and pfSense are not on the same subnet.

Please post a diagram of the current configuration including IP addresses and netmasks of all relevant interfaces, the tests you have tried and what is reported by these tests.

Edit the config.xml file and search-and-replace the old device name with the new one (e.g. em -> igb)

lol, i really doubt i'll have that much cache. Plus i only have 1gb of ram for this machine. I have quite a few older IDE drives laying about i just really don't trust them long term.

but at the same time, i want it to function at 100% and not have to worry about replacing something that craps out… Oh well guess i'll try it.

Thanks for your help Steve.

I found this forum page…. will try it out and update this forum thread
http://forum.pfsense.org/index.php?topic=50711.0

Brilliant! Thx Jim!

Yes, pretty much.
You should be able to upgrade directly from the GUI without separately downloading anything.
Read this: http://doc.pfsense.org/index.php/Redundant_Firewalls_Upgrade_Guide
and this: http://doc.pfsense.org/index.php/Upgrade_Guide

If you have any doubts the safest thing you can do is buy two new CF cards and use those instead. Restore a config backup onto the new 2.0 image and you should be good to go. That way you can quickly and easily go back to the old cards if something doesn't quite go to plan.

Steve