In/Out errors :(
-
Thanks for the help Hoba, using the following command eliminated my in/out error :
sysctl dev.ath.0.rxantenna=1
sysctl dev.ath.0.txantenna=1
sysctl dev.ath.0.diversity=0However, I can't make it work on statup, I put these command inside /etc/sysctl.conf and reboot the router :
dev.ath.0.rxantenna=1
dev.ath.0.txantenna=1
dev.ath.0.diversity=0But after reboot, If I do sysct, It show the old figures.
inside /etc/rc.bootup, I noticed that functions interfaces_wan_configure() interfaces_lan_configure() interfaces_vlan_configure(); are called after system_setup_sysctl()
Can those function overwrite my sysctl command.I also noticed the function system_do_shell_commands() (/* run any shell commands specified in config.xml */)
Where inside config.xml file I can put my shell command ?
Maybe puting my sysctl command there would help. -
Maybe http://pfsense.blogspot.com/2005/06/new-xml-system-tag-introduced.html (another of our hidden xml options: http://faq.pfsense.com/index.php?action=artikel&cat=10&id=38&artlang=en&highlight=hidden ) would be a good option to put it as this then will also be run after you changed wireless settings from the gui. Please try and report back.
Btw, we are working on getting these advanced options in the gui for pfSense 1.1. -
Hoba thank you very much for all help.
I now manage to reduce my In/Out Error to 3 figures instead of 6 figures.
In my configuration, I have only one antenna connected to CM9 card.1. Based on lsf recomendation,the first thing I did was changing my pfsense config trough webGUI to :
Standard = 802.11g
Mode = Access Point
802.11g OFDM Protection Mode = Protection mode RTS and CTS
802.11g only = Check
Transmit power = 20
Channel = Auto
Distance setting = 302. Based on Hobas help, I changed my Antenna configuration trough shell :
sysctl dev.ath.0.rxantenna=1
sysctl dev.ath.0.txantenna=1
sysctl dev.ath.0.diversity=03. Again, based on Hobas Help, I modify my /cf/conf/config.xml :
Find the tag :Change it to :
<shellcmd>sysctl dev.ath.0.rxantenna=1;sysctl dev.ath.0.txantenna=1;sysctl dev.ath.0.diversity=0</shellcmd>4.Reboot
Hoba, maybe you should update WIKI for Wirless and explain how to change sysctl command and put it on startup (Number 2 and 3)
-
Maybe we should hardcode these settings for pfSense 1.0. This way it will work for people regardless if they have 1 antenna or 2 (one of them then would simply not be used though present unless you change the sysctl's). Like written in my earlier post the next pfSense version should have settings for these values at the webgui. Updating the wiki won't hurt. I'll do that later (unless lsf does this before I find the time ;) ).
-
Right now I am using BETA3-PLUS-11548-PLUS-11567
I changed /cf/conf/config.xml from :
To :
<afterfilterchangeshellcmd>sysctl dev.ath.0.rxantenna=1;sysctl dev.ath.0.txantenna=1;sysctl dev.ath.0.diversity=0</afterfilterchangeshellcmd>and save the file.
But when I changed some configuration in WebGui for my WLAN, the <afterfilterchangeshellcmd>inside config.xml had been removed automaticly.</afterfilterchangeshellcmd>
-
Hoba,
I did some more testing and now I fiugre out what should be done.
Whenever, you change the /cf/conf/config.xml file, you need to reboot the router immediately once .So this is how I make it work :
1.Search /cf/conf/config.xml for
Replace it with :
<afterfilterchangeshellcmd>sysctl dev.ath.0.rxantenna=1;sysctl dev.ath.0.txantenna=1;sysctl dev.ath.0.diversity=0</afterfilterchangeshellcmd>2.Reboot
3.Now, Whenever you change config for interfaces inside WebGUI, you don't loose the wirless parameters.
-
You have to remove /tmp/rules.debug as well after changing config.xml as its the cached version and will simply overwrite config.xml on the next filter reload operation.
So technically the reboot is not needed.
-
You have to remove /tmp/rules.debug as well after changing config.xml as its the cached version and will simply overwrite config.xml on the next filter reload operation.
So technically the reboot is not needed.
close… /tmp/config.cache :)
--Bill
-
You have to remove /tmp/rules.debug as well after changing config.xml as its the cached version and will simply overwrite config.xml on the next filter reload operation.
So technically the reboot is not needed.
close… /tmp/config.cache :)
--Bill
Grr. Bill is absolutely right. This head cold is driving me ape shit.
-
My Tx was set to 0, and Rx to 1 (on Atheros).
Is 0 or 1 the First antenna? And, what does it mean when set to "2".
Thank you,
-Pete -
The second time I link to http://forum.pfsense.org/index.php?topic=1149.msg6765#msg6765 in this thread :P
-
Thanks hoba!
Although it's fairly obvious, I was just hoping to see it spelled out in no uncertain terms that 0=Main and 1=Aux.
I was careful to read the card's docs to be sure I put the First pigtail (labeled "Antenna#1") on Main,
and the Second pigtail (labeled "Antenna#2") on Aux. -Pete -
2 means Auto.
What I did was to set both antenna to 0 fisrt and check the in/out errror, then set both to 1 and check the errors again.
Do the same and see when you get less error, then you know which antenna port you should use. -
nima.m, is it possible that you plugged your single pigtail into the card's Aux antenna port, and that is why you had to set it to 1?
-
Thanks hoba!
Although it's fairly obvious, I was just hoping to see it spelled out in no uncertain terms that 0=Main and 1=Aux. -PeteI think that is related to the hardwarelayout. I have even seen cards with no label on either of the antennaoutputs. I recommend doing what nima.m suggested. Try to see what gives you the best results. Generate some traffic (try to load it) and you should see errors increasing rather fast with the wrong setting. Closing the case might help finding the wrong setting too, so you get some noise reflections inside the case with the non hooked up output.
-
I have no idea :-)
I bought one of those Lintex 6 Nic router and told them to install a CM9 minipci and a external antenna and send it to me.
And they did that, And I havn't open my case for checking it. -
I just tried the above procedure on beta4, deleted /tmp/config.cache, rebooted for good measure, and it didn't change.
I loaded up /cf/conf/config.xml , and re-checked it…
<maximumstates><afterfilterchangeshellcmd>sysctl dev.ath.0.rxantenna=0;sysctl dev.ath.0.txantenna=0;sysctl dev.ath.0.diversity=0</afterfilterchangeshellcmd>but in shell it still reports...
sysctl dev.ath.0.diversity
dev.ath.0.diversity: 1
sysctl dev.ath.0.rxantenna
dev.ath.0.rxantenna: 1
sysctl dev.ath.0.txantenna
dev.ath.0.txantenna: 0</maximumstates>
-
Change it to :
<shellcmd>sysctl dev.ath.0.rxantenna=1;sysctl dev.ath.0.txantenna=1;sysctl dev.ath.0.diversity=0</shellcmd>
<afterfilterchangeshellcmd>sysctl dev.ath.0.rxantenna=1;sysctl dev.ath.0.txantenna=1;sysctl dev.ath.0.diversity=0</afterfilterchangeshellcmd>then reboot and check
sysctl dev.ath.0.diversity
-
It's still unchanged. -Pete
-
Is there a way to simply run a shell script after pfsense finishes booting? If so, I could put the sysctl commands there.
This problem with the antennas is causing us quite a bit of hassle.
Also, I wouldn't recommend pfSense pre-determining the antenna settings because people will often attach a single pigtail on the "wrong" mini-pci U.FL connector or transpose two connectors for main/aux. If you must, perhaps setting both Tx & Rx to Auto would be the most generally helpful; but, having the ability to set them in the GUI is golden.
Thank you, -Pete