@holunde said in Trouble in FTP-land:
so it has addresses from 192.168.1.129 - 192.168.1.254, broadcast 192.168.1.255.
I was thinking 1 to 127 - 128 and urther up using bit 8 (set) which lies outside the mask.
For memory :
/24
1111 1111 1111 1111 1111 1111 0000 0000
/25
1111 1111 1111 1111 1111 1111 1000 0000
@holunde said in Trouble in FTP-land:
192.168.241.3
Ok, I get it - I guess. The FTP server makes up some IP being totally outside it's network.
Like : I'm a.b.c.d - talk back to using e.f.g.h.
I always thought FTP servers messed around with sets of ports numbers - not IP adrresses.
If NATting was used, then IP becomes important - but that is not the case here. It's just direct routing.
@holunde said in Trouble in FTP-land:
what you think of this whole mess?
Like millions : so happy that this FTP mess is finally over .....
Still, I'm using an FTP client and server, a DVR Dashua record on my LAN network that blast several screenshots every 20 seconds to my web server (webcam !), a dedicated server some where on the Internet.
The FTP server is locked to my @work WAN IP. No TLS, nothing the like because the images are posted anyway.
What about a clean setup :
LAN default 192.168.1.1/24
OPT1 : 192.168.2.1/24
And WAN something else, also /24