Show Posts
1
General Discussion / Opnsense on Truenas VM
« on: February 01, 2021, 05:28:09 pm »
Hello all,
sorry for my poor English ...
I am new here, and I'm coming to seek your help on a subject that I have a little trouble understanding.
First, the context:
On a new machine, devoid of any other installation, I installed Truenas 12, this one configured and working correctly, I created a VM in which I installed Opnsense, which boots well.
I configured all this connected to my network, but without really inserting it in its final location (between the box and the rest of the network) so as not to create a problem for me while the debugging takes place.
On the machine I have 3 network interfaces, this is how they are assigned:
LAN> TRUENAS [igb0] OPNSENSE [em1]
WAN> TRUENAS [em0] OPNSENSE [em0]
LAN2> TRUENAS [ue0] OPNSENSE [em2]
So far everything is fine, even if you have to find your way around the different naming of the same physical interfaces by the two systems.
Where I am wondering, it is on the allocation of IPs, I have a little trouble understanding how to do this, and especially how a physical interface can be addressed by two IPs, here is my current config:
LAN> TRUENAS [192.168.1.42] OPNSENSE [192.168.1.248]
WAN> TRUENAS [192.168.0.253] OPNSENSE [192.168.0.252]
LAN2 not used at the moment, in the future dedicated to IOTs that I have in large numbers
LAN IPs are assigned based on the rest of the current network config.
The web interfaces of Truenas and Opnsense work perfectly with their respective IPs on the LAN interface (TRUENAS [igb0] OPNSENSE [em1]).
For the WAN, I have no error message, but before trying to put this into service I would like to be reassured about my config and understand the miracle of two IPs on the same interface.
I spent a lot of time reading tutorials and other forums to try to understand a little, I only got confused even more with bridges, VLANs and others which I do not get much.
I end by specifying that I have always worked in IT maintenance since the 80s, then as a dev. hardware HMI for 10 years, so I know the PC world quite a bit, but I am not far from being a nozzle in the network field.
If you could enlighten me a bit on how it all works and tell me about any mistakes and how to fix them ...
thank you in advance
sorry for my poor English ...
I am new here, and I'm coming to seek your help on a subject that I have a little trouble understanding.
First, the context:
On a new machine, devoid of any other installation, I installed Truenas 12, this one configured and working correctly, I created a VM in which I installed Opnsense, which boots well.
I configured all this connected to my network, but without really inserting it in its final location (between the box and the rest of the network) so as not to create a problem for me while the debugging takes place.
On the machine I have 3 network interfaces, this is how they are assigned:
LAN> TRUENAS [igb0] OPNSENSE [em1]
WAN> TRUENAS [em0] OPNSENSE [em0]
LAN2> TRUENAS [ue0] OPNSENSE [em2]
So far everything is fine, even if you have to find your way around the different naming of the same physical interfaces by the two systems.
Where I am wondering, it is on the allocation of IPs, I have a little trouble understanding how to do this, and especially how a physical interface can be addressed by two IPs, here is my current config:
LAN> TRUENAS [192.168.1.42] OPNSENSE [192.168.1.248]
WAN> TRUENAS [192.168.0.253] OPNSENSE [192.168.0.252]
LAN2 not used at the moment, in the future dedicated to IOTs that I have in large numbers
LAN IPs are assigned based on the rest of the current network config.
The web interfaces of Truenas and Opnsense work perfectly with their respective IPs on the LAN interface (TRUENAS [igb0] OPNSENSE [em1]).
For the WAN, I have no error message, but before trying to put this into service I would like to be reassured about my config and understand the miracle of two IPs on the same interface.
I spent a lot of time reading tutorials and other forums to try to understand a little, I only got confused even more with bridges, VLANs and others which I do not get much.
I end by specifying that I have always worked in IT maintenance since the 80s, then as a dev. hardware HMI for 10 years, so I know the PC world quite a bit, but I am not far from being a nozzle in the network field.
If you could enlighten me a bit on how it all works and tell me about any mistakes and how to fix them ...
thank you in advance