Motion problems

[Karl Auer]

On Mon, 2019-01-14 at 13:34 +0000, Grizzly via ubuntu-users wrote:
> > on the same premises, as it is seems you are going through a NAT
> > router.
> No, on the same local network (in fact on the same table beside the
> first PC)

If you are on the same local network, then (unless you have some pretty
advanced networking going on like VLANS) the router is not involved and
you do not need port forwarding or whatever. Also any changes you made
to the router are unlikely to have had any effect at all. You WILL need
those changes or something similar to access Motion from outside your
network.

> > Another possibility is that the streamer is listening for
> > connections only on the loopback interface (lo).

Another user here with actual experience of Motion says that exactly
this is the case, so do what he says :-)

> > If you know the port that the streamer uses, you can grep for it in
> > the output from "netstat -an".
> 8080 & 8081

:-) You need to use netstat to find out what interfaces it's listening
on. Grep for those ports in the output of "netstat -an" and look for
lines with "LISTEN" at the end. This is what the ssh server looks like
on my laptop (spaces compressed to avoid line-wrap I hope):

$ netstat -an | grep "^tcp" | grep ":22"
tcp  0 0 0.0.0.0:22 0.0.0.0:* LISTEN     
tcp6 0 0 :::22      :::*      LISTEN

The values in the third column indicate that ssh is listening for
connections on all available interfaces. Here is the same thing for
SMTP, which runs only on my loopback interface:

$ netstat -an | grep "^tcp" | grep ":25"
tcp  0 0 127.0.0.1:25 0.0.0.0:* LISTEN     
tcp6 0 0 ::1:25       :::*      LISTEN

Here the third column shows specific interface addresses, those on my
loopback interface.

If you run the same command but substitute 8080 or 8081, you will be
able to see whether Motion is listening on a particular interface or on
all.

Regards, K.
 
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://twitter.com/kauer389

GPG fingerprint: A0CD 28F0 10BE FC21 C57C 67C1 19A6 83A4 9B0B 1D75
Old fingerprint: A52E F6B9 708B 51C4 85E6 1634 0571 ADF9 3C1C 6A3A