[mythtv-users] Web Frontend stopped working yesterday

[Janusz S. Bień]

On Sat, Mar 09 2019 at  4:54 +00, Ian Cameron wrote:
> On Sat, 9 Mar 2019 at 03:14, James Linder <jam at tigger.ws> wrote:
>
>  > On 9 Mar 2019, at 12:09 am, mythtv-users-request at mythtv.org wrote:
>  > Nmap doesn't show the port 6544:
>
> Try:
>
> sudo netstat -anp | grep myth
>
> to see the ports the back-end is listening on.



--8<---------------cut here---------------start------------->8---
tcp        0      0 0.0.0.0:6543            0.0.0.0:*               LISTEN      1241/mythbackend    
tcp        0      0 192.168.0.4:37086       192.168.0.2:65001       ESTABLISHED 1241/mythbackend    
tcp6       0      0 :::6543                 :::*                    LISTEN      1241/mythbackend    
udp        0      0 0.0.0.0:53352           0.0.0.0:*                           1241/mythbackend    
unix  3      [ ]         STREAM     CONNECTED     1468747  1241/mythbackend     
unix  2      [ ]         STREAM     CONNECTED     379355   1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     32895    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     29589    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     29588    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     31785    1241/mythbackend     
unix  2      [ ]         STREAM     CONNECTED     31851    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     32680    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     31854    1241/mythbackend     
unix  3      [ ]         STREAM     CONNECTED     31570    1241/mythbackend 
--8<---------------cut here---------------end--------------->8---

As I said before:

the Web frontend port 6544 is not open at all,

an attempt to connect to the open port 6543 takes forever.

>
> Cheers, Ian

On Sat, Mar 09 2019 at 11:13 +08, James Linder wrote:

[...]

> 1. The modem firewall’s ONLY purpose is to stop window machines that have been virused calling OUT
>    Your modem does NAT and noone on the internet can call into your machines
>       Internet routers may not route private IPs eg 10.x.y.z 192.168.x.y (and class B’s
>    Even if your router gets hacked, reboot restores all files.

Irrelevant.

> 2. Every modem I’ve encountered *can* set their own IP

Which IP? Anyway mine cannot.

>
> 3. 127.0.0.1 is the loopback address, you cannot use it as a network address.

Of course I can.
>
> 4. Ofcourse you can and it’s easy but not trivial to deal with

???

At http://127.0.0.1/ there is just Apache2 Debian Default Page.

>
> 5. You can arrange internet access. A ssh tunnel is a good option
>    http://tigger.ws/wiki/index.php5?title=Port_Forward
>    but there are password solutions with server options on your modem

Irrelevant. Tunnel to what???

>
> 6. Now none of your machines (on a trusted network ie you trust everyone) need a firewall (1)

Irrelevant.

Best regards

Janusz

-- 
             ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien