1

enter image description hereI have a problem regarding routing between two subnets. Here is how the structure of my company network looks like:

  • There's a subnet that has an IP: 172.16.218.0 (which is company's main network connected directly to the internet through the router)
  • Second subnet would be the network with the IP: 192.168.0.0
  • Between the network 172.16.218.0 and 192.168.0.0 there's another router (router 2), which is used for VPN-connection with devices in the network 192.168.0.0 (remote access from outside the company network).

Now there's a device (device 1 - virtual server) in the network 172.16.218.0, which need to exchange the data with another device (device 2 - Siemens PLC) in the network 192.168.0.0 via so called OPC-Server (used mainly in industrial automation). Ideal situation would be that these two devices were in the same subnet, but unfortunately that's not the case.

I had trouble to configure the router 2, so it would work as VPN-interface and at the same time would allow data exchange between device 1 and device 2. I have added the route using "add route" command but it didn't work (route between device 1 and 2).

My idea was to configure yet another router (router 3) between device 1 and device 2 and establish VPN connection between them. Before I do that, I wanted to ask if that all makes sense.

Edit: to be more specific: I added a picture in which you can see how the structure of the network looks like.
- Devices on the subnet 1 are getting IP-Adresses via DHCP.
- Devices on the subnet 2 are getting static IP-Addresses.
- Router 1 is used to get an access to internet.
- Router 2 is used to make a tunnel for a remote access to devices on the subnet 2 from outside subnet 1 and subnet 2 (via Internet).
- Device 1 and Device 2 need to communicate somehow (there is an OPC-Server running on the device 1).
- OPC-Communication works perfectly if the Device 1 and Device 2 are on the same subnet.
In the configuration of the OPC-Server (Device 1) we can set the IP-Address of the slave (Device 2) and the communication should already work (assuming we are on the same subnet). Here it's more complicated as they are on two different subnets.
- Router 2 is configured using mbConnect24 (Web Client) and router itself is an industrial router (mbNET). In the configuration there're two main aspects - LAN-Address for subnet 2 (192.168.0.0), let's say 192.168.0.100 and WAN address via DHCP. Configuration of this router is loaded to the device using mbConnect24 Portal.
- Now the question is - how to configure that network that Device 1 and 2 can exchange data?

That you for your help.

  • 1
    Please edit your questions to include the model of your router(s) and the configurations. There's not enough information to help you. – Ron Trunk Aug 15 '18 at 0:56
  • What are the router models? – Ron Trunk Aug 16 '18 at 0:40
  • The industrial router mbNET - is MDH859. I unfortunately don't have any information about another router. I have full information about subnet 2, bacause I configured it. I suppose the other router is just a regular router working as an access point. – lukasmoulin Aug 16 '18 at 0:46
  • You will need to modify the configuration . of router 1. If you can't, there's no point going further. Unfortunately, router 2 has very limited configuration ability. You don't need a VPN between 1 and 2. – Ron Trunk Aug 16 '18 at 1:21
1

Ideally, all routers need to know the routes to each subnet.

Router 1

  • subnet 1 (directly attached)
  • subnet 2 via router 2
  • route to main network
  • default route to Internet (if not via main network)

Router 2

  • subnet 1 (directly attached)
  • subnet 2 (directly attached)
  • default route via Router 1

Obviously, nodes on subnet 1 need to use Router 2 to communicate with subnet 2, either by having an explicit route or by using Router 2 as default gateway (which would need to handle traffic destined for everything behind Router 1 as well).

If Router 1 cannot learn the subnet 2 route then no device within that subnet can use any route across that router. A solution is to source NAT that subnet on Router 2 - this creates the problem that you cannot connect into subnet 2 from anywhere else. You can work around that using destination NAT / port mapping but this is where it gets really ugly.

If there's a VPN tunnel on Router 2 leading elsewhere (you aren't clear on this) the nodes behind that tunnel have the same problem as those on subnet 2.

Basically, you need to get Router 1's routing table updated, either statically or by a routing protocol like OSPF.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.