If you have some source(s), and especially if they provide some background, as to why you need to do specifically this, why it helps, etc. – it could be very useful to other people with the same – or similar but somewhat different – problem if you provide your sources here.
It is possible that the router either does not support this, or its firmware version includes a bug. This info can only be obtained from the router, though (or the maker). If other routers work without disabling 11n, then it’s a router issue rather than a Fedora one.
@FranciscoD Yes I don’t think it’s a Fedora issue, and not the Apple router issue either. It’s an excellent router, I’ve been using it for about 2 years now. And Fedora is a great OS too, I recently moved away from Ubuntu because it had issues, so I had to make this one work. It’s probably the way I have the home network setup. It’s a complex setup so there must’ve been a collision or incompatibility somewhere.
@nightromantic I really have no idea, I tried a lot of things until something worked.
To all whom it may concern, I’ve updated my answer.
I thought the first solution regarding 11n_disable:disable fixed it, but it only seemed so. I’ve since been investigating. It turned out to be a known DoSS virus, infected the new Fedora installation via an open SSH port on the router.
How come you didn’t figure it out if you’re such an expert? I don’t understand people who hang around forums and all they do is talk and criticize, but offer no resolve to any problem. They leave others figure out everything for themselves. You see such folks everywhere nowadays. It’s painful to watch.
Nobody here should be an expert that criticize other people! And people should not read posts in that way.
What I read is that @nightromantic was really surprised that SSH was exposed on the public Internet on port 22 with root access allowed. Because this is a basilar thing to avoid. I don’t read criticism or jeers coming from @nightromantic or anybody else.
All in all it was not clear in any previous post that the host was exposed on internet allowing ssh access on port 22.
If you do that and you look at the logs, you will see the logs flooded by attempts of access from all around the world If you allow root access and your password is weak, it won’t take too long for some intrusion to happen.
I’m no expert, I have some experience – mainly with troubles I’ve encountered myself, some things I’ve read or talked with other people about – that’s all. Basically, I’m exactly the same user as you. I try to help, but I’m absolutely not the oracle or infallible know-it-all. I share what I know and what I think (and when I speculate I clearly say it) – and it helps some people.