Jellyfin portforwarding

Installing and Using OpenWrt Network and Wireless Configuration
7

I have removed [202:34164] -A zone_wan_prerouting -m comment --comment "!fw3: Plex" -j DNAT --to-destination 192.168.0.124

Gateway was a mistake

0.124 has definitely OpenWrt as a gateway, here is dhpcpcd.conf

interface eth0
static ip_address=192.168.0.121/24
static routers=192.168.0.2
static domain_name_servers=192.168.0.172
8

I guess you can see the mistake.

9

I need holidays :slight_smile: Thanks

1 Like
10

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.

11

Unfortunately no, it's still not working when I enter my public IP

12

iptables-save -c -t nat | grep Jellyfin

13

Could it be that my WAN interface shows this `IPv4 Upstream
Protocol: DHCP client
Address: 10.112.101.23/25
Gateway: 10.112.101.1
DNS 1: 192.168.0.172

But my public IP is something completely different?`

14

Why is your router at 192.168.0.2?

1 Like
15

This is an RFC1918 address and is not publicly routable. Is your OpenWrt router directly connected to your internet connection, or is there another NAT device upstream (such as a modem+router combo unit or an ISP supplied router, etc.)?

2 Likes
16

Because my original router, Archer C6, was 0.1 and Raspberry Pi was plugged into it. I then swapped them around

17

Yes it is, it''s connected to a power line in my study which in turn connects to powerline in our living room where our ISP has placed the lan port to connect routers/modems
Port forwarding worked before on Archer C6 without any issues
My network is like this

Network setup
Network setup1536×864 27.8 KB

18

What address do you get if you plug a device directly into the "ISP LAN port" ?

19

I will try that later on tonight after I stop working. I want to measure speed without powerlines anyway

20

Don't forget to post the iptables command too.

21 
[0:0] -A zone_lan_postrouting -s 192.168.0.0/24 -d 192.168.0.124/32 -p tcp -m tc                             p --dport 8096 -m comment --comment "!fw3: Jellyfin (reflection)" -j SNAT --to-s                             ource 192.168.0.2
[0:0] -A zone_lan_postrouting -s 192.168.0.0/24 -d 192.168.0.124/32 -p udp -m ud                             p --dport 8096 -m comment --comment "!fw3: Jellyfin (reflection)" -j SNAT --to-s                             ource 192.168.0.2
[0:0] -A zone_lan_prerouting -s 192.168.0.0/24 -d 10.112.101.23/32 -p tcp -m tcp                              --dport 8096 -m comment --comment "!fw3: Jellyfin (reflection)" -j DNAT --to-de                             stination 192.168.0.124:8096
[0:0] -A zone_lan_prerouting -s 192.168.0.0/24 -d 10.112.101.23/32 -p udp -m udp                              --dport 8096 -m comment --comment "!fw3: Jellyfin (reflection)" -j DNAT --to-de                             stination 192.168.0.124:8096
[0:0] -A zone_wan_prerouting -p tcp -m tcp --dport 8096 -m comment --comment "!f                             w3: Jellyfin" -j DNAT --to-destination 192.168.0.124:8096
[0:0] -A zone_wan_prerouting -p udp -m udp --dport 8096 -m comment --comment "!f                             w3: Jellyfin" -j DNAT --to-destination 192.168.0.124:8096
22

All hits are 0, so no packet reached the firewall.

23

That is not what I asked...

1 Like
24

I have plugged the Raspberry directly to the lan port at home, by passing both powerline devices, and the IP is still the same 10.112.101.23/25 even though my public IP starts with 185...... when I check it via curl ifconfig.me command

25

If you don't have any control on the ISP lan port, then you cannot do much. Most likely you are behind CGNAT and you can only discuss it with your ISP, if they can offer you a public IP.

3 Likes
26

What about setting up VPN, would that help? I have IPVanish on my phone