Proper configuration of interfaces

nikpony

Hello,

i need your help regarding the proper setup of interfaces in my instance, because i feel that there is a false part in my settings.

First of all i install my pfsense in a Hyper-V using a virtual NIC, and set it as internal.
In this NIC i set the following settings
IPv4: 192.168.30.200
Subnet: 255.255.255.0

In my network, i have not set DHCP. All machines have already a static IP.
My network looks like 192.168.20.0/24 and my gateway's ip is 192.168.20.1

Then, inside the Pfsense configuration, i have correctly assigned 2 interfaces, with the following settings.

WAN (where i have assigned my physical network card)
LAN (virtual network card)

WAN ip: 192.168.20.15
LAN ip: 192.168.30.2

Also, i have set a Gateway enabled, which is assigned to WAN interface with IP address 192.168.20.1
This Gateway is assign to WAN interface only.

So, could you tell me where is my fault? I can see traffice per ip, after installing the BANDWIDTHG package, but i.e. i can limit the traffic per ip, or block some urls.

Thanks all of you, in advance.

Gertjan

@nikpony said in Proper configuration of interfaces:

First of all i install my pfsense in a Hyper-V using a virtual NIC, and set it as internal.

.... To virtualize pfSense software, first create two Virtual Switches via Hyper-V Manager. ...

You saw the word 'two' ?
pfSense is a router, an needs at least two interfaces.

The important way to set up pfSense :
Start with an installation on a dedicated device - no need to buy a xxxx $ PC type - and old PC, saved from the waste bin will do just fine. Add a 5 $ second NIC, and you'll be fine.

Then, if you need some complexity, or just for pure amusement, set up a network without DHCP. If things start to stop working, you know now why you should keep "DHCP".

Still there ?
Set up a VM, like the Hyper V example in the documentation.
Take one or two hours of preparation, and look also some "How to VM pfSense" on Youtube.
Now try to set up one exactly like an example given.

I didn't understand this :

@nikpony said in Proper configuration of interfaces:

Hyper-V using a virtual NIC, and set it as internal.
In this NIC i set the following settings
IPv4: 192.168.30.200
Subnet: 255.255.255.0

Compare with what you've seen at the pfSense doc.
With the HypeV manager, you have to create two virtual NIC's. No IP info is entered here.

@nikpony said in Proper configuration of interfaces:

WAN (where i have assigned my physical network card)

So you did create two virtual NICs ? One as a dedicated WAN interface, reserved for pfSense usage only (the host system doesn't use this interface) ?
And one LAN, shared among pfSense, other VMs, if present, and the hosts system ?

@nikpony said in Proper configuration of interfaces:

My network looks like 192.168.20.0/24 and my gateway's ip is 192.168.20.1

Your LAN has IP 192.168.20.1 - the LAN network is 192.168.20.0/24 - right ?

Then this won't work :
@nikpony said in Proper configuration of interfaces:

WAN ip: 192.168.20.15

LAN ip: 192.168.30.2 ....
30.2 ? I thought 20.1
Why .2 ? Who is .1 ? Normally, it is .1 or .254

nikpony

@gertjan Dear friend,

Thank you for your time spending to reply in my request.

Finally, i manage to configure it properly, following the instructions of the Official Netgate manual, using two virtual cards, one of them (LAN) as private.

Previously, i used the host network card, and probably this was my fault.

Many thanks again!