Listening Report Issues

[jean-christophe manciot]

When we try to scroll down the "Listening Report" box, it always goes back to the first line even though we"re looking at the last lines of the report. It seems to be tied to the refresh timer. Every time the box is refreshed, the current displayed line is put back to the first one.

Also, if we change the refresh interval value, we have to restart gufw for the new value to be taken into account.

At last, some ports are unknown to the application. It should be possible to edit some entries from within gufw and enter an application description.

[costales (costales)]

Hi Jean :) How are you?
I'll reply between lines,

Every time the box is refreshed, the current displayed line is put back to
> the first one.
>

Yes, I'm afraid that is correct. The complete list is refreshed and we lost
the current view :(
But I'll think in a solution.

> Also, if we change the refresh interval value, we have to restart gufw
> for the new value to be taken into account.
>

Sure? :O The change has to be in the moment. Could you do a test for me?
I'll need your Gufw version and you need to edit a file.

> At last, some ports are unknown to the application. It should be
> possible to edit some entries from within gufw and enter an application
> description.
>

"edit some entries" > In the Listening? Now, you can create rules from the
Listening Report and set a rule name :)
http://gufw.org/img/screenshots/1.png
http://gufw.org/img/screenshots/6.png

Best regards and thanks for your feedback!

[jean-christophe manciot (manciot-jeanchristophe)]

Hi, I"m fine and thanks for your reply.

Regarding the refresh interval value: Gufw release 14.04.2 LTS.

Regarding the port numbers, how about adding one or two columns in the listening report table with the services names and/or description from the official "Service Name and Transport Protocol Port Number Registry": http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml
It should be easy to include the previous file in your package.

[costales (costales)]

Here we go! :)

#1353507 New bug for the scroll in the Listening Report. I have to think in
a solution yet :P

Regarding the refresh interval value: Gufw release 14.04.2 LTS.
>

Please, find your Gufw path:
sudo find /usr -type f -name "gufw.py"
I'm thinking it will be
/usr/lib/python2.7/dist-packages/gufw

Edit that file with:
sudo gedit /usr/lib/python2.7/dist-packages/gufw/view/listening.py

Change this line 72:
        self.gufw.listening_model.clear()

for these lines (be careful with the spaces!):
        self.gufw.listening_model.clear()
        print("doing...")

run Gufw from the command line:
sudo gufw
Play with the Listening Report frame and refresh time. You'll see a message
into the Terminal every time Gufw is refreshing the Listening Report.
Please, confirm me what is happen.

> Regarding the port numbers, how about adding one or two columns in the
> listening report table with the services names and/or description from the
> official "Service Name and Transport Protocol Port Number Registry":
> http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml
> It should be easy to include the previous file in your package.
>

Please, could you give me an example of a port without app and which
service you're using for generate that line in the Listening Report?
FYI An '*' is used in place of the address of the interface when the
executable is bound to all interfaces on that port.

In other way, what is showing this command for that port without app (by
example 110)?
grep "110" /etc/services
Could be /etc/services a solution? I think is the same file :)

I created a new bug for this: #1353508

Best regards Jean :)

[jean-christophe manciot (manciot-jeanchristophe)]

Actually, the paths are:
/usr/share/gufw/gufw/view/gufw.py
/usr/share/gufw/gufw/gufw.py

and the two files are very different....

After adding the printf, and starting gufw, the message is generated regularly in the window.

/etc/services is only a small part of the file I was talking about.

[jean-christophe manciot (manciot-jeanchristophe)]

I've just found a workaround for the first issue: if we select a line while scrolling down, the refresh does not scroll back to the first line of the report.

[jean-christophe manciot (manciot-jeanchristophe)]

So my suggestion to solve this slight issue is to select the first current line of the report while the user scrolls down.
The next refresh won't change anything regarding the current displayed lines.

[jean-christophe manciot (manciot-jeanchristophe)]

About the unkown ports: how do I know which application(s) open(s) a particular UDP/TCP port?

[costales (costales)]

>
> /usr/share/gufw/gufw/view/gufw.py
>

It is /usr/share/gufw/gufw/view/gufw.py

> After adding the printf, and starting gufw, the message is generated
> regularly in the window.
>

Then, the refresh Listening Report is working right :) Isn't it?

> /etc/services is only a small part of the file I was talking about.
>

I'd prefer a system file to an external file. In other way, could you tell
us a port example with an empty app? :)

> if we select a line while scrolling down, the refresh does not scroll
back to the first line of the report.

Yes, that it's because if you select a line, gufw is saving that and in the
refresh, gufw is selecting it again :P But it'll not fix the issue :P

> So my suggestion to solve this slight issue is to select the first
current line of the report while the user scrolls down. The next refresh
won't change anything regarding the current displayed lines.

I'm afraid that the frame is not working like that and I can't select a
line if the user is not select it previously ;)

> About the unkown ports: how do I know which application(s) open(s) a
particular UDP/TCP port?

Just tell me the port/s :)

Thanks in advance Jean!
Costales.

[jean-christophe manciot (manciot-jeanchristophe)]

> Then, the refresh Listening Report is working right :) Isn't it?

I never siad it was not wortking; I said that changing the refresh interval needed a gufw restart to be taken into account.

> About the unkown ports: how do I know which application(s) open(s) a particular UDP/TCP port?
Sorry, I'd rather not disclose suspect open ports on my system until I'm sure whether they are legit or not...

I've tried all the following commands unsuccessfully: they all lead to "-" for some port numbers;
- netstat -tulpn
- fuser port-number/protocol
- lsof -i protocol:port-number

Is there another way to discover which process opened them?

[jean-christophe manciot (manciot-jeanchristophe)]

Also, some open ports are missing in the listening report: if I do "netstat -tulpn", I collect 5 more ports...

[jean-christophe manciot (manciot-jeanchristophe)]

The hidden ports are within the dynamic ports zone (49152-65535) and below, in some unassigned portions (above ~ 30000).
They mutate when I try to block them, several times a day and on system restart.

[jean-christophe manciot (manciot-jeanchristophe)]

I've solved the "hidden ports" mystery: they are used by NFS deamon (nfs-kernel-server). More details on this thread: http://ubuntuforums.org/showthread.php?t=2238950&p=13102309#post13102309

[costales (costales)]

Thanks a lot for the info Jean :)