0

I am kind of new to networking so pardon me if my question looks trivial.

I am trying to make 2 LANs communicate.

My infrastructure is simple, we have an ISP router => Fortinet 300E (which also serves as the LAN gateway, this is the network 192.168.0.0/22) => Lan switches.

Now I created another network (192.168.100.0/22) on another interface on my Fortinet. Then I connected this new LAN interface to a dumb switch, where I connected some servers to that LAN. I can communicate with other servers on 192.168.100.0/22

NOTE: The network 192.168.0.0/22 is NATed to the internet through Fortinet, and it is the default network being used by users (including me) over the WiFi.

I have a web server hosted on the 192.168.100.0/22 network. Is there a way I can configure my Fortinet to route traffic from 192.168.0.0/22 (which I am connected on) to any IP on 192.168.100.0/22? Basically, I want to be able to communicate with 192.168.100.0/22 on 192.168.0.0/22.

This is what I have done so far on my Fortinet: I have created a policy route to manage this but it is still not working. I keep getting this error message ÉRR_CONNECTION_TIMED_OUT. and if I ping the web server, I get Request timed out error.

Please note the webserver is Ubuntu 20.04 and the clients are PCs

New contributor
Oluwadamilola Sonaike is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.
2
  • Please edit the question to include the [sanitized] Fortinet configuration. We cannot guess where you may have gone wrong.
    – Ron Maupin
    Aug 4 at 12:17
  • Policy-based routing (PBR) routes by source or by protocol. You need standard/simple routing by destination, no PBR. For a directly attached subnet, the route is included automatically, so no further route setup is required. All you need is a firewall policy permitting the traffic - without NAT.
    – Zac67
    Aug 4 at 13:02

0

Browse other questions tagged or ask your own question.