Re: Upgrade to Debian 11 and still have the same problems.

[Jeffrey Walton]

On Sun, Jul 16, 2023 at 5:22 PM Maureen L Thomas  wrote:
>
> So I have been snooping around the system and found this message in the lshw 
> command:
>
> *-generic DISABLED
>
> description: Wireless interface
>
> product: RTL8821CE 802.11ac PCIe Wireless Network Adapter
>
> vendor: Realtek Semiconductor Co., Ltd.
>
> physical id: 0
>
> bus info: pci@:02:00.0
>
> logical name: wlp2s0
>
> version: ff
>
> serial: 3e:c2:77:77:6a:31
>
> width: 32 bits
>
> clock: 66MHz
>
> capabilities: bus_master vga_palette cap_list ethernet physical wireless
>
> configuration: broadcast=yes driver=rtw_8821ce driverversion=5.10.0-23-amd64 
> firmware=N/A latency=255 link=no maxlatency=255 mingnt=255 multicast=yes 
> wireless=IEEE 802.11
>
> resources: irq:129 ioport:d000(size=256) memory:df00-df00
>
> Could this be part of the problem.  I have no wifi so that is part of the 
> problem.  This is Disabled so how do I enable it?
>
> Thank you guys for being patient with this old lady..

See the part about non-free-firmware at https://wiki.debian.org/DebianUpgrade .

Jeff

Re: Upgrade to Debian 11 and still have the same problems.

[David Wright]

On Sun 16 Jul 2023 at 17:21:37 (-0400), Maureen L Thomas wrote:
> So I have been snooping around the system and found this message in
> the lshw command:
> 
> *-generic DISABLED
> description: Wireless interface
> product: RTL8821CE 802.11ac PCIe Wireless Network Adapter
> vendor: Realtek Semiconductor Co., Ltd.
> physical id: 0
> bus info: pci@:02:00.0
> logical name: wlp2s0
> version: ff
> serial: 3e:c2:77:77:6a:31
> width: 32 bits
> clock: 66MHz
> capabilities: bus_master vga_palette cap_list ethernet physical wireless
> configuration: broadcast=yes driver=rtw_8821ce
> driverversion=5.10.0-23-amd64 firmware=N/A latency=255 link=no



> maxlatency=255 mingnt=255 multicast=yes wireless=IEEE 802.11
> resources: irq:129 ioport:d000(size=256) memory:df00-df00
> 
> Could this be part of the problem.  I have no wifi so that is part of
> the problem. This is Disabled so how do I enable it?

Have you installed the package firmware-realtek?

Cheers,
David.

Re: Unable to ssh to Debian 9 from 9 or 11

[tomas]

On Sun, Jul 16, 2023 at 03:21:06PM -0400, Timothy M Butterworth wrote:

[...]

> Do you have TCP wrappers installed and running? Please post the output
> of: `less
> /etc/hosts.allow` `less /etc/hosts.deny`

tcpwrappers would lead to a connection refused, not a timeout.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Debian, Awstats, Nginx server blocks?

[Gareth Evans]

> On 17 Jul 2023, at 02:29, David Mehler  wrote:
> 
> Hello,
> 
> Does anyone have the above working? I've read several howtos on this
> and use to (way back) have it going on a *BSD with Apache setup, but
> I'm wanting to get Awstats going on Debian with Nginx and multiple tls
> server blocks each a different domain. Manually running awstats.pl on
> my test domain I can get a text database output but when running from
> the CGI get the message datadir doesn't exist or is nonwritable it
> does and nginx can.

Anything in nginx's logs?  

G


> 
> Confused.
> Thanks.
> Dave.
> 

Re: gnome-schedule gone from bullseye and bookworm

[Rick Macdonald]

On 2023-07-14 16:26, songbird wrote:

   here's the removal bug for more details:

   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808060



BTW, for anybody interested, I found a simple Tcl-based cron/at GUI: 
vcron. No binaries (but requires Tcl/Tk installed) and the tar file is 
set up to put the files into /usr/local/{bin,lib}.


Rick

Debian, Awstats, Nginx server blocks?

[David Mehler]

Hello,

Does anyone have the above working? I've read several howtos on this
and use to (way back) have it going on a *BSD with Apache setup, but
I'm wanting to get Awstats going on Debian with Nginx and multiple tls
server blocks each a different domain. Manually running awstats.pl on
my test domain I can get a text database output but when running from
the CGI get the message datadir doesn't exist or is nonwritable it
does and nginx can.

Confused.
Thanks.
Dave.

Upgrade to Debian 11 and still have the same problems.

[Maureen L Thomas]

So I have been snooping around the system and found this message in the 
lshw command:


*-generic DISABLED

description: Wireless interface

product: RTL8821CE 802.11ac PCIe Wireless Network Adapter

vendor: Realtek Semiconductor Co., Ltd.

physical id: 0

bus info: pci@:02:00.0

logical name: wlp2s0

version: ff

serial: 3e:c2:77:77:6a:31

width: 32 bits

clock: 66MHz

capabilities: bus_master vga_palette cap_list ethernet physical wireless

configuration: broadcast=yes driver=rtw_8821ce 
driverversion=5.10.0-23-amd64 firmware=N/A latency=255 link=no 
maxlatency=255 mingnt=255 multicast=yes wireless=IEEE 802.11


resources: irq:129 ioport:d000(size=256) memory:df00-df00


Could this be part of the problem.  I have no wifi so that is part of 
the problem. This is Disabled so how do I enable it?


Thank you guys for being patient with this old lady..

Moe

Re: I reinstalled debian bullsee and still have the same messages and this one too

[Maureen L Thomas]

I have seen the problems with Bookworm and will wait for awhile to see 
how it goes.


On 7/16/23 3:22 AM, john doe wrote:

On 7/16/23 03:59, Maureen L Thomas wrote:

Sender:  pipewire

time:  6:02:34 PM

message:  Failed to receive portal pid:
org.freedesktop.DBus.Error.Name.Has.NO.Owner!  Could not get PID of name
"org.freedesktop.portal.Desktop:" no such name

Audit: 3

Priority: 3

So I went online and it seems everyone has a different opinion as to
what it is with one actually saying that it is inconsequential. So which
is it?

I am using debian 11 with gnome.



Any reasons why you would reinstall Debian 11 instead of Debian stable 
(12)?


What you are seeing might no longer be  an issue on Bookworm.

--
John Doe

Re: Unable to ssh to Debian 9 from 9 or 11

[Timothy M Butterworth]

On Sat, Jul 15, 2023 at 4:32 PM Roger Price  wrote:

> On Sat, 15 Jul 2023, to...@tuxteam.de wrote:
>
> > @Roger: what does "sudo ss -antp" (or "netstat -antp") say? Is sshd
> > listening on 0.0.0.0:22? Then it's firewall, otherwise (not very
> > probable,but hey) it's sshd config.
>
> Here is netstat -antp on one of the Debian 9 machines where I am currently
> logged in locally as root via ssh.
>
>   Active Internet connections (servers and established)
>   Proto Recv-Q Send-Q Local AddressForeign Address   State
>  PID/Program name
>   tcp0  0 0.0.0.0:22   0.0.0.0:* LISTEN
> 521/sshd
>   tcp0  0 127.0.0.1:6310.0.0.0:* LISTEN
> 4578/cupsd
>   tcp0  0 127.0.0.1:22 127.0.0.1:50124   ESTABLISHED
> 2905/sshd: root@pts
>   tcp0  0 127.0.0.1:50124  127.0.0.1:22  ESTABLISHED
> 2903/ssh
>
> Roger
>

Do you have TCP wrappers installed and running? Please post the output
of: `less
/etc/hosts.allow` `less /etc/hosts.deny`

--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: I reinstalled debian bullsee and still have the same messagesandthis one too

[gene heskett]

On 7/16/23 11:33, Andy Smith wrote:

Hello,

On Sun, Jul 16, 2023 at 09:10:31AM -0400, gene heskett wrote:

On 7/16/23 04:38, didier gaumet wrote:

This error message could probably disappear if you install
xdg-desktop-portal.service package.


[…]


What repo is this in, its a not found in an sudo apt install command.


$ apt-file search xdg-desktop-portal.service
xdg-desktop-portal: /usr/lib/systemd/user/xdg-desktop-portal.service

I have no input on whether that is the source of the OP's error
message however.

Cheers,
Andy


That is installed, so that isn't the src of my problems.  Thanks Andy

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: I reinstalled debian bullsee and still have the same messages andthis one too

[Andy Smith]

Hello,

On Sun, Jul 16, 2023 at 09:10:31AM -0400, gene heskett wrote:
> On 7/16/23 04:38, didier gaumet wrote:
> > This error message could probably disappear if you install
> > xdg-desktop-portal.service package.

[…]

> What repo is this in, its a not found in an sudo apt install command.

$ apt-file search xdg-desktop-portal.service
xdg-desktop-portal: /usr/lib/systemd/user/xdg-desktop-portal.service

I have no input on whether that is the source of the OP's error
message however.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Unable to ssh to Debian 9 from 9 or 11

[Roger Price]

On Sun, 16 Jul 2023, Anssi Saari wrote:


Roger Price  writes:

Does the style of comment give a clue to the tool used ?

Earlier you posted a list of firewall rules like this:

iptables -L -n --line-numbers reports

Chain INPUT (policy ACCEPT)
 num  targetprot opt source destination
  1ufw-before-logging-input  all  --  0.0.0.0/0  0.0.0.0/0

So I would guess ufw.


That's what I thought, but there is no ufw in this Debian 9 machine.  So I had 
to do some archaeology.


It took me a while to discover that long ago this machine ran openSuSE 12.2 and 
was directly attached to the internet, so it ran a modification of the openSuSE 
firewall.  The machine was then migrated to Debian and placed behind a box 
supplied by the internet provider, but it kept running the openSuSE firewall.


 root@kananga ~ systemctl is-enabled SuSEfirewall2
 enabled

The years have gone by. It's still running on Debian 9!. I stopped it with

 root@kananga ~ systemctl disable SuSEfirewall2
 Removed /etc/systemd/system/SuSEfirewall2_setup.service.
 Removed /etc/systemd/system/multi-user.target.wants/SuSEfirewall2.service.
 Removed /etc/systemd/system/multi-user.target.wants/SuSEfirewall2_init.service.
 root@kananga ~ systemctl stop SuSEfirewall2

 root@kananga ~ systemctl is-enabled SuSEfirewall2
 disabled

I then recycled the machine, power off, power on, and I can now ssh into this 
Debian 9 machine from Debian 11 :-) , so I have a permanent solution.


My thanks to all who participated in the discussion,  Roger

Re: I reinstalled debian bullsee and still have the same messages andthis one too

[gene heskett]

On 7/16/23 04:38, didier gaumet wrote:


Hello

This error message could probably disappear if you install 
xdg-desktop-portal.service package. There is also a backported version 
for Bullseye and that could suggest also that for whatever reason the 
ordinary Bullseye package does not function anymore at least in certain 
conditions




What repo is this in, its a not found in an sudo apt install command. 
However, if the .service is removed, synaptic says 90% of the xdg stuff 
is installed.


Something in bookworm+kde is getting in the way of both openscad and 
cura's ability to open a file write requestor, generally it eventually 
works but takes up 5 frustrating minutes to do what should take a 
millisecond.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Unable to ssh to Debian 9 from 9 or 11

[Anssi Saari]

Roger Price  writes:

> Does the style of comment give a clue to the tool used ?

Earlier you posted a list of firewall rules like this:

 iptables -L -n --line-numbers reports

 Chain INPUT (policy ACCEPT)
  num  targetprot opt source destination
   1ufw-before-logging-input  all  --  0.0.0.0/0  0.0.0.0/0
   2ufw-before-input  all  --  0.0.0.0/0  0.0.0.0/0
   3ufw-after-input   all  --  0.0.0.0/0  0.0.0.0/0
   4ufw-after-logging-input   all  --  0.0.0.0/0  0.0.0.0/0
   5ufw-reject-input  all  --  0.0.0.0/0  0.0.0.0/0
   6ufw-track-input   all  --  0.0.0.0/0  0.0.0.0/0

So I would guess ufw.

Re: Nvidia graphics driver naming convention

[Anssi Saari]

Nicolas Marie  writes:

> My question is about the package naming: is the 
> nvidia-graphics-drivers-tesla-470 specifically built for Tesla
> graphics, and the fact that I can use it for my consumer Nvidia GPU is
> a positive "side effect"?

The description of package nvidia-tesla-470-driver seems clear on what
GPU families are supported and gives a reference to a documentation file
with more details.

I have no idea about the why of the tesla naming. I'd guess it's a
historical reason and lack of manpower to update.

Re: Unable to ssh to Debian 9 from 9 or 11

[Klaus Singvogel]

Roger Price wrote:
> After the restart, I tried to ssh from Debian 11 to that Debian 9 machine
> 
>  rprice@titan ~ ssh -v rprice@kananga
>  ssh: connect to host kananga port 22: Connection timed out
> 
> So it's something else?  Roger

Sorry, but I didn't follow the whole thread complete. Maybe parts of this were 
already asked...

• Can you check on the host kananga, if sshd is running and really listening on 
port 22?

  Can you (as root) on host kanaga, and send us the output:

lsof -P -i -n | grep ssh | grep root | grep LISTEN

  Check especially, if ssh is listening for all hosts (indicated by an asterisk 
'*')?

• Can you check, if there are no Firewall restrictions for Port 22 on host 
kanaga:

  Do as root:

iptables -L -n | grep dpt:22

• Check, if there are no Firewall restrictions regarding the host on host 
kanaga for your host titan:

  Do as root:

for i in `host titan | awk '{print $NF}'` ; do iptables -L -n | grep $i 
; done

• Finally, if you didn't get the answer yet, check on host titan, what ssh is 
really doing, with lots of more verbose messages:

ssh -vvv rprice@kananga date

Thanks.

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Re: Unable to ssh to Debian 9 from 9 or 11

[Nicolas George]

mick.crane (12023-07-16):
> I'd compare the public key of you at 11 to what's in the authorized_keys on
> 9.
> and what's in known_hosts.
> and what's in the sshd config file on 9 about "Listen"
> after that I dunno.

Oh, please stop. The symptoms do not point to issues with the key AT ALL
and the issue has been fixed for hours anyway.

-- 
  Nicolas George


signature.asc
Description: PGP signature

Re: Unable to ssh to Debian 9 from 9 or 11

[mick.crane]

On 2023-07-16 10:53, Roger Price wrote:

On Sun, 16 Jul 2023, mick.crane wrote:


did you try to ssh to the ip address?
I vaguely remember something to do with the keys where I could ssh by 
number but not name.


I ssh from Debian 11 to Debian 9 :

 rprice@titan ~ ssh rprice@192.168.1.13
 ssh: connect to host 192.168.1.13 port 22: Connection timed out

Roger
I'd compare the public key of you at 11 to what's in the authorized_keys 
on 9.

and what's in known_hosts.
and what's in the sshd config file on 9 about "Listen"
after that I dunno.
mick

Re: Unable to ssh to Debian 9 from 9 or 11

[Roger Price]

On Sun, 16 Jul 2023, mick.crane wrote:


did you try to ssh to the ip address?
I vaguely remember something to do with the keys where I could ssh by number 
but not name.


I ssh from Debian 11 to Debian 9 :

 rprice@titan ~ ssh rprice@192.168.1.13
 ssh: connect to host 192.168.1.13 port 22: Connection timed out

Roger

Re: Unable to ssh to Debian 9 from 9 or 11

[mick.crane]

On 2023-07-16 09:28, Roger Price wrote:

On Sun, 16 Jul 2023, mick.crane wrote:


Can you ping the problem machine by name?


 rprice@titan ~ ping -c2 kananga
 PING kananga (192.168.1.16) 56(84) bytes of data.
 64 bytes from kananga (192.168.1.16): icmp_seq=1 ttl=64 time=1.38 ms
 64 bytes from kananga (192.168.1.16): icmp_seq=2 ttl=64 time=1.37 ms

Roger

did you try to ssh to the ip address?
I vaguely remember something to do with the keys where I could ssh by 
number but not name.

mick

Re: Unable to ssh to Debian 9 from 9 or 11

[tomas]

On Sun, Jul 16, 2023 at 11:03:52AM +0200, Roger Price wrote:

[...]

> On a Debian 9 machine I typed the commands
> 
>   iptables -F
>   iptables -X
>   iptables -P INPUT ACCEPT
>   iptables -P FORWARD ACCEPT
>   iptables -P OUTPUT ACCEPT
> 
> and then _immediately_ attempted to ssh from Debian 11 to that Debian 9 
> machine.
> 
> rprice@titan ~ ssh rprice@kananga
> rprice@kananga's password:
> Linux kananga 4.9.0-4-686 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) i686
> ...
> 
> Success! I can ssh 11->9 after flushing the firewall and before rebooting.

\o/

:-)

> I do not know what firewall management tool is in use.  The first 4 lines
> shown by iptables -L were
> 
>  Chain INPUT (policy DROP)
>  num  target  prot opt source destination
>  1ACCEPT  all  --  0.0.0.0/0  0.0.0.0/0 /* 
> "main[2993]-set_basic_rules[971]" */
>  2ACCEPT  all  --  0.0.0.0/0  0.0.0.0/0 ctstate ESTABLISHED /* 
> "set_basic_rules[1028]-allow_basic_established[878]" */
>  3ACCEPT  icmp --  0.0.0.0/0  0.0.0.0/0 ctstate RELATED /* 
> "set_basic_rules[1028]-allow_basic_established[892]" */
> 
> Does the style of comment give a clue to the tool used ?

I must pass up on this one. I'm not very much into
all those tools (and a bit tight on time, guests now
getting up and hoping for some breakfast :-)

I'll dig into it later unless someone (TM) beats me
to it.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Unable to ssh to Debian 9 from 9 or 11

[Roger Price]

On Sun, 16 Jul 2023, to...@tuxteam.de wrote:


On Sun, Jul 16, 2023 at 09:39:35AM +0200, Roger Price wrote:


I tried to clear out the existing firewall on a Debian 9 machine with the 
commands


This would be a good time to try ssh :-)



But before chasing that culprit it'd be nice to know we are
barking up the right tree: can you ssh after flushing the
firewalls and /before/ rebooting?


On a Debian 9 machine I typed the commands

  iptables -F
  iptables -X
  iptables -P INPUT ACCEPT
  iptables -P FORWARD ACCEPT
  iptables -P OUTPUT ACCEPT

and then _immediately_ attempted to ssh from Debian 11 to that Debian 9 machine.

rprice@titan ~ ssh rprice@kananga
rprice@kananga's password:
Linux kananga 4.9.0-4-686 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) i686
...

Success! I can ssh 11->9 after flushing the firewall and before rebooting.

I do not know what firewall management tool is in use.  The first 4 lines shown 
by iptables -L were


 Chain INPUT (policy DROP)
 num  target  prot opt source destination
 1ACCEPT  all  --  0.0.0.0/0  0.0.0.0/0 /* 
"main[2993]-set_basic_rules[971]" */
 2ACCEPT  all  --  0.0.0.0/0  0.0.0.0/0 ctstate ESTABLISHED /* 
"set_basic_rules[1028]-allow_basic_established[878]" */
 3ACCEPT  icmp --  0.0.0.0/0  0.0.0.0/0 ctstate RELATED /* 
"set_basic_rules[1028]-allow_basic_established[892]" */

Does the style of comment give a clue to the tool used ?

Roger

Re: I reinstalled debian bullsee and still have the same messages and this one too

[didier gaumet]

Hello

This error message could probably disappear if you install 
xdg-desktop-portal.service package. There is also a backported version 
for Bullseye and that could suggest also that for whatever reason the 
ordinary Bullseye package does not function anymore at least in certain 
conditions

Re: Unable to ssh to Debian 9 from 9 or 11

[Roger Price]

On Sun, 16 Jul 2023, mick.crane wrote:


Can you ping the problem machine by name?


 rprice@titan ~ ping -c2 kananga
 PING kananga (192.168.1.16) 56(84) bytes of data.
 64 bytes from kananga (192.168.1.16): icmp_seq=1 ttl=64 time=1.38 ms
 64 bytes from kananga (192.168.1.16): icmp_seq=2 ttl=64 time=1.37 ms

Roger

Re: Unable to ssh to Debian 9 from 9 or 11

[tomas]

On Sun, Jul 16, 2023 at 09:07:03AM +0100, mick.crane wrote:

[...]

> Can you ping the problem machine by name?
> mick

No, it isn't a name resolution issue. The original "ssh -v" output,
which I re-quote here shows that clearly:

| rprice@kananga:~$ ssh -v rprice@maria
| OpenSSH_7.4p1 Debian-10+deb9u2, OpenSSL 1.0.2l  25 May 2017
| debug1: Reading configuration data /etc/ssh/ssh_config
| debug1: /etc/ssh/ssh_config line 19: Applying options for *
| debug1: Connecting to maria [192.168.1.13] port 22.
| debug1: connect to address 192.168.1.13 port 22: Connection timed out
| ssh: connect to host maria port 22: Connection timed out

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Unable to ssh to Debian 9 from 9 or 11

[mick.crane]

On 2023-07-16 07:26, Roger Price wrote:

On Sun, 16 Jul 2023, Intense Red wrote:


  Are you trying to ssh into the box as the root user?


I do not ssh into remote boxes as root; I use ssh to root only within 
the box.



If so, remember Debian's ssh configuration stops root from logging in.


In my Debian 9 and 11 boxes I see in /etc/ssh/sshd_config
"PermitRootLogin yes" by default, and by default local and remote root
login is possible.

Roger

Can you ping the problem machine by name?
mick

Re: Unable to ssh to Debian 9 from 9 or 11

[tomas]

On Sun, Jul 16, 2023 at 03:46:06PM +0800, jeremy ardley wrote:
> 
> On 16/7/23 15:39, Roger Price wrote:
> > So it's something else?  Roger
> 
> 
> Have you checked /etc/ssh/sshd_config on the target to see if it is actually
> listening on port 22? You can also use netstat to see listening ports and
> processes

OP has checked with netstat/ss. Yes, sshd /is/ listening on 0.0.0.0:22
Besides this would lead (as Greg noted) to a "connection refused", not
to a timeout.

> Second is to check the /etc/ssh/ssh_config on the originating machine to
> make sure nothing funny.
> 
> Finally check ~/.ssh/config on your originating machine and see if there is
> any conflicting lines that may perhaps make you try and connect to the wrong
> host

All those options effect too late for the observed behaviour.

cheers
-- 
t


signature.asc
Description: PGP signature

Re: Unable to ssh to Debian 9 from 9 or 11

[tomas]

On Sun, Jul 16, 2023 at 09:39:35AM +0200, Roger Price wrote:
> On Sat, 15 Jul 2023, Greg Wooledge wrote:
> > On Sat, Jul 15, 2023 at 11:59:33AM +0200, Roger Price wrote:
> > > rprice@kananga:~$ ssh -v rprice@maria
> > > ssh: connect to host maria port 22: Connection timed out
> > 
> > A timeout is an ENTIRELY different symptom, and when combined with
> > "but I can ping the remote", it means a firewall is involved.  Every
> > time.
> 
> I tried to clear out the existing firewall on a Debian 9 machine with the
> commands
> 
>  iptables -F
>  iptables -X
>  iptables -P INPUT ACCEPT
>  iptables -P FORWARD ACCEPT
>  iptables -P OUTPUT ACCEPT
> 
>  iptables -L -n --line-numbers reports
> 
>  Chain INPUT (policy ACCEPT)
>  num  targetprot opt source destination
>  1ufw-before-logging-input  all  --  0.0.0.0/0  0.0.0.0/0
>  2ufw-before-input  all  --  0.0.0.0/0  0.0.0.0/0
>  3ufw-after-input   all  --  0.0.0.0/0  0.0.0.0/0
>  4ufw-after-logging-input   all  --  0.0.0.0/0  0.0.0.0/0
>  5ufw-reject-input  all  --  0.0.0.0/0  0.0.0.0/0
>  6ufw-track-input   all  --  0.0.0.0/0  0.0.0.0/0
> 
>... and so on

This would be a good time to try ssh :-)

> I then recycled the Debian 9 machine, power off, power on, for a clean 
> restart,
> After the restart, I tried to ssh from Debian 11 to that Debian 9 machine

That's too late: the iptables command just modifies the kernel's
settings. They are not persistent across a reboot. This is the
job of whatever firewall management thingy sets the firewall at
boot (it may be as simple as a self-made script calling iptables
or as complex as some firewalld or ufw, or some systemd thingmajig).

>  rprice@titan ~ ssh -v rprice@kananga
>  ssh: connect to host kananga port 22: Connection timed out
> 
> So it's something else?  Roger

No, this is to be expected: whatever did set up your firewall
on first boot will do that again at every reboot.

But before chasing that culprit it'd be nice to know we are
barking up the right tree: can you ssh after flushing the
firewalls and /before/ rebooting?

Cheers
-- 
tomás


signature.asc
Description: PGP signature

Re: Unable to ssh to Debian 9 from 9 or 11

[jeremy ardley]

On 16/7/23 15:39, Roger Price wrote:
So it's something else?  Roger 



Have you checked /etc/ssh/sshd_config on the target to see if it is 
actually listening on port 22? You can also use netstat to see listening 
ports and processes


Second is to check the /etc/ssh/ssh_config on the originating machine to 
make sure nothing funny.


Finally check ~/.ssh/config on your originating machine and see if there 
is any conflicting lines that may perhaps make you try and connect to 
the wrong host

Re: Unable to ssh to Debian 9 from 9 or 11

[Roger Price]

On Sat, 15 Jul 2023, Greg Wooledge wrote:

On Sat, Jul 15, 2023 at 11:59:33AM +0200, Roger Price wrote:

rprice@kananga:~$ ssh -v rprice@maria
ssh: connect to host maria port 22: Connection timed out


A timeout is an ENTIRELY different symptom, and when combined with
"but I can ping the remote", it means a firewall is involved.  Every
time.


I tried to clear out the existing firewall on a Debian 9 machine with the 
commands


 iptables -F
 iptables -X
 iptables -P INPUT ACCEPT
 iptables -P FORWARD ACCEPT
 iptables -P OUTPUT ACCEPT

 iptables -L -n --line-numbers reports

 Chain INPUT (policy ACCEPT)
 num  targetprot opt source destination
 1ufw-before-logging-input  all  --  0.0.0.0/0  0.0.0.0/0
 2ufw-before-input  all  --  0.0.0.0/0  0.0.0.0/0
 3ufw-after-input   all  --  0.0.0.0/0  0.0.0.0/0
 4ufw-after-logging-input   all  --  0.0.0.0/0  0.0.0.0/0
 5ufw-reject-input  all  --  0.0.0.0/0  0.0.0.0/0
 6ufw-track-input   all  --  0.0.0.0/0  0.0.0.0/0

   ... and so on

I then recycled the Debian 9 machine, power off, power on, for a clean restart,
After the restart, I tried to ssh from Debian 11 to that Debian 9 machine

 rprice@titan ~ ssh -v rprice@kananga
 ssh: connect to host kananga port 22: Connection timed out

So it's something else?  Roger

Re: I reinstalled debian bullsee and still have the same messages and this one too

[john doe]

On 7/16/23 03:59, Maureen L Thomas wrote:

Sender:  pipewire

time:  6:02:34 PM

message:  Failed to receive portal pid:
org.freedesktop.DBus.Error.Name.Has.NO.Owner!  Could not get PID of name
"org.freedesktop.portal.Desktop:" no such name

Audit: 3

Priority: 3

So I went online and it seems everyone has a different opinion as to
what it is with one actually saying that it is inconsequential. So which
is it?

I am using debian 11 with gnome.



Any reasons why you would reinstall Debian 11 instead of Debian stable (12)?

What you are seeing might no longer be  an issue on Bookworm.

--
John Doe