Revised New Build
-
Thanks again, guys, the information you have supplied is exactly what I needed and the article on the PfSense application of the motherboard I was considering was interesting and informative. I went ahead and ordered all my components from New Egg yesterday. Hopefully, they will arrive in time that I may assemble them this weekend. I ordered a 4 GB USB thumb drive along with an internal 6-inch header to USB-A cable. I should be able to strap the thumb drive somwhere inside the chassis with a plastic wire tie. I can always replace it with something more elegant at a later date. Once I get the rig up and running, I will consider purchasing a riser card and a Viking PCI ADSL-2 modem card (if I can find a vendor that sells them in the USA). I will assume that the correct version of the PfSense embedded firmware that I will need to download (I'd like to run the 64-bit version) is "pfSense-2.0.1-RELEASE-4g-amd64-nanobsd_vga.img" ???
-
Unless you have bought a particularly long USB drive you should just be able to plug it into the internal USB socket on the board.
That is the correct image if you need VGA. That board has a serial port though so you could use the standard Nano image with a null modem cable. Either way you will probably be faced with a mount root error the first time you boot. Don't panic! That's normal, you simply have to tell pfSense where your USB drive is connected and then edit the fstab so it knows next time.
Steve
-
Thanks stephenw10, I goofed in assuming the on-board headers did not include a USB-A port. I just purchased a mini-USB device at Staples and loaded the firmware on it as the USB drive I purchased through New Egg is indeed too tall to plug into the onboard USB-A port. I received all my other hardware in the mail today and will assemble it tomorrow. Wish me well.
-
Up-n-Running! And it's already a heck of a lot faster than my old Trendnet router! Now I have to make sure all logging is turned off.
:D
-
Logging is all to ram only so no worries there. If you used the NanoBSD image it's all taken care of anyway. No need to worry about flash memory life.
Steve
-
O.K., thanks Steve. I may buy a SATA DOM eventually–USB works but it takes a long time to boot!
-
How long? How often do you plan on re-booting!?
My machine is usually up until there's either a new release or I do something to kill it. ::)Steve
-
Once it is fully configured I plan to leave it on continuously without rebooting. It takes ca. two minutes for PfSense to boot up after the motherboard posts.
-
That's similar to my Firebox booting from CF. Not unusually slow.
Steve
-
By the way, it turned out I did not have to do any compensation for the boot to USB option. I have rebooted my build several times and have not run into such a problem. I just purchased an ADSL2+ PCI card (it is made in Australia and I had to buy it from a vendor in Europe). It will take a couple of weeks to arrive, but I plan to use it to bypass my external DSL modem.
-
The Vikiking card from Traverse? (They also seem to have re-branded as rocksolid electronics)
I ran their earlier Pulsar ADSL card under IPCop for years, totally reliable.Steve
-
"The Vikiking card from Traverse?"
Yes, I guess I'll have to adjust the settings to get it to work with my Verizon DSL service.
-
When using Snort in the embedded version of PfSense that I am using, will the updates download to RAM or will they write on my solid state memory? I don't want to install anything that will do periodic memory writes. ???
-
Hmm, I'm not too sure about this but if it's available for embedded installs then someone else has probably already thought of it.
How often does snort update? Even the most basic flash memory still has a large number of writes in it's lifespan.Steve
-
-
stephenw10:
You mentioned you had experience with something similar to the Viking card. I was able to install the card in my PfSense router and place it in bridge mode. I adjusted VPI/VCI to 0 and 35 per the Westel modem I use with my Verizon DSL account. All seemed to go well until I plugged my DSL telephone line into the card. The power and LAN lights are on but the DSL light just flashes slowly–the card does not appear to be trying to negotiate a sync with the DSLAM in my local central office. I will check to see if it a simple problem with my phone cord, but it seems odd that everything else has gone o.k. with the setup and then the card will not sync to my DSL service. I already tried changing the settings between ADSL2, ADSL2Plus, etc. Any ideas? ???
-
The Pulsar adsl card was a true modem rather than a router on a PCI card like the Viking is.
There will almost certainly be some logging available on the Viking card. If not on the web interface maybe on a telnet interface?Steve
-
I can't seem to get the web interface to work. I am using IPMI with the console. I guess I have to download the command index file and do some more research. I may not have hit on the right ADSL settings as yet.
-
How do you have it setup?
This should still apply to your situation:
http://doc.pfsense.org/index.php/How_can_i_access_my_PPPoE_Modem_on_WAN#For_2.0Steve
-
Steve:
It turns out that my Viking card was not getting 12VDC (to power its DSL front end) through my PCIe slot. My riser card adapter, however, has a 12VDC power connector; once I found the right adapter cable I was able to install it and supply 12VDC to the adapter and Viking cards (in addition to the 5VDC already present). The Viking card now works, yippie! :D
