Marvell 88W8363 AP and Wireless Client not working!



  • Hello!

    Im new on this Forum. First time i had to register and post a issue. I just bought a Marvell 88W8363 mini-pci card (with a generic mini-pci to pci card) , that i foud to be a  Cybertan WM821 http://www.cybertan.com.tw/Products/WM821.htm acording to WikiDev http://www.wikidevi.com/wiki/CyberTAN_WM821-M .
    I buy this card to be a muti client ( acess internet router in other room) and acess point mode to be able to use internet with notebook.
    Have installed and try pfsense 2.0.1; 2.0.2 and beta 2.1 . No matter what, i can only use the client mode (BBS) without WPA (either TKIP and AES) and WEP, only with open autentication. With WPA and WEP its shows associated, but, cant get IP address from DHCP or even if i put a static ip, it does not work. cant ping the router. I even try to ping from router to pfsense it does not work!

    The Acess Point mode does not work, shows the card ready, i can see the wifi network i created but wen i put the password i cant connect, i try the WPA, WEP, and open authentication, and none works. try to associate, and no way that connect, it drops with open auth and with WPA/WEP its ask for password again.

    I tested everything, G mode, N mode, A mode, nothing, the only thing i can make to work is the client mode but only with open autentication.

    Thats very frustrating, i have special request this card based on the pfsense supported cards https://docs.google.com/spreadsheet/ccc?key=0AojFUXcbH0ROdHgwYkFHbkRUdV9hVWljVWl5SXkxbFE&hl=en#gid=0

    Anyone can help me? i dont know what to do. already read all the post and threads on the Forum, and no clue. Im stucked. ???



  • @foxround:

    Hello!

    Im new on this Forum.

    Welcome.

    @foxround:

    The Acess Point mode does not work, shows the card ready, i can see the wifi network i created but wen i put the password i cant connect, i try the WPA, WEP, and open authentication, and none works. try to associate, and no way that connect, it drops with open auth and with WPA/WEP its ask for password again.

    What operating system was the client running? (A few years ago I had a couple of Windows Vista laptops that all of a sudden stopped getting responses from pfSense to WiFi DHCP requests. A registry change seemed to be needed to fix this.)

    What WiFi hardware was the client using? Why didn't you try WPA2?

    What values do the relevant pfSense interface counters have before and after the client attempts to connect? (this will indicate if the pfSense AP is seeing any traffic.) If the client is issuing DHCP requests do you see the requests logged in the pfSense DHCP log?

    Does pfSense Status -> Wireless page show the laptop associated?



  • Hi!

    i thing i got most of the information you ask:

    Im using 3 OS, one notebook/tablet Lenovo x200t with Windows 7 Ultimate and Linux Mint 14, the other notebook is a macbook pro 13'' mid 2010 with SnowLeopard.

    I have tested all authentication (Open, WEP, WPA, WPA2) none work.

    before

    WLAN interface (mwl0_wlan1)
    Status up
    MAC address xx:xx:xx:xx:xx:xx
    IP address 192.168.1.2  
    Subnet mask 255.255.255.0
    Media autoselect mode 11g <hostap>Channel 11
    SSID testerwifi
    In/out packets 0/0 (0 bytes/0 KB)
    In/out packets (pass) 0/0 (0 bytes/0 KB)
    In/out packets (block) 0/0 (0 bytes/0 bytes)
    In/out errors 0/5
    Collisions 0
    Bridge (bridge0) learning

    after

    WLAN interface (mwl0_wlan1)
    Status up
    MAC address xx:xx:xx:xx:xx:xx
    IP address 192.168.1.2  
    Subnet mask 255.255.255.0
    Media autoselect mode 11g <hostap>Channel 11
    SSID testerwifi
    In/out packets 2/0 (656 bytes/9 KB)
    In/out packets (pass) 0/58 (0 bytes/9 KB)
    In/out packets (block) 2/0 (656 bytes/0 bytes)
    In/out errors 0/5
    Collisions 0
    Bridge (bridge0) learning

    Wireless (hostapd) log entries

    Dec 29 14:20:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:21:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:22:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: event 1 notification
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: start authentication
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.1X: unauthorizing port
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/4 msg of 4-Way Handshake
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: received EAPOL-Key frame (2/4 Pairwise)
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 3/4 msg of 4-Way Handshake
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: received EAPOL-Key frame (4/4 Pairwise)
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.1X: authorizing port
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx RADIUS: starting accounting session 50DEF8C2-00000000
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
    Dec 29 14:23:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:23:55 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/2 msg of Group Key Handshake
    Dec 29 14:23:55 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: EAPOL-Key timeout
    Dec 29 14:23:55 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/2 msg of Group Key Handshake
    Dec 29 14:23:56 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: EAPOL-Key timeout
    Dec 29 14:23:56 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/2 msg of Group Key Handshake
    Dec 29 14:23:57 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: EAPOL-Key timeout
    Dec 29 14:23:57 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/2 msg of Group Key Handshake
    Dec 29 14:23:58 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: EAPOL-Key timeout
    Dec 29 14:23:58 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.1X: unauthorizing port
    Dec 29 14:23:58 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
    Dec 29 14:23:58 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deassociated
    Dec 29 14:24:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:25:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:26:55 hostapd: mwl0_wlan1: WPA rekeying GTK

    if i miss something plz tell me what you need, thx for now,

    Forgot to tell that no DHCP for that wifi interface :(

    i turn of the wpa and got the same results on wireless log:

    Dec 29 14:20:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:21:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:22:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: event 1 notification
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: start authentication
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.1X: unauthorizing port
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/4 msg of 4-Way Handshake
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: received EAPOL-Key frame (2/4 Pairwise)
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 3/4 msg of 4-Way Handshake
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx2 WPA: received EAPOL-Key frame (4/4 Pairwise)
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.1X: authorizing port
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx RADIUS: starting accounting session 50DEF8C2-00000000
    Dec 29 14:23:35 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
    Dec 29 14:23:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:23:55 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/2 msg of Group Key Handshake
    Dec 29 14:23:55 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: EAPOL-Key timeout
    Dec 29 14:23:55 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/2 msg of Group Key Handshake
    Dec 29 14:23:56 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: EAPOL-Key timeout
    Dec 29 14:23:56 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/2 msg of Group Key Handshake
    Dec 29 14:23:57 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: EAPOL-Key timeout
    Dec 29 14:23:57 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: sending 1/2 msg of Group Key Handshake
    Dec 29 14:23:58 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx WPA: EAPOL-Key timeout
    Dec 29 14:23:58 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.1X: unauthorizing port
    Dec 29 14:23:58 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request
    Dec 29 14:23:58 hostapd: mwl0_wlan1: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deassociated
    Dec 29 14:24:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:25:55 hostapd: mwl0_wlan1: WPA rekeying GTK
    Dec 29 14:26:55 hostapd: mwl0_wlan1: WPA rekeying GTK</hostap></hostap>



  • I was a bit surprised to see RADIUS mentioned in the hostapd log extracts you posted. Surprised because you hadn't mentioned radius. But maybe the wireless log reports radius even if a radius server hasn't been specified. My pfSense has been up long enough for the startup entries to have long disappeared from the wireless log so I can't compare what my system (which doesn't use RADIUS) reports with your report.

    I suggest you start with a basic WiFi configuration: either client or AP mode (not both) and gradually work up to where you want to be. Say, start with client mode to the router, no encryption. Verify that works. Change to WPA2 encryption (if you really want encryption why bother with anything weaker than WPA2?) and reboot (the reboot might not be necessary but it won't hurt) both systems. Then if you get that configuration working, add to pfSense the interface for the AP (no encryption, very different channel from that used between pfSense and the router) reboot pfSense, check the laptops can connect, check you still have connectivity with the router etc.

    How far apart are the router and pfSense? If they are too close together (for example, separated just by a gyprock wall) they may not appreciate the other system shouting at them! (The wireless receivers might be overloaded by the nearby transmitters.)

    If I recall correctly, jimp has reported using multiple virtual interfaces on a similar device.



  • Sorry, i was in hollidays!

    I have sucess on AP mode. Actually, i only have 2 network cards, one is RJ45 100/1000 and the other is that marvell. I just create a rule to allow me to open the adm gui from wan interface and setup the AP mode with marvel. i had it working with wpa and wpa2 (did not test wep).
    But i reset the pfsense and did the same, but now i create the Client mode and i wasnt sucessfull! it connects (i see the client associated on the wifi router but only 2/2(T/R) packets, and in pfsense shows only a DS/auto 1mpbs on the interface, cant get dhcp, cant ping, etc.. but it shows associated, even on interface status or wireless status.
    Another thing is that wen on AP mode i try to create client mode or another AP mode but, after commit the new settings it disconnect the both interfaces. I just follow your advice and restart the pfsense. Wen i login i see that the first AP mode now changed to second AP mode or client mode Channel. I dont know how to solve this.

    I hope this have a solution otherwise i must forget this (its said that this card is able to do all this things on pfsense docs)

    Thx



  • @foxround:

    but now i create the Client mode and i wasnt sucessfull!

    Do you recall what you did at that step?

    Please post the output of pfSense shell commands```
    ifconfig
    /etc/rc.banner


Locked