I know I can get it to pull the gateway from config.xml for the inernet connection test. Should I add an entry in config.xml for the external site or just leave it yahoo? I guess a DNS server would also work.
I only have my WRAP for a few days this week before it's shipped off to a client. Having a lot of fun with it though. :)
Any good M$ software to check for CF read/write errors out there?
That's a good question. I've never run across anything such as this.
Simply create a dump file the size of the CF, with a value of hex 0xAA ( 10101010 ), and write it to the flash card. Then verify that there are no errors when comparing against the dump file.
Now write another dump file of hex 0x55 (01010101), and do the same.
This will veryfy that all bits on each byte of memory are set/unset and written/verified correctly.
It does work, however, kernelpolling has a lot of timings that should be tweaked to the appropriate platform/cpu performance. m0n0 aims at slow hardware and has an image for each platform which makes it possible to supply different sets for different hardware. As pfsense has only a general image supplying different optimizations is not that easy (unless we add some kind of pulldown menu with different optimizations or even a tweak page). This is something we already have discussed and even tested different settings with a wrap (see http://wiki.pfsense.com/wikka.php?wakka=Tuning ) and might appear in a version after 1.0.
Sorry about that but I didn't check this thread for a while.
My box specs are in my signature.
I have reflashed my box with 0.97 and all seems fine right now.
Maybe a CF card issue.
Gotta buy a Sandisk instead of this cheap stuff…
Actually I started one of the "other" topics. I never did find out what the problem was. And the problem I was having then is different. As the blink wasn't random flashes it was at a specific interval of about 2 seconds. This can be anywhere from less than a second to flashing very rapidly even when nothing is connected.
I fixed the problem last time by starting fresh with a new version. I guess I could try that again.
I was just posting incase someone else had experienced this. I've gone on holiday for a month and a half so I can't get back to fix/diagnose it anymore unfortunatly. Was worth a try.
Packagesupport might be split in 2 sorts of packages (suitable for all platforms / suitable for embedded builds).
This definitely won't make it in 1.0 though.
No worries, we wouldn't want to postpone 1.0 just because of that ;).
Most Atheros based cards are good.
Wistron Neweb CM-9 cards work fine. (minipci)
Senao 5354 MP PLUS ARIES2 4G (minipci)
Dlink DWL-AG530/AG520 (PCI)
3com 3CRDAG675 (PCI)
In general you can refer to this list: http://www.madwifi.org/wiki/Compatibility since the freebsd HAL and the MadWiFi HAL is the same. (cards reported working on madwifi-ng might not work !!)
But forget about pcmcia/cardbus cards, they might work on linux and not on freebsd and vice versa.
Via epia boards ?
There are a lot of platforms out there.
Problem is to support all this we need to cross compile a bunch of versions. For now your best bet will be a via epia board if you are looking for some performance while still keeping it small.
Or you could have a look at the nexcom boxes. www.nexcom.com.tw
I replaced the image with 0.92 and it now see the wireless ath0.. Thanks guys.
If you still need the dmesg on this new release, let me know.
Get the newest version (0.92), it has a newer HAL/driver for ath.
And it should support that card.
Also add all the dmesg lines regarding ath.
And a pciconfg -vl from the shell would be nice.
We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.
Subscribe to our Newsletter
Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.