Yes, we will look at adding this in a future version.

If someone wants to create a package, go for it and we'll commit it.

Don't think anyone has tried it, but if it works in FreeBSD, it can be made to work here.  You have to use the Developer's ISO, recompile the kernel to re-add your network interface, then add the interface type to /etc/interfaces.inc.

Might be a few other minor hacks required, but shouldn't be anything too major.

@sullrich:

Then I am not too sure at the moment.  I'll have to do a test install with Vmware shortly.

Just made the partition smaler.. then It works  ???
Thanks for helping anyway :)

Depends.

If you have just one AP - then there isn't much difference, although its simpler to mange the access (if restriction applies) on one system. Complicated Hotspot pages ? Forget about these AP’s, handle them from pFsense box.

If you need a bigger surface (multiple floors) to cover, then using the WRTG(S)’s as simple AP’s, and pFsense to manage the lot – will be simpler. Some ‘simple’ filtering has to be done on a per AP basis (think about the Network Neighbourhood from Windows  - and protecting the AP’s them self).

I’m using myself a pFsense PC-based system – and an OPT1 interface. The hotspot function is enabled on it – behind it is a switch and 5 AP’s (WRT54GS + Sveasoft firmware). This never failed on me.

That should work.

Yes, that's a pcengines WRAP and atheros based wireless cards. I have several of these units here running pfSense very well. See http://pfsense.com/mirror.php?section=/tutorials/wrap_install/wrap_install.htm how to set it up.

Hello again,

i figured out that the miniPCI modem has an pct303a chipset - a so called softmodem.

Martin

@Numbski:

Just as a point of interest, I never did get Ghost to work properly with FreeBSD.  If you do manage to get this to work, you'll likely have to run growfs in order to grow the available disk space.

I've just recently started playing with LVM2 on a Debian NAS device I have here, and although I was originally very hesitant, I have to say that the combination of md devices (not to be confused with FreeBSD's md's) and lvm's is quite a refreshing change, and it's a pity it cannot be used under FreeBSD.  Instead of being stuck with just /dev/ad0, you could make a pv (physical volume) out of /dev/pv0, then add it to your volume group, /dev/vg0.  Once there, then create a logical volume, say pfsense, /dev/vg0/pfsense, and install there.  Run out of disk space?  Add another drive, create another pv, add it to vg0, run growfs, life goes on. :\

Ah well, please ignore my postulations. ;)

You really should check out GEOM.

i updated to rc2e, and i still get timeout, i'm just gonna buy another nic…thanks for the help guys ;)

uggggh don't bother respoding to this. I just noticed that there are bootp broadcasts from the previous cable providers gateway coming in on the LAN interface. Even though I had the guy check this at least 4 times he must have put the old cable modem on the LAN port instead of the LAN lol. Hopefully this is all it is.

Well that seems to have done it… using 50ft crossovers at both sites but now I have another massive problem, have to start another thread for that. Thanks again Hoba!

@hoba:

Disable device polling.

I agree - My P166 has intel NICs that support polling, but there's a continuous background load imposed, which turns out to be a good 30-40% of CPU on my box.

Test it and see is the best answer.

Thanks for pointing that out to me Bill, Let me know when you got that snapshot ready ;)
EDIT : I tested the snapshot and the driver seems to work good !
Regards
Ponl

Hi all,

I've got the same problem on a VIA EPIA M10000 running VMWare Server 1.0.0.
Any news with this?

Booting with RC1 livecd iso image stops with the same kernel panic at newfs.

Already searched VIA and VMWARE forums for similar reports, there doesn't seem to be any.

I've tried already disabling Acceleration and "memory page trimming" in the VM - didn't work.

VMWare edition and Developer edition didn't work too.

I'll try to get the Embedded edition into a vmdk somehow (maybe dd it from a knoppix live cd onto the hard disk), I'll report back my results.

Marc

I have via rhine based nics at my via c3s and they are working without issues. Check your cables. You might need crossovercables somewhere depending where you plug them to.

And get the latest BIOS you can find for them, then disable LPT, AUDIO, GAMEPORT, USB, COM etc. and reset Extended BIOS info and turn of "plug and pray".
If it still doesn't work, grab some other HW.

@hoba:

Check out your bios settings. You should turn off plug'n'play os and make sure the bios configures the cards properly.

After posting the earlier message, I searched my spare parts bin and found two other 10/100 NICs – an Intel (yay), and a Realtek (ugh).  I swapped those in place of the NDCs, and pfSense was happy.  The integrated 3Com NIC also works without problems.  I may go back at some point and use one of the NDCs to replace the Realtek, and I'll check the PnP/BIOS settings at that time.  Thanks for the help!

Scott

well, now it's ok with the RC1…

What'S the target system? try to play around with CHS/LBA mode and or enable/disable advanced ata and ultradma modes. I needed to do this to make my via c3s boot from cfcards.