I’ve set up Fedora Workstation on a computer, and I’ve confirmed that when the wifi is turned on, it breaks the wifi router. The router starts to behave in a strange manner, it keeps dropping the connection roughly every few seconds.
It also breaks the router when connecting to the wifi router directly via ethernet cable, but not as frequently and not noticeable at first that I thought it didn’t affect it, until I carefully observed it.
I’ve earlier ran Windows and Ubuntu on the same device that I installed Fedora on, so I am certain it’s not a network card issue.
Things I tried:
Forgeting the wifi connection and reconnecting.
Enabling/disabling NAT-PMP, IGMP snooping, 5G, firewalld, one at a time.
Network controller is Intel Wireless-AC 9560.
Ethernet controller is Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller.
It’s hard to diagnose this issue until we have more information. It is unlikely to be related to the bugzilla issue—that is quite clearly a firmware issue and therefore, should not affect your ethernet hardware.
Can you please look at the output of dmesg to see what it says when you turn on your wifi hardware and so on?
Ok I’ve updated my original post regarding ethernet, so it does affect it but not as much that at first I thought it didn’t.
To answer your questions: #1 Yes I have 6 other devices connect to the router via wifi, and 1 switch on ethernet. I even tried to drop the switch from the network, no change. This is not unusual, as I mentioned, before Fedora I had ran Ubuntu and Windows on this same device, same network setup, for about 2 years there were no issues.
#2 It breaks the router, so yes it affects all devices connected to it.
#3 The moment I disconnect this Fedora from either wifi or ethernet, everything goes back to normal, without restarting the router.
@maxfedora, thanks for clarifying. That’s pretty weird)
Also if that’s an issue specific to AirportExtreme, then it would be very hard to debug without at least someone else with the same router.
I’ve tried to search for AirportExtreme with Linux, and haven’t found any trouble reports – or indeed almost no mentions at all.
Also you’ve mentioned disabling 5G. That means you’re using 2,4 GHz on Fedora right?
Once more shooting in the dark here, there were some reports here on Ask Fedora about 5Ghz WiFi not working with F30, and they tracked it down to driver assigning wrong country code to wireless client on Linux. After setting proper county code the connections worked as expected.
The probability of this being your case is almost null, and I don’t have the links ready, but it should be quite easy to check / rule out (and the posts should be very easy to find).
Yes I tried to disable 5G and had the same issue on 2,4. I had since restored dual mode.
Its certainly not an issue with the Apple router, unless you mean compatibility with Fedora. The router ran fine on Ubuntu and Windows, with the same network setup for a long time I’ve never seen anything like this.
Yes, it can be some specifics of interactions between F30 and this model of router (or Intel wireless driver with this router, or Network Manager or wpa_supplicant currently used by Fedora with this router, etc.).
We can be pretty sure it isn’t Fedora 30 with all the routers problem
When I connect Fedora to the router the top Internet indicator starts to toggle from green to orange, and if I keep it long enough the bottom AE router disappears, soon after everything disappears and it’d say no router is found, after that they’ll come back and it goes on like this.
I am not 100% sure this issue started from when I installed Fedora, I think it started after I tried to connect to it via VNC remote desktop. I had earlier installed tigervnc-server, xrdp and xrdp-sesman, but I had since reversed everything. The fact that others reported the same issue makes me think it’s not related.
It shouldn’t be related to remote desktop (though weird things happen, of course). It could have worked with freshly installed Fedora, but then brake after some updates – Linux kernel or Network Manager or some other ones.
You can boot your computer from the Fedora Live USB, try to connect to wireless and see if it works ok or you have the same problems.
Are you talking about the link from stackexchange you’ve posted? Actually, it’s quite hard to say, if it’s the same issue or totally different one. )
The MTU issue above accurately describes my problem, I do think it’s the same issue, because of the discrepancy between MTU packet sizes of wifi and ethernet, and the fact that it’s happening on both interfaces, as I and the original post reported.
Did you boot the live image downloaded from getfedora.org? If yes, it contains an “old” kernel and “old” packages too.
To test and confirm that and if it is some regression or behaviour related to an update, you could try a Fedora respin.
Fedora Respins are not the same as Fedora Spins: the latter are different flavours of Fedora with specific desktop environments and configurations. The respin is an image of the current Fedora version containing more updated packages, like Ubuntu point releases. In other words, if you boot a live respi you will have for instance the latest (at the date when the image was built) kernel and other packages as you would have updating an installation performed with the image downloaded from getfedora.org