• 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 8 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
<p>What are the ips of the wan and lan in pfsense</p>
<p>&nbsp;</p>
<p>What adapter is wan and lan attached to in virtualbox?</p>

Also, did you do a basic install or did you start adding the vpn stuff already?
 
<p>What are the ips of the wan and lan in pfsense</p>
<p>&nbsp;</p>
<p>What adapter is wan and lan attached to in virtualbox?</p>

Also, did you do a basic install or did you start adding the vpn stuff already?

my setup NOW is
ip for WAN 192.168.1.199 set by DHCP
LAN 10.10.10.1
WAN is attached to my physical Intel NIC
LAN is set to internal
basic install
 
my setup NOW is
ip for WAN 192.168.1.199 set by DHCP
LAN 10.10.10.1
WAN is attached to my physical Intel NIC
LAN is set to internal
basic install

set wan to internal and lan to nic in virtualbox see if you can reach the web configurator. of course make sure the internal ip is on the same subnet as yours and use itself as gateway.
 
I kept saying you should create a Linux or Windows VM when using Internal Network, it seems you didn't since you never mentioned you created one.
 
3 VMs running behind pfSense using Internal Network adapter

getting DHCP addresses from pfSense VM (IP 10.1.1.1)

all of them able to access internet through pfSense

2bo5m0.png


8vnqs6.png
 
nothing. on either configuration.
Thanks for trying to help.
I tried a windows 64 bit other as the OS when you first set up the VM still no go. It does not work with Linux either.
 
Last edited:
I thought you said you can get the text console? That means pfsense is running, it is just a co figuration issue.
 
yes it appears to be running, I can even ping the WAN but I cannot connect to it using my browsers. I can even ping the loopback NIC but it wont connect in a browser.
 
Last edited:
While waiting for my hardware to come in, I set up a VM using VMWare player and two virtual NIC's connecting only to the host (i.e. no physical network card - only virtual). Set the WAN and LAN to those virtual NIC's using the console, set the IP address and the host can access the GUI via browser on both the LAN and WAN ip. Has to be some sort of setting in Virtualbox that's causing the issue (at least my guess).

First time I've ever laid eyes on pfsense....so many options!

Head explodes...I can see why it could potentially lead to issues.

Edit: Even though the two network cards should be between the VM and the host only, I can access them from other devices on the network so it's passing the information to the physical network card (or most likely, I don't understand the terminology well enough to realize that the virtual connection to the host is going to host then to network card).
 
Last edited:
While waiting for my hardware to come in, I set up a VM using VMWare player and two virtual NIC's connecting only to the host (i.e. no physical network card - only virtual). Set the WAN and LAN to those virtual NIC's using the console, set the IP address and the host can access the GUI via browser on both the LAN and WAN ip. Has to be some sort of setting in Virtualbox that's causing the issue (at least my guess).

First time I've ever laid eyes on pfsense....so many options!

Head explodes...I can see why it could potentially lead to issues.

You dont need to touch the options though to setup. Just interfaces and ip.
 
I did have it where I could ping either NIC but now I can't get back to that.
Thanks for all the help you guys.
I've heard somewhere not to use an SSD with this to choose a hard disk because there is a lot of caching involved, so I guess pfsense can't do TRIM?
 
Last edited:
You dont need to touch the options though to setup. Just interfaces and ip.

When you state setup, you mean console or via the GUI?

I'll probably, when getting the real hardware, set up VPN and QoS rules (whatever it's called on pfsense - Traffic shaper or something like that).

As for the VM, really have no interest in that other than to help BirdDad and to see how hard it was to get going (about 5 minutes or so) but since I'm using VMWare Player, it's an apples to oranges to comparison anyway.
 
I did have it where I could ping either NIC but now I can't get back to that.
Thanks for all the help you guys.
I've heard somewhere not to use an SSD with this to choose a hard disk because there is a lot of caching involved, so I guess pfsense can't do TRIM?

Trim does not prevent wear.
 
When you state setup, you mean console or via the GUI?

I'll probably, when getting the real hardware, set up VPN and QoS rules (whatever it's called on pfsense - Traffic shaper or something like that).

As for the VM, really have no interest in that other than to help BirdDad and to see how hard it was to get going (about 5 minutes or so) but since I'm using VMWare Player, it's an apples to oranges to comparison anyway.

Setup as initial setup, you can configure it completely from command line anyway, just less convenient.

VMs are fun. I had setup a test lab with two win 2003 Domain Crontrollers on different sites sitting on the same host :awe:
 
Last edited:
now I've got to figure out how to use this thing, I tried using NAT for my first NIC but auto detection could not figure out the settings and I was in an endless loop, no matter the NIC I choose it says no link up.
Thanks
 
now I've got to figure out how to use this thing, I tried using NAT for my first NIC but auto detection could not figure out the settings and I was in an endless loop, no matter the NIC I choose it says no link up.
Thanks

so you setup 2 virtual nic?
do you have two vms? one pfsense and one win7?


so let's say your internal network is 192.168.1.x and the gateway is 192.168.1.1

on the pfsense vm, set wan to dhcp, lan is some other range,let's call it 192.168.10.1

configure a virtual switch for that subnet then on vm 2, set ip to 192.168.10.10 and gateway is 192.168.10.1

get on vm2 and attempt to connect to 192.168.10.1 with browser.
 
now I've got to figure out how to use this thing, I tried using NAT for my first NIC but auto detection could not figure out the settings and I was in an endless loop, no matter the NIC I choose it says no link up.
Thanks

I had to manually assign the connections.

First, I deleted the NAT connection and created two NIC's with direct host connection from the VM Settings parge. After that, I booted pfsense and the two connections showed up in the console window of pfsense (I think they were el0 and el1 but I could be wrong as I don't remember). I also set the interface for the WAN IP to one in the range on my network, subnet and the gateway to my router's IP (for good kicks) and once doing that, I could browse from the host (apparantely, directly to the WAN).

I then, through the GUI, set the LAN IP and I could then browse from the host to either the WAN or LAN IP addresses.

login: admin
password: pfsense
 
Last edited:
Which settings should I choose for my NICs? I got one that is bridged sharing with the host and the other one I can't figure out what to do with. em0 is not receiving an ip address.
 
Back
Top