Thank you Gerdriaan, your suggestion has solved the problem which
actually I had tried before with no success, this means that I was
wrong in something else. Your help has been decisive!
A minor issue: I've applied a similar rule to port 5900 and obviously
I've launched "systemctl -restart u
Hi Aldo,
Please also reply to the list, so the other members can read along.
I've redacted your MAC addresses in the quote below, because I think
they are not needed.
On 7 February 2018 at 23:22, Aldo Maggi wrote:
> I switched the level of logging of ufw to "full" and in "kern.log" I
> have foun
Can you check whether you can access your home pc from the
192.168.1.0/24 network? So, connect a device to your router on the LAN
side, acquire an IP lease in the 192.168.1.0/24 network, and connect
to 192.168.1.120 on port .
If that doesn't work, can you insert extra logging rules in ufw?
Pac
Luis,
I'm sure it must a problem of Nat but if you look at the output
of "iptables -t nat -L -n -v" you can read this line (a bit mixed up!):
Chain PREROUTING (policy ACCEPT 1081 packets, 70666 bytes)
> > pkts bytes target prot opt in out source
> > destination 0 0 DNAT tc
Aldo,
"Router" and "My PC" are not in the same network. Does your "File
Server" do NAT ??
Luis.-
On 07/02/18 16:41, Aldo Maggi wrote:
I'm having problems with ssh from the Wan while contacting my Pc in the
Lan.
It worked when I just had to go through the Router provided by the ISP
but prob
5 matches
Mail list logo