Bug 1021550

Summary: Virt-viewer doesn't honour 'ignore hosts' field in proxy settings
Product: [Fedora] Fedora Reporter: Pablo Iranzo Gómez <pablo.iranzo>
Component: virt-viewerAssignee: Daniel Berrangé <berrange>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 19CC: berrange, cfergeau, marcandre.lureau, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:46:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pablo Iranzo Gómez 2013-10-21 13:41:45 UTC
Description of problem:

I was unable to connect to LAN host with virt-viewer.

It always timed out, but a netstat showed that it was trying to connect to my proxy.

Proxy was configured as:
(gnome proxy settings window)

http  127.0.0.1 8118
https  127.0.0.1 8118
ftp
socks  127.0.0.1 9999
ignore: localhost, 127.0.0.0/8, ::1, 192.168.2.0/24

remote-viewer should ignore the proxy settings for a host in 192.168.2.* subnet, but it was trying to use it.


Version-Release number of selected component (if applicable):
virt-viewer-0.5.6-1.fc19.x86_64

How reproducible:
Configure socks proxy and put an entry for it in 'ignore', fire up remote-viewer and use netstat to verify the connection:

[iranzo@x201 Descargas]$ netstat -anputa|grep remote
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 127.0.0.1:47908         127.0.0.1:9999          ESTABLISHED 22678/remote-viewer 


Actual results:
It tries to use sock proxy (which would be OK, if it weren't in the ignore part)


Expected results:

Ignore proxy for hosts listed in ignore field

Comment 1 Christophe Fergeau 2013-10-30 11:22:39 UTC
Have you also set a SPICE_PROXY environment variable? My understanding is that spice-gtk/remote-viewer do not use GNOME proxy settings.

Comment 2 Pablo Iranzo Gómez 2013-10-30 11:38:23 UTC
(In reply to Christophe Fergeau from comment #1)
> Have you also set a SPICE_PROXY environment variable? My understanding is
> that spice-gtk/remote-viewer do not use GNOME proxy settings.


[iranzo@x201 ~]$ set|grep -i proxy
all_proxy=socks://127.0.0.1:9999/
ftp_proxy=socks://127.0.0.1:9999/
http_proxy=http://127.0.0.1:8118/
https_proxy=https://127.0.0.1:8118/
no_proxy=localhost,127.0.0.0/8


No, no SPICE_PROXY, and just changed the gnome proxy settings and it started working

Comment 3 Fedora End Of Life 2015-01-09 20:19:53 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-02-17 17:46:19 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.