Can't connect locally with bridge mode

[tunt19]

Hey, NextPVR was working fine with NAT but I set my gateway to bridge mode and using cmd 'ipconfig' IPv4 address is showing my actual public IP (same as whatsmyip sites show). I can get Kodi working on NextPVR machine with 127.0.0.1 but any other computer can't connect to it unless I set "remote access" on. Any ideas how to fix without using public IPs?

[mvallevand]

Remote access simply means it is not a private non-routable IP. It doesn't mean you have to expose NextPVR to the internet. You will need to change the default username, password and PIN.

Martin

[tunt19]

Remote access simply means it is not a private non-routable IP.  It doesn't mean you have to expose NextPVR to the internet.  You will need to change the default username, password and PIN.

Martin

Yeah I have used the remote access every now and then. I have changed the default port, password and PIN.

The problem is when gateway is in bridge mode I can't find computer's "local IPs" because IPv4 address in command prompt when typing 'ipconfig' shows my public IP instead of 192.168.0.x and I don't want to expose my system to internet 24/7.
Is the only option to set back to NAT or is there a way to find local IP in bridge mode?

[mvallevand]

If ipconfig is showing you on public IP then you are on the Internet and you are depending on your firewall.

Martin

[tunt19]

I found a way. I set my server's 'Link-local IPv6 Address' found under 'ipconfig' to Kodi and web browser and it worked like a charm.

[mvallevand]

You would still be on the internet with the ipv4 and ipv6 though. Most times when you use an Internet gateway router in bridge mode, you should still connect it to a router and not to a PC.

Martin

[tunt19]

I'm not 100% sure what you meant with that since I'm not familiar with networking. But I tested this by physically disconnecting my bridge mode Arris gateway from internet and using NextPVR server's 'Link-Local IPv6' address I could connect to it from my other PCs and everything is working now. And after connected systems back to internet I couldn't access it with public IPv4 as intended.