I'm headed out for a few hours I'll reply to any other questions later in the day. Thank you

What error are you seeing?

Nano or full install?

32 or 64bit?

Steve

Aaah yes, now why didn't I think of that. Fixed. Thanks

Can you ping the OPT1 gateway, 192.168.1.1?
What is the actual error produced when you try to ping from the OPT1 WAN?

Is that your own IP address, 21.1.1.7/24? If not why are you using it?

Anything in the logs?

Steve

I would highly recommend that you stop right now and grab pfSense 2.2-x64 and start from there.

I've setup a small lab in Virtualbox many times before and I usually create a 3-NIC vm with em0 simulating a WAN link on my LAN, em1 on intnet1 and em2 on intnet2 to simulate a LAN and DMZ (nevermind em2 if you're not doing a DMZ).  Then I create a small vm (Lubuntu or something) on intnet1 to talk to pfSense WebGUI and do all my testing and playing in the small vm.  Slap a LAMP serve rin the DMZ and play away.  BY default, your WAN is set to block private IP space, so you need to disable that if you want to access it from your real LAN, like testing a port-forwarded server in your DMZ.  Uncheck Interfaces - WAN - Private networks - Block private networks.

From what I gather both hard drives are fine. I ran Seagate tools on both using quick test and the both passed.

I can do it from lan, it doesn't matter since the configuration is being done locally.

The devs do not analyse every crash dump received, that is just not viable. If nobody comes up with a good idea about your hardware in the near future, you could PM one of the devs (jimp?) with the public IP the crash dump would have come from - then they can have a look.

one other thing i noticed was i had sent a pull request for UPNP and it was merged but seems it didnt end up in the snapshot i downlaoded which was dated 18th feb so i guess something wrong there too

That was commit: https://github.com/pfsense/pfsense/commit/8f637a0c4e323fe48f910aabf8e1662c307ac564
It was committed to master but then never to RELENG_2_2 branch.
Maybe PM to Renato to see if he intended that change to wait for a later release or if it was just an error forgetting to merge to RELENG_2_2.

In most cases at home, WAN or LAN NIC cards, its all the same.  Just get yourself at least two nice compatible Intel NICs (can be on a single card).

Not sure about you second question, but you can get gigabit throughput pretty cheap.  Possibly even rummaging in a junk yard for hardware.  haha.

Sure - You can get your DHCP IPs from your modem, no problem in most cases.

@epimeteo:

@ha11oga11o:

Hello all,

im trying to setup new pfSense to check it before i upgrade from 2.1. have another box which will be actually production one and i bought Intel® PRO/1000 PT Dual Port Server Adapter which is x4 PCIEX. Well, i put it on x16 port and on another OS like windows works fine.

But when i install 2.2 Release, theres no WAY it start. No way to be recognized as vlan capable adapter. Sometimes, just sometimes if pfSense boot on good mood and do some cleaning, checking and asking to assign WAN again, i got it work like em0 and em1. Then after enabling it as LAN and OPT1 interface, reboot pfSense everything goes downstream. Same problems again…

Im complete n00b about any advance consoling, digging on files on HDD with that OS, but i think i could do copy/paste :)

Now, if someone had same issue or even have clue whats happening to me, can you please give advice or point me to right direction?

Heres system log, but im not sure is that enough,... i filtered it with "em0" word and got this: http://pastebin.com/re48tN7G

Many thnx in advance :)

I have the same problem on an old ProLiant P4 server. To solve I had to configure better the IRQ under BIOS for the x16 port… hope that will help cheers

Thank you for tip,

but im not sure this s++++ty board could have that advanced feature. I saw that IRQs are shared with 4 NICs. I think 16 and 17. Ill try to fiddle with it (if there's section to do so), and post results here.

thanks :)

For me satisfying is not chasing my tail for a week.

You shouldn't have to do that. Check that your DNS forwarder (or resolver) is bound to localhost.

Steve

Thanks BBcan177, looks like that was the issue.  Following the fix in the thread you linked fixed it.

It looks like that when I uninstall and reinstall the LCDProc package the custom files I put in the directory get removed and then re-added. Where would those be held so I can delete them to start fresh?

Please search the forum on reverse proxy issue. pfSense wont allow squid to bind to a lower port. You'll have to use a higher port… Then using nat, redirect wan port 443 to that higher port, ex 8443?

c-icap and clamd is part of squid proxy, config is under Proxy server - Antivirus.

yep, you are right!
Infact, it's need to connect via ssh after installation for changing captive portal source code.

Thank you very much for your support.

Cheers
SM

I have the same problem, a VSAT wan (supposed to be always more than 500ms) and a WIMAX (supposed to be always more than 120ms), after 2.2 upgrade (well, fresh installation) are 20/10/0ms