WAN, LAN, OPT and What is the Next One?

Started by forum111, January 22, 2024, 11:00:10 AM

Previous topic - Next topic
January 22, 2024, 11:00:10 AM Last Edit: January 22, 2024, 11:03:28 AM by forum111
OK, let me explain my problem.

I have two physical interfaces:
- WAN - DHCP

- LAN - DHCP
- OPT1 - DHCP
- OPT2 - DHCP
- OPT3 - DHCP
- OPT4 - DHCP

-  ILAN0 - Internal-virtual (Static IP 192.168.1.1)
set DHCP server set here and give ips to LAN and OPT(n)

I need one virtual interface which will be static IP and this virtual-internal interface will have DHCP server set it up. Then the LAN and OPT will be set as DHCP and will get ip from virtual-internel network.

How the f**ck to create this internal-virtual interface.

At the end all interfaces except WAN must be in the same range 192.168.1.0/24

One of the proposals answer is related to "Virtual IP"?


Create a Virtual IP (VIP):

Go to Firewall > Virtual IPs.
Add a new Virtual IP with the type "IP Alias."
Set the IP address to 192.168.1.1 and the subnet mask to /24.
Create a Virtual Interface (ILAN0):

Go to Interfaces > (assign) > Interface assignments.
Assign the Virtual IP (VIP) you created to a new interface, e.g., ILAN0.
Configure ILAN0 with a static IP address of 192.168.1.1/24.
Set Up DHCP Server on ILAN0:

Go to Services > DHCP Server.
Select the ILAN0 interface from the "Interface" drop-down.
Enable the DHCP server and configure the DHCP settings for the internal network.
Configure LAN and OPT Interfaces for DHCP:

Go to Interfaces > (assign) > Interface assignments.
Edit the LAN and OPT interfaces, setting their IPv4 Configuration Type to "DHCP."
Ensure All Interfaces Are in the Same Range:

Confirm that WAN has a different range.
Ensure that LAN, OPT1, OPT2, OPT3, OPT4 interfaces, and the ILAN0 interface are all in the 192.168.1.0/24 range.
Verify Connectivity:

Save the changes and apply the configuration.
Connect devices to LAN and OPT interfaces and verify if they receive IP addresses from the DHCP server on the ILAN0 interface.
This approach effectively creates a virtual interface (ILAN0) associated with the Virtual IP (VIP) and sets up a DHCP server on that interface. The LAN and OPT interfaces then obtain their IP addresses from the ILAN0 DHCP server. Please adjust the instructions based on the specific options and interface names available in your OPNsense version.

It seems the solution is to make the brindge between all physical interfaces.
Then set bridge interface to static and assign dhcp server.
All physical nicks must be set to internet type: None.

Now the first problem is related to shell cli console.

how to set interface to None?


Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Wait a minute?! This is wrong!!! Step Three is fiasco and none sense. Let me explain.
What if I am part of the very big cloud infrastructure? I can not just take router (physical machine). This will work only for Youtubers ;)

Dudes... Come on... Take a look here. I will try to explain it.
Take a look here -> https://forum.opnsense.org/index.php?topic=38324.0;topicseen




Quote from: Patrick M. Hausen on January 25, 2024, 09:48:38 AM
Just do it this way:

https://docs.opnsense.org/manual/how-tos/lan_bridge.html

In a cloud setup you can invoke the UI over WAN and reconfigure all the LAN interfaces into a bridge without losing connectivity to the UI.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

I did and not work.  Something with firewall ?
All interface are set with rule to pass any to any.

If you create a LAN bridge you must not set rules on the individual interfaces. All rules go on the bridge.

But you MUST set the two tunables from the LAN bridge documentation!
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)