can I connect the client that I created using the vm to the pfsense interface in virtualbox?

stephenw10

You have 3 interfaces in the pfSense VM. Are they all assigned?

I would expect to see WAN, LAN and OPT1 but only LAN will allow connections to the webgui by default.

That is probably adapter 2 which you currently have set as host only.

If your Lubuntu VM is connected via the Internal Network to the pfSense adapter 3 (OPT1) then you will need to add firewall rules on OPT1 to allow it to connect.

Steve

ezvink

@stephenw10
Yes, that's right, sir, because if adapter 2 isn't loaded with a host-only web gui, it won't work.

What are the firewall rules, sir?

stephenw10

@ezvink said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

if adapter 2 isn't loaded with a host-only web gui, it won't work.

Won't work how?

Host-Only adapters only allow access from the VBox host. It won't allow access from the Lubuntu VM.

@ezvink said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

What are the firewall rules

I would start off by adding a rule on WAN allowing access from the WAN subnet:
https://docs.netgate.com/pfsense/en/latest/recipes/remote-firewall-administration.html#restricted-firewall-access

Steve

Patch

@ezvink said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

The project that I will make is about IDS Suricata and Snort.
I need 1 client as server 1 client for attacker then pfsense as firewall.

What is the context of this project?
Why are you doing it?
Who is funding it?
When completed what will it be used for?

ezvink

@stephenw10
Yes, the web gui can't be accessed, sir, I don't know why if I change adapter 2 other than the host-only web gui it always can't be accessed.

which material should i take sir

ezvink

@patch

this is a project for my final project sir.

Patch

@ezvink said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

my final project

So it is part of an IT training course?

ezvink

@patch
Yes, that's right, sir, I took a networking class and took the title.

do you want to help me sir? step by step to connect client and pfsens

ezvink

@stephenw10

which one should i edit sir?

Patch

@ezvink said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

I took a networking class and took the title.
do you want to help me sir

To help you be a good network engineer you do not want a step by step guide of how to do your final year project.

What books have you read and found useful?
What projects have YOU done so far (excluding things you have needed considerable help to do)?

stephenw10

@ezvink Add a new rule on WAN to allow traffic from the WAN subnet to the WAN address on the webgui port.
Anything on the bridged subnet should then be able to access the webgui which is fine in a test setup like this.

ezvink

@stephenw10
What kind of settings should I have, sir?, I see the module you provided from the netgate site is not the same as the picture I provided

stephenw10

@stephenw10 said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

Add a new rule on WAN to allow traffic from the WAN subnet to the WAN address on the webgui port.

So use:

Source: WAN net
Destination: WAN address
Destination Port: https (assuming your webgui is on the default port)

Steve

ezvink

@stephenw10
what next sir? is this correct?

stephenw10

Yes. That should allow other devices in your local network to login to the pfSense via it's WAN IP. Including the host if needed.

ezvink

@stephenw10
so in lubuntu VM must use adapter 1 bridge sir? is that so sir? then the client can access the pfsense

ezvink

@stephenw10
I always have problems pinging from pfsense to the client it connects but when I try to ping from the client to pfsense it still doesn't connect sir.
even though I've used the rules you gave.

stephenw10

No the Lubuntu VM should be connected to the Internal Network adapter and that should already have access to the pfSense GUI as long as the NIC you're using for the pfSense LAN is also an Internal Network adapter.

You removed the 3rd NIC from the pfSense VM right?

Patch

@ezvink said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

I took a networking class

@ezvink said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

this is a project for my final project

@ezvink said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

The project that I will make is about IDS Suricata and Snort.
I need 1 client as server 1 client for attacker then pfsense as firewall.

@ezvink said in can I connect the client that I created using the vm to the pfsense interface in virtualbox?:

I'm confused how to connect it

Then you need to develop your networking skill if you are ever going to be employed for your network skills.

How all engineering task are done, is you develop ability with the basic building blocks then combine multiple building blocks to achieve more complex tasks.

You were set this project not because anyone cares about the end result, what matters is the skill you develop in doing a Network engineering task. For you to actually have the competence to do your project you need skills in

Hypervisor virtual machine configuration
How to configure a virtual network within the Hypervisor
Firewall installation and network configuration
How to configure the basic firewall features within your chosen firewall application
Installation of advanced firewall capabilities to support IDS (eg Suricata or Snort)
Configuration of the IDS package
Designing & building a firewall test station including a simulated attacking computer, a firewall under test, and a defended work station.
Testing the effectiveness of the of your Firewall with IDS
Understanding and reporting on the limitations of your choosen threat protection approach (eg encrypted messaging).

Your start this engineering task by getting the basic stuff working first. Your questions indicate you have not got a firm understanding of step 2. yet, so do just that and get just that working. After which you should be able to create a VM and have it network reliably with what ever other VM or NIC you choose.

After which you can learn about step 3. Which is best done by reading the manual and experimenting. Asking others to build your project for you deprives you of the learning opportunity and will prevent you from becoming a competent network engineer. If you want a successful career there is no other way.

ezvink

@stephenw10

i didn't remove it the pack persists, so the lubuntu VM keeps using the internal network?