Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 17 replies
  • Subscribers 28 subscribers
  • Views 3078 views
  • Users 0 members are here
Options
Suggested
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

multiple LAN ranges on same interface

Marc Van der Smissen

Hi there. Newbie here. I don't get it.

I have two ip ranges in my network 10.0.0.0/24 and 192.168.1.0/24

I've setup the XG210 with the 192.168.1.0 range as LAN and everything works fine except I can't reach the 10.0.0.0 range from 192.168.1.0 range.

How can I remedy this ?

Thanks, Marc



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi Marc, Thanks for reaching out to Sophos Community.

    If the network range 10.0.0.0/24  isn’t configured on any of the firewall interfaces then you can add a static route 

    But it's recommended to configure the same network on an Alias IP and add a LAN to LAN rule to allow communication between these hosts.

    Also, there's a possibility if the Gateway isn’t defined for 10.0.0.0/24 network then the traffic might not even hit XG and would rather be routed through the defined gateway.

  • 0 in reply to FormerMember

    Thanks for the answer DeveshM

    Setting up a static route didn't help, so I followed your recommendation to configure an Alias IP and a LAN to LAN rule. 

    That didn't work either. Maybe I didn't setup the rule correctly, can you give me an example ?

    Marc

  • 0 in reply to Marc Van der Smissen

    My knowledge of doing this with an XG is limited but in the absence of any other responses I will add these comments and suggestions.

    Static route would not work. If the XG doesn't have an IP in the 10.0.0.0 subnet, there is not way for it to discover hosts and know how to route the traffic.

    What you are trying to do with the IP alias, is hairpin traffic - traffic going in and then back out of the same interface. Have a search for hairpin NAT in the XG section and you may be able to get this to work. I've set one up but it isn't the easiest of things to do if you don't have a good understanding of networking.

    What I don't understand from the details you have supplied is why you don't just setup a new LAN interface on the XG with a 10.0.0.0/24 address. This would be much simpler and a lot easier to manage traffic between the two subnets going forward.

  • 0 in reply to JasP

    Thanks JasP, 

    The 10.0.0.0/24 range is the range used by the cluster, the 192.168.1.0/24 range is the range where the virtual servers are in. There is no physical difference.

    Can I just plug in another cable to the (unmanaged) switch and use another LAN interface on the XG without messing things up ?

    I would prefer to go that route but otherwise I'll look for "hairpin traffic".

  • 0 in reply to Marc Van der Smissen

    Forget the hairpin it is not reliable and very difficult to get work on internal networks.

    ian

Reply Children
No Data