What's new

Routing RT-AX88U

  • 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!

What should I set rules in the ASUSA routing table to see devices from the TP-LINK network?

  • a

    Votes: 0 0.0%
  • a

    Votes: 0 0.0%

  • Total voters
    0

mawoj

New Around Here
Hello, Could someone help me set up routing table rules on my network The LAN-WAN network looks like this; (Modem from ISP) - (WAN Router ASUS RT-AX88U (192.168.50.0) LAN- (WAN Router TP-LINK192.168.7.0)
I have various printer devices, cameras etc. connected to ASUS and TP-LINK.
Being logged in to the TP LINK network (192.168.7.X), I can see devices in the ASUS network (192.168.50.X).
Being in the ASUS network (192.168.50.X) I can not see devices in the TP LINK network (192.168.7.X.
What should I set rules in the ASUSA routing table to see devices from the TP-LINK network?. Can you help?
Below are TP-LINK routing settings
 

Attachments

  • routing TP LINK.jpg
    routing TP LINK.jpg
    38.3 KB · Views: 83
The TPLink needs to have a fixed address on your 192.168.50.0 network - set this up as a static entry in your Asus's DHCP table.

Then you need a routing entry on the Asus router "192.168.7.0 255.255.255.0 192.168.50.xxx", where xxx is the fixed address of the TPLink.
 
Unfortunately, you still don't see anything in the address 192.168.7.xxx
TPLink has the address 192.168.50.50
 

Attachments

  • Asus routing .jpg
    Asus routing .jpg
    64.7 KB · Views: 85
  • DHCP ASUS reserwation address.jpg
    DHCP ASUS reserwation address.jpg
    28.4 KB · Views: 83
I may be slightly misunderstanding the topology here. What exactly is the TPLink configured to do? Does it have a separate WAN connection, or is your 192.168.50.0 its "WAN"?

You talk about "seeing" devices. What exactly do you mean by that? Part of your post suggests there's some communication possible - can you ping from one device to another? In which directions?

My initial answer was just supposing that you have WAN <Asus> 192.168.50.0 <TPLink> 192.168.7.0 setup, and we just needed to make that the Asus knew how to get to 192.168.7.0 (and it in turn should tell anyone else on the 50 network).
 
I may be slightly misunderstanding the topology here. What exactly is the TPLink configured to do? Does it have a separate WAN connection, or is your 192.168.50.0 its "WAN"?

You talk about "seeing" devices. What exactly do you mean by that? Part of your post suggests there's some communication possible - can you ping from one device to another? In which directions?

My initial answer was just supposing that you have WAN <Asus> 192.168.50.0 <TPLink> 192.168.7.0 setup, and we just needed to make that the Asus knew how to get to 192.168.7.0 (and it in turn should tell anyone else on the 50 network).
TP LINK WAN192.168.50.50 LAN 192.168.7.1
ASUS WAN xxx.xxx.1.1, LAN 192.168.50.1
PING 192.168.7.1 to 192.168.50.1 etc is working fine
PING 192.168.50.1 to 192.168.7.1 is not working
 
You have correct downward routing, as shown by the fact that 192.168.50.1 can reply to the ping.

So it must be the firewall (and maybe an unwanted NAT?). The TPLink is regarding the 50 network as "outside" and refusing incoming connections. You probably need to totally shut off the NAT and firewall on the TPLink.
 
NAT and firewall on TP Link has been turned off, the router has been reset but nothing has changed, from the network xxx.xxx.50.x no devices in the network xxx.xx.7.x can be seen
 
Are you sure the TPLink responds to incoming pings on the WAN side? That's an option on Asus, which defaults to off. Try another device?

Although disabling the firewall generally might defeat such a rule anyway.
 
Please find attached below PING information.
 

Attachments

  • Ping from 192.168.7.1 (TPLINK) to 192.168.50.1 (ASUS) not OK .jpg
    Ping from 192.168.7.1 (TPLINK) to 192.168.50.1 (ASUS) not OK .jpg
    64.1 KB · Views: 80
  • Routing ASUS 20220106.jpg
    Routing ASUS 20220106.jpg
    70.5 KB · Views: 86
  • PING 192.168.50.1 to 192.168.50.50 (TP LInk WAN) OK.jpg
    PING 192.168.50.1 to 192.168.50.50 (TP LInk WAN) OK.jpg
    68.1 KB · Views: 74
  • Ping from 192.168.50.1 to 192.168.7.1 NOT OK.jpg
    Ping from 192.168.50.1 to 192.168.7.1 NOT OK.jpg
    40.1 KB · Views: 73
Based on your responses, here is what I've gathered.

net_diagram.png



First, let's find a device that responds to ping on the 192.168.7.x network.
From the TP-Link router, can you ping another device on the 192.168.7.x network? (don't ping the TP-Link's 192.168.7.1 interface, were going to avoid that for now).

Once you find a device that responds to ping in the 192.168.7.x network, try to ping it from the ASUS router.

If you can ping from TP-Link but not from ASUS, you still have something filtering the pings.
If successful from ASUS to device in 192.168.7.x, next, try from a device in the 192.168.50.x network.

If you can't ping from a device in the 192.168.50.x network, but can from ASUS, it may be an issue with ICMP redirects and routes.
Try to add a manual route to a device in the 192.168.50.x network, consult the device's documentation for how to do this. The route should look identical to what you added to the ASUS router "add route 192.168.7.0 255.255.255.0 192.168.50.50"
 
Thank you for all your help.
Unfortunately it does not work.
So I created the LAN -LAN network, despite its imperfections.
 

Latest threads

Sign Up For SNBForums Daily Digest

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