From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: Willy Tarreau <w@1wt.eu>, Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org,
Steven Noonan <steven@uplinklabs.net>,
Dave Jones <davej@redhat.com>
Subject: Re: ath9k microwave anomaly
Date: Sat, 03 Jan 2009 12:15:26 -0800 [thread overview]
Message-ID: <495FC75E.3090403@gmail.com> (raw)
In-Reply-To: <20090103195115.GA31855@vanheusden.com>
Folkert van Heusden wrote:
>>> BTW, having any WiFi stopping working at 30 feet around a microwave oven
>>> makes me think that beast is leaking like mad. I've already ran experiences
>>> with mine in the past, and it could only slightly perturbate the traffic
>>> within one meter (3 ft) which I already considered huge. You may want to
>>> try to put some aluminium foil on the front door, it is possible that the
>>> protection grid is damaged or not properly sealed.
>>>
>>>
>> great!!
>> (should I build a cement barrier?);
>> I had timeouts like this with the wireless phone
>> (then went out a bought an encrypted phone for this purpose);
>>
>
> Since a few months my wifi connections dropped during the day and sometimes
> at nights well. So I took my laptop with the WiSpy dongle and went for a
> walk in the neighbourhood. Found out that outside there's fresh air that
> feels really good to your nose and also that one of my neighbours has a
> wireless security camera which he occasionally switches on during the day.
> (weblog entry: http://vanheusden.com/misc/blog/2008-12-11-wifi.php ).
>
>
>> now the microwave is causing the same issue.(silently though);
>> like what I had mentioned, the microwave causes this when
>> it's cold started, making wonder if the waves are better handled
>> when the metal or grate is warm as opposed to cold.
>> (molecules are jumping around as opposed to moving around);
>> in any case as long as that microwave isn't active the internet
>> connection seems O.K.(knock on wood);
>>
>
> There are devices with which you can measure the leakage of a micro-
> wave (which should not be more than 50 watt per m^2 on a distance of
> 5 cm; read that at http://members.lycos.nl/return/mgnetron.htm ).
> Iirc conrad.nl has these.
>
>
> Folkert van Heusden
>
>
That device looks interesting.
looked at the article, just one problem
I suck at reading german, or speaking the
language. although I would love to checkout
oldenbourg or ingostadt one of these days.
regards;
Justin P. Mattock
next prev parent reply other threads:[~2009-01-03 20:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 2:47 ath9k microwave anomaly Justin P. Mattock
2009-01-03 3:21 ` Dave Jones
2009-01-03 3:31 ` Justin P. Mattock
2009-01-03 3:48 ` Dave Jones
2009-01-07 16:45 ` Pavel Machek
2009-01-03 3:49 ` Steven Noonan
2009-01-03 3:59 ` Justin P. Mattock
2009-01-03 4:48 ` Robert Hancock
2009-01-03 7:30 ` Willy Tarreau
2009-01-03 8:11 ` Justin P. Mattock
2009-01-03 19:51 ` Folkert van Heusden
2009-01-03 20:15 ` Justin P. Mattock [this message]
2009-01-03 20:20 ` Folkert van Heusden
2009-01-03 20:58 ` Justin P. Mattock
2009-01-03 21:26 ` Bastien ROUCARIES
2009-01-03 22:52 ` Justin P. Mattock
2009-01-03 14:15 ` Bastien ROUCARIES
2009-01-03 16:52 ` Justin P. Mattock
2009-01-03 13:49 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=495FC75E.3090403@gmail.com \
--to=justinmattock@gmail.com \
--cc=davej@redhat.com \
--cc=folkert@vanheusden.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=steven@uplinklabs.net \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox