Prev: Finder disappears...
Next: help: cloning Windows partition - "not enough space"
From: Geoffrey S. Mendelson on 26 Oct 2009 17:39
Amanda Ripanykhazov wrote:
> As to trying to get the 150N to work, I didnt realise that the N
> protocol worked at 5.8 GHz?? And had worse range at that frequency?

It works at both 2.4 and 5.8 (depending upon where you are, 5.8 is illegal
here). It has about 1/4 of the range for the same power output, but much
wider bandwidth.


>I wonder how you change this using DD-WRT? (I have never played around
> with DD-WRT on the 150N. Maybe I should?) In any event, it may be a
> consumer unit, - though it is no Linksys, - and I cant believe that
> the Buffalo can be operationally exhausted by my using it at under a
> watt?

Sure the legal limit is 100mW, it depends upon how close they get to it.
A 1 watt 5.8gHz transmitter is very expensive, so they use one that maxes
out at 100mW, but probably expect you to use it at a lower level.

I could spend hours discussing designing hardware to fit price/performance
specs, but it's not relevant here. Suffice it to say, there is some limit at
which the signal becomes unuseable, and it's very close to the maximum.

Generally, it's about .125 watts if the unit is rated at .100 watts (100mW),
but it could be 100mW if it is normally used at .075 Watts. There are also
issues with antennas, and how resonant they have to be. The higher the power,
the more slight imperfections affect the signal, the transmitter, how much
power it uses and so on.

Geoff.

--
Geoffrey S. Mendelson, Jerusalem, Israel gsm(a)mendelson.com N3OWJ/4X1GM
From: Adam on 27 Oct 2009 03:34
On Oct 26, 8:23 am, Amanda Ripanykhazov <dmanzal...(a)googlemail.com>
wrote:
> changing networks, changing from DHCP to Manual Assign etc etc etc,
> about a dozen tries later, he got the mysterious error message
> Do you want the application "configd" to accept incoming network
> connections
> and
> Do you want the application "mdnsresponder" to accept incoming network
> connections (both of which he allowed, although he had never seen
> those either and said they must be some kind of firewall) and suddenly
> it connected"

You have little snitch installed - Uninstall it. I know you said you
don't, but do yourself a favor, go search your machine for little
snitch right now... Try /Applications for the little snitch
configuration. Or next time one of the those messages pop up, choose a
different option like open preferences or rule list.

From: David Empson on 27 Oct 2009 04:19
Adam <ascinto(a)gmail.com> wrote:

> On Oct 26, 8:23 am, Amanda Ripanykhazov <dmanzal...(a)googlemail.com>
> wrote:
> > changing networks, changing from DHCP to Manual Assign etc etc etc,
> > about a dozen tries later, he got the mysterious error message
> > Do you want the application "configd" to accept incoming network
> > connections
> > and
> > Do you want the application "mdnsresponder" to accept incoming network
> > connections (both of which he allowed, although he had never seen
> > those either and said they must be some kind of firewall) and suddenly
> > it connected"
>
> You have little snitch installed - Uninstall it. I know you said you
> don't, but do yourself a favor, go search your machine for little
> snitch right now... Try /Applications for the little snitch
> configuration. Or next time one of the those messages pop up, choose a
> different option like open preferences or rule list.

Those messages are not from Little Snitch.

Little Snitch alerts for outgoing network connections. The messages
described by the original poster are relating to incoming connections,
not outgoing connections.

They are probably being generated by the firewall which is part of Mac
OS X 10.5 and later. (Sometimes referred to as the "application
firewall", to distinguish it from the port-based firewall which was used
in Mac OS X 10.4 and earlier and is still available in 10.5 if you use
third-party software to configure it.)

If the "Genius" didn't know that, he wasn't trained very well.

I see a similar message as soon as I start the Firewall in System
Preferences > Security, if I have anything running which is not signed
and which is trying to accept incoming network connections.

--
David Empson
dempson(a)actrix.gen.nz
From: Fred Moore on 27 Oct 2009 10:00
In article <slrnhebq44.9s2.gsm(a)cable.mendelson.com>,
"Geoffrey S. Mendelson" <gsm(a)mendelson.com> wrote:

> Fred Moore wrote:
>
> > Go to the Network prefs pane. Select Using BootP from the Configure:
> > popup. Click Apply and see if you can connect. If you do, you can change
> > the Configure selection back to DHCP or whatever. Don't ask me why this
> > works, but it might. BootP forces the issue somehow.
>
> BootP and the incompatible BootParam where two older methods of assigning
> an IP address upon request. Most DHCP servers also support BootP.
>
> DHCP has more features. One of the features of modern DHCP servers is to
> verify an address is unused (ping it) before assigning it so that you can
> have more than one DHCP server running on the network at the same time,
> or a coding error in the control files.

Thanks for the technical details, Geoff. Nice to know there's something
more than voodoo going on. ;)
From: Geoffrey S. Mendelson on 1 Nov 2009 14:09
Amanda Ripanykhazov wrote:
> Got a problem which has stumped Apple so naturally I turned here.

Was this ever resolved?

Geoff.

--
Geoffrey S. Mendelson, Jerusalem, Israel gsm(a)mendelson.com N3OWJ/4X1GM
First  |  Prev  | 
Pages: 1 2 3
Prev: Finder disappears...
Next: help: cloning Windows partition - "not enough space"