Kernel error after configuring new Wireless interface
-
Hello,,
I was trying to add new interface to make Hot Spot in my neighbourhood so I bouth TPLINK w722n (though it will be OK, while it has Atheros Chipset - but sadly i was wrong ; )Today I received TENDA 311U and after conecting to pfsense - yupi ;x there is new run0 interface ;) so i tried to configure new interface… I did everything according to instructions but after applying changes server stucked ;x I rebootet it, but still nothing so i connected monitor and keybord to check what`s wrong,,, and what i saw is that the whole configuration is missing, it was asking me to assign all the interfaces from the beginning :( uff, good i made backup yesterday,,,, after 2 hours of fighting with that ;x (must restored default and only then do the backup ;x ) i tried one more time... and after setting up new interface, i did dhcp on this interface too and then applied interface changes, and one more time, my server stucked ;x but i hadmy monitor connected and i probably have a thing responsible for that :(
After applying there is Fatal Trap ;x
I would be really apreciated for any help ;)
-
I saw crashes like that months ago but not on more recent pfSense 2.0 snapshot builds. What build are you using?
-
Hey, 3 days ago i upgrated from beta4 from november 2010
to
2.0-RC3 (i386)
built on Sun Aug 21 17:58:22 EDT 2011cause i was hope it will help with TPLINK wireless adapter (thought there will be new drivers)
Maybe I should install new fresh pfsense ?
-
As far as I can recall, I have only ever used my Tenda W311U in Access Point mode. What mode are you attempting to use? (I presume you ultimately want to get to AP mode for the hot spot but you may not have set that up yet.)
I saw similar sorts of crashes with the rum driver (controls an earlier Ralink USB WLAN chipset) when it was set into AP or AdHoc modes but not Infrastructure mode. (quite possibly some of these modes don't get as much FreeBSD testing as other modes.)
Do you still have a backup of the configuration file? If so, please post the section for run0 configuration. It should look something like this extract from my config file:```
<opt4><if>run0</if>
<wireless><standard>11g</standard>
<mode>hostap</mode>
<protmode>off</protmode>
<ssid>xxx</ssid>
<channel>6</channel>
<authmode><txpower>99</txpower>
<distance><regdomain><regcountry>AU</regcountry>
<reglocation>indoor</reglocation>
<wpa><macaddr_acl><auth_algs>1</auth_algs>
<wpa_mode>2</wpa_mode>
<wpa_key_mgmt>WPA-PSK</wpa_key_mgmt>
<wpa_pairwise>CCMP</wpa_pairwise>
<wpa_group_rekey>60</wpa_group_rekey>
<wpa_gmk_rekey>3600</wpa_gmk_rekey>
<passphrase>xxx</passphrase>
<ext_wpa_sw><enable></enable></ext_wpa_sw></macaddr_acl></wpa>
<auth_server_addr><auth_server_port><auth_server_shared_secret></auth_server_shared_secret></auth_server_port></auth_server_addr></regdomain></distance></authmode></wireless>
<enable><spoofmac><ipaddr>xxx</ipaddr>
<subnet>24</subnet></spoofmac></enable></opt4>(I have masked some of the irrelevant information, you should do similarly.)
-
Hey, i
ve tried to configute it as AP or Ad-hoc. And according to the backup ;x i don
t have one with this wireless interaface… I have one without and im restoring it to get my server works without it usb adapter ;x cause i
m unable to run this with it :( -
OK, please try configuring it in Infrastructure mode to see if that makes a difference.
And next time you get a similar looking crash please type bt at the db> prompt and post the output here.
-
-
I just upgraded from a snapshot build of around 20 Jul to 2.0-RC3 (i386) built on Fri Aug 26 18:54:18 EDT 2011 and my run interface works fine in AP mode. I won't be able to attempt to reproduce the crash you are seeing for another day or two.
If you haven't tried this already I suggest you configure interface completely (presumably as AP) and save (but not apply) then backup the configuration file and reboot with run adapter plugged in. Does the system crash on or soon after startup?
I'd also be interested to see the run0 section of the configuration file I suggested you backup for comparison with the similar section out of my configuration file (section posted in an earlier reply).
-
Hey ;) I did as you said => configuration without applying and backup and here my settings:
<opt2><if>run0</if>
<wireless><standard>11b</standard>
<mode>adhoc</mode>
<protmode>off</protmode>
<ssid>DELTA_HOT_SPOT</ssid>
<channel>0</channel>
<authmode><txpower>99</txpower>
<distance><regdomain><regcountry>PL</regcountry>
<reglocation>outdoor</reglocation>
<wpa><macaddr_acl><auth_algs>1</auth_algs>
<wpa_mode>1</wpa_mode>
<wpa_key_mgmt>WPA-PSK</wpa_key_mgmt>
<wpa_pairwise>CCMP TKIP</wpa_pairwise>
<wpa_group_rekey>60</wpa_group_rekey>
<wpa_gmk_rekey>3600</wpa_gmk_rekey>
<passphrase><ext_wpa_sw></ext_wpa_sw></passphrase></macaddr_acl></wpa>
<auth_server_addr><auth_server_port><auth_server_shared_secret><apbridge><enable></enable></apbridge></auth_server_shared_secret></auth_server_port></auth_server_addr></regdomain></distance></authmode></wireless>
<enable><ipaddr>192.168.10.1</ipaddr>
<subnet>24</subnet>
<spoofmac></spoofmac></enable></opt2>should I run it in Ad-hoc (<mode>adhoc</mode>) cause i see you have APmode (<mode>hostap</mode>) ??
I had this crash on both, but which should be better ? anyway, i
m trying to reboot, i
ll see what`s going on now ;xAfter reboot =>
During startup there were error that system couldn load the firmware for this Wireless adapter, and then the same problem ;x Interface configuration mismatched and one more time i must restore my system to default and restore the configuration :(
-
During startup there were error that system couldn load the firmware for this Wireless adapter, and then the same problem
You need to edit pfSense file /boot/loader.conf.local (create it if it doesn't already exist) to include the line
runfw_load="YES"
so the boot loader will load the firmware so the driver can find it during system startup.
should I run it in Ad-hoc (<mode>adhoc</mode>) cause i see you have APmode (<mode>hostap</mode>) ??
If you want to use the adapter as a hot spot you almost certainly want to run it in AP mode rather than ad-hoc or Infrastructure.
-
OK, I`ll try after work, but now I have a question because im not sure what mode i need…. I was thinking about setting up new DHCP server - different network and joint them two that they can see each other but after authorisation in CP or wireless key (WEP,WPA). I know i can do that in ADHOC :> or it is in ap ? Or then it works like on my basic ethernet interface, clients get ip from my basic pool of addresses ?
And one more thing ;x I get error after applying, when the firmware is loaded,,, and then configuration is lost ;x what when i automaticly load firmware,, then after rebot i still will be receiving this error probably :( I think its not the solution ;x
I have 40 ppl connected to this server and recovery takes at least 30 minutes, and i tried 5 times,,, so maybe better solution to put fresh copy of newest pfsense ?
-
Sorry I have taken so long to get back to this.
I was thinking about setting up new DHCP server - different network and joint them two that they can see each other but after authorisation in CP or wireless key (WEP,WPA). I know i can do that in ADHOC :> or it is in ap ?
DHCP needs to happen BEFORE CP authorisation (since CP authorisation implies an IP address). I'm not sure what you are asking in ADHOC vs ap.
Or then it works like on my basic ethernet interface, clients get ip from my basic pool of addresses ?
How are you planning to connect this mix of systems? bridge interfaces in pfSense?
And one more thing ;x I get error after applying, when the firmware is loaded,,, and then configuration is lost ;x what when i automaticly load firmware,, then after rebot i still will be receiving this error probably :( I think its not the solution ;x
What error? the kernel panic at ieee80211_getcapinfo+0x80?
Do you then remove your USB WLAN NIC so its not present when the system restarts after the panic?I have 40 ppl connected to this server and recovery takes at least 30 minutes, and i tried 5 times,,, so maybe better solution to put fresh copy of newest pfsense ?
Have you tried configuring the NIC in AP mode with the same parameters that work for me?
I disabled my run0 interface from pfSense GUI, rebooted then typed the following in a pfSense console session```
ifconfig wlan create wlandev run0 wlanmode adhoc bssid
wlan1
ifconfig wlan1 up ssid bree
So on pfSense snapshot build _2.0-RC3 (i386) built on Fri Aug 26 18:54:18 EDT 2011_ my system panics just like yours if I attempt to configure my Tenda W311U in adhoc mode but works just fine if I configure my Tenda W311U in Access Point mode and my system didn't panic within seven minutes of me configuring my Tenda W311U in Infrastructure mode. Does your system panic when the Tenda W311U is configured with the parameters I gave earlier in the extract from the pfSense configuration file?