Not to be biased - but can you drop your CentOS box for pfSense and simplify your life? In any case…I believe VLANs will be the answer to your questions.  You can create a rule that specifically blocks all traffic between your two VLANs except for specified IPs (printers).  Best of luck.

@Vincenzo: chipset is Intel 945Gc A2…I've already selected in the bios settings "legacy"...but nothing....sometimes it hangs on just before the free-bsd menu! I have to buy another mainboard? Which kind of mainboard / chipset isbetter fo pfsense? thank again I don't see know of any reason why pfSense wouldn't work with that motherboard.

Because you didnt search the forum for the zig-million threads about this. http://forum.pfsense.org/index.php/topic,7001.0.html

Yes it's a bug. With Konqueror I have a new menu what i hadn't with firefox3, the menu 'Diagnostic' :p So with Knoqueror all works.  :-\

That's really make sense. I never thought about that. and…the CIDR rules is the way to go, I just realize that my range of per-vlan subnet are all start 192.168.x.x and of course I need only one rule to solve it. I think that I was to inside of the problem without looking all the possibilities. Thanks a lot.

Try with 1.2.1 RC2 if it still is a no go then try 2.0 http://blog.pfsense.org/?p=207

I tried 1.3RC2… I'm successful on the installation... Thanks :D

If you donate to ermal's bounty for the traffic shaper he has a build that includes his new traffic shaper running pfSense 1.2 running on FreeBSD 6.3. After donation of whatever amount he will send you a link to it. http://forum.pfsense.org/index.php/topic,2718.0.html

I've installed pfSense 1.x to 2.0 successfully on many systems. Make sure there is not a usb thumb drive plugged in during the install to the hard drive. With IDE systems make sure the hard drive is the primary and the CD-ROM is secondary.

There is no console upgrade in 1.0, you can upgrade in the GUI using the Firmware page as described in the upgrade guide to go from 1.0 to 1.2 or 1.2.1.

@HalNineThousand: I didn't mention in the first post that I was puzzled because the line about media failure said to check the cable, so I figured that was off. That error refers to the onboard network interface not detecting a link (the hint was in the reference to PXE).

Ok After further looking into this. I have switched modems now and that means I have changed everything except the underlying software. I have even changed ADSL providers to see if that is the issue. When disconnecting from a remote PPTP server there are issues that have presented themselves on totally different modems. These issues are not apparent when using PPPoe within the pfsense box.  Both modems reboot themselves when disconnecting. The connections hang and then about 3 minutes later both connections work again. I have used different hardware for everything and it seems like a software issue. I would really appreciate some kind of help here. I know the devs are busy but this seems like a pretty important issue not just for me but for pfsense.

Last I checked you can't upgrade embedded installs.  I'm sure if that's no longer the case somebody will say shortly ;)

Thanks perry it works perfectly!

Hello, indeed, lighthttpd provides you GUI  :D cheers,

The answer to this thread is given. I'm locking this thread since schlumpf still doesnt know how to express himself.

This might help you: http://forum.pfsense.org/index.php/topic,8358.0.html