I was able to print from any remote computer in F20, now when I try to print I get socket not connected.I deleted and re-installed remote printer but when I try to print a test page it says that printer is not connected. Network printing is a nightmare for me, sorry to say...
antonio ha scrito il 01/02/2015 alle 12:08:
I was able to print from any remote computer in F20, now when I try to print I get socket not connected.I deleted and re-installed remote printer but when I try to print a test page it says that printer is not connected. Network printing is a nightmare for me, sorry to say...
it seems that the soultion is to check ipp and ipp-client in Firewall zones, not so obvious when you have done a standard installation of Fedora-Workstation (or in my case un upgrade of F20 where everything was fine). I still think that Firewalld settings should be adjusted by system when a printer is shared (as they were in F20 in my home zone in F20)
On Sun, Feb 1, 2015 at 9:23 AM, antonio antonio.montagnani@gmail.com wrote:
antonio ha scrito il 01/02/2015 alle 12:08:
it seems that the soultion is to check ipp and ipp-client in Firewall zones, not so obvious when you have done a standard installation of Fedora-Workstation (or in my case un upgrade of F20 where everything was fine). I still think that Firewalld settings should be adjusted by system when a printer is shared (as they were in F20 in my home zone in F20)
Yeah ick. And firewall-config isn't installed by default in Fedora 21. I think this should be mentioned on desktop@ so the Workstation WG is aware of it. A brief search of desktop@ doesn't bring up printing related subjects in 6 months.
Chris Murphy ha scrito il 01/02/2015 alle 17:46:
On Sun, Feb 1, 2015 at 9:23 AM, antonio antonio.montagnani@gmail.com wrote:
antonio ha scrito il 01/02/2015 alle 12:08:
it seems that the soultion is to check ipp and ipp-client in Firewall zones, not so obvious when you have done a standard installation of Fedora-Workstation (or in my case un upgrade of F20 where everything was fine). I still think that Firewalld settings should be adjusted by system when a printer is shared (as they were in F20 in my home zone in F20)
Yeah ick. And firewall-config isn't installed by default in Fedora 21. I think this should be mentioned on desktop@ so the Workstation WG is aware of it. A brief search of desktop@ doesn't bring up printing related subjects in 6 months.
Chris
https://bugzilla.redhat.com/show_bug.cgi?id=1187999
Please check my last comment and see if it is clear, otherwise please add your comments
On 01.02.2015 17:23, antonio wrote:
antonio ha scrito il 01/02/2015 alle 12:08:
I was able to print from any remote computer in F20, now when I try to print I get socket not connected.I deleted and re-installed remote printer but when I try to print a test page it says that printer is not connected. Network printing is a nightmare for me, sorry to say...
it seems that the soultion is to check ipp and ipp-client in Firewall zones, not so obvious when you have done a standard installation of Fedora-Workstation (or in my case un upgrade of F20 where everything was fine). I still think that Firewalld settings should be adjusted by system when a printer is shared (as they were in F20 in my home zone in F20)
The last time I set up a printer, a mechanism to adjust the firewall was working https://git.fedorahosted.org/cgit/system-config-printer.git/tree/serversetti...
poma ha scrito il 01/02/2015 alle 18:37:
On 01.02.2015 17:23, antonio wrote:
antonio ha scrito il 01/02/2015 alle 12:08:
I was able to print from any remote computer in F20, now when I try to print I get socket not connected.I deleted and re-installed remote printer but when I try to print a test page it says that printer is not connected. Network printing is a nightmare for me, sorry to say...
it seems that the soultion is to check ipp and ipp-client in Firewall zones, not so obvious when you have done a standard installation of Fedora-Workstation (or in my case un upgrade of F20 where everything was fine). I still think that Firewalld settings should be adjusted by system when a printer is shared (as they were in F20 in my home zone in F20)
The last time I set up a printer, a mechanism to adjust the firewall was working https://git.fedorahosted.org/cgit/system-config-printer.git/tree/serversetti...
correct, it was working in F20, but only if you were installing a new printer, if you had already set a printer (as in my case) from F19, you had to adjust by hand the Firewalld settings
On 01.02.2015 18:50, antonio wrote:
poma ha scrito il 01/02/2015 alle 18:37:
On 01.02.2015 17:23, antonio wrote:
antonio ha scrito il 01/02/2015 alle 12:08:
I was able to print from any remote computer in F20, now when I try to print I get socket not connected.I deleted and re-installed remote printer but when I try to print a test page it says that printer is not connected. Network printing is a nightmare for me, sorry to say...
it seems that the soultion is to check ipp and ipp-client in Firewall zones, not so obvious when you have done a standard installation of Fedora-Workstation (or in my case un upgrade of F20 where everything was fine). I still think that Firewalld settings should be adjusted by system when a printer is shared (as they were in F20 in my home zone in F20)
The last time I set up a printer, a mechanism to adjust the firewall was working https://git.fedorahosted.org/cgit/system-config-printer.git/tree/serversetti...
correct, it was working in F20, but only if you were installing a new printer, if you had already set a printer (as in my case) from F19, you had to adjust by hand the Firewalld settings
I just checked with my Fedora 21 LiveDVD compilation with full support for printing, and this mechanism does not work at all.
Mister Waugh, whether it's worth a try latest and greatest? https://git.fedorahosted.org/cgit/system-config-printer.git/
poma
On Sun, Feb 1, 2015 at 12:28 PM, poma pomidorabelisima@gmail.com wrote:
On 01.02.2015 18:50, antonio wrote:
correct, it was working in F20, but only if you were installing a new printer, if you had already set a printer (as in my case) from F19, you had to adjust by hand the Firewalld settings
I just checked with my Fedora 21 LiveDVD compilation with full support for printing, and this mechanism does not work at all.
Huh. Well my gut instinct is this should work out of the box and that it's an oversight with firewalld-config-workstation.noarch not permitting IPP.
I posted a message on desktop@ whether there should be a printing related release criteria.
On 01.02.2015 21:41, Chris Murphy wrote:
On Sun, Feb 1, 2015 at 12:28 PM, poma pomidorabelisima@gmail.com wrote:
On 01.02.2015 18:50, antonio wrote:
correct, it was working in F20, but only if you were installing a new printer, if you had already set a printer (as in my case) from F19, you had to adjust by hand the Firewalld settings
I just checked with my Fedora 21 LiveDVD compilation with full support for printing, and this mechanism does not work at all.
Huh. Well my gut instinct is this should work out of the box and that it's an oversight with firewalld-config-workstation.noarch not permitting IPP.
I posted a message on desktop@ whether there should be a printing related release criteria.
The compilation I mentioned is based on Xfce.
Therefore this issue is much wider then "Desktop/Workstation/GNOME" narrow understanding of the concept of a firewall. https://lists.fedoraproject.org/pipermail/devel/2014-December/205010.html
On Sun, Feb 1, 2015 at 3:22 PM, poma pomidorabelisima@gmail.com wrote:
On 01.02.2015 21:41, Chris Murphy wrote:
On Sun, Feb 1, 2015 at 12:28 PM, poma pomidorabelisima@gmail.com wrote:
On 01.02.2015 18:50, antonio wrote:
correct, it was working in F20, but only if you were installing a new printer, if you had already set a printer (as in my case) from F19, you had to adjust by hand the Firewalld settings
I just checked with my Fedora 21 LiveDVD compilation with full support for printing, and this mechanism does not work at all.
Huh. Well my gut instinct is this should work out of the box and that it's an oversight with firewalld-config-workstation.noarch not permitting IPP.
I posted a message on desktop@ whether there should be a printing related release criteria.
The compilation I mentioned is based on Xfce.
Therefore this issue is much wider then "Desktop/Workstation/GNOME" narrow understanding of the concept of a firewall. https://lists.fedoraproject.org/pipermail/devel/2014-December/205010.html
poma and antonio, what do you get for: rpm -qa | grep firewalld-config
And can both of you confirm which firewall-config checkbox you're checking to resolve this? Is it ipp or ipp-client or both? I'm going to guess it's just ipp-client that's needed.
Note that ipp and ipp-client uses port 631 which is below the open ports 1025+ for Fedora 21. It has to be explicitly permitted and on a clean Fedora 21 Workstation VM for me ipp and ipp-client are disabled and thus blocked by firewalld. Thing is, it's not obvious because firewall-config isn't installed by default. So it's actually an interesting question what the intended workflow for printing to network or remote CUPS printers is supposed to be? It's a little silly (not really in the funny way) if it's "oh yeah so, yum install firewall-config and check ipp-client and then you can print." Umm really?
With the IPP Everywhere work in progress, I think this has to be enabled by default in order for its goals to be achievable. https://www.pwg.org/ipp/everywhere.html
Chris Murphy ha scrito il 02/02/2015 alle 05:02:
On Sun, Feb 1, 2015 at 3:22 PM, poma pomidorabelisima@gmail.com wrote:
On 01.02.2015 21:41, Chris Murphy wrote:
On Sun, Feb 1, 2015 at 12:28 PM, poma pomidorabelisima@gmail.com wrote:
On 01.02.2015 18:50, antonio wrote:
correct, it was working in F20, but only if you were installing a new printer, if you had already set a printer (as in my case) from F19, you had to adjust by hand the Firewalld settings
I just checked with my Fedora 21 LiveDVD compilation with full support for printing, and this mechanism does not work at all.
Huh. Well my gut instinct is this should work out of the box and that it's an oversight with firewalld-config-workstation.noarch not permitting IPP.
I posted a message on desktop@ whether there should be a printing related release criteria.
The compilation I mentioned is based on Xfce.
Therefore this issue is much wider then "Desktop/Workstation/GNOME" narrow understanding of the concept of a firewall. https://lists.fedoraproject.org/pipermail/devel/2014-December/205010.html
poma and antonio, what do you get for: rpm -qa | grep firewalld-config
And can both of you confirm which firewall-config checkbox you're checking to resolve this? Is it ipp or ipp-client or both? I'm going to guess it's just ipp-client that's needed.
Note that ipp and ipp-client uses port 631 which is below the open ports 1025+ for Fedora 21. It has to be explicitly permitted and on a clean Fedora 21 Workstation VM for me ipp and ipp-client are disabled and thus blocked by firewalld. Thing is, it's not obvious because firewall-config isn't installed by default. So it's actually an interesting question what the intended workflow for printing to network or remote CUPS printers is supposed to be? It's a little silly (not really in the funny way) if it's "oh yeah so, yum install firewall-config and check ipp-client and then you can print." Umm really?
With the IPP Everywhere work in progress, I think this has to be enabled by default in order for its goals to be achievable. https://www.pwg.org/ipp/everywhere.html
firewalld-config-workstation-0.3.13-1.fc21.noarch
I checked box, I do not remember why I checked both :-) , when I have some spare time I will uncheck only ipp .Tnx for your help. Please add also your comments to my bugzilla
On 02.02.2015 05:02, Chris Murphy wrote:
On Sun, Feb 1, 2015 at 3:22 PM, poma pomidorabelisima@gmail.com wrote:
On 01.02.2015 21:41, Chris Murphy wrote:
On Sun, Feb 1, 2015 at 12:28 PM, poma pomidorabelisima@gmail.com wrote:
On 01.02.2015 18:50, antonio wrote:
correct, it was working in F20, but only if you were installing a new printer, if you had already set a printer (as in my case) from F19, you had to adjust by hand the Firewalld settings
I just checked with my Fedora 21 LiveDVD compilation with full support for printing, and this mechanism does not work at all.
Huh. Well my gut instinct is this should work out of the box and that it's an oversight with firewalld-config-workstation.noarch not permitting IPP.
I posted a message on desktop@ whether there should be a printing related release criteria.
The compilation I mentioned is based on Xfce.
Therefore this issue is much wider then "Desktop/Workstation/GNOME" narrow understanding of the concept of a firewall. https://lists.fedoraproject.org/pipermail/devel/2014-December/205010.html
poma and antonio, what do you get for: rpm -qa | grep firewalld-config
And can both of you confirm which firewall-config checkbox you're checking to resolve this? Is it ipp or ipp-client or both? I'm going to guess it's just ipp-client that's needed.
Note that ipp and ipp-client uses port 631 which is below the open ports 1025+ for Fedora 21. It has to be explicitly permitted and on a clean Fedora 21 Workstation VM for me ipp and ipp-client are disabled and thus blocked by firewalld. Thing is, it's not obvious because firewall-config isn't installed by default. So it's actually an interesting question what the intended workflow for printing to network or remote CUPS printers is supposed to be? It's a little silly (not really in the funny way) if it's "oh yeah so, yum install firewall-config and check ipp-client and then you can print." Umm really?
With the IPP Everywhere work in progress, I think this has to be enabled by default in order for its goals to be achievable. https://www.pwg.org/ipp/everywhere.html
Thank you for your concern.
# ./uld/install-printer.sh ... **** Are you going to use network devices ? If yes, it is recommended to configure your firewall. **** If you want to configure firewall automatically, enter 'y' or just press 'Enter'. To skip, enter 'n'. : y **** Registering CUPS backend ... **** CUPS restart OK. **** Print driver has been installed successfully. **** Install finished.
$ firewall-cmd --list-ports 22161/udp
$ grep -R 22161 uld/ uld/noarch/firewall.sh:DEFAULT_SNMP_BROADCAST_PORT="22161" uld/noarch/security.pkg:# allow cups bind 22161 udp port uld/noarch/security.pkg: "$SEMANAGE" port "$1" -t ipp_port_t -p udp 22161
poma
On 01.02.2015 20:28, poma wrote:
On 01.02.2015 18:50, antonio wrote:
poma ha scrito il 01/02/2015 alle 18:37:
On 01.02.2015 17:23, antonio wrote:
antonio ha scrito il 01/02/2015 alle 12:08:
I was able to print from any remote computer in F20, now when I try to print I get socket not connected.I deleted and re-installed remote printer but when I try to print a test page it says that printer is not connected. Network printing is a nightmare for me, sorry to say...
it seems that the soultion is to check ipp and ipp-client in Firewall zones, not so obvious when you have done a standard installation of Fedora-Workstation (or in my case un upgrade of F20 where everything was fine). I still think that Firewalld settings should be adjusted by system when a printer is shared (as they were in F20 in my home zone in F20)
The last time I set up a printer, a mechanism to adjust the firewall was working https://git.fedorahosted.org/cgit/system-config-printer.git/tree/serversetti...
correct, it was working in F20, but only if you were installing a new printer, if you had already set a printer (as in my case) from F19, you had to adjust by hand the Firewalld settings
I just checked with my Fedora 21 LiveDVD compilation with full support for printing, and this mechanism does not work at all.
Mister Waugh, whether it's worth a try latest and greatest? https://git.fedorahosted.org/cgit/system-config-printer.git/
https://git.fedorahosted.org/cgit/system-config-printer.git/commit/?id=83177...
# system-config-printer --debug ... update_jobs Connected as user root Authentication pass: 1 Authentication: password callback set <authconn.Connection object at 0x7f6762c9bd68>: Operation += fetching server settings Authentication pass: 1 Authentication: password callback set <authconn.Connection object at 0x7f6762c9bd68>: Operation ended on_server_changed: <CheckButton object at 0x7f676332bb40 (GtkCheckButton at 0x398ff80)> on_server_changed: <CheckButton object at 0x7f676332bb40 (GtkCheckButton at 0x398ff80)> on_server_changed: <CheckButton object at 0x7f676332be58 (GtkCheckButton at 0x39f7180)> on_server_changed: <CheckButton object at 0x7f676332bea0 (GtkCheckButton at 0x39f7340)> <authconn.Connection object at 0x7f6762c9bd68>: Operation += modifying server settings Authentication pass: 1 Authentication: password callback set <authconn.Connection object at 0x7f6762c9bd68>: Operation ended Using system-config-firewall Caught non-fatal exception. Traceback: File "/usr/share/system-config-printer/serversettings.py", line 552, in saveBasic allowed = f.check_ipp_server_allowed () File "/usr/share/system-config-printer/firewallsettings.py", line 252, in check_ipp_server_allowed "--service=" + IPP_SERVER_SERVICE])) File "/usr/share/system-config-printer/firewallsettings.py", line 228, in _check_any_allowed (args, filename) = self._get_fw_data () TypeError: 'NoneType' object is not iterable Continuing anyway.. Connected as user root D-Bus signal from CUPS... calling update Next notifications fetch in 200ms (update called) get_notifications update_jobs ...
On Sun, 2015-02-01 at 20:28 +0100, poma wrote:
Mister Waugh, whether it's worth a try latest and greatest? https://git.fedorahosted.org/cgit/system-config-printer.git/
The problem is that firewalld only provides Python2 bindings, whereas system-config-printer is Python3.
Tim. */
On 02.02.2015 12:41, Tim Waugh wrote:
On Sun, 2015-02-01 at 20:28 +0100, poma wrote:
Mister Waugh, whether it's worth a try latest and greatest? https://git.fedorahosted.org/cgit/system-config-printer.git/
The problem is that firewalld only provides Python2 bindings, whereas system-config-printer is Python3.
Tim. */
Thanks for your response.
Mister Woerner, Popelka can we users of Fedora 21 also get support for Py3?
# system-config-printer --debug ... Caught non-fatal exception. Traceback: File "/usr/share/system-config-printer/serversettings.py", line 552, in saveBasic allowed = f.check_ipp_server_allowed () File "/usr/share/system-config-printer/firewallsettings.py", line 252, in check_ipp_server_allowed "--service=" + IPP_SERVER_SERVICE])) File "/usr/share/system-config-printer/firewallsettings.py", line 228, in _check_any_allowed (args, filename) = self._get_fw_data () TypeError: 'NoneType' object is not iterable Continuing anyway..
poma
Ref. Enable Python3 support in spec file https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=f087e22
On 02/02/2015 02:39 PM, poma wrote:
On 02.02.2015 12:41, Tim Waugh wrote:
On Sun, 2015-02-01 at 20:28 +0100, poma wrote:
Mister Waugh, whether it's worth a try latest and greatest? https://git.fedorahosted.org/cgit/system-config-printer.git/
The problem is that firewalld only provides Python2 bindings, whereas system-config-printer is Python3.
Tim. */
Thanks for your response.
Mister Woerner, Popelka can we users of Fedora 21 also get support for Py3?
# system-config-printer --debug ... Caught non-fatal exception. Traceback: File "/usr/share/system-config-printer/serversettings.py", line 552, in saveBasic allowed = f.check_ipp_server_allowed () File "/usr/share/system-config-printer/firewallsettings.py", line 252, in check_ipp_server_allowed "--service=" + IPP_SERVER_SERVICE])) File "/usr/share/system-config-printer/firewallsettings.py", line 228, in _check_any_allowed (args, filename) = self._get_fw_data () TypeError: 'NoneType' object is not iterable Continuing anyway..
poma
Ref. Enable Python3 support in spec file https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=f087e22
Yes, sure - it is building already: http://koji.fedoraproject.org/koji/taskinfo?taskID=8794185
Regards, Thomas
On 02.02.2015 14:41, Thomas Woerner wrote:
On 02/02/2015 02:39 PM, poma wrote:
On 02.02.2015 12:41, Tim Waugh wrote:
On Sun, 2015-02-01 at 20:28 +0100, poma wrote:
Mister Waugh, whether it's worth a try latest and greatest? https://git.fedorahosted.org/cgit/system-config-printer.git/
The problem is that firewalld only provides Python2 bindings, whereas system-config-printer is Python3.
Tim. */
Thanks for your response.
Mister Woerner, Popelka can we users of Fedora 21 also get support for Py3?
# system-config-printer --debug ... Caught non-fatal exception. Traceback: File "/usr/share/system-config-printer/serversettings.py", line 552, in saveBasic allowed = f.check_ipp_server_allowed () File "/usr/share/system-config-printer/firewallsettings.py", line 252, in check_ipp_server_allowed "--service=" + IPP_SERVER_SERVICE])) File "/usr/share/system-config-printer/firewallsettings.py", line 228, in _check_any_allowed (args, filename) = self._get_fw_data () TypeError: 'NoneType' object is not iterable Continuing anyway..
poma
Ref. Enable Python3 support in spec file https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=f087e22
Yes, sure - it is building already: http://koji.fedoraproject.org/koji/taskinfo?taskID=8794185
Regards, Thomas
Thank you, this is now working. http://goo.gl/MrB9x1
firewall-applet-0.3.13-2.fc21.noarch firewall-config-0.3.13-2.fc21.noarch firewalld-0.3.13-2.fc21.noarch firewalld-config-standard-0.3.13-2.fc21.noarch firewalld-filesystem-0.3.13-2.fc21.noarch python2-firewall-0.3.13-2.fc21.noarch python3-firewall-0.3.13-2.fc21.noarch
Mister Waugh, can this mechanism be improved in the way when you chose not to want to share the printer that the relevant port is closed?
poma
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
can this mechanism be improved in the way when you chose not to want to share the printer that the relevant port is closed?
Is there a sane way of doing that though? I think applications wanting to 'reset' ports for a zone would need to know what the default was to start with.
Tim. */
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
can this mechanism be improved in the way when you chose not to want to share the printer that the relevant port is closed?
Is there a sane way of doing that though? I think applications wanting to 'reset' ports for a zone would need to know what the default was to start with.
Tim. */
I really do not understand what should be an obstacle. :) Just to close the port that is no longer used, the same way that we opened.
poma
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
can this mechanism be improved in the way when you chose not to want to share the printer that the relevant port is closed?
Is there a sane way of doing that though? I think applications wanting to 'reset' ports for a zone would need to know what the default was to start with.
Tim. */
I really do not understand what should be an obstacle. :) Just to close the port that is no longer used, the same way that we opened.
Mister Woerner, Popelka care to comment? Perhaps I missed some technicalities related.
poma ha scrito il 02/02/2015 alle 17:55:
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
can this mechanism be improved in the way when you chose not to want to share the printer that the relevant port is closed?
Is there a sane way of doing that though? I think applications wanting to 'reset' ports for a zone would need to know what the default was to start with.
Tim. */
I really do not understand what should be an obstacle. :) Just to close the port that is no longer used, the same way that we opened.
Mister Woerner, Popelka care to comment? Perhaps I missed some technicalities related.
just from an humble user POV, shall I have to make any adjustment to my firewaslld settings after installation of such an update???
On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
can this mechanism be improved in the way when you chose not to want to share the printer that the relevant port is closed?
Is there a sane way of doing that though? I think applications wanting to 'reset' ports for a zone would need to know what the default was to start with.
Tim. */
I really do not understand what should be an obstacle. :) Just to close the port that is no longer used, the same way that we opened.
Mister Woerner, Popelka care to comment? Perhaps I missed some technicalities related.
I think it would make sense to be able to see if ipp* was enabled in the initial configuration of a zone. Right now this is not possible.
We might be able to add interfaces to get initial zone, service etc. configuration settings.
Regards, Thomas
On 03.02.2015 11:07, Thomas Woerner wrote:
On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
can this mechanism be improved in the way when you chose not to want to share the printer that the relevant port is closed?
Is there a sane way of doing that though? I think applications wanting to 'reset' ports for a zone would need to know what the default was to start with.
Tim. */
I really do not understand what should be an obstacle. :) Just to close the port that is no longer used, the same way that we opened.
Mister Woerner, Popelka care to comment? Perhaps I missed some technicalities related.
I think it would make sense to be able to see if ipp* was enabled in the initial configuration of a zone. Right now this is not possible.
We might be able to add interfaces to get initial zone, service etc. configuration settings.
Regards, Thomas
I think I understand, but I also think that I did not understand. Cogito ergo sum.
On 03.02.2015 18:15, poma wrote:
On 03.02.2015 11:07, Thomas Woerner wrote:
On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
can this mechanism be improved in the way when you chose not to want to share the printer that the relevant port is closed?
Is there a sane way of doing that though? I think applications wanting to 'reset' ports for a zone would need to know what the default was to start with.
Tim. */
I really do not understand what should be an obstacle. :) Just to close the port that is no longer used, the same way that we opened.
Mister Woerner, Popelka care to comment? Perhaps I missed some technicalities related.
I think it would make sense to be able to see if ipp* was enabled in the initial configuration of a zone. Right now this is not possible.
We might be able to add interfaces to get initial zone, service etc. configuration settings.
Regards, Thomas
I think I understand, but I also think that I did not understand. Cogito ergo sum.
https://git.fedorahosted.org/cgit/firewalld.git/tree/TODO#n24 Future Features:
- reflect config changes in firewalld status? CONFIG_CHANGED/RELOAD_NEEDED?
If you refer to this possible future feature you represent as a requirement for external applications to participate in the configuration?
On 04.02.2015 20:08, poma wrote:
On 03.02.2015 18:15, poma wrote:
On 03.02.2015 11:07, Thomas Woerner wrote:
On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote: > can this mechanism be improved in the way when you chose not to want > to share the printer that the relevant port is closed?
Is there a sane way of doing that though? I think applications wanting to 'reset' ports for a zone would need to know what the default was to start with.
Tim. */
I really do not understand what should be an obstacle. :) Just to close the port that is no longer used, the same way that we opened.
Mister Woerner, Popelka care to comment? Perhaps I missed some technicalities related.
I think it would make sense to be able to see if ipp* was enabled in the initial configuration of a zone. Right now this is not possible.
We might be able to add interfaces to get initial zone, service etc. configuration settings.
Regards, Thomas
I think I understand, but I also think that I did not understand. Cogito ergo sum.
https://git.fedorahosted.org/cgit/firewalld.git/tree/TODO#n24 Future Features:
- reflect config changes in firewalld status? CONFIG_CHANGED/RELOAD_NEEDED?
If you refer to this possible future feature you represent as a requirement for external applications to participate in the configuration?
Mister Woerner, Popelka please consider, so users don't get confused further. There is no real reason to wait for Fedora 22.
--- firewalld.spec | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/firewalld.spec b/firewalld.spec index 06b5b05..7727644 100644 --- a/firewalld.spec +++ b/firewalld.spec @@ -1,6 +1,6 @@ %if (0%{?fedora} >= 13 || 0%{?rhel} >= 7) %define with_python3 1 -%if (0%{?fedora} >= 22 || 0%{?rhel} >= 8) +%if (0%{?fedora} >= 21 || 0%{?rhel} >= 8) %define use_python3 1 %endif %endif @@ -8,7 +8,7 @@ Summary: A firewall daemon with D-Bus interface providing a dynamic firewall Name: firewalld Version: 0.3.13 -Release: 2%{?dist} +Release: 3%{?dist} URL: http://www.firewalld.org License: GPLv2+ Source0: https://fedorahosted.org/released/firewalld/%%7Bname%7D-%%7Bversion%7D.tar.b... @@ -413,6 +413,10 @@ fi %endif
%changelog +* Thu Feb 05 2015 poma poma@gmail.com - 0.3.13-3 +- use python3 bindings also on Fedora 21 for "publish shared printers" + functionality in system-config-printer + * Wed Jan 28 2015 Thomas Woerner twoerner@redhat.com - 0.3.13-2 - enable python2 and python3 bindings for fedora >= 20 and rhel >= 7 - use python3 bindings on fedora >= 22 and rhel >= 8 for firewalld,
On 02/05/2015 06:57 PM, poma wrote:
On 04.02.2015 20:08, poma wrote:
On 03.02.2015 18:15, poma wrote:
On 03.02.2015 11:07, Thomas Woerner wrote:
On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote: > On Mon, 2015-02-02 at 17:32 +0100, poma wrote: >> can this mechanism be improved in the way when you chose not to want >> to share the printer that the relevant port is closed? > > Is there a sane way of doing that though? I think applications wanting > to 'reset' ports for a zone would need to know what the default was to > start with. > > Tim. > */ >
I really do not understand what should be an obstacle. :) Just to close the port that is no longer used, the same way that we opened.
Mister Woerner, Popelka care to comment? Perhaps I missed some technicalities related.
I think it would make sense to be able to see if ipp* was enabled in the initial configuration of a zone. Right now this is not possible.
We might be able to add interfaces to get initial zone, service etc. configuration settings.
Regards, Thomas
I think I understand, but I also think that I did not understand. Cogito ergo sum.
https://git.fedorahosted.org/cgit/firewalld.git/tree/TODO#n24 Future Features:
- reflect config changes in firewalld status? CONFIG_CHANGED/RELOAD_NEEDED?
If you refer to this possible future feature you represent as a requirement for external applications to participate in the configuration?
Mister Woerner, Popelka please consider, so users don't get confused further. There is no real reason to wait for Fedora 22.
I think there is, because switching to Python3 also in Fedora 21 will change requirements for already installed systems and also for fresh installations. This will result in having both Python versions in the default installation.
With Python3 as the default python interpreter in Fedora 22 this is expected there, but not in Fedora 21.
firewalld.spec | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/firewalld.spec b/firewalld.spec index 06b5b05..7727644 100644 --- a/firewalld.spec +++ b/firewalld.spec @@ -1,6 +1,6 @@ %if (0%{?fedora} >= 13 || 0%{?rhel} >= 7) %define with_python3 1 -%if (0%{?fedora} >= 22 || 0%{?rhel} >= 8) +%if (0%{?fedora} >= 21 || 0%{?rhel} >= 8) %define use_python3 1 %endif %endif @@ -8,7 +8,7 @@ Summary: A firewall daemon with D-Bus interface providing a dynamic firewall Name: firewalld Version: 0.3.13 -Release: 2%{?dist} +Release: 3%{?dist} URL: http://www.firewalld.org License: GPLv2+ Source0: https://fedorahosted.org/released/firewalld/%%7Bname%7D-%%7Bversion%7D.tar.b... @@ -413,6 +413,10 @@ fi %endif
%changelog +* Thu Feb 05 2015 poma poma@gmail.com - 0.3.13-3 +- use python3 bindings also on Fedora 21 for "publish shared printers"
- functionality in system-config-printer
- Wed Jan 28 2015 Thomas Woerner twoerner@redhat.com - 0.3.13-2
- enable python2 and python3 bindings for fedora >= 20 and rhel >= 7
- use python3 bindings on fedora >= 22 and rhel >= 8 for firewalld,
Regards, Thomas
On 06.02.2015 14:05, Thomas Woerner wrote:
On 02/05/2015 06:57 PM, poma wrote:
On 04.02.2015 20:08, poma wrote:
On 03.02.2015 18:15, poma wrote:
On 03.02.2015 11:07, Thomas Woerner wrote:
On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote: > On 02.02.2015 17:36, Tim Waugh wrote: >> On Mon, 2015-02-02 at 17:32 +0100, poma wrote: >>> can this mechanism be improved in the way when you chose not to want >>> to share the printer that the relevant port is closed? >> >> Is there a sane way of doing that though? I think applications wanting >> to 'reset' ports for a zone would need to know what the default was to >> start with. >> >> Tim. >> */ >> > > I really do not understand what should be an obstacle. :) > Just to close the port that is no longer used, the same way that we opened. >
Mister Woerner, Popelka care to comment? Perhaps I missed some technicalities related.
I think it would make sense to be able to see if ipp* was enabled in the initial configuration of a zone. Right now this is not possible.
We might be able to add interfaces to get initial zone, service etc. configuration settings.
Regards, Thomas
I think I understand, but I also think that I did not understand. Cogito ergo sum.
https://git.fedorahosted.org/cgit/firewalld.git/tree/TODO#n24 Future Features:
- reflect config changes in firewalld status? CONFIG_CHANGED/RELOAD_NEEDED?
If you refer to this possible future feature you represent as a requirement for external applications to participate in the configuration?
Mister Woerner, Popelka please consider, so users don't get confused further. There is no real reason to wait for Fedora 22.
I think there is, because switching to Python3 also in Fedora 21 will change requirements for already installed systems and also for fresh installations. This will result in having both Python versions in the default installation.
With Python3 as the default python interpreter in Fedora 22 this is expected there, but not in Fedora 21.
If possible I would appreciate clearer explanation.
To gain "publish shared printers" functionality in 'system-config-printer', required is to install 'python3-firewall'. Will it be done manually # yum install python3-firewall or the 'python3-firewall' will be automatically pulled by the main package # yum update firewalld it still has to be done. The only difference is that in the second case it works on more friendly way.
firewalld.spec | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/firewalld.spec b/firewalld.spec index 06b5b05..7727644 100644 --- a/firewalld.spec +++ b/firewalld.spec @@ -1,6 +1,6 @@ %if (0%{?fedora} >= 13 || 0%{?rhel} >= 7) %define with_python3 1 -%if (0%{?fedora} >= 22 || 0%{?rhel} >= 8) +%if (0%{?fedora} >= 21 || 0%{?rhel} >= 8) %define use_python3 1 %endif %endif @@ -8,7 +8,7 @@ Summary: A firewall daemon with D-Bus interface providing a dynamic firewall Name: firewalld Version: 0.3.13 -Release: 2%{?dist} +Release: 3%{?dist} URL: http://www.firewalld.org License: GPLv2+ Source0: https://fedorahosted.org/released/firewalld/%%7Bname%7D-%%7Bversion%7D.tar.b... @@ -413,6 +413,10 @@ fi %endif
%changelog +* Thu Feb 05 2015 poma poma@gmail.com - 0.3.13-3 +- use python3 bindings also on Fedora 21 for "publish shared printers"
- functionality in system-config-printer
- Wed Jan 28 2015 Thomas Woerner twoerner@redhat.com - 0.3.13-2
- enable python2 and python3 bindings for fedora >= 20 and rhel >= 7
- use python3 bindings on fedora >= 22 and rhel >= 8 for firewalld,
Regards, Thomas
On 02/06/2015 11:47 PM, poma wrote:
On 06.02.2015 14:05, Thomas Woerner wrote:
On 02/05/2015 06:57 PM, poma wrote:
On 04.02.2015 20:08, poma wrote:
On 03.02.2015 18:15, poma wrote:
On 03.02.2015 11:07, Thomas Woerner wrote:
On 02/02/2015 05:55 PM, poma wrote: > On 02.02.2015 17:49, poma wrote: >> On 02.02.2015 17:36, Tim Waugh wrote: >>> On Mon, 2015-02-02 at 17:32 +0100, poma wrote: >>>> can this mechanism be improved in the way when you chose not to want >>>> to share the printer that the relevant port is closed? >>> >>> Is there a sane way of doing that though? I think applications wanting >>> to 'reset' ports for a zone would need to know what the default was to >>> start with. >>> >>> Tim. >>> */ >>> >> >> I really do not understand what should be an obstacle. :) >> Just to close the port that is no longer used, the same way that we opened. >> > > Mister Woerner, Popelka care to comment? > Perhaps I missed some technicalities related. > > I think it would make sense to be able to see if ipp* was enabled in the initial configuration of a zone. Right now this is not possible.
We might be able to add interfaces to get initial zone, service etc. configuration settings.
Regards, Thomas
I think I understand, but I also think that I did not understand. Cogito ergo sum.
https://git.fedorahosted.org/cgit/firewalld.git/tree/TODO#n24 Future Features:
- reflect config changes in firewalld status? CONFIG_CHANGED/RELOAD_NEEDED?
If you refer to this possible future feature you represent as a requirement for external applications to participate in the configuration?
Mister Woerner, Popelka please consider, so users don't get confused further. There is no real reason to wait for Fedora 22.
I think there is, because switching to Python3 also in Fedora 21 will change requirements for already installed systems and also for fresh installations. This will result in having both Python versions in the default installation.
With Python3 as the default python interpreter in Fedora 22 this is expected there, but not in Fedora 21.
If possible I would appreciate clearer explanation.
To gain "publish shared printers" functionality in 'system-config-printer', required is to install 'python3-firewall'. Will it be done manually # yum install python3-firewall or the 'python3-firewall' will be automatically pulled by the main package # yum update firewalld it still has to be done. The only difference is that in the second case it works on more friendly way.
With a requirement of python2-firewall and python3-firewall we end up with the same situation: Both Python versions are installed - even if they are not used.
For now I do not have a solution besides adding a requirement for python3-firewall to system-config-printer. The impact might be small enough with these requirements of python3-firewall:
python(abi) = 3.4 python3-dbus python3-decorator python3-gobject python3-slip-dbus rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsXz) <= 5.2-1
Tim, what do you think?
Regards, Thomas
firewalld.spec | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/firewalld.spec b/firewalld.spec index 06b5b05..7727644 100644 --- a/firewalld.spec +++ b/firewalld.spec @@ -1,6 +1,6 @@ %if (0%{?fedora} >= 13 || 0%{?rhel} >= 7) %define with_python3 1 -%if (0%{?fedora} >= 22 || 0%{?rhel} >= 8) +%if (0%{?fedora} >= 21 || 0%{?rhel} >= 8) %define use_python3 1 %endif %endif @@ -8,7 +8,7 @@ Summary: A firewall daemon with D-Bus interface providing a dynamic firewall Name: firewalld Version: 0.3.13 -Release: 2%{?dist} +Release: 3%{?dist} URL: http://www.firewalld.org License: GPLv2+ Source0: https://fedorahosted.org/released/firewalld/%%7Bname%7D-%%7Bversion%7D.tar.b... @@ -413,6 +413,10 @@ fi %endif
%changelog +* Thu Feb 05 2015 poma poma@gmail.com - 0.3.13-3 +- use python3 bindings also on Fedora 21 for "publish shared printers"
- functionality in system-config-printer
- Wed Jan 28 2015 Thomas Woerner twoerner@redhat.com - 0.3.13-2
- enable python2 and python3 bindings for fedora >= 20 and rhel >= 7
- use python3 bindings on fedora >= 22 and rhel >= 8 for firewalld,
Regards, Thomas
On Sat, 2015-02-07 at 13:02 +0100, Thomas Woerner wrote:
For now I do not have a solution besides adding a requirement for python3-firewall to system-config-printer. The impact might be small enough with these requirements of python3-firewall:
Yes, that doesn't look too bad. I'll include that requirement in the current test update.
Tim. */
On 07.02.2015 23:52, Tim Waugh wrote:
On Sat, 2015-02-07 at 13:02 +0100, Thomas Woerner wrote:
For now I do not have a solution besides adding a requirement for python3-firewall to system-config-printer. The impact might be small enough with these requirements of python3-firewall:
Yes, that doesn't look too bad. I'll include that requirement in the current test update.
Tim. */
scpname=system-config-printer scpver=1.5.5 scprel=2 scpurl=https://kojipkgs.fedoraproject.org/packages/$scpname/$scpver/$scprel.fc21 scpurlx64=$scpurl/x86_64 scpurlnoarch=$scpurl/noarch
wget \ $scpurlx64/$scpname-$scpver-$scprel.fc21.x86_64.rpm \ $scpurlx64/$scpname-applet-$scpver-$scprel.fc21.x86_64.rpm \ $scpurlx64/$scpname-udev-$scpver-$scprel.fc21.x86_64.rpm \ $scpurlnoarch/$scpname-libs-$scpver-$scprel.fc21.noarch.rpm
su -c 'yum install $scpname*$scpver*$scprel.fc21*.rpm'
Thanks.
https://admin.fedoraproject.org/updates/system-config-printer-1.5.5-2.fc21 ... bodhi - 2015-02-16 09:09:19 This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
This should be a karmathematics? :) + raveit65 + cicku + lnie + yuwata = 4
Karma: 2
On Fri, 2015-02-20 at 14:38 +0100, poma wrote:
https://admin.fedoraproject.org/updates/system-config-printer-1.5.5-2.fc21 ... bodhi - 2015-02-16 09:09:19 This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
This should be a karmathematics? :)
- raveit65
- cicku
- lnie
- yuwata
= 4
Karma: 2
The package was updated after the first two scores, which reset the karma.
Tim. */
On 20.02.2015 16:52, Tim Waugh wrote:
On Fri, 2015-02-20 at 14:38 +0100, poma wrote:
https://admin.fedoraproject.org/updates/system-config-printer-1.5.5-2.fc21 ... bodhi - 2015-02-16 09:09:19 This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes
This should be a karmathematics? :)
- raveit65
- cicku
- lnie
- yuwata
= 4
Karma: 2
The package was updated after the first two scores, which reset the karma.
Tim. */
Now that makes sense. raveit, cicku, care to re-karmaised scp?
-
Antonio M -
Chris Murphy -
poma -
Thomas Woerner -
Tim Waugh