• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

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

Page 7 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
You should put em0 and em1 on different networks!

At Enter an option prompt, choose 2) Set Interface(s) IP address

Assign em1 to IP like 10.1.1.1, it just can't be 192.168.1.x

And make sure pfSense's 2nd adapter is not the same as 1st adapter.

ether use "Internal Network" and create another VM using same "Internal Network" adapter Or use KM-Test Loopback adapter like the video.
 
Last edited:
mxnerd said:
You should put em0 and em1 on different networks!

At Enter an option prompt, choose 2) Set Interface(s) IP address

Assign em1 to IP like 10.1.1.1, it just can't be 192.168.1.x

And make sure pfSense's 2nd adapter is not the same as 1st adapter.

ether use "Internal Network" and create another VM using same "Internal Network" adapter Or use KM-Test Loopback adapter like the video.
Click to expand...

I don't think he has configured pfsense as his firewall yet, it is stil sitting behind his router.
 
sdifox said:
I don't think he has configured pfsense as his firewall yet, it is stil sitting behind his router.
Click to expand...

I know. That's why he is getting 2 DHCP IP addresses from his router and I think he configured both virtual NICs to bridge to the same physical NIC that's connected to the existing router.

It's only for testing, it should be fine for him to put pfSense behind the router.

But he still needs to configure the pfSense VM's LAN and WAN interface on different networks. I don't know how pfSense can work if LAN and WAN are in same network range.

If he wants to use pfSense as firewall now so other devices can connect to it, he needs two physical NICs.
 
Last edited:
I tried WAN on 10.1.1.1 and LAN on 192.168.1.26
didn't work, I tried switching them and it screamed at me on the WAN not in subnet!
I've tried it according to that video and a lot of others.
 
Last edited:
Don't know how to align text so I use picture.

ygqf.png


@OP

If you want people to help, you have to give as much info as possible, it's extremly hard to figure out what out what you have and how you link your devices and how you install VirtualBox and it's NICs config. Like you never answer what's Virtualbox NIC2 config. It seems you keeps ignoring some questions.
 
Last edited:
i7 8 core 16 thread@3997MHz
ASRock fatality 3 mother board
32 GB of physical DDR4 @ 3000MHz
m.2 SSD Samsung
3 4TB WD black hard drives
680GTX
liquid cooled
Intel NIC
runs very stable
about virtualbox now
last configuration tried:
Nic one bridged to Intel NIC
NIC 2 bridged M$ loop back
 
Last edited:
Is your router handing out DHCP in 192.168.1.x range? If yes, I don't see why you can't connect to pFsense VM if you follow video/instruction carefully.
 
Op can you list the general steps you have gone through so far?
I have a feeling it is just a small thing missing.
 
Last edited:
BirdDad said:
I am not a pirate and we do not download porn. That's the only things I can see the tor network to be useful for since we do not live in an overly (yet) oppressive country. Besides tor has a lot of latency.
Click to expand...

Its pretty much the same as obscuring yourself via a vpn...
 
Actually, I think this should fix the problem. In virtualbox setting set nic1(wan) as not connected or loopback and nic2(lan) as intel nic. You need the lann working right now.
 
You're right it must be something simple that I am overlooking.
I will try your video again as none of the others are working for me either.
I already placed the order for the dual Intel NIC so I am committed to this.
I did it just like the video and it won't connect. He is using a 32 bit version while I am using the 64 bit version, I don't know if that has anything to do with it or not. I did notice when I checked the status of my loopback adapter that it had outrageously high numbers in the sent and receive.
Following another video I was able to ping the server but still no go.
 
Last edited:
@OP

Sorry, I have a distant memory about pfSense and I think I completely screwed up on method 1, which require pFsense Squid proxy package.

But when I try to install the package, somehow there is an error and it won't install. I tried Squid3 and got error too.

The error message I got.

Beginning package installation for squid .
Downloading package configuration file... done.
Saving updated package information... done.
Downloading squid and its dependencies...
Checking for package installation...
Downloading https://files.pfsense.org/packages/10/All/squid-2.7.9_4-amd64.pbi ... (extracting)
ERROR: Failed to read PBI header! Possible corrupt PBI, or wrong PBI version for this OS.
of squid-2.7.9_4-amd64 failed!

Installation aborted.Removing package...
Starting package deletion for squid-2.7.9_4-amd64...done.
Removing squid components...
Tabs items... done.
Menu items... done.
Services... done.
Loading package instructions...
Include file squid.inc could not be found for inclusion.
Deinstall commands...
Not executing custom deinstall hook because an include is missing.
Removing package instructions...done.
Auxiliary files... done.
Package XML... done.
Configuration... done.
done.
Failed to install package.

Installation halted.
Click to expand...

Please use method 2. Which works without problem. No proxy config for browser and no proxy package required for pfSense.

pfSense default login/password combo is admin/pfsense

Once you login into pfsense, you probably need to disable 2 firewall rules.

Click edit icon on the right

2czdguu.png



then uncheck 2 rules at the bottom and save it.
97v1i8.png
 
Last edited:
sdifox said:
Did you try what I suggested? Assigning the lan to the intel nic and wan to loopback in virtualbox settings.
Click to expand...

Will this work? If WAN is assigned to Loopback adapter, the loopback's traffic will be forwarded to internet?

And how do you assign IP to this adapter suppose my physical IP address is 192.168.10.20?
 
Last edited:
mxnerd said:
Will this work? If WAN is assigned to Loopback adapter, the loopback's traffic will be forwarded to internet?

And how do you assign IP to this adapter suppose my physical IP address is 192.168.10.20?
Click to expand...

I am just trying to make sure he can hit it. So you have two nic, one wan and one lan. You configure with the lan nic. Right now his actual nic is given to wan with the lan on loopback. I dont think you can reach the webserver that way.
He is just testing this on virtualbox and not actually prod.

this is just for his test, not actual deployment. For actual deployment he is getting a dual port nic, one wan one lan.
 
@OP

For method 1:

I thought I installed pfSense onto disk but I didn't, that's why the squid package won't install. After I install pfSense to disk using option 99, the package install without problem.

So make sure after pfSense live CD basic configuration (after IP config for LAN & WAN in console), you choose option 99 to install it on disk.

Then you can install squid package from pfSense web interface's System menu. After squid installation, you have to put 10.1.1.10 (Loopback adapter's IP) in Proxy Server (from Services menu) tab's Unrestricted IP entry in order to reach internet.

1zodizb.png


Before you finish squid install & basic config, you don't have to mess with proxy settings.

Only after you need to reach internet and test pfSense you change the proxy setting.

That's quite a few steps.

===============

Setting up another VM using method 2 is easier, you don't have to change browser's proxy setting and no need to config proxy on pfSense.

===============

I have tested both methods and both works.

The reason method 1 require proxy setting is it guarantees that the browser traffic will go through pfSense VM instead physical NIC since you have two NICs now, one physical and one loopback on your PC.

if you use method 2, the Linux or Windows VM only have one NIC and the VM doesn't have to worry which adapter/network to use.
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Back
Top