Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 Networking Routing & Subnet Issue, Accessing to different Subnet

views
     
TSaoisky
post Feb 23 2017, 05:45 PM, updated 8y ago

Regular
******
Senior Member
1,200 posts

Joined: Dec 2008
My Network Environment is a Modem connected by a Dlink WiFi Router via Bridge Mode and another MikroTik WiFi Router connected to the Dlink WiFi Router. Hence the

Dlink Router
IP: 192.168.1.254
subnet mask: 255.255.255.0
gateway: 10.233.161.34

MikroTik Router
IP: 192.168.88.1
subnet mask: 255.0.0.0
gateway: 192.168.1.254

Having PC under Dlink Router IP range / subnet group 192.168.1.xx while MikroTik Router IP range / subnet group 192.168.88.xx

My PC under 192.168.88.xx can access to IP range / subnet group 192.168.1.xx However IP range / subnet group 192.168.1.xx unable to access to IP range / subnet group 192.168.88.xx

Appreciate if any expert could advise how to solve it so that my PC under 192.168.1.xx can connect to 192.168.88.xx

soonwai
post Feb 23 2017, 05:57 PM


*******
Senior Member
9,989 posts

Joined: Oct 2007
From: KL


Check on your DLink that you have a route to 192.168.88.xx.

Any reason why you use 2 routers? Why not just use the Mikrotik as the router? DLink can still use as AP.
tailtwist
post Feb 23 2017, 05:59 PM

Regular
******
Senior Member
1,564 posts

Joined: Jan 2003
From: working@SG, hometown in Kay L



u likely need a static route......to tell the ip range/subnet of the dlink subnet connecting to the mikrotik subnet to route via 192.168.88.1(mikrotik gateway) otherwise it will route via your WAN gateway(10.233.161.34)
nikrizal
post Feb 23 2017, 06:06 PM

Regular
******
Senior Member
1,223 posts

Joined: Oct 2005
QUOTE(aoisky @ Feb 23 2017, 05:45 PM)
My Network Environment is a Modem connected by a Dlink WiFi Router via Bridge Mode and another MikroTik WiFi Router connected to the Dlink WiFi Router. Hence the 

Dlink Router
IP: 192.168.1.254
subnet mask: 255.255.255.0
gateway: 10.233.161.34

MikroTik Router
IP: 192.168.88.1
subnet mask: 255.0.0.0
gateway: 192.168.1.254

Having PC under Dlink Router IP range / subnet group 192.168.1.xx while MikroTik Router IP range / subnet group 192.168.88.xx

My PC under 192.168.88.xx can access to IP range / subnet group 192.168.1.xx However IP range / subnet group 192.168.1.xx unable to access to IP range / subnet group 192.168.88.xx

Appreciate if any expert could advise how to solve it so that my PC under 192.168.1.xx can connect to 192.168.88.xx
*
Standardise all the IP range for all routers/bridge by changing the same ip prefix. Eg. all start with 192.168.1.x

shredder
post Feb 23 2017, 06:09 PM

Getting Started
**
Junior Member
235 posts

Joined: Dec 2006


try to use the same subnet 192.168.1.XXX for all device
soonwai
post Feb 23 2017, 06:19 PM


*******
Senior Member
9,989 posts

Joined: Oct 2007
From: KL


QUOTE(nikrizal @ Feb 23 2017, 06:06 PM)
Standardise all the IP range for all routers/bridge by changing the same ip prefix. Eg. all start with 192.168.1.x
*
QUOTE(shredder @ Feb 23 2017, 06:09 PM)
try to use the same subnet 192.168.1.XXX for all device
*
Maybe TS has a reason to use 2 subnets. TS, care to elaborate?
TSaoisky
post Feb 23 2017, 10:04 PM

Regular
******
Senior Member
1,200 posts

Joined: Dec 2008
QUOTE(soonwai @ Feb 23 2017, 06:19 PM)
Maybe TS has a reason to use 2 subnets. TS, care to elaborate?
*
You are absolutely right I needed to have 2 subnet (192.168.1.xx) for office use and (192.168.88.xx) for training section use.

The MikroTik Router (192.168.88.xx) is a more powerful, more feature and there are already some rules being set that to computers IP's. While Under Dlink Router (192.168.1.xx) just normal router for Office staff usage.

Again the Dlink router is bridge to Modem and the MikroTik router is connected to the Dlink Lan Port.

I did add on the Dlink router for static route to 192.168.88.1 unfortunately subnet under 192.168.1.xx still unable to connect to 192.168.1.xx.
soonwai
post Feb 23 2017, 10:47 PM


*******
Senior Member
9,989 posts

Joined: Oct 2007
From: KL


QUOTE(aoisky @ Feb 23 2017, 10:04 PM)
You are absolutely right I needed to have 2 subnet (192.168.1.xx) for office use and (192.168.88.xx) for training section use.

The MikroTik Router (192.168.88.xx) is a more powerful, more feature and there are already some rules being set that to computers IP's. While Under Dlink Router (192.168.1.xx) just normal router for Office staff usage.

Again the Dlink router is bridge to Modem and the MikroTik router is connected to the Dlink Lan Port.

I did add on the Dlink router for static route to 192.168.88.1 unfortunately subnet under 192.168.1.xx still unable to connect to 192.168.1.xx.
*
Sometimes the reason things don't work is because it's a DLink. Just joking. :-) But seriously, I thought it's just missing a route, can't really say what else is wrong without actually being there to diagnose.

This post has been edited by soonwai: Feb 23 2017, 10:48 PM
TSaoisky
post Feb 23 2017, 11:00 PM

Regular
******
Senior Member
1,200 posts

Joined: Dec 2008
QUOTE(soonwai @ Feb 23 2017, 10:47 PM)
Sometimes the reason things don't work is because it's a DLink. Just joking. :-) But seriously, I thought it's just missing a route, can't really say what else is wrong without actually being there to diagnose.
*
I thought so, that mean adding the static route for Dlink correctly should be able to access other subnet right ?

Current
Modem <---- Dlink Router <---- MikroTik
[192.168.1.XX] [192.168.88.xx]

Wonder how to make also can
Modem <---- Dlink Router <----> MikroTik
[192.168.1.XX] [192.168.88.xx]


This post has been edited by aoisky: Feb 23 2017, 11:04 PM
jio
post Feb 23 2017, 11:12 PM

Casual
***
Junior Member
368 posts

Joined: May 2005
You probably had the mikrotik connected to the dlink with port 1 (the default WAN port) with dhcp and the connection from mikrotik to dlink being NATed plus with the default firewall of mikrotik dropping the incoming connection from the WAN port. Below is based on what I think your current setup is.

1. Based on your current network subnets, don't use netmask 255.0.0.0 on your mikrotik side.
2. You will need a static 192.168.1.x ip for the mikrotik & add a new route for dlink to 192.168.88.x with that ip you assigned to the mikrotik as the gateway.
3. But I will recommend to use mikrotik as your main router instead of the dlink, but that can wait when you have time to reconfigure your network.

This post has been edited by jio: Feb 23 2017, 11:14 PM
TSaoisky
post Feb 23 2017, 11:30 PM

Regular
******
Senior Member
1,200 posts

Joined: Dec 2008
QUOTE(jio @ Feb 23 2017, 11:12 PM)
You probably had the mikrotik connected to the dlink with port 1 (the default WAN port) with dhcp and the connection from mikrotik to dlink being NATed plus with the default firewall of mikrotik dropping the incoming connection from the WAN port. Below is based on what I think your current setup is.

1. Based on your current network subnets, don't use netmask 255.0.0.0 on your mikrotik side.
2. You will need a static 192.168.1.x ip for the mikrotik & add a new route for dlink to 192.168.88.x with that ip you assigned to the mikrotik as the gateway.
3. But I will recommend to use mikrotik as your main router instead of the dlink, but that can wait when you have time to reconfigure your network.
*
Router MikroTik (WAN Port) connect to Router Dlink (Lan Port) static IP assign. The reason why Dlink as main router is Dlink is permanent while MikroTik isn't as MikroTik may be move out for other function in short mobility purpose.

Looking at my current network setup 192.168.88.xx can access to 192.168.1.xx but 192.168.1.xx can't access to 192.168.88.xx, Not Possible for 192.168.1.xx to access to 192.168.88.xx subnet ?

This post has been edited by aoisky: Feb 23 2017, 11:33 PM
jio
post Feb 23 2017, 11:49 PM

Casual
***
Junior Member
368 posts

Joined: May 2005
The mikrotik need a static 192.168.1.x ip (e.g 192.168.1.253) & new route added to the dlink for 192.168.88.x with the static 192.168.1.x ip of the mikrotik as the gateway. Also you will need to disable the firewall rule (forward to WAN port) that drop the incoming connection to the WAN port.

This is basically what I already hinted in my original post & I assumed you should know enough basic knowledge of what it was.

This post has been edited by jio: Feb 23 2017, 11:50 PM
TSaoisky
post Feb 24 2017, 08:25 PM

Regular
******
Senior Member
1,200 posts

Joined: Dec 2008
QUOTE(jio @ Feb 23 2017, 11:49 PM)
The mikrotik need a static 192.168.1.x ip (e.g 192.168.1.253) & new route added to the dlink for 192.168.88.x with the static 192.168.1.x ip of the mikrotik as the gateway. Also you will need to disable the firewall rule (forward to WAN port) that drop the incoming connection to the WAN port.

This is basically what I already hinted in my original post & I assumed you should know enough basic knowledge of what it was.
*
If that the case, all under same subnet it'll be easy and no such issue arise from one subnet can connect to other and the other unable to connect to it.

There is a reason why my network environment has to be set two different subnet group.
jio
post Feb 24 2017, 09:12 PM

Casual
***
Junior Member
368 posts

Joined: May 2005
I don't know what to say other than you don't understand what I wrote.

1. When you connecting your mikrotik to the dlink, it does get a dynamic IP 192.168.1.x via DHCP. That means your mikrotik had a static IP 192.168.88.1 & a dynamic IP 192.168.1.x.
2. The reason why your clients on mikrotik side can connect to the 192.168.1.x range is because the connection NAT by mikrotik router. That means your mikrotik will connect to the server on 192.168.88.x client behalf and the originating connection IP will be masqueraded as 192.168.1.x IP of the mikrotik. The server will see the connections is made by mikrotik's 192.168.1.x & not by 192.168.88.x.
3. The clients on dlink side cannot connect to 192.168.88.x because there is no route to that subnet. The dlink router will have to route it somewhere or else it will use the default route to the internet which in this case will not work. That's why it will have to route it to mikrotik but mikrotik will need a static 192.168.1.x IP or else the route won't work if the IP changed.
4. And mikrotik by default (if you use quickset) will have firewall filter rules to drop incoming connections from the WAN port, that you will have to disable or else you still cannot connect from 192.168.1.x to 192.168.88.x.
5. Stop trying to justify your network decision what so ever. I never questioned it & it has nothing to do with your problem nor my answer.

This post has been edited by jio: Feb 24 2017, 09:17 PM
TSaoisky
post Feb 25 2017, 01:04 AM

Regular
******
Senior Member
1,200 posts

Joined: Dec 2008
QUOTE(jio @ Feb 24 2017, 09:12 PM)
I don't know what to say other than you don't understand what I wrote.

1. When you connecting your mikrotik to the dlink, it does get a dynamic IP 192.168.1.x via DHCP. That means your mikrotik had a static IP 192.168.88.1 & a dynamic IP 192.168.1.x.
2. The reason why your clients on mikrotik side can connect to the 192.168.1.x range is because the connection NAT by mikrotik router. That means your mikrotik will connect to the server on 192.168.88.x client behalf and the originating connection IP will be masqueraded as 192.168.1.x IP of the mikrotik. The server will see the connections is made by mikrotik's 192.168.1.x & not by 192.168.88.x.
3. The clients on dlink side cannot connect to 192.168.88.x because there is no route to that subnet. The dlink router will have to route it somewhere or else it will use the default route to the internet which in this case will not work. That's why it will have to route it to mikrotik but mikrotik will need a static 192.168.1.x IP or else the route won't work if the IP changed.
4. And mikrotik by default (if you use quickset) will have firewall filter rules to drop incoming connections from the WAN port, that you will have to disable or else you still cannot connect from 192.168.1.x to 192.168.88.x.
5. Stop trying to justify your network decision what so ever. I never questioned it & it has nothing to do with your problem nor my answer.
*
Ya don't understand you. can you simplify it please.

I just want my client in 192.168.1.xx to be able to connected to the 192.168.88.xx

so referring to your guide i should have 192.168.1.xx ip on MT router as well ? MT router to have both .1.xx and .88.xx IP ? for this part can Master jio enlighten. and then needed to check on the firewall rules for MT router side right.

btw Master Jio it is not my network decision, my management need it to have it two different subnet. If for me all under single subnet would not have such hassle.

appreciate you masterly skill and advise

 

Change to:
| Lo-Fi Version
0.0130sec    0.60    5 queries    GZIP Disabled
Time is now: 29th March 2024 - 09:45 PM