this is strange, I tried again, sudo apt install openssh -y and it said that package is not available, but may be under another package and it sounded like it said try openssh-client I don't think, that may only outbound on 22. Glenn ----- Original Message ----- From: "K0LNY_Glenn" <glenn@ervin.email> To: "Brian Buhrow" <buhrow@xxxxxxxxxx>; "Willem van der Walt" <wvdwalt@xxxxxxxxxx> Cc: "Speakup is a screen review system for Linux." <speakup@xxxxxxxxxxxxxxxxx>; <buhrow@xxxxxxxxxx> Sent: Wednesday, August 24, 2022 2:40 PM Subject: Re: hopefully some help with AntiX Is ufw the only method to open or close ports? I still cannot get in... I did: sudo ufw allow 22/tcp and it didn't give me an error. I tried system restart ufw and systemctl restart ufw with sudo of course, and it did not like the command. So I rebooted, but I still get connection refused when trying to SSH into it. I've tried to stop the ufw, but I don't know if it got stopped. I say, what the hell are people thinking about closing all ports. A bunch of paranoid people. Why don't they leave at least 22 open and they could create a pop up message on startup that if not using SSH, it may be good to close it. This really fucks things up for the Blind! Glenn ----- Original Message ----- From: "Brian Buhrow" <buhrow@xxxxxxxxxx> To: "K0LNY_Glenn" <glenn@ervin.email>; "Willem van der Walt" <wvdwalt@xxxxxxxxxx> Cc: "Speakup is a screen review system for Linux." <speakup@xxxxxxxxxxxxxxxxx>; <buhrow@xxxxxxxxxx> Sent: Wednesday, August 24, 2022 11:49 AM Subject: Re: hopefully some help with AntiX Hello Glen. There is a faster way to determine if the machine you're trying to reach is listening on the network on the appropriate ports. Nmap is good for finding which ports a machine is paying attention to, but if you know the port numbers, use telnet instead. If you don't have telnet installed on your working machine, I highly recommend installing it. Then, do something like: telnet <ipaddress of target machine> <port number> You should see something like: trying <ipaddress> ... Then, you'll either get one of three things: 1. A long delay followed by: connectioned timed out trying to reach <ip address> 2. Connect: connection refused. 3. Connected, escape is control-], followed by any banners the far end might produce, or none if it waits for you to send the first message. If you get option 2 and the machine you're connecting to is on the same network as the one you're connecting from, then you know the machine is on the network, but not listening on the port you tried. If you get option 1, then it's highly likely the target machine is not connected to the network. I use this for testing connections to a huge variety of ports as it allows me to determine at which layer a problem is occurring. -thanks -Brian
