I'm using the 64-bit build (2.1, not 2.0.3) on my DN2800MT, no issues at all.

@lindsay:

It`s this one.
I use an 4GB flash so the space is not a problem.

This particular Soekris box seems quite low on both RAM and CPU … For the past 4-5 years people have been using the Alix 2d3 http://www.pcengines.ch/alix2d3.htm board for this task.

Btw, even if you use 4GB flash, you might still want to use the 1GB image of pfSense (it'is supposed to help prolong the CF card's life, due to how the wear-levelling algo works)

Thank you,
Its the first time that the entire concept of VLANs actually clicked for me so I am just a bit unsure of what is and isn't possible with them.

http://files.pfsense.org/netgate/ contains the current firmware files for those devices, they just haven't been put into the 'updates' directory for one reason or another there.

@stephenw10:

Swapping out the cable is an easy test though.  ;)

Steve

Guess what? That solved it! Used a CAT-6 patch cable and now it works. Guess something is wrong with that other cable…

Thank you SO much! I was about to give up. Had already downloaded Smoothwall, just to see if the issue was with pfSense on my box.

Thanks a lot again. Now I got to get working with the configuration of the firewall. :)

Ideally, yes, that's how it's supposed to work.

I'm not aware of any known issues in the upgrade process currently, but there is always a chance something may go awry. It's usually fairly uneventful.

When starting the RADIUS server with

radiusd -X

it must show you at the end the ports on which the server is listening. If it shows you the accouting port and interfaces and tells you "Ready to process requests" then the server is probably ok and running.
More information will be shown on syslog if you enable logging on freeradius –> settings.

final post - solved the interrupt storm issue by enabling APIC in bios - one of the few options the board gave me.

everything is up and running now, thank you again for your effort :)

WTF, you got it working out of the blue? how did it work for you ? have you done anything? at least post what you did so any other people who had/have same problem can follow your solution  ??? ??? ??? ??? ???

By far the best way to do this is to run both pfSense and your NAS product here virtualised. That way you minimise any customisation to pfSense which you will have to maintain.

Steve

Nice! That doc talks about both of which I have in my server.  :o

Ya, I figured the box was a little overkill but it was a good deal that I couldn't pass up.

From what I have found the 2wire does not have a bridge mode, so I will have to try and change the IP range on the pfsense box.

Give me a day or two and I will see what I get worked out.

I looked at a few of the crash dumps submitted from your IP address, and they were all different, seemingly in random places, and there were also some signal 11 errors.

If it has DIMMs you can pull you might try swapping them out to make sure it isn't a RAM problem.

The way it's acting is, in general, indicative of a hardware issue. Aside from RAM, it could equally be a power supply issue, cooling, the MB/BIOS, the HDD, some combination of the above, or a general issue with that hardware and FreeBSD.

Check the upgrade log (viewable from Diag > NanoBSD)

Difficult to say for sure what might have happened, but from 2.0.1 to 2.0.3 isn't a very drastic update.

It would be better to see both the upgrade log and the console output from the time of the upgrade, if you can get it.

This is the working one…

<widgets><sequence>system_information-container:col1:show,gateways-container:col1:show,pfBlocker-container:col1:show,interfaces-container:col1:show,log-container:col1:close,captive_portal_status-container:col1:close,carp_status-container:col1:close,cpu_graphs-container:col1:close,gmirror_status-container:col1:close,installed_packages-container:col1:show,interface_statistics-container:col1:close,ipsec-container:col2:close,load_balancer_status-container:col2:close,picture-container:col2:close,rss-container:col2:close,services_status-container:col2:show,openvpn-container:col2:none,wake_on_lan-container:col2:none,snort_alerts-container:col2:show,traffic_graphs-container:col2:show</sequence>
<traffic_graphs-config>WAN_graph-config:show,LAN_graph-config:show,DMZ_graph-config:show,MAIL_graph-config:show,WEB_graph-config:show,FORUM_graph-config:show,refreshInterval=1</traffic_graphs-config>
<filterlogentries>20</filterlogentries></widgets>

This is the one screwing me!

<widgets><sequence>system_information-container:col1:show,gateways-container:col1:show,interfaces-container:col1:show,captive_portal_status-container:col1:close,carp_status-container:col1:close,cpu_graphs-container:col1:close,gmirror_status-container:col1:close,installed_packages-container:col1:show,interface_statistics-container:col1:show,ipsec-container:col2:close,load_balancer_status-container:col2:close,log-container:col2:close,picture-container:col2:close,rss-container:col2:close,services_status-container:col2:show,snort_alerts-container:col2:show,traffic_graphs-container:col2:show,openvpn-container:col2:none,wake_on_lan-container:col2:none</sequence>
<traffic_graphs-config>WAN_graph-config:show,LAN_graph-config:show,refreshInterval=1</traffic_graphs-config></widgets>

I have disabled it.. its actually got two 3.5" floppy's listed…  I even plugged one in just  to see if I could get by the lockup.. I will take a double look tho..

thanks..

What do you see in the Proxy Filter logs?

It's the extra security…

My view is that, if security is so much of a concern, it may be better not to virtualize pfSense at all.  As you may have seen on those "other sites", opinions about virtualizing pfSense (or any firewall) vary a lot.

I suggest you try it without the pass-through.

BSD:

gzip -dc whatever.img.gz | dd of=/dev/adX

or

gzip -dc whatever.img.gz | dd of=/dev/adX obs=64k

Mac:

gzcat whatever.img.gz | dd of=/dev/diskX

(Make sure diskX is not mounted and has no mounted slices first)

Linux:

gunzip -c whatever.img.gz | dd of=/dev/hdX

Windows:
Use Win32 Disk Imager or Physdiskwrite/PhysGUI, make sure to remove existing partitions in Disk Manager to be sure it's getting a clean write.

It should "Just Work" in terms of booting. If it was written correctly, it's up to the BIOS from there. And the USB key can play a part in it. For example, my Soekris net6501 will boot on less than half of my USB sticks, due to quirks in its BIOS when dealing with older sticks.