On Mon, 17 Feb 2020 09:24:54 +1100 Cameron Simpson wrote:
> Just to this part:
> For things to which I connect regularly I allocate extra 127.0.0.n
> addresses to my local interface. This lets you bind to a specific
> address without conflict.
...
> Our home server does similar (on a lesser sca
Hi.
On Sun, 16 Feb 2020 23:07:28 +0100 "Patrick Dupre" wrote:
> Now it works. I add to install additional packages for gnome.
Good.
If you encounter conflicts between components of the (eventual) native
gnome session and the VNC one, choose another session (ex: MATE xfce
openbox ...) for VNC.
On 2020-02-17 07:27, Samuel Sieb wrote:
>
> I've never seen someone firewall localhost, not sure if that's even possible.
> So any port that isn't open will be closed, not filtered.
Yes, but I was actually referring to when he stated that...
From Client:
nmap -v -n -P0 -p5900-5906 euripide
Warn
On 2/16/20 2:08 AM, Ed Greshko wrote:
On 2020-02-16 17:33, Samuel Sieb wrote:
On 2/16/20 1:20 AM, Patrick Dupre wrote:
nmap -v -n -Pn -p5900-5906 localhost
PORT STATE SERVICE
5900/tcp closed vnc
5901/tcp open vnc-1
5902/tcp closed vnc-2
5903/tcp closed vnc-3
5904/tcp closed unknown
5905/
) [7 ports]
Discovered open port 5901/tcp on 193.52.235.60
Completed Connect Scan at 11:46, 0.00s elapsed (7 total ports)
Nmap scan report for euripide (193.52.235.60)
Host is up (0.00037s latency).
Other addresses for euripide (not scanned): fe80::de89:7b2c:9cf1:d1c9
PORT STATE SERVICE
5900/
On 16Feb2020 13:44, Patrick Dupre wrote:
I also tried:
ssh -f -L 5901:localhost.fr:5901 euripide sleep 10
bind [127.0.0.1]:5901: Address already in use
channel_setup_fwd_listener_tcpip: cannot listen to port: 5901
Could not request local forwarding.
Just to this part:
For things to which I c
Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
===
> Sent: Sunday, February 16, 2020 at 10:26 PM
> From: francis.montag...@inria.fr
> To: "Community support for Fedora users"
>
On 2020-02-17 02:33, francis.montag...@inria.fr wrote:
> With "vncviewer SERVERNAME:1 -via localhost" you are first opening an
> ssh tunnel to localhost. This is useless.
Yes, it is useless.
The reason it worked for me is that the intermediate F/W which I thought had
the vnc ports
blocked, didn'
On Sun, 16 Feb 2020 21:53:53 +0100 "Patrick Dupre" wrote:
>> On Sun, 16 Feb 2020 20:57:05 +0100 "Patrick Dupre" wrote:
>> You have chosen to start "vncserver ;1" instead of
>> "systemctl start vncserver@:1.service" ... arguable.
> It works the same.
Almost yes.
>> Does it work now? Do you hav
>
> On Sun, 16 Feb 2020 20:57:05 +0100 "Patrick Dupre" wrote:
> >> Kill this Xvnc process and start again vncserver@:1.service.
>
> > I made vncserver -kill :1
> > and
> > vncserver :1
>
> You have chosen to start "vncserver ;1" instead of
> "systemctl start vncserver@:1.service" ... arguable.
I
On Sun, 16 Feb 2020 20:57:05 +0100 "Patrick Dupre" wrote:
>> Kill this Xvnc process and start again vncserver@:1.service.
> I made vncserver -kill :1
> and
> vncserver :1
You have chosen to start "vncserver ;1" instead of
"systemctl start vncserver@:1.service" ... arguable.
You haven't also en
>
>
> On Sun, 16 Feb 2020 20:12:55 +0100 "Patrick Dupre" wrote:
> >> vncviewer -via pdupre@euripide :1
>
> > Very good, I get
> ...
>
> > I can connect, but I just get a xclock.
>
> Probably due to half brojen VNC session:
>
> > lsof -i tcp:5901
> > COMMAND PID USER FD TYPE DEVICE SIZE/O
On Sun, 16 Feb 2020 20:12:55 +0100 "Patrick Dupre" wrote:
>> vncviewer -via pdupre@euripide :1
> Very good, I get
...
> I can connect, but I just get a xclock.
Probably due to half brojen VNC session:
> lsof -i tcp:5901
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> Xvnc1
>
> > vncviewer euripide:1 -via localhost
>
> Needs direct access to port 5901 on euripide
>
> > works as badly as
>
> > vncviewer -via pdupre@euripide:1
>
> You missed a space before the :1 here: It should be:
>
> vncviewer -via pdupre@euripide :1
Very good, I get
DecodeManager: Detected 4
>
> >>> On 2020-02-16 20:44, Patrick Dupre wrote:
> I followed both options:
> vncviewer -via euripide
> >>> Shouldn't the format of the command be something like...
> >>> vncviewer SERVERNAME:1 -via localhost
> >> No: the -via option of vncviewer is a short way to setup an ssh tunnel
>
On Sun, 16 Feb 2020 19:27:56 +0100 "Patrick Dupre" wrote:
> vncviewer euripide:1 -via localhost
Needs direct access to port 5901 on euripide
> works as badly as
> vncviewer -via pdupre@euripide:1
You missed a space before the :1 here: It should be:
vncviewer -via pdupre@euripide :1
--
fr
On Mon, 17 Feb 2020 01:55:01 +0800 Ed Greshko wrote:
> On 2020-02-16 23:05, francis.montag...@inria.fr wrote:
>> On Sun, 16 Feb 2020 20:59:19 +0800 Ed Greshko wrote:
>>> On 2020-02-16 20:44, Patrick Dupre wrote:
I followed both options:
vncviewer -via euripide
>>> Shouldn't the format o
> On 2020-02-16 23:05, francis.montag...@inria.fr wrote:
> > On Sun, 16 Feb 2020 20:59:19 +0800 Ed Greshko wrote:
> >
> >> On 2020-02-16 20:44, Patrick Dupre wrote:
> >>> I followed both options:
> >>> vncviewer -via euripide
> >> Shouldn't the format of the command be something like...
> >> vncvi
>
> On Sun, 16 Feb 2020 17:30:08 +0100 "Patrick Dupre" wrote:
> >>> I suspect that you have specified the 3022 port fo connect to euripide
> >>> in your ~/.ssh/config file.
>
> >> We should focus on runing vncviewer from the client machine to
> >> euripide (running vncserver vith vncserver@:1.ser
On 2020-02-16 23:05, francis.montag...@inria.fr wrote:
> On Sun, 16 Feb 2020 20:59:19 +0800 Ed Greshko wrote:
>
>> On 2020-02-16 20:44, Patrick Dupre wrote:
>>> I followed both options:
>>> vncviewer -via euripide
>> Shouldn't the format of the command be something like...
>> vncviewer SERVERNAME:1
On Sun, 16 Feb 2020 17:30:08 +0100 "Patrick Dupre" wrote:
>>> I suspect that you have specified the 3022 port fo connect to euripide
>>> in your ~/.ssh/config file.
>> We should focus on runing vncviewer from the client machine to
>> euripide (running vncserver vith vncserver@:1.service)
> Of co
>
> >> I suspect that you have specified the 3022 port fo connect to euripide
> >> in your ~/.ssh/config file.
>
> > 1)
> > I do have an issue with vncserver:
> > I can run remmina (ssh) on 2 machines, but never vncserver
>
> We should focus on runing vncviewer from the client machine to
> eurip
On Sun, 16 Feb 2020 16:33:34 +0100 "Patrick Dupre" wrote:
>>> ssh: connect to host euripide.u-bourgogne.fr port 3022: Connection refused
>> I suspect that you have specified the 3022 port fo connect to euripide
>> in your ~/.ssh/config file.
> 1)
> I do have an issue with vncserver:
> I can run
> >> vncviewer -via euripide
>
> > Shouldn't the format of the command be something like...
>
> > vncviewer SERVERNAME:1 -via localhost
>
> No: the -via option of vncviewer is a short way to setup an ssh tunnel
> to the SERVER running Xvnc (vncserver).
>
> On Sun, 16 Feb 2020 13:44:43 +0100 "Patri
On Sun, 16 Feb 2020 20:59:19 +0800 Ed Greshko wrote:
> On 2020-02-16 20:44, Patrick Dupre wrote:
>> I followed both options:
>> vncviewer -via euripide
> Shouldn't the format of the command be something like...
> vncviewer SERVERNAME:1 -via localhost
No: the -via option of vncviewer is a short
===
> Sent: Sunday, February 16, 2020 at 1:59 PM
> From: "Ed Greshko"
> To: users@lists.fedoraproject.org
> Subject: Re: open port
>
> On 2020-02-16 20:44, Patrick Dupre wrote:
> > Thanks.
> > I followed both options:
> >
> > TightVNC
>
On 2020-02-16 20:44, Patrick Dupre wrote:
> Thanks.
> I followed both options:
>
> TightVNC
> vncviewer -via euripide
>
Shouldn't the format of the command be something like...
vncviewer SERVERNAME:1 -via localhost
Assuming you have sshd running on the localhost.
--
The key to getting good an
Thanks.
I followed both options:
TightVNC
vncviewer -via euripide
TigerVNC Viewer 64-bit v1.10.1
Built on: 2020-01-13 09:16
Copyright (C) 1999-2019 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
ssh: connect to host euripide.u-bourgogne.fr
On 2020-02-16 20:04, Patrick Dupre wrote:
>> On 2020-02-16 19:12, Patrick Dupre wrote:
>>> Yes, there is probably it another device/firewall between the client and
>>> server.
>>> But the ssh works fine
>> Well, sure.
>>
>> But ssh is on port 22. If that port is open/configured but not the port
I tried:
ssh -L 5900:localhost:5900 -N -f -l pdupre euripide
(and ssh -L 5901:localhost:5901 -N -f -l pdupre euripide)
It works, and
then
vncviewer -via pdupre@euripide
(A passwd is required)
I try to connect (again a passwd is required).
but again:
Sun Feb 16 13:08:08 2020
DecodeManager: Detec
>
> On 2020-02-16 19:12, Patrick Dupre wrote:
> > Yes, there is probably it another device/firewall between the client and
> > server.
> > But the ssh works fine
>
> Well, sure.
>
> But ssh is on port 22. If that port is open/configured but not the port
> needed for VNC you won't be
> able to
On 2020-02-16 19:12, Patrick Dupre wrote:
> Yes, there is probably it another device/firewall between the client and
> server.
> But the ssh works fine
Well, sure.
But ssh is on port 22. If that port is open/configured but not the port needed
for VNC you won't be
able to connect.
However, sin
Yes, there is probably it another device/firewall between the client and server.
But the ssh works fine
> Sent: Sunday, February 16, 2020 at 11:08 AM
> From: "Ed Greshko"
> To: users@lists.fedoraproject.org
> Subject: Re: open port
>
> On 2020-02-16 17:33, Samuel Sie
ver)
>
> 1. nmap
>
>nmap -v -n -Pn -p5900-5906 euripide
>
Starting Nmap 7.70 ( https://nmap.org ) at 2020-02-16 11:46 CET
Initiating Connect Scan at 11:46
Scanning euripide (193.52.235.60) [7 ports]
Discovered open port 5901/tcp on 193.52.235.60
Completed Connect Scan at 11
0.
I say this since it has been my experience if a firewalld rule is blocking a
connection it will show up
as "filtered".
For example, f32k is the server and meimei the client. Using ssh as the
example server.
With sshd running on the server and firewall open.
PORT STATE SERVICE
2
Hi
On Sun, 16 Feb 2020 01:33:56 -0800 Samuel Sieb wrote:
> On 2/16/20 1:20 AM, Patrick Dupre wrote:
>> nmap -v -n -Pn -p5900-5906 localhost
>> PORT STATE SERVICE
>> 5900/tcp closed vnc
>> 5901/tcp open vnc-1
...
> Now you have it running, so the next step is to figure out how to ask
> f
On 2/16/20 1:20 AM, Patrick Dupre wrote:
nmap -v -n -Pn -p5900-5906 localhost
PORT STATE SERVICE
5900/tcp closed vnc
5901/tcp open vnc-1
5902/tcp closed vnc-2
5903/tcp closed vnc-3
5904/tcp closed unknown
5905/tcp closed unknown
5906/tcp closed unknown
Now you have it running, so the nex
Scan at 10:11
Scanning localhost (127.0.0.1) [7 ports]
Discovered open port 5901/tcp on 127.0.0.1
Completed Connect Scan at 10:11, 0.00s elapsed (7 total ports)
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00019s latency).
Other addresses for localhost (not scanned): ::1
PORT STATE
On 2020-02-16 04:19, Patrick Dupre wrote:
> Hello,
>
> On a server
> nmap -v -n -Pn -p5900-5910 localhost
> provides:
>
> Starting Nmap 7.70 ( https://nmap.org ) at 2020-02-15 15:07 EST
> Initiating SYN Stealth Scan at 15:07
> Scanning localhost (127.0.0.1) [11 ports]
> Completed SYN Stealth Scan
On 2020-02-16 04:19, Patrick Dupre wrote:
> How can I open the port vnc?
You have been on this list for some time. So, not sure if you need pointers or
exact instructions.
For now, pointers.
For firewalld admin use
firewall-cmd for command line
firewall-config for gui
--
The key to g
Hello,
On a server
nmap -v -n -Pn -p5900-5910 localhost
provides:
Starting Nmap 7.70 ( https://nmap.org ) at 2020-02-15 15:07 EST
Initiating SYN Stealth Scan at 15:07
Scanning localhost (127.0.0.1) [11 ports]
Completed SYN Stealth Scan at 15:07, 0.42s elapsed (11 total ports)
Nmap scan report f
On Sat, 18 May 2013 14:22:10 -0700
"T.C. Hollingsworth" wrote:
> On Sat, May 18, 2013 at 2:12 PM, আনন্দ কুমার সমাদ্দার
> wrote:
> > On Sat, 18 May 2013 22:07:15 +0100
> > আনন্দ কুমার সমাদ্দার Ananda Samaddar wrote:
> >> I tested the port on ShieldsUP and it informs me that it is
> >> 'stealth'
On Sat, May 18, 2013 at 2:12 PM, আনন্দ কুমার সমাদ্দার
wrote:
> On Sat, 18 May 2013 22:07:15 +0100
> আনন্দ কুমার সমাদ্দার Ananda Samaddar wrote:
>> I tested the port on ShieldsUP and it informs me that it is 'stealth'
>> mode so obviously not open. I don't think the router is the problem
>> as wh
On Sat, 18 May 2013 22:07:15 +0100
আনন্দ কুমার সমাদ্দার Ananda Samaddar wrote:
> On Sat, 18 May 2013 14:02:06 -0700
> "T.C. Hollingsworth" wrote:
>
> > On Sat, May 18, 2013 at 1:47 PM, আনন্দ কুমার সমাদ্দার
> > wrote:
> > > Hello all,
> > >
> > > So I've found out that by default my script cont
On Sat, 18 May 2013 14:02:06 -0700
"T.C. Hollingsworth" wrote:
> On Sat, May 18, 2013 at 1:47 PM, আনন্দ কুমার সমাদ্দার
> wrote:
> > Hello all,
> >
> > So I've found out that by default my script controlled ethernet
> > connection is in the public zone in firewalld. I however cannot
> > open a p
On Sat, May 18, 2013 at 1:47 PM, আনন্দ কুমার সমাদ্দার
wrote:
> Hello all,
>
> So I've found out that by default my script controlled ethernet
> connection is in the public zone in firewalld. I however cannot open a
> port for Transmission, the torrent client. I set Transmission to use
> the stat
Hello all,
So I've found out that by default my script controlled ethernet
connection is in the public zone in firewalld. I however cannot open a
port for Transmission, the torrent client. I set Transmission to use
the static default port 51413.
I then do the following:
firewall-cmd --zone=pub
47 matches
Mail list logo
