/tech/ - technology

>>1339
It its a standard star based topology it should be fine, unless there is NAT between one and two. Then the NAT Router on Level two will need to forward for you.

Unless the routers are using a protocol like RIP then they won't be able to communicate across networks as they routing tables of the far left router (as an example) would not be populated with the network address of the far right router. If a static route or default route was setup to a gateway router with a populated routing table then this would negate the issue.

I suppose the first question should be this, can you ping the target PC?

Also port forwarding, unless the target PC is behind a NAT will likely not be the solution as I assume this is a Local Area Network and all PCs are on a 192.168.0.0 style network.

>>1341
I thought NAT as I have sen that implemented a few times.

Does OP know the IP Range, and the Router IP? Can OP ping the router?

>>1342
I can't ping the router, no.
For some reason it can connect to the internet just fine though. All I did was plug the first router into the second, set the DNS server to 192.168.1.1, and set the static IP address to 192.168.1.145.

>>1343
Did you set these up yourself?

>>1344
yes

>>1347
At a guess the PCs individually know where to send their traffic for the internet through the configured Default Gateway but that's where their knowledge of the network ends. The ARP protocol means they can find other PCs on the local network, but not the extended network. The router's can pass information up the chain to the default gateway, but that's where it ends. I think you should look into a Routing Protocol such as RIP (there are others and different versions) in order to ensure the routers all have filled in Routing Tables of the different networks.

Check the router models and see if they support a routing protocol (most, of not all do) and then research how to best configure it. I genuinely believe this will be the solution, assuming it's not already implemented automatically.

>>1339
ping 192.168.1.255
arp -a

if router 1 is alias alice@alice:22 with eth-lan as 192.168.1/24, then if router 2 is alias bob@bob:22 with eth-wan as some host within 192.168.1/24, then the above command will find hostname bob. ensure that bob has port forwarding enabled, and that bob accepts ssh:22 from eth-wan interface. then configure your session to open the ports accordingly on bob.

guidance circa 2001, reaffirm 2003, reaffirm 2006, and last reaffirm 2011: recommend abandon all netgear product lines with permanent prejudice. same for trendnet, linksys (all soho/home hw versions post 2006), cisco (mirror linksys), and tplink.

t. first user to this obscure arcanum site.

>>1341
is RIP necessary for only a Cascade LAN though? I can understand needing it for say, each of the routers on level 1. But I'll mention again I'm only working with the PCs on the far right of the network in the pic I posted
>>1350
the think is I have no trouble "finding" the hostname. If I go onto Optimum's firmware, I can easily see that 192.168.1.145 is WNDR3500. The trouble is I can't ping that router as you can see:
>>1342
>>1343

>>1354
I'm afraid you'll need some sort of routing table, static route, default route or routing protocol between the routers if (referring to the attached photo) PC0-5 cannot ping PC6-8.

This is because when PC0 issues a ping to an issued address (let's say 192.168.1.3) it first goes to the configured default gateway, of R2 and is then routed onto the 192.168.1.0 network. R2 is aware of all networks DIRECTLY connected to it by using ARP address resolution (something done automatically).

Because R2 is directly connected to R3 and the 10.10.10.0 network is (probably manually and static) assigned to the port, it also knows that R3 is attached. That however, is where R2's knowledge ends.

In order for PC1 to ping PC8 there MUST be a routing table record of the 192.168.20.0 network in R2. This is essentially just telling the router "If you receive a packet directed to 192.168.20.0 network, send it to R1 on the 10.10.10.0 network".

You could setup a static route in both routers to configure it all manually, but if the network is likely to change or expand then you'll want a dynamic protocol like RIP or another type.

It's been a while since I studied this, so hopefully I haven't made any mistakes. I'm sure someone can point them out if I did. Hope this helps.