Steve

Thanks for the heads up on the better builds. I think I will be going with your advice. I'll search for a good sandy build, if you happen to remember one please post a link here.

****As I was scouring through the forum I saw the post for 2.0.2 and saw that it was released TODAY!!! I just downloaded and installed without a hitch. ****

I will follow up with a post with screenshots of performance.

Thanks for the help guys.

That might be possible to put in as a checkbox. However, if it shows up at all it's because the card and driver claim it is supported.

If it claims to be supported but it doesn't actually work, it could either be a driver issue or an issue with the NIC's chip improperly handling the feature.

For now you can just add a shellcmd tag (manually or with the shellcmd package) to execute the ifconfig … -vlanhwtag command at bootup.

You can open up a feature request ticket on http://redmine.pfsense.org/ and request it that way.

Hi,

thank you for your reply.
Will check it.

Ben

When I ran:   1) Assign Interfaces    .   plugging in a patch cable would not help auto assign the interfaces.

using these :

I was able to determine that the operating system recognized the nics.

So manual assignment worked.  I used plugging in a cable and running dmesg from cli to determine the em numbers for the 4 nics.

Thank you for the responses here and at pfSense support.

Just ordered the ALIX kit. I liked the Hacom unit, but decided against it because of the minimal amount of memory.

@JoeMcJoe:

Is it possible to use a 2 port pfsense box, and then use VLANs with a managed switch to connect to multiple DSL modems, all using MLPPP on the pfsense?
I know an unmanaged switch won't work.

Being in the hardware forum I'll give you the hardware portion of the answer: yes.  To pfSense, as far as it pertains to software functions, VLANs are no different than physical ports.

Now, the other half, getting multiple DSL modems to load balance, that's a question for the Routing and Multi WAN section of the forums: http://forum.pfsense.org/index.php/board,21.0.html  You might get better answers from there since more of the guys that know quite possibly hang out there more than here.

I have heard that single bit flips are more common than.. ugh.. commonly thought.

sure you didn't do something like write an image to the card that was far too large?

I can't think of any reason why the slice would have just disappeared like that unless it was never written to the card. And since the cf slice is at the end of the card, if the image was too big (think writing a 2GB image to a 1GB card) then it may behave like that.

I suppose if the CF had a large number of bad sectors causing the disk to "shrink" it may also do that, but I don't think I've seen one act quite like that when it happens.

Sorry I haven't replied sooner.. work has been pushing for crazy overtime. I did fix the previous config issue but in the end a reinstall of pfSense fixed the issue. I have no idea why but I have a working box now. I'll post pics of the build when a get a minute to breath.

Thanks for all your help everyone!

Glad you could resolve it.

I know this is a really old thread but it's coming up high in search results for the problem so I thought a follow-up was in order.

Seems the errors on NanoBSD with the net6501 on an mSATA are due to it needing DMA and/or write caching enabled.

I wrote up the solution here:
http://doc.pfsense.org/index.php/Boot_Troubleshooting#NanoBSD_on_Newer_Hardware

I've used the CM9 and the WLM54G cards from Netgate successfully:
http://store.netgate.com/miniPCI-Cards-C26.aspx

@PistolPete:

@Sc0rian:

yup even know the company advised me it comes with a motherboard, it didnt. Thanks for that lambda-tek.

Anyway I have ordered http://www.ebay.co.uk/itm/Intel-D2500CC-D2500CCE-Mini-ITX-Dual-Core-ATOM-CPU-2x-Intel-LAN-Car-PC-Carputer-/200725215717?pt=US_Motherboard_CPU_Combos&hash=item2ebc27b9e5 at a cost of £88.64.

Good price for a good spec Atom motherboard. Since lambda will not take it back because i have opened the parcel tape, which apparently now means its opened. I will just use this case with above motherboard.

What ever happened to distance selling regulations, and goods being sold not as described???
Looks like I'll be avoiding them in future too.

Yeah with distance selling regulations they should not only take it and give you your money back - your free to do this even if you just decide you don't want it within 14 days.

But if its not as described they should also refund the shipping to you and also the return shipping!

This is my setup

Here is maybe a way to do it…..
pfSense is a superb border router, most consumer wireless routers pales in comparison to the performance, reliability and flexibility you get with pfSense. If your going to spend time and money setting up a pfSense you might as well make it your border router! I use this as the basis for my home network:

WAN ---> pfSense --> switch1

Connect all your home devices to switch1 (wireless router, computers, game consoles, etc.). For most people you just set up your wireless router as a WAP only - no routing!

For your multiple networks (VLAN) requirement - first question is your wireless router supported by dd-wrt? If so, you could set up dd-wrt with port base vlan. Then each of the ports is a separate network. I use dd-wrt for my WAPs (runs very well) but I don't run multiple networks so I don't know how well this works.

If you can't or don't want to change the firmware on your wireless router to dd-wrt, you can buy a managed switch and set up your networks (VLANs) on it.

I've decided to make home router from normal PC, this card is buggy under linux too:
– skiped --
[  120.369436] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  120.369913] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  120.370350] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  120.370756] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  120.371181] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  120.371612] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  120.372038] asix 1-7:1.0: eth2: asix_rx_fixup() Bad RX Length 1626
[  120.372473] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  120.372901] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  120.373332] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  120.373763] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  146.648898] martian destination 0.0.0.0 from 109.86.255.60, dev eth2
[  171.505176] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.505609] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.506059] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.506487] asix 1-7:1.0: eth2: asix_rx_fixup() Bad RX Length 1955
[  171.506923] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.507372] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.507797] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.508215] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.508639] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.509093] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.509523] asix 1-7:1.0: eth2: asix_rx_fixup() Bad Header Length
[  171.509943] asix 1-7:1.0: eth2: asix_rx_fixup() Bad RX Length 1743
– skiped --
my netbook going into reboot when I downloading large file, tried d-link dub-e100 with the same result

msk0 working without any errors

You should be able to just move the hard drive to a new system. You are likely to run into two "problrms".
1. The drive may have a different (e.g. ad3 instead of ad0) but that is fairly straight foward to correct.
2. The interface name will likely be different (e.g. em0 and re instead of bge0 and bge1). Again that is fairly easy to correct because the startup will prompt you to reassign interfaces.

@cmb:

The "multi-WAN on a stick" scenario (that is multiple WANs on VLANs) is documented in detail in http://pfsense.org/book

Hello again… I was reading some more and Ive based this multiple WANS on VLANS with some commercial products.  IS this the same concept and function that is TRUFFLE on mushroom network have been advertised? Thank you for your honest and utmost opinions.

It's not broken on any version or architecture in general. If it's a driver issue, it could be specific to 64 bit. That sounds like the symptom when you're doing MAC spoofing on a DHCP WAN on 2.0x versions pre-2.0.1.

More information please!  :)
You are using the same Supermicro board?
64bit install?
pfSense 2.0.1?

Steve