I have reported the fact that I am having trouble with connecting to my 5ghz wifito bugzilla. Was that the place to report. If not where do I report this problem. I am running Fedora 19 Beta TC2 on Dell 9400 Inspiron with iwl4965 card which handles 2.4ghz and 5ghz bands. I replaced the card and then installed Fedora 18 and it worked fine so that told me it was not my cardbut problem with network manager.
On 05/03/13 07:29, Lawrence Graves wrote:
I have reported the fact that I am having trouble with connecting to my 5ghz wifito bugzilla. Was that the place to report. If not where do I report this problem. I am running Fedora 19 Beta TC2 on Dell 9400 Inspiron with iwl4965 card which handles 2.4ghz and 5ghz bands. I replaced the card and then installed Fedora 18 and it worked fine so that told me it was not my cardbut problem with network manager. -- All things are workable but don't all things work. Prov. 3:5 & 6
Lawrence,
If you replaced the card and then it worked I'm not sure how you can then report that the problem was not the card. Not only did you replace the card but then you also installed Fedora 18, thereby eliminating any chance at that time of knowing if your problem was hardware or software related. Have you tried reinstalling F19 Beta TC2 with the "working" card? Did it work/not work if you did? I'm not saying that it's not NM that's the problem but you need to debug things one step at a time to determine that.
Kevin
On 05/03/2013 07:28 AM, Kevin Martin wrote:
On 05/03/13 07:29, Lawrence Graves wrote:
I have reported the fact that I am having trouble with connecting to my 5ghz wifito bugzilla. Was that the place to report. If not where do I report this problem. I am running Fedora 19 Beta TC2 on Dell 9400 Inspiron with iwl4965 card which handles 2.4ghz and 5ghz bands. I replaced the card and then installed Fedora 18 and it worked fine so that told me it was not my cardbut problem with network manager. -- All things are workable but don't all things work. Prov. 3:5 & 6
Lawrence,
If you replaced the card and then it worked I'm not sure how you can then report that the problem was not the card. Not only did you replace the card but then you also installed Fedora 18, thereby eliminating any chance at that time of knowing if your problem was hardware or software related. Have you tried reinstalling F19 Beta TC2 with the "working" card? Did it work/not work if you did? I'm not saying that it's not NM that's the problem but you need to debug things one step at a time to determine that.
Kevin
I did try re-installing Fedora 19 and found that in fact did not work . I did a lot of debugging before I even mentioned it. I used two different cards to make sure it wasn't my card that was the problem. Both cards are new. I always keep a spare card. I buy a new card every year. I am sorry I mislead you on my initial report but I have exhausted my little know how in trying to fix this problem. I started to replace my Netgear Wndr3700 Dualband router.
On Fri, 3 May 2013, Kevin Martin wrote:
On 05/03/13 07:29, Lawrence Graves wrote:
Lawrence,
If you replaced the card and then it worked I'm not sure how you can then report that the problem was not the card. Not only did you replace the card but then you also installed Fedora 18, thereby eliminating any chance at that time of knowing if your problem was hardware or software related. Have you tried reinstalling F19 Beta TC2 with the "working" card? Did it work/not work if you did? I'm not saying that it's not NM that's the problem but you need to debug things one step at a time to determine that.
Kevin
It may not be the card, but the driver. For some reason, I commonly have wifi problems with new Fedora releases, particularly on a Toshiba laptop I use -- I don't have the machine here and can't remember the NIC, but I think it uses a realtek driver of some sort. I make a report to bugzilla, and it sits there for a couple of months. Eventually I'll get an email saying "we upgraded the kernel -- did that fix it?" and it did. I tend to run Mint in the meantime.
billo
On 05/03/2013 08:14 AM, Bill Oliver wrote:
On Fri, 3 May 2013, Kevin Martin wrote:
On 05/03/13 07:29, Lawrence Graves wrote:
Lawrence,
If you replaced the card and then it worked I'm not sure how you can then report that the problem was not the card. Not only did you replace the card but then you also installed Fedora 18, thereby eliminating any chance at that time of knowing if your problem was hardware or software related. Have you tried reinstalling F19 Beta TC2 with the "working" card? Did it work/not work if you did? I'm not saying that it's not NM that's the problem but you need to debug things one step at a time to determine that.
Kevin
It may not be the card, but the driver. For some reason, I commonly have wifi problems with new Fedora releases, particularly on a Toshiba laptop I use -- I don't have the machine here and can't remember the NIC, but I think it uses a realtek driver of some sort. I make a report to bugzilla, and it sits there for a couple of months. Eventually I'll get an email saying "we upgraded the kernel -- did that fix it?" and it did. I tend to run Mint in the meantime.
billo
I agree with you, I believe it is the drivers too. I assumed it was the network manager because I am able to connect to my 2.4ghz wi-fi. Aren't the same drivers used to connect to 2.4ghz the drivers to connect to 5ghz.
On Fri, 3 May 2013, Lawrence Graves wrote:
On 05/03/2013 08:14 AM, Bill Oliver wrote: I agree with you, I believe it is the drivers too. I assumed it was the network manager because I am able to connect to my 2.4ghz wi-fi. Aren't the same drivers used to connect to 2.4ghz the drivers to connect to 5ghz.
Yeah, I think so. But kernel wackiness can be odd. For instance, on my toshiba with F18, the wireless worked fine *except* with certain Cisco routers. So, I could use it from home where I have an old obsolete Belkin router, and I could use it at Barnes and Nobel, but I it had severe problems at my hospital and at McDonalds -- it found the router and got an ip address and everything was fine for about four minutes, then it started dropping packets and became frozen after about 10 minutes. Of the two or three places it didn't work and I could find out, it was always with a Cisco router. So, when I install a new version of fedora, I throw an old USB Alfa adapter in my computer case and use it instead of the onboard adapterif it blinks out. If I can't fix it, as I said, then I take a break from fedora until it gets fixed in the kernel. This has happened with F16,17, and 18, though I haven't switched that particular box back to 18 from Mint yet.
There comes a point where I just don't have the energy to flog these things, particularly with wifi. I don't have high bandwidth requirements, so keeping a little old usb adapter in my backpack basically takes care of the problem without me spending hours running down blind alleys.
For me, at least, configuration issues and driver/hardware issues tend to act very differently, with the latter being more intermittent and making less sense on first glance (and, of course, resistant to configuration changes).
That's not to say there haven't been issues with using NetworkManager over the years as well...
billo
On 05/03/2013 08:56 AM, Bill Oliver issued this missive:
On Fri, 3 May 2013, Lawrence Graves wrote:
On 05/03/2013 08:14 AM, Bill Oliver wrote: I agree with you, I believe it is the drivers too. I assumed it was the network manager because I am able to connect to my 2.4ghz wi-fi. Aren't the same drivers used to connect to 2.4ghz the drivers to connect to 5ghz.
Yeah, I think so. But kernel wackiness can be odd. For instance, on my toshiba with F18, the wireless worked fine *except* with certain Cisco routers. So, I could use it from home where I have an old obsolete Belkin router, and I could use it at Barnes and Nobel, but I it had severe problems at my hospital and at McDonalds -- it found the router and got an ip address and everything was fine for about four minutes, then it started dropping packets and became frozen after about 10 minutes. Of the two or three places it didn't work and I could find out, it was always with a Cisco router. So, when I install a new version of fedora, I throw an old USB Alfa adapter in my computer case and use it instead of the onboard adapterif it blinks out. If I can't fix it, as I said, then I take a break from fedora until it gets fixed in the kernel. This has happened with F16,17, and 18, though I haven't switched that particular box back to 18 from Mint yet.
It is not uncommon for the routers to have MTUs set to <1500 and that can cause problems--especially if you're using a VPN gateway. Depending on how screwy it is, I often have to use
NAT Traversal Mode cisco-udp
in my vpnc configs. While it is often a driver issue with a given kernel, in these cases it's a router with an MTU <1500 that causes the problem. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Do not taunt the sysadmins, for they are subtle and quick to anger - ----------------------------------------------------------------------
On Fri, 3 May 2013, Rick Stevens wrote:
It is not uncommon for the routers to have MTUs set to <1500 and that can cause problems--especially if you're using a VPN gateway. Depending on how screwy it is, I often have to use
NAT Traversal Mode cisco-udp
in my vpnc configs. While it is often a driver issue with a given kernel, in these cases it's a router with an MTU <1500 that causes the problem.
Hmmm. Never thought of that. I'll put F18 on my toshiba and bring it in on Monday and see if that changes anything. And, yeah, I use a vpn.
Thanks for the tip!
billo
On 05/03/2013 10:01 AM, Bill Oliver issued this missive:
On Fri, 3 May 2013, Rick Stevens wrote:
It is not uncommon for the routers to have MTUs set to <1500 and that can cause problems--especially if you're using a VPN gateway. Depending on how screwy it is, I often have to use
NAT Traversal Mode cisco-udpin my vpnc configs. While it is often a driver issue with a given kernel, in these cases it's a router with an MTU <1500 that causes the problem.
Hmmm. Never thought of that. I'll put F18 on my toshiba and bring it in on Monday and see if that changes anything. And, yeah, I use a vpn.
Thanks for the tip!
Hope it works for you. "Even a blind pig finds the occasional truffle." (the blind pig being me!) ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - They say when you play a Microsoft CD backwards, you'll hear - - Satanic messages, but if you play it forwards, it will install - - Windows...which means Satan is in your system. - ----------------------------------------------------------------------
On Fri, 3 May 2013, Rick Stevens wrote:
Hmmm. Never thought of that. I'll put F18 on my toshiba and bring it in on Monday and see if that changes anything. And, yeah, I use a vpn.
Thanks for the tip!
Hope it works for you. "Even a blind pig finds the occasional truffle." (the blind pig being me!)
Heh. It'll be funny, after all that I wrote about telling the difference between a hardware/driver problem and config problem that this turns out to be a config problem. Doh.
billo
On 05/03/2013 10:17 AM, Bill Oliver issued this missive:
On Fri, 3 May 2013, Rick Stevens wrote:
Hmmm. Never thought of that. I'll put F18 on my toshiba and bring it in on Monday and see if that changes anything. And, yeah, I use a vpn.
Thanks for the tip!
Hope it works for you. "Even a blind pig finds the occasional truffle." (the blind pig being me!)
Heh. It'll be funny, after all that I wrote about telling the difference between a hardware/driver problem and config problem that this turns out to be a config problem. Doh.
Not necessarily. It's sometimes rather difficult to differentiate between a hardware problem, driver issue or something further upstream. You just have to be methodical in analyzing the issue. Often it is out of your control (e.g. not being able to see how a router is configured) and that makes it more difficult.
I can't tell you how many times I've examined logs, run tcpdumps, replaced NIC cards, replaced edge switches, updated kernel drivers, etc. only to find out we had a flaky CAT5 or fiber cable. GRRRRRR!
"Most problems can be solved by careful analysis of the situation, thoughtful planning and rational execution of a plan. But when you're up to your ass in alligators, it's hard to remember your job was to drain the swamp!" ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - It is better to have loved and lost. Cheaper, too! - ----------------------------------------------------------------------
On 05/03/2013 02:10 PM, Rick Stevens wrote:
Not necessarily. It's sometimes rather difficult to differentiate between a hardware problem, driver issue or something further upstream. You just have to be methodical in analyzing the issue. Often it is out of your control (e.g. not being able to see how a router is configured) and that makes it more difficult.
How true. I can well remember when most people would blame hardware first, regardless of the symptoms. Now, many people, even those who should know better, act as though the hardware can't ever be responsible.
-
Joe Zeff -
kevin martin -
Lawrence E Graves -
Rick Stevens -
William Oliver