> On 24 Oct 2023, at 17:36, Arno Lehmann wrote:
>
> Hello,
Hi Arno,
>
> Am 24.10.2023 um 16:19 schrieb Henggi:
> ...
>> As I mentioned in my 1st email, I think (afaik) that no other netfitler
>> module/service is running.
>
> My anecdote was intende
> On 24 Oct 2023, at 16:33, Max Nikulin wrote:
>
> On 24/10/2023 19:04, Henggi wrote:
>> - iptables on server are cleared/open (firewalld or other firewall
>> frameworks are not used/installed).
>
> Nowadays nft or iptables is not the only option to drop packets.
> On 24 Oct 2023, at 17:22, Charles Curley
> wrote:
>
> On Tue, 24 Oct 2023 15:30:14 +0200
> Arno Lehmann wrote:
>
>> Recently I encountered something similar, and my usual test for local
>> firewall being active,
>>
>> iptables -L -n
>>
>> came back with policies "accept" all over the p
> On 24 Oct 2023, at 15:30, Arno Lehmann wrote:
>
> Hi Henggi, all,
Hi Arno, thanks for your reply!
>
> Am 24.10.2023 um 14:04 schrieb Henggi:
>> Hi list,
>> Completely stuck here, any clue appreciated!
>> Trying to bring up XRDP service on Debian 11-bull
> On 24 Oct 2023, at 15:14, Dan Ritter wrote:
>
> Henggi wrote:
>>
>>> On 24 Oct 2023, at 14:46, Dan Ritter wrote:
>>>
>> - when using „port=tcp://:3389“ in xrdp.ini:
>> root@server:~# ss -tlnp | grep 3389
>> LISTEN 0 2
> On 24 Oct 2023, at 14:46, Dan Ritter wrote:
>
> Henggi wrote:
>> Hi list,
>>
>> Completely stuck here, any clue appreciated!
>>
>> — by default xrdp.ini listening config is set to "port=3389“ (which is
>> expected to listen on ipv4 &
> This isn’t necessarily an issue but since my issue is related to the
listening on network interface I thought it’s worth to point-out this
observation.
Thanks for any clue!
Best,
Henggi
xrdp.ini
Description: Binary data
root@server:~# tcpdump -i eth0 port 3389 -n
tcpdump: verbose
7 matches
Mail list logo
