What's new

how to connect to a device in a different subnet?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

CLaudio

Occasional Visitor
hello in my house i have the main router which is connected to internet and create a local network like this (call it NET-A):

router ip: 192.168.1.254
DHCP 192.168.1.11 - 192.168.1.199

connected to NET-A through the ethernet there's an access point to create a wireless network (call it NET-B) and it's configured like this:

-- WAN --
IP Address:192.168.1.13
Subnet Mask:255.255.255.0
Gateway:192.168.1.254

-- LAN -- (the wireless network)
ip: 192.168.2.1
subnet mask: 255.255.255.0
DHCP enabled from 192.168.2.100 to 192.168.2.200

now my problem is that i want to connect a device in the NET-A (let's say with ip: 192.168.1.5) with a device connected on NET-B (WI-FI, let's say 192.168.2.106) and it seems NOT POSSIBLE.

what's my mistake? if i ping the second device from the first device it doesn't work... if i do the opposite it DOES WORK.

i m not such a great expert on LAN systems thanks

my problem is that i want to map a port from the main router to redirect the WEB traffic to a device connected to the WI-FI access point
 
You have 2 subnets, the clients connected to this 2 nets can not see
each other only clients to same NET can see each other.
1: 192.168.1.xxx
2: 192.168.2.xxx

Try to change the IP on main (1) router lets say 192.168.1.1.
IP Address:192.168.1.1
Subnet Mask:255.255.255.0
Gateway:192.168.1.1

From Router (1) LAN port to LAN port on AP (2).
Now you should see that the Router (1) gives AP (2) a IP
The setting can look like this on the AP (2):
IP Address:192.168.1.25
Subnet Mask:255.255.255.0
Gateway:192.168.1.1
 
Last edited:
You have 2 subnets, the clients connected to this 2 nets can not see
each other only clients to same NET can see each other.
1: 192.168.1.xxx
2: 192.168.2.xxx

Try to change the IP on main (1) router lets say 192.168.1.1.
IP Address:192.168.1.1
Subnet Mask:255.255.255.0
Gateway:192.168.1.1

From Router (1) LAN port to LAN port on AP (2).
Now you should see that the Router (1) gives AP (2) a IP
The setting can look like this on the AP (2):
IP Address:192.168.1.25
Subnet Mask:255.255.255.0
Gateway:192.168.1.1

actually from the device on the NET-B (192.168.2.x) i can ping a device on the NET-A (192.198.1.x).... the opposite way doesn't work.
on the other hand when i try to set the DHCP of the access point to assign a ip-range like 192.168.1.x it says "The LAN IP should not be in the same subnet with WAN IP. Please input another one."
 
Are you using double-NAT? If so, don't.

You should be able to put the WiFi into AP-mode or simply use only the LAN ports to accomplish this.

I'm a bit confused about your network topology though, so sharing that would probably help.
 
Are you using double-NAT? If so, don't.

You should be able to put the WiFi into AP-mode or simply use only the LAN ports to accomplish this.

I'm a bit confused about your network topology though, so sharing that would probably help.

well
the access point (TP-LINK TD-W8970)
has 3 operation modes:
ADSL Modem Router Mode
3G Router Mode
Wireless Router Mode

and it's set to the third one - WIreless Router Mode
this is the configuration:
mhg3s1.jpg
 
Because you have a double NAT situation as @Nullity suspected, you need to create a static route on the main router that says that network 192.168.2.x is accessible via gateway device 192.168.1.13.
 
Are you using double-NAT? If so, don't.

You should be able to put the WiFi into AP-mode or simply use only the LAN ports to accomplish this.

I'm a bit confused about your network topology though, so sharing that would probably help.
do you mean i should disable the DHCP on the second router (NET-B) ?
 
OK NOW I GOT IT
just connected the second router to the first through the LAN port instead of WAN
and it's working perfectly

NOW
i only have one problem :)
i have connected a 3rd tp-link router to the second one as a repeater... and it worked quite good
now... after i changed the second router to be simply an access point... the repeater is not working anymore. well it's working for the local network but it doesnt connect me to the internet
 
AND the really bad new here is that i can't configure the Accesso Point while in Access Point mode
so i have no clue how to make the repeater working...
and that maybe brings me back to my first situation
 
the repeater is not working anymore. well it's working for the local network but it doesnt connect me to the internet
Have you completely powered off the repeater before turning it back on?

And the same for any clients attached to the repeater.
 
Have you completely powered off the repeater before turning it back on?

And the same for any clients attached to the repeater.
yeah.
but it's a really complicated procedure for Tp-link to Tp-link only
it goes through the MAC address
i m afraid config broken after i changed the TP-Link router to an AP


and now i don't even know how to access the AP... the default IP doesnt work even through direct cable... probably i should reset to defaults... what a mess
 
use the DHCP connection report on the router assigning its address or if static you should already know it and can ping it from the lan side. There may also be something in the device logs or
routing table.
 
Because you have a double NAT situation as @Nullity suspected, you need to create a static route on the main router that says that network 192.168.2.x is accessible via gateway device 192.168.1.13.
So how would you add this?

I have a FiOS actiontec router and I can add a new route:
Destination: 192.168.2.0
Netmask: 255.255.255.255
Gateway: 192.169.1.3
Mertic: 0

So would this work for all subnet-2 networking?
 
So how would you add this?

I have a FiOS actiontec router and I can add a new route:
Destination: 192.168.2.0
Netmask: 255.255.255.255
Gateway: 192.169.1.3
Mertic: 0

So would this work for all subnet-2 networking?
Sorry, I don't know anything about Actiontec routers, but I'd guess you need the following:

Destination: 192.168.2.0 <-- Assuming subnet-2 is 192.168.2.1 to 192.168.2.254
Netmask: 255.255.255.0 <-- Assuming subnet-2 netmask is 255.255.255.0
Gateway: 192.168.1.3 <-- I assume 169 was a typo, and 192.168.1.3 is the WAN address of router-2.
Mertic: 0

http://support.actiontec.com/doc_files/Static_Routing_Explained.pdf
 
Sorry, I don't know anything about Actiontec routers, but I'd guess you need the following:

Destination: 192.168.2.0 <-- Assuming subnet-2 is 192.168.2.1 to 192.168.2.254
Netmask: 255.255.255.0 <-- Assuming subnet-2 netmask is 255.255.255.0
Gateway: 192.168.1.3 <-- I assume 169 was a typo, and 192.168.1.3 is the WAN address of router-2.
Mertic: 0

http://support.actiontec.com/doc_files/Static_Routing_Explained.pdf
Yep sorry for the typos. I wasn't sure about the metric value.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top