build your own passthrough device capable of PIA openVPN AES 256 SHA 256 RSA-4096

[BirdDad]

My problem with the Intel dual NIC was that I could not get pfSense to autorecognise it and I did not know how to invoke telling it manually.

 

[BirdDad]

Newer motherboard probably only support UEFI boot. So if you burn the pfSense in MBR boot mode, it probably won't boot after installation.

You probably have to make sure it writes in UEFI boot mode for USB flash drive.

Ignore Realtek patent message, it's on all motherboards with realtek chip.

The part that you said the motherboard still wants to boot from Realtek after you disable it in BIOS, that's really weird.

How do I burn pfSense to UEFI boot mode? My MB is set to boot in legacy/UEFI.
And I'll say this also-pfSense would not install to my SSD, it would only install to a hard drive.

 

[mxnerd]

rufus has the option to let you choose.

 

[sdifox]

Given you are going to encrypt to hell, I would not use an ssd at all.

 

[BirdDad]

Given you are going to encrypt to hell, I would not use an ssd at all.

just to boot from- all the encryption will take place in the memory.

 

[sdifox]

just to boot from- all the encryption will take place in the memory.

Ok as long as you make sure the ssd is not thrashed.

 

[mxnerd]

This instruction is much clearer than the one on PIA, tons of stuff to configure.

https://forum.pfsense.org/index.php?topic=76015.0

I'm afraid you won't be able to use RSA-4096 after all unless you use PIA's own client.

 

[BirdDad]

the problem that I am having right now is comming up with a valid name for the WAN interface since auto detect does not work and em0 does not work either.
that's what it is telling me.
It's saying no link up detected

 

[BirdDad]

the hard drive boots just fine as long as the onboard realtek NIC is disabled in BIOS

 

[sdifox]

the problem that I am having right now is comming up with a valid name for the WAN interface since auto detect does not work and em0 does not work either.
that's what it is telling me.
It's saying no link up detected

If you didn't hook it up to your cable modem, how do you expect it to detect a link?

 

[mxnerd]

Engineer has told you not to use auto detect.

Can't use auto detect. Had to manually set. You should see your choices right before it asks you the interface name or to hit 'a' for auto select. You'll need to choose your network connection for the WAN and LAN.

If not working, switch the cables.

You should be able to tell if an adapter port is working by looking at its LED light.

 

[BirdDad]

I have tried naming it em0 when that failed em1
I have it hooked up to an AP that is connected to a DSL modem

 

[BirdDad]

when autodetect fails
it gives me this
invalid argument supplied for foreach()
on line 436
no link-up detected

 

[sdifox]

I have tried naming it em0 when that failed em1
I have it hooked up to an AP that is connected to a DSL modem

remove the ap from the chain, so DSL Modem - Intel NIC named WAN. Name doesn't matter really, as long as you recognise it.

 

[mxnerd]

You are not naming em0 or em1, you are assigning it.

You assign em0 to LAN, and assign em1 to WAN or vice versa.

When you want to do auto detect, you have to plug in a cable!

And did you choose option 99 to install to disk?

 

[BirdDad]

remove the ap from the chain, so DSL Modem - Intel NIC named WAN. Name doesn't matter really, as long as you recognise it.

The AP worked fine with it when it was on VirtualBox
and yes I installed to disk, did a custom install this last time to make sure there wasn't something about NICs that I was missing.And yes I am plugging in my cables.

 

[mxnerd]

Installation Troubleshooting

https://doc.pfsense.org/index.php/Installation_Troubleshooting

 

[BirdDad]

when I try assigning them it says : Invalid interface name 'em0'
I don't know the mac addresses of this card

 

[sdifox]

when I try assigning them it says : Invalid interface name 'em0'
I don't know the mac addresses of this card

https://doc.pfsense.org/index.php/Installation_Troubleshooting#Interface_link_up_not_detected

 

[mxnerd]

"em" means it's Intel NIC, "le" means it's AMD NIC, etc. pfsense use 2 to 4 letters to identify different NIC vendors.

what do you see on the middle of screen like this?

if it's detected as "ab0" and "cd1", then you have to use "ab0" and "cd1" to assign LAN & WAN, not em0 & em1.

 

[BirdDad]

"em" means it's Intel NIC, "le" means it's AMD NIC, etc. pfsense use 2 to 4 letters to identify different NIC vendors.

what do you see on the middle of screen like this?

if it's detected as "ab0" and "ab1", then you have to use "ab0" and "ab1" to assign LAN & WAN, not em0 & em1.

Nothing like that, it immediately wants me to assign names, it doesn't just give them. I know it is a valid card because pfSense would not let me proceed unless there were two NICs present.

 

[mxnerd]

Which adapter did you get?

Unless it's latest chipset vendor (I suppose it's Intel?) just released, there is no reason pfSense won't detect.

Did you seat the adapter properly in the slot?

 

[BirdDad]

http://www.ebay.com/itm/151726955194?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT
it is seated well

 

[mxnerd]

http://www.ebay.com/itm/151726955194?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT
it is seated well

Intel 82540 is supported.

https://www.freebsd.org/cgi/man.cgi?query=em&sektion=4

pfsense kernel is based on FreeBSD. As long as FreeBSD supports a device, it's supported by pfsense.

Maybe re-try the installation?

Or try Windows/other Linux distro install on the system to make sure the dual ports adapter is working and it's pfsense's problem.

 

[BirdDad]

I have retryed the onboard Realtek NIC and the TP-Link card that I have bought (Realtek) and after a reinstall they are working. If the PIA installation goes well then I will retry the Intel card.