Skip navigation

Lion WiFi Connection Problem

666369 Views 2,659 Replies Latest reply: Apr 6, 2014 5:02 PM by rilihong RSS
  • renzofromroma Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 5, 2013 11:01 AM (in response to gphonei)

    So the airport express is using it's ethernet/wan port to provide you a wireless network through the ISP provide wi-max router using a wired connection to that router?

     

    yes that is exactly my configuration

     

    It has to have a "default" route that is provided either manually, by you configuring it

     

    I didn't do anything manually on the router nor in the airport express

     

    or in the DHCP response from the Wi-Max router to your airport express over the "wire"

     

    I don't know what a response is and where to look for it

     

    Are you sure there isn't another wireless network, with the same name and parameters as yours that you are connecting to by mistake?

     

    I can see other 5 networks around me none of them have my name

     

    this is my netstat -rn I don't understand anything about it. The only thing I can tell is that my router ip address is 192.168.1.1, all the others 192.x.x.x that you see are my other devices currently on. Also I don't know what is the internet6 that came out from my netstat which I don't see in your listing.

    After the netstat command I'm also copying the wi-fi information if that could be of any help to understand, my interface is en1 and my network name is mandrake; even if it's in italian I think can understand everything.

     

    Anyway, I confirm that the connection is still working well. No slow-down, no drops so far.

     

    netstat -rn

    Routing tables

     

    Internet:

    Destination        Gateway            Flags        Refs      Use   Netif Expire

    default            192.168.1.1        UGSc           68        0     en1

    127                127.0.0.1          UCS             0        0     lo0

    127.0.0.1          127.0.0.1          UH              4       56     lo0

    169.254            link#5             UCS             0        0     en1

    192.168.1          link#5             UCS             5        0     en1

    192.168.1.1        4:c0:6f:fb:20:60   UHLWIir        69       75     en1   1185

    192.168.1.2        127.0.0.1          UHS             0        0     lo0

    192.168.1.3        70:56:81:83:f6:fc  UHLWIi          0        0     en1   1177

    192.168.1.4        8c:fa:ba:92:7:6a   UHLWIi          0        0     en1    103

    192.168.1.5        70:56:81:83:f6:fc  UHLWIi          0        0     en1    753

    192.168.1.6        70:56:81:83:f6:fc  UHLWIi          0        0     en1    921

     

    Internet6:

    Destination                             Gateway                         Flags         Netif Expire

    ::1                                     link#1                          UHL             lo0

    fe80::%lo0/64                           fe80::1%lo0                     UcI             lo0

    fe80::1%lo0                             link#1                          UHLI            lo0

    fe80::%en1/64                           link#5                          UCI             en1

    fe80::5e96:9dff:fe77:558f%en1           5c:96:9d:77:55:8f               UHLI            lo0

    ff01::%lo0/32                           fe80::1%lo0                     UmCI            lo0

    ff01::%en1/32                           link#5                          UmCI            en1

    ff02::%lo0/32                           fe80::1%lo0                     UmCI            lo0

    ff02::%en1/32                           link#5                          UmCI            en1

    ff02::fb%en1                            link#5                          UHmW3I          en1   3557

     

     

     

    Versioni software:

      CoreWLAN:    3.0.1 (301.12)

      CoreWLANKit:    2.0 (200.10)

      Menu extra:    8.0 (800.7)

      plugin configd:    8.3 (830.18)

      Informazioni di sistema:    8.0 (800.1)

      Famiglia IO80211:    5.1 (510.4)

      Diagnostica Wi-Fi:    1.1 (110.26)

      Utility AirPort:    6.1 (610.31)

      Interfacce:

    en1:

      Tipo di scheda:    AirPort Extreme  (0x14E4, 0xF5)

      Versione firmware:    Broadcom BCM43xx 1.0 (5.106.98.100.14)

      Indirizzo MAC:    5c:96:9d:77:55:8f

      Locale:    ETSI

      Codice paese:    IT

      Modalità PHY supportate:    802.11 a/b/g/n

      Canali supportati:    1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 36, 40, 44, 48, 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140

      Wake On Wireless:    Supportato

      AirDrop:    Supportato

      Stato:    Connesso

      Informazioni network attuale:

    mandrake:

      Modalità PHY:    802.11n

      BSSID:    70:56:81:83:f6:fd

      Canale:    36,1

      Codice paese:    IT

      Tipo network:    Infrastruttura

      Sicurezza:    WPA2 Personal

      Segnale/disturbo:    -56 dBm / -88 dBm

      Velocità di trasmissione:    300

      Indice MCS:    15

      Altri network Wi-Fi locali:

    Afrus-Saude:

      Modalità PHY:    802.11n

      BSSID:    58:6d:8f:18:7e:40

      Canale:    1,+1

      Tipo network:    Infrastruttura

      Sicurezza:    WPA2 Personal

      Segnale/disturbo:    -89 dBm / -90 dBm

    CLA-FRA:

      Modalità PHY:    802.11n

      BSSID:    f8:d1:11:50:2c:2c

      Canale:    4,+1

      Tipo network:    Infrastruttura

      Sicurezza:    WPA2 Personal

      Segnale/disturbo:    -56 dBm / -90 dBm

    HOME:

      Modalità PHY:    802.11g

      BSSID:    30:87:30:c5:ee:63

      Canale:    6

      Codice paese:    US

      Tipo network:    Infrastruttura

      Sicurezza:    WPA2 Personal

      Segnale/disturbo:    -84 dBm / -88 dBm

    linksys_SES_32876:

      Modalità PHY:    802.11g

      BSSID:    00:90:4c:91:00:01

      Canale:    11

      Tipo network:    Infrastruttura

      Sicurezza:    WPA Personal

      Segnale/disturbo:    -83 dBm / -81 dBm

  • gphonei Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 5, 2013 6:58 PM (in response to renzofromroma)

    renzofromroma wrote:

     

    Internet:

    Destination        Gateway            Flags        Refs      Use   Netif Expire

    default            192.168.1.1        UGSc           68        0     en1

    This shows that your computer has the correct gateway information

    192.168.1.2        127.0.0.1          UHS             0        0     lo0

    This shows that your computer's network address is correct.

     

    So this looks reasonable.  Where did you see the 169.254.X.Y address at? 

  • renzofromroma Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 6, 2013 9:35 AM (in response to gphonei)

     

    So this looks reasonable.  Where did you see the 169.254.X.Y address at? 

    it is address of the airport express

    Schermata 2013-02-06 alle 18.23.44.png

    now, just after I took this screenshot the airport disappered from the airport-utility-screen, it says that it doesn't belong to my network. Maybe it will reappear again later on. Mean time, Internet is still working very well. Infact I'm sending this mail right now.

  • gphonei Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 6, 2013 11:23 AM (in response to renzofromroma)

    renzofromroma wrote:

     

     

    So this looks reasonable.  Where did you see the 169.254.X.Y address at? 

    it is address of the airport express

    Schermata 2013-02-06 alle 18.23.44.png

    now, just after I took this screenshot the airport disappered from the airport-utility-screen, it says that it doesn't belong to my network. Maybe it will reappear again later on. Mean time, Internet is still working very well. Infact I'm sending this mail right now.

    Okay, so the airport express is showing that it thinks the router is also 192.168.1.1.  This looks like the airport express is in bridge mode, so that it just provides the ethernet to WiFi connectivity, and your ISP provided router is still doing the DHCP business.   Indirizzo IPv4 indicates that the router hasn't received an address from your ISPs router.  It seems that you are in the "create a network" with "bridge" mode and this is how things are working for you.  That's an okay configuration, and is one of the ways to attach a/another WiFi radio to your wired network and not introduce a "double NAT" configuration where the routers are  "stacked", and each providing a different private network.

  • renzofromroma Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 7, 2013 12:33 AM (in response to gphonei)

    confirmed, I am in " create network" and "bridge" mode. The strange is that when the airport gets the correct IP (usually 192.168.1.2), the connection starts failing. Who knows what the difference is!!!!!

  • gphonei Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 7, 2013 8:35 PM (in response to renzofromroma)

    renzofromroma wrote:

     

    confirmed, I am in " create network" and "bridge" mode. The strange is that when the airport gets the correct IP (usually 192.168.1.2), the connection starts failing. Who knows what the difference is!!!!!

    Only one device can have the address 192.168.1.2 at a time.  Is your computer set to use DHCP or did you give it an address manually?  When the airport express is 192.168.1.2, what address does your computer have?

  • renzofromroma Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 7, 2013 11:50 PM (in response to gphonei)

    all devices use DHCP and all have different IP, the assignment depends on "first come first served".

  • gphonei Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 8, 2013 7:32 AM (in response to renzofromroma)

    renzofromroma wrote:

     

    all devices use DHCP and all have different IP, the assignment depends on "first come first served".

    Okay.  In the configuration you have, the IP address of the airport express is only useful when you need to do admin activities on it.  The "airport utility" can find it, no matter what it's address.  In you ISP router, there should be a range of addresses that are allocated for use by DHCP.  If that range is something like 2 to 100, then you might try giving your airport express a fixed address using something above 100; e.g. 192.168.1.101.  That would let you at least discover if there is something awry with DHCP allocations that might cause your computer and the airport express to be confused about who has what address.

  • renzofromroma Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 9, 2013 12:17 PM (in response to gphonei)

    ok, I did it. Let's see now if it will be stable.

  • renzofromroma Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 10, 2013 7:16 AM (in response to renzofromroma)

    nothing to do, wi-fi on mountain-lion and standard configuration simply doesn't work. Today after the lunch time All devices couldn't reconnect because the provider router has been disconnected. I had to go into the router as admin, disconnect it and reconnect it again in order to have internet back. This is what I'm doing since one year and a half. .... now I have to wait until airport express gets a wrong ip number again to have the network working again, this has been the only configuration that was stable for more then two weeks. Manually I cannot put that 169.254.x.x into airport express because it doesn't accept it, maybe I have to play with the router and airport unplugging, re-plugging until express gets that wrong ip again.

  • gphonei Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 10, 2013 7:41 AM (in response to renzofromroma)

    renzofromroma wrote:

     

    nothing to do, wi-fi on mountain-lion and standard configuration simply doesn't work. Today after the lunch time All devices couldn't reconnect because the provider router has been disconnected. I had to go into the router as admin, disconnect it and reconnect it again in order to have internet back. This is what I'm doing since one year and a half. .... now I have to wait until airport express gets a wrong ip number again to have the network working again, this has been the only configuration that was stable for more then two weeks. Manually I cannot put that 169.254.x.x into airport express because it doesn't accept it, maybe I have to play with the router and airport unplugging, re-plugging until express gets that wrong ip again.

    I just saw an airport utility update come in.  If you have that visible to you, install it to see if there is a bug fix there.

  • renzofromroma Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 10, 2013 8:03 AM (in response to gphonei)

    I did it the other day. There no fix as there is no fix for wi.fi since lion.  I would like to know and understand what apple engineers and commercials think about all this s... it seems to me that they only care to steal our money.

  • gphonei Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 10, 2013 8:24 AM (in response to renzofromroma)

    renzofromroma wrote:

     

    I did it the other day. There no fix as there is no fix for wi.fi since lion.  I would like to know and understand what apple engineers and commercials think about all this s... it seems to me that they only care to steal our money.

    I believe that you are on mountain lion, correct?  Hold down the "Option" key, and click on your "airport" icon in the top right corner of the screen.  At the bottom of the menu which will pop up, you will find an "Open Wi-Fi Diagnostics..." selection.  Select that, and then pick the "Turn on Debug Logs" option and click Continue.  Open the "Basic Logs" tree and select DHCP and "Wi-Fi Logging".  At the bottom of that pane, check the check box and then select "Notify me when the Wi-Fi interface [Disconnects from the network]".

     

    Click continue, and try to connect to Wi-Fi and see what happens.  The generated logging information should allow you to see what is failing.

  • renzofromroma Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 10, 2013 9:59 AM (in response to gphonei)

    Yes, mountain lion. should I keep it on until wi-fi fails? How long that log can be?

  • gphonei Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 12, 2013 8:03 AM (in response to renzofromroma)

    renzofromroma wrote:

     

    Yes, mountain lion. should I keep it on until wi-fi fails? How long that log can be?

    Yes, leave it on until WiFi fails so that we might see what error Mountain Lion detected which caused the connection to "break".

Actions

More Like This

  • Retrieving data ...

Bookmarked By (79)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.