Bug 912666 - Connection timeout if wireless and wired connections are both active
Summary: Connection timeout if wireless and wired connections are both active
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: firewalld
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-19 11:15 UTC by Gianluca Sforna
Modified: 2014-02-05 19:18 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 19:18:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
firewalld log (64.78 KB, text/plain)
2013-02-20 07:44 UTC, Gianluca Sforna
no flags Details
Output of firewall-cmd --list-all-zones before attaching wire (873 bytes, text/plain)
2013-02-20 07:58 UTC, Gianluca Sforna
no flags Details
Output of firewall-cmd --list-all-zones after attaching wire (877 bytes, text/plain)
2013-02-20 07:59 UTC, Gianluca Sforna
no flags Details

Description Gianluca Sforna 2013-02-19 11:15:22 UTC
If I'm on wireless and then connect the ethernet wire all connections timeout
and nothing will resolve until I manually disable wireless.

Initially, I thought about a NetworkManager issue (https://bugzilla.gnome.org/show_bug.cgi?id=694151), but things work properly if I stop firewalld

Comment 1 Jiri Popelka 2013-02-19 14:45:14 UTC
Have you perhaps changed some firewalld setting, i.e. is there anything in 
/etc/firewalld/zones/ ?

Add FIREWALLD_ARGS=--debug=2 to /etc/sysconfig/firewalld
and 'systemctl restart firewalld.service'

Then attach the /var/log/firewalld and output of 'firewall-cmd --list-all-zones'
before and after you connect the ethernet wire.

thanks

Comment 2 Richard Hughes 2013-02-19 16:12:03 UTC
Nothing in /etc/firewalld/zones/ for me.

Comment 3 Jiri Popelka 2013-02-19 16:29:55 UTC
hughsie, Rex:

have you been always (in F18) seeing this or has it started with some recent update ?

Comment 4 Rex Dieter 2013-02-19 18:33:00 UTC
I personally don't encounter this issue on KDE, though I don't believe I have any firewall enabled.   I just CC'd myself to lurk (and help, if able).

Comment 5 Gianluca Sforna 2013-02-19 22:28:03 UTC
I started seeing this as soon as I upgraded to F18, nothing in /etc/firewalld/zones/

I will be able to perform the suggested operations tomorrow morning, then will attach the requested files.

Comment 6 Gianluca Sforna 2013-02-20 07:44:21 UTC
Created attachment 699865 [details]
firewalld log

Comment 7 Gianluca Sforna 2013-02-20 07:58:53 UTC
Created attachment 699867 [details]
Output of firewall-cmd --list-all-zones before attaching wire

Comment 8 Gianluca Sforna 2013-02-20 07:59:27 UTC
Created attachment 699868 [details]
Output of firewall-cmd --list-all-zones after attaching wire

Comment 9 Jiri Popelka 2013-02-20 11:32:47 UTC
Hmmm, can't see anything wrong in the logs, both interfaces were correctly added to public zone.

Comment 10 Ferry Huberts 2013-02-20 11:37:38 UTC
The connection tracking table must not be touched when an interface is added or removed. I bet that table is being touched somehow.

Comment 11 Ferry Huberts 2013-02-20 18:01:44 UTC
BTW. I have this issue too on F17: when I dock my laptop after using it off the dock and with wireless only, NM switches to the cable and my connections no longer work (for example: thundebird connects to my imap server but the connection is no longer functional). When I disable the cable connection while still on the dock then the connections resume.

Comment 12 Fedora End Of Life 2013-12-21 11:31:55 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 13 Fedora End Of Life 2014-02-05 19:18:14 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


Note You need to log in before you can comment on or make changes to this bug.