The only option I see then, is to teach LinkLiar to do what you do: Turn off your Airport and turn it on again whenever the MAC address changes. I was hoping for a -reconnect flag, but that does not seem to exist. Also, thag flag is listed in the "legacy commands" section of the airport tool, so I should probably not use it. It would only disconnect from the base station. But the -disassociate flag would not force your Airport to reconnect. Now, one thing I thought I would do is to issue a airport -disassociate command (the airport executable is usually located in the directory /System/Library/PrivateFrameworks/amework/Versions/Current/Resources). But cable interfaces tend to "catch themselves" much faster than the Airport does.) (In fact, the same problem that the Airport has applies to all interfaces. I believe there is a popup message that warns you about this behavior the first time you try to modify any MAC address. Only recently a MAC address could be changed on the fly, which is what LinkLiar happily will do. Not long ago, Mac OS prevented any change the MAC address of an Airport that was currrently powered on (just for the mail man reason, I guess). And no letters arriving to your home basically means no Internet. The mail man will be totally confused as to where the building with number 42 went. Changing the MAC address of an Interface is like changing the street number of your house from 42 to 55. At this point it gets stuck infinitely trying to do so. I usually assume that the network has gone down, but eventually my computer will realize that it's not getting any connection to the internet and tries to reconnect. I believe that the Airport MAC address is only reset when actually shutting down your Mac (or does this happen even if you just "log out"?). Do you need to do this? Most people only go to sleep mode or simply log out (which is why nobody reported this issue yet). Ok, first of all - just to think out of the box here for a moment - I'm curious as to why you shut down your Macbook at all. Do you see the same behavior as on log in? Or can it reconnect all by itself now? Again, this is just to verify. This will help us to verify that what happens is what I think happens :) The debug setting is remembered upon reboot.Īnother thing I would like you to test is to change the MAC address of your Airport manually to something else right now. The log messages will appear in the Console app, just along the log messages that you posted. You can do this by simply holding down the option key (or alt depending on your keyboard), while the LinkLiar menu in the top bar is open. I suggest that you turn on debugging in LinkLiar. Your Airport is confused (rightfully so).LinkLiar dutifully changes the MAC address of the Airport.Your Airport connects to a known network.Your Airport interface is powered up as part of the boot process.Sometime after (during?) this point the wifi tries to reconnect but fails to do so: Then this group of messages is repeated 52 times in the Console (from 5:53:56 to 6:02:01). Unfortunately, I am already connected to the network at that point and it will not try to reconnect again for quite a few minutes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |