F5F Stay Refreshed Power Users Networks Attempting to route traffic via two network devices

Attempting to route traffic via two network devices

Attempting to route traffic via two network devices

F
Folsam
Junior Member
11
06-23-2023, 09:31 PM
#1
I have a primary router assigned a public IP via PPOE, while another connected via LAN receives a dynamic IP. This setup likely explains why Router 2 has a private IP. A Raspberry Pi is linked to Router 2, and you need to forward a port for remote access to your Plex server. You mentioned trying an article but it didn’t work—can you clarify how to proceed? I’m new to this.
F
Folsam
06-23-2023, 09:31 PM #1

I have a primary router assigned a public IP via PPOE, while another connected via LAN receives a dynamic IP. This setup likely explains why Router 2 has a private IP. A Raspberry Pi is linked to Router 2, and you need to forward a port for remote access to your Plex server. You mentioned trying an article but it didn’t work—can you clarify how to proceed? I’m new to this.

B
baris070x
Junior Member
49
06-30-2023, 07:27 PM
#2
You don’t require direct physical access, as long as you can reach their management interface. Ideally, you’d simply redirect a port from router 1 to a port on router 2, then forward it to the Pi. However, you must be able to set up both routers accordingly.
B
baris070x
06-30-2023, 07:27 PM #2

You don’t require direct physical access, as long as you can reach their management interface. Ideally, you’d simply redirect a port from router 1 to a port on router 2, then forward it to the Pi. However, you must be able to set up both routers accordingly.

M
matt455
Member
188
06-30-2023, 07:44 PM
#3
I have the ability to reach their management panel, and as discussed earlier, I attempted the steps from the article but they failed. I used port 32400, setting it up in both routers' port forwarding configurations—from router 1 I forwarded 32400 to the private IP of router 2, and in router 2 I forwarded 32400 to the Pi's IP address. Please remember that all these settings use the same internal and external ports: 32400.
M
matt455
06-30-2023, 07:44 PM #3

I have the ability to reach their management panel, and as discussed earlier, I attempted the steps from the article but they failed. I used port 32400, setting it up in both routers' port forwarding configurations—from router 1 I forwarded 32400 to the private IP of router 2, and in router 2 I forwarded 32400 to the Pi's IP address. Please remember that all these settings use the same internal and external ports: 32400.

H
Hooded_Master
Member
187
07-16-2023, 06:52 PM
#4
Obtain the IP address of Router 2. Navigate to Router 1's interface and instruct it to forward port 32400 to the IP of Router 2. Within Router 2, configure the same port forwarding to the desired destination IP address for the target device. Regarding Router 2's perspective, verify that Router 1 is serving clients under 192.x.x.x and Router 2 is directing them to 196.x.x.x.
H
Hooded_Master
07-16-2023, 06:52 PM #4

Obtain the IP address of Router 2. Navigate to Router 1's interface and instruct it to forward port 32400 to the IP of Router 2. Within Router 2, configure the same port forwarding to the desired destination IP address for the target device. Regarding Router 2's perspective, verify that Router 1 is serving clients under 192.x.x.x and Router 2 is directing them to 196.x.x.x.

S
SrGeed
Junior Member
13
07-24-2023, 05:38 AM
#5
The router 2's IP address should remain consistent since it relies on DHCP. Consider assigning a static IP or reserving a DHCP slot for it. Also, verify that the devices are on separate subnets.
S
SrGeed
07-24-2023, 05:38 AM #5

The router 2's IP address should remain consistent since it relies on DHCP. Consider assigning a static IP or reserving a DHCP slot for it. Also, verify that the devices are on separate subnets.

K
Killeraft
Junior Member
22
07-28-2023, 01:13 AM
#6
Another point is why router 2 was created initially. If the goal is to extend WiFi coverage, setting it up as a bridge rather than leaving it in router mode is the best approach. Making it a standalone network isn't very practical since NAT can still let you reach devices on router 1 if you remember their IP address.
K
Killeraft
07-28-2023, 01:13 AM #6

Another point is why router 2 was created initially. If the goal is to extend WiFi coverage, setting it up as a bridge rather than leaving it in router mode is the best approach. Making it a standalone network isn't very practical since NAT can still let you reach devices on router 1 if you remember their IP address.

L
lizzypink
Junior Member
16
07-28-2023, 06:05 AM
#7
Router 2's IP is 192.168.0.x while router 1 uses 192.168.1.x. It seems router 2 lacks a WAN connection, which might be the issue. I followed your previous steps but results weren't helpful. Checked openportchecktool.com, but no traffic found. Plex also didn’t show any routes. The SPI Firewall is enabled on both devices—could that be affecting connectivity? Should I forward additional ports as well?
L
lizzypink
07-28-2023, 06:05 AM #7

Router 2's IP is 192.168.0.x while router 1 uses 192.168.1.x. It seems router 2 lacks a WAN connection, which might be the issue. I followed your previous steps but results weren't helpful. Checked openportchecktool.com, but no traffic found. Plex also didn’t show any routes. The SPI Firewall is enabled on both devices—could that be affecting connectivity? Should I forward additional ports as well?