Installation/ Wan-Lan setup
-
Hi,
I am new to pfSense and I am stuck. The installation procedure proceeds to the point were the VLan/Wan/Lan
selection is called for. Vlan =no, Wan= a= enter Plug in the internet connection get a green light.
The return message: No connection detected. What do I need to do to get past this point.
Hardware: MSI A88XI Board + AMD A6. Board sas one Lan port. Intel Quad Pro1000 PCIe provides 4 more.
Can someone help? Thank's
Paul -
Don't use autodetect. Just select the desired port. In your case, it's probably em0 or em1. Sometimes the numbering is confusing- you can plug in connections and check ifconfig from the shell to verify which port is which.
-
Usually you will get a message at the console when you connect one of the NICs, even if you're in the interface selection menu, that shows which NIC it is. Somthing like:
Interface UP, em0Steve
-
If I resemble it correctly, before the VLAN question all available interfaces are listed with full name ("Broadcom xyz" or "Intel pro acb"), followed by a letter/number code for the respective interface, like em0, bgd1 etc.
Do not choose "autodetect", but enter the correct letter/number code for the interface you want to assign and ENTER. Then it will work… ;)
-
Thank's to all.
Got by the interface connection but now it seems it will not proceed past the "Configuring firewall".
I do not know how long that takes, but have waited for at least 15 minutes and nothing happens.
All I can think of " Is the DVD to small". I will try a larger one. Also the board NIC ( re0 ) is not recognized.Paul
-
Not sure what you mean by 'dvd is too small'. :-
At that point you have already installed to the HD?The on board Realtek look like it an RTL8111G on that board which, as you said, isn't supported in 2.1.3. You could try a 2.2 snapshot which does have support, bare in mind that the snapshots are still in alpha.
It shouldn't take more than, say, ~10s to bring up the firewall. No where near 15mins!
Steve
-
To be fair, I've seen the last bit of the start sequence lag noticeably if there's nothing plugged in the WAN port on some installs. Perhaps up to 45s total, but it sure feels like 15min when you're used to a normal 10s start ;)
-
Having nothing plugged to WAN port is a non-standard usage scenario. You can't expect the system to behave normally under such conditions.
-
Hey I can expect anything I want to!
It's just not reasonable to do so ;)
I fully agree with you for an operational box, you need something on all the ports you're using, but when setting up with new/odd hardware I've often just set it on the bench and load the software to see how far I can get before something dies. If I get a console, then I'll hook up network connections to see how various cards respond.
The time lag I noticed is more an indication of how well pfsense performs when you set it up right than a criticism of it's handling of boundary cases.
I wouldn't use anything else if I have a choice…....
-
Figured out what my problem was. With 4GB Ram installed the 64 bit version does not install. Used the
32 bit version and all went fine. The Info on plugged in WAN Port and the Realtek NIC helps me to the next step.
I will give 2.2 alpfa a try after I get this setup going. Appreciate not to have to hunt for a solution to the Realtek NIC.
Paul :) -
With 4GB Ram installed the 64 bit version does not install.
Interesting. That should not be the case, there's no minimum RAM with 64bit. At least it's not different to 32bit (256MB).
Steve
-
With 4GB Ram installed the 64 bit version does not install.
Interesting. That should not be the case, there's no minimum RAM with 64bit. At least it's not different to 32bit (256MB).
Steve
There are known problems with some BIOSes on certain motherboards when using a 64-bit OS and 4GBs or more of RAM. A BIOS update should solve the problem if one is available.
-
Right, but not by the time you get to the interface detection? I would expect it to hang or panic at the bootloader, unable to load the kernel, or in the BIOS itself. Of course I'm all ears if you know something different.
Maybe a 64bit driver issue? :-\Steve
-
A couple of hours ago I was happy, got all the way to writing the hard disk. However I could not
access the GUI via 192.168.1.1. Also it shut itself down and booted up again and again.
So I start over thinking I messed up somewhere. Now I get a mount error notice. Do not
know were to go from here.Paul :(
-
Hmm, repeatedly rebooting sounds more like a hardware problem. Do you know the history of the board/RAM/harddrive? I think I would be running a few cycles through memtest86+ just to verify the board and RAM. That might also explain the 32/64bit difference you had.
Steve
-
I'm with Steve on a possible hardware issue.
As well as the memtest, I'd suggest a burnin routine. The UBCD (Ultimate Boot CD, Google should easily find it) has some good all in one tools that are helpful in these scenarios.
No point in using pfsense as your trusted firewall if you can't trust the hardware it runs on.
