Right, if you don't have a switch that supports VLAN tagging (and know how to set that up), there's not much we can do to help.  Either a switch that supports VLANs or another NIC is what you need.  But, do yourself a favor and do not get a USB NIC.

If you tell us more about what hardware you're running on we can help point you in the direction of inexpensive NICs or other solutions.

omg i've finally fixed it after trying thousands of different combinations. I really hate this cn, dn, ou, stuff.

Here is my final working configuration;

While it might be a problem with the CD on your hardware, it's not a general issue that happens to everyone. Many people that I talk to have used the LiveCD without issue.

Have you tried a 2.1 livecd? http://snapshots.pfsense.org/

What NICs are you using that are supported by the rl(4) driver? I didn't think it supported any pci-e NICs.  :-\

If 300ms is within your 'normal' range of latency you might have to tune the apinger parameters. Is think 200ms is the default setting for latency warnings.

Steve

@wallabybob:

Try a pfSense 2.1 snapshot build. It includes much more up to date device drivers than any of the pfSense 2.0.x builds.

That did it!! Thanks!! I hope I dont miss any of the features of the stable release. This beta is going to a production environment…thanks again!

Hi,

Just to report an upgrade problem : 2.0.1 + siproxy -> 2.0.2
I have lost the DNS, as described in the release notes (PPPOE problem).
But I have broken all the packaging system too. Siproxy was broken in the interface & not running.

Revert to previous 2.0.1 & waiting for stable 2.0.3, as I don't have issues for my needs.

If you are interested in, I have keep the update log file & the diff file from my previous user setup.

Thanks for the good job.

Phil

@trunix:

LinuxTracker - you may want to consider this nic if you have to purchase another pcmcia adapter in the future. I moved off realtek and onto this card based on the dc driver and it's been great.

Appreciate the reply.
Unfortunately the WAN adapter is giving me trouble right now and it's onboard.
The notebook only has one PCMCIA slot and for whatever reason I don't like USB NICs.

The location where this is has a newer notebook on hand; I'll just swap it out.
That should put an end to this saga - or at least to this thread.

@trunix:

NETGEAR FA511 10/100Mbps PCMCIA Ethernet Adapter

I was wondering what chipset was inside that card.
It took me a while but I finally found a partial list of Netgear Chipsets
http://tuto.netgear-forum.com/Documentation/Chipsets/

The pfSense webgui listens on all interfaces so you would be able to access it from a VLAN interface as long as you have firewall rules to allow it (which LAN does by default).
The difficulty would be accessing the webgui for the switch which is usually on the default vlan only. You need to make sure you don't lock yourself out of it which I can tell you from personal experience can be very frustrating!

Steve

Edit: That linked youtube video is informative. It would seem that the main reason for not using the default vlan is that it exposes the management interface to the general LAN network. I guess it depends how much of a concern that is to you.

No problem!  :)

Thankyou all. I will try using the 2.2 version, and see if that works.

I'm planning to put this device into production so i may need to revert back to a stable release, but my first goal is just to get it running.

Will keep you posted as to progress.

Hello

I think the DL380 Gen8 has a new controller built in (SmartArray 420i, not the 410i). There are several options you have with the DL380 if the built in controller does not work with pfsense:
1. install another PCIe controller that does work
2. Use USB and embedded set up (internal USB port)
3. use the SD card and embedded install

Just a reminder that teh SD card is not HOT PLUG. server should be turned off before you install the SD card, otherwise it will not detect it and will not boot from it. If you manage to install it on SD or USB memory then chances are you will not need those $450+ SAS HDDs :D

Yesterday night I reinstalled Squid.. looks like the old configuration is reused when reinstalling.

After reinstalling it, a very loud buzzing started (meaning: my wife screaming that Internet was down).. I checked the configuration but I did not find what could be going wrong.. I guess it's the most simple squid setup ever..  Transparent proxy in LAN, and "allow users on interface", logs configured, disk and memory cache increased and thats it

I deactivated the service and the alarm was still buzzing (alarm started to be annoying)

I uninstalled Squid and the alarm stopped (and Internet was working again)

Now comes the funny part.. I installed Squid3 instead of Squid.. Squid3 took automatically my old Squid Configuration.. after the install the Alarm was silent.. Internet was working and Squid was caching…

I start to be confused.. :)

I had Squid3 working all night and everything works like a charm.

There really isn't any benefit, aside from fitting more user/package data.

If your card does wear leveling it's actually better to use a small image size and leave more cells free to disappear as they wear out.

You can run pfSense on those boxes (Firebox II and III) but 128MB is now the minimum spec for RAM. People often run m0n0wall instead.
There are a number of threads about it here.

Steve

yes! confirm these are, then I can not do anything to use the panel lcm? you can not compile for freebsd? excuse my ignorance!

thanks steve

Well, that was easy.. :)

2.0.2-RELEASE (i386)
built on Fri Dec 7 16:30:38 EST 2012

FreeBSD 8.1-RELEASE-p13

You are on the latest version.

I may have more questions to come.. but will be sure to put them in a new post.
Thank you..

The additional information provided points to an issue on the WAN side.

Please post the contents of the PPP log (pfSense GUI: Status -> System Logs, PPP tab). and the output of pfsense shell command:```
ifconfig; /etc/rc.banner