[ previous ] [ next ] [ threads ]
 From:  rgreiner <mrgreiner at gmail dot com>
 To:  Jean Everson Martina <everson at inf dot ufsc dot br>, Monowall Support List <m0n0wall at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall] Mac OS problem with Monowall
 Date:  Fri, 06 Feb 2009 10:41:30 -0200

sorry for bringing this topic back, but where did you get this
information about the Mac OS X drivers?

Thank you,


Jean Everson Martina wrote:
> Is this problem of yours just with wifi connections, or does it happen
> on wired network as well?
> If it is just with a wifi connection, welcome to the club :)
> Appleââ¬Â²s Mac OS X wifi drivers are the worst implemented drivers
> ever. I discovered a flaw (misinterpretation of a standard) in my
> macbook driver 4 months ago. They simply suppose your wifi station
> implements 802.11d, and if not, they just keep guessing specific
> country frequencies, not letting you specify this. The outcome is
> basically the same you reported.
> I took my macbook 5 times to apple store, and they said they changed
> the wifi card twice (but always the same brand/model). The solution
> was to change to a 802.11d enabled router. I reported the problem, but
> in this case we have the worst of the two world. The OS is as closed
> as windows and as complex as any unix. Even knowing the problem and
> being able to correct it, apple doesn't let me do it.
> Then comes the question to m0n0wall people: Does monowall broadcast
> 802.11d information on the wifi frame?
> Jean
> Ps.: Be careful with Apple! ( I usually say it is like diarrhoea: 
> different shape but the same old sh**)
> On 16 Dec 2008, at 15:40, rgreiner wrote:
>> Hi,
>> I'm having a problem with our MacBook users behind Monowall.
>> We are using Monowall 1.235, DHCP is done by an independent FreeBSD 6.1
>> box. The DHCP is working properly and all user stations are receiving
>> addresses.
>> For some reason, the MacBooks are not able to navigate in the Web (I
>> didn't try non-MacBook Macintosh stations, because there is none
>> available here). The captive portal, when it opens at all, takes a hell
>> of a long time (>1 min.)
>> Strange part: A not logged in MacBook manages to ping our DNS outside
>> the Monowall network. A Windows station, not logged, can't (which would
>> be the proper reaction).
>> Traceroute from the MacBook gets almost no answer, no matter what the
>> target (outside the Monowall network). When an answer appears, it
>> indicates a time of >1500ms (and that's for the monowall box itself).
>> Windows stations in the same situation get responses in the area of 1-5
>> ms. Even weirder, the ping mentioned above, when the MacBook isn't
>> connected, get fast times (1-5ms). Traceroute in exactly the same
>> situation, same target, gets no answer at all. I'm not familiar with
>> Macintosh (we have only a couple of users in the campus) and I do not
>> know what other tools I should try for a diagnosis. I'm completely lost
>> and baffled. Could someone give some ideas of what could be going on, or
>> how I should proceed for a diagnosis?
>> Tks,
>> Roberto

                Marcos Roberto Greiner

   Os otimistas acham que estamos no melhor dos mundos
    Os pessimistas tem medo de que isto seja verdade