I want to install the wireless card, but the pfsense collapse…



  • Hi All,

    I want to install the wireless card, but the pfsense collapse…  :'(

    i reinstall the pfsense many times...i only use default config is fail too, the following is my install step,

    1, In webUI, assign Opt1 to ath0.
    2, In Opt1 config area, "Enable Interface", set the SSID and chose "Ad-hoc (IBSS)" as the mode.
    3, "Save" and then "Apply Changes"

    and then well show this error message, can't to do anything, only reboot...reboot..reboot...

    
    Welcome to pfSense 2.0.1-RELEASE  ...
    
    Creating symlinks......done.
    External config loader 1.0 is now starting... ad0s3
    Launching the init system... done.
    Initializing............................ done.
    Starting device manager (devd)...done.
    Loading configuration......done.
    Updating configuration...done.
    Cleaning backup cache........done.
    Setting up extended sysctls...done.
    Setting timezone...done.
    Starting Secure Shell Services...done.
    Setting up polling defaults...done.
    Setting up interfacre0: link state changed to DOWN
    es microcode...done.
    Configuring LAGG interfaces...done.
    Configuring VLAN interfaces...done.
    Configuring QinQ interfaces...done.
    Configuring WAN interface...starting pppoe0 link...done.
    Configuring LAN interface...re1: link state changed to DOWN
    done.
    Configuring WLAN interface...wlnagn00::  cchhaanngginign name gt on 'aatmhe0_ wtloa n1''
    pppoe0'
    done.
    Syncing OpenVPN settings...done.
    Starting syslog...done.
    Configuring firewall......done.
    Starting PFLOG...done.
    Setting up gateway monitors...done.
    Synchronizing user settings...
    
    Fatal trap 12: page fault while in kernel mode
    cpuid = 1; apic id = 01
    fault virtual address   = 0xffff
    fault code              = supervisor read, page not present
    instruction pointer     = 0x20:0xc0a0fd50
    stack pointer           = 0x28:0xed537bac
    frame pointer           = 0x28:0xed537bb8
    code segment            = base 0x0, limit 0xfffff, type 0x1b
                            = DPL 0, pres 1, def32 1, gran 1
    processor eflags        = interrupt enabled, resume, IOPL = 0
    current process         = 0 (ath0 taskq)
    trap number             = 12
    panic: page fault
    cpuid = 1
    Uptime: 19s
    Cannot dump. Device not defined or unavailable.
    Automatic reboot in 15 seconds - press a key on the console to abort
    --> Press a key on the console to reboot,
    --> or switch off the system now.
    panic: bufwrite: buffer is not busy???
    cpuid = 1
    
    

    this spec for my pfsense:
    intel atom d525
    kingstron ddr3 1333 4G
    kingstron 8G cf card
    atheros AR5B91 b/g/n mPCI-e

    pfsense version:
    pfSense-2.0.1-RELEASE-4g-i386-nanobsd.img.gz 07-Jan-2012

    attachment is the full logs.

    please help me , thanks a lots!!!@@
    pfsense_wifi.txt



  • The log doesn't provide conclusive evidence that the problem is related to the wireless interface.

    I suggest you remove the wireless interface and see if the pfSense system boots cleanly. It will almost certainly prompt you for the interfaces assignment because one of the previous interfaces is missing. If it boots cleanly then change the configuration to disable the wireless interface, shutdown, restore the wireless interface and reboot. Does it then boot cleanly?

    I suspect pfSense wireless interfaces are much more commonly run in Access Point mode or Infrastructure mode than Ad-hoc mode so I would be inclined to try to enable the wireless interface in Access Point mode (first) or Infrastructure mode and see if that rectifies the problem. You are probably more likely to find bugs in less frequently used sections of code.



  • Hi, thx for your replay.

    I sure the system boots is cleanly, but choose ad-hoc mode is collapse too…

    and i try to use Infrastructure mode, it can save and config, but the state is show "no carrier", and the clients can't find the wifi...

    @wallabybob:

    The log doesn't provide conclusive evidence that the problem is related to the wireless interface.

    I suggest you remove the wireless interface and see if the pfSense system boots cleanly. It will almost certainly prompt you for the interfaces assignment because one of the previous interfaces is missing. If it boots cleanly then change the configuration to disable the wireless interface, shutdown, restore the wireless interface and reboot. Does it then boot cleanly?

    I suspect pfSense wireless interfaces are much more commonly run in Access Point mode or Infrastructure mode than Ad-hoc mode so I would be inclined to try to enable the wireless interface in Access Point mode (first) or Infrastructure mode and see if that rectifies the problem. You are probably more likely to find bugs in less frequently used sections of code.



  • @juliet.sljf:

    and i try to use Infrastructure mode, it can save and config, but the state is show "no carrier", and the clients can't find the wifi…

    If you have multiple WiFi clients wanting to associate with pfSense WiFi then the pfSense WiFi interface needs to operate in Access Point mode.


Locked