This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

LAN - VLAN routing

Hi!
I have an XG125 where the network of port 6 is 192.168.12.0/24 and the port 1 is 192.168.0.0/24, both in LAN zone.
Port 6 has a DHCP server
I've added a VLAN on port 1 (Port1.40) with IP in DHCP

I've created 2 rules:
1:
Source zones: LAN
Source network: #Port1.40
Destination zones LAN
Destination networks: #Port6
Service: Any

2:

Source zones: LAN
Source network: #Port6
Destination zones LAN
Destination networks: #Port1.40
Service: Any

But the VLAN interface doesn't get the any IP from the DHCP server on port6.

What am I doing wrong?



This thread was automatically locked due to age.
Parents
  • Hello Mario,

    you are mixing / confusing Layer 2 and Layer 3 here.

    While "Port 1" and "VLAN 40" sit on the same physical Interface, these are complete different Networks, which don't "see each other" in terms of IP-addresses.

    The same with "Port 6", the network on Port 1 does not "see" the traffic on "Port 1" or "Port1.40" simply by putting them into the same Firewall-Zone.

    You either have to build a bridge (connection on Layer 2), or you have to route between the IP-nets on top of those interfaces (connection on Layer 3).

    Like now, the VLAN-Port 1.40 will never get a DHCP address from the server running on Port 6, nor will it get one, if you run that on Port 1.

    Please tell us, what you want to achieve, so that we can help you to find a solution for your use case.

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • You either have to build a bridge (connection on Layer 2), or you have to route between the IP-nets on top of those interfaces (connection on Layer 3).

    Isn't the routing what I've done with the 2 firewall rules?

  • Routing is Routing.

    Firewall rules is packet filter.

    These are two different things, you first have to have functional network, either routed or bridged, so that packets can flow from A to B.

    Then you allow or deny certain IP-connections or ports with firewall rules.

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • BTW: I prefer routing over bridging.

    Bridging is simple but has serious disadvantages when trying to build a clean, segmented network architecture.

    Mit freundlichem Gruß, best regards from Germany,

    Philipp Rusch

    New Vision GmbH, Germany
    Sophos Silver-Partner

    If a post solves your question please use the 'Verify Answer' button.

  • Which I think indicates that the VLAN should not have the same network as the network hanging off of Port 6. Which would indicate two different DHCP servers. I currently have three SSIDs on my AP, for example, and two of them are VLANs (less trusted networks) and one of them is bridged onto the main LAN that the AP is on (more trusted network). The LAN and the two VLANs each have their own DHCP server to serve their distinct networks.

Reply
  • Which I think indicates that the VLAN should not have the same network as the network hanging off of Port 6. Which would indicate two different DHCP servers. I currently have three SSIDs on my AP, for example, and two of them are VLANs (less trusted networks) and one of them is bridged onto the main LAN that the AP is on (more trusted network). The LAN and the two VLANs each have their own DHCP server to serve their distinct networks.

Children
No Data