In/Out errors :(

nima.m · May 10, 2006, 9:56 PM

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.

pcatiprodotnet · May 10, 2006, 10:39 PM

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>

nima.m · May 10, 2006, 10:35 PM

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

pcatiprodotnet · May 10, 2006, 10:50 PM

It's still unchanged. -Pete

pcatiprodotnet · May 13, 2006, 3:59 PM

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

lsf · May 13, 2006, 6:33 AM

This is not something we controll, it's controlled by the freebsd driver/HAL. One of the reasons i haven't added these settings are just because of that. What should be defaults ? should I first up the card and enable it, and then allow the values to be changed ? if not, how should i get the defaults ? (the defaults "change" based on what settings it found "sensible" when the interface was up'ed and configured).
Basically what i'm trying to say is that the driver does not behave the same on every HW combo/user setup. So it's hard to pick any default. I know the driver does not do this perfectly, but it probably does a better job then us presetting/hardcoding this.

nima.m · May 13, 2006, 10:07 AM

@pcatiprodotnet:

Is there a way to simply run a shell script after pfsense finishes booting? If so, I could put the sysctl commands there.

Thats what shellcmd tag do,

Lets try this
1.Change your config file in this way :
<shellcmd>echo 1 > /beforeShell;sysctl dev.ath.0.rxantenna=1;sysctl dev.ath.0.txantenna=1;sysctl dev.ath.0.diversity=0;echo 1 > /afterShell</shellcmd>
<afterfilterchangeshellcmd>echo 1 > /beforeFilter;sysctl dev.ath.0.rxantenna=1;sysctl dev.ath.0.txantenna=1;sysctl dev.ath.0.diversity=0;echo 1 > /afterFilter;</afterfilterchangeshellcmd>

2.Reboot

3.SSH to your router

4.Run this command one by one and see the result :

ls /beforeShell
ls /afterShell
ls /beforeFilter
ls /afterFilter

pcatiprodotnet · May 14, 2006, 8:33 PM

After some investigation, I discovered that boot commands are working; however, after a little time, the old settings get put back. I'm not quite sure what to make of this. Perhaps with Diversity is On, the wireless card is changing the Rx antenna setting based on what it thinks is best at the moment?

Another handy command: athstats

Although information is sparse, it appears that for tx/rxantenna setting: 0=auto, 1=antenna1, 2=antenna2.

-Pete

billm · May 14, 2006, 1:36 PM

@pcatiprodotnet:

After some investigation, I discovered that boot commands are working; however, after a little time, the old settings get put back. I'm not quite sure what to make of this.
-Pete

Yeah, I believe some of that is the ATH driver. It's annoying. FWIW, I have a machine with two antenna's attached and I constantly get errors - it doesn't seem to impact the performance of the unit, so I've just learned to ignore it.

–Bill

lsf · May 16, 2006, 10:20 PM

@pcatiprodotnet:

Although information is sparse, it appears that for tx/rxantenna setting: 0=auto, 1=antenna1, 2=antenna2.

To be honest i haven't checked this in a while, so it might have changed in the ath driver, however madwifi also seems to have what I stated earlier, and it used to be the defautls of the HAL.
So this might be some weirdness with athstats as well (i'll check this out later)
BTW: both=auto

If diversity is on then it should change antennas whenever it needs to (autosense), however if diversity is off then it should stick to what you set it to. And diversity should not turn on again unless you change the interface settings or up/down the interface.

rneily · May 18, 2006, 3:03 AM

Another question.. If I enable TPC via sysctl commands, it seems to turn on both antennas, and diversity. Does TPC require the use of two antennas? I have searched on this, but I cant find anything? (I'm using a CM9)

lsf · May 19, 2006, 12:39 AM

That really depends on the implemetation, to be honest I'm not sure how this is controlled in sams HAL.
Normally it should not require diversity and/or two antennas.

rneily · May 20, 2006, 4:16 AM

Nevermind. I got it working, I was using the wrong antenna connector on the card. On the Cm9, the main port is the one nearest the corner of the card. What I didnt know was that this was antenna 1, not 0… Everything is good with TCP now.

pcatiprodotnet · May 27, 2006, 2:18 AM

It seems the pfSense default antenna settings are great as is (for Atheros).
I just tested this at extreme range (pfSense default is Transmit=Auto and Receive=Diversity).
No matter which antenna port I plugged the antenna into, I got a stable connection with zero ping loss.
I also tested using antenna port #1 with a directional antenna for backhaul and port #2 with an omni for re-transmittion, worked great; it was very good at determining which antenna to use. So, from now on, I'm just going to leave the antenna settings alone. The current defaults work great.

One thing I noticed though, no matter how I setup antennas, on every unit I get enormous FIFO Overrun Errors, even when they're not in use, but it still works fine; is this normal? (fyi, I'm using EMP-8602, ad-hoc mode, odfm cts/rts protection, olsr, on wrap.2c if that matters)
-pc

billm · May 28, 2006, 2:33 PM

Heh, 3x more input errors than packets ;) It all works well (it seems), so I dunno. I kinda don't really care much as long as it works though. I'll have to poke at the driver code and see events increase Ierrs.

$ netstat -ni -I ath0
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
ath0 1500 <link#1>00:0b:6b:4d:58:10 3348424 9424614 3895234 99 0
ath0 1500 fe80:1::20b:6 fe80:1::20b:6bff: 0 - 4 - -
ath0 1500 192.168.255 192.168.255.254 247 - 0 - -</link#1>

btrafela · Jan 8, 2007, 3:06 PM

is this problem solved?

because I have a lot of In errors and wirreless speed is very low. when i ping host it's fine, but when i have load (like http), then
in errors are increasing and i am loosing ping packets.

I have tried all setting above (onl 11b, mixed mode, sysctl settings) but nothing is better

I have atheros 5212 wireless card and 1.0.1 Embended image

regards

pabloamitelo · Feb 16, 2007, 8:42 AM

@btrafela:

is this problem solved?

because I have a lot of In errors and wirreless speed is very low. when i ping host it's fine, but when i have load (like http), then
in errors are increasing and i am loosing ping packets.

I have tried all setting above (onl 11b, mixed mode, sysctl settings) but nothing is better

I have atheros 5212 wireless card and 1.0.1 Embended image

regards

I have one wireless link point to point. One pfsense is configured in access point mode, and the other in infrastructure. The distance between them is 10km with line of sight. The equiment works in 5 Ghz (atheros 5213) and the received signal is very good. I don't have interferences with others networks in the same band. My hardware is wrap 2c and minipci atheros ubiquiti. I have low capacity (6mb) in transmition and 54mb in reception, many "in errors" and 0 "out errors". I have tested different parameters: dev.aht.0.txantenna=1,… rxantenna=1, diversity=0. I have configured dev.ath.0.tpc=0, tpscale=0 and tpack=tpcts=63

My ifconfig -v:

ath0: flags=8843 <up,broadcast,running,simplex,multicast>mtu 1500
inet6 fe80::215:6dff:fe53:a06a%ath0 prefixlen 64 scopeid 0x1
inet _________ netmask 0xffffff00 broadcast ______________
ether 00:15:6d:53:a0:6a
media: IEEE 802.11 Wireless Ethernet autoselect mode 11a (OFDM/6Mbps)
status: associated
ssid channel 140 (5700) bssid 00:15:6d:53:25:14
authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF
powersavesleep 100 txpowmax 36 txpower 63 rtsthreshold 2346
mcastrate 1 fragthreshold 2346 -pureg protmode OFF -wme burst
roaming AUTO bintval 100

I don't have packet loss. What could be the problem?</up,broadcast,running,simplex,multicast>

baskin · May 18, 2007, 11:16 AM

I'm not opening a new topic because this problem has been discussed here.

I have edit /cf/conf/config.xml and added the following

<shellcmd>sysctl dev.ath.0.rxantenna=1;sysctl dev.ath.0.txantenna=1;sysctl dev.ath.0.diversity=0</shellcmd>
<shellcmd>sysctl dev.ath.1.rxantenna=1;sysctl dev.ath.1.txantenna=1;sysctl dev.ath.1.diversity=0</shellcmd>
<afterfilterchangeshellcmd>sysctl dev.ath.1.rxantenna=1;sysctl dev.ath.1.txantenna=1;sysctl dev.ath.1.diversity=0;sysctl dev.ath.0.rxantenna=1; sysctl dev.ath.0.txantenna=1;sysctl dev.ath.0.diversity=0</afterfilterchangeshellcmd>

Everything works after reboot, but as soon as i change something in the web interface (for example the channel or the power) the diversity goes to on (diversity=1). tx and rx antenna stays untouched.

Any ideas;

redonisc · Jun 30, 2007, 11:37 PM

I've errors on my wireless interface too, also i noticed this:

sysctl dev.ath.0.rxantenna

dev.ath.0.rxantenna: 1

sysctl dev.ath.0.rxantenna

dev.ath.0.rxantenna: 1

sysctl dev.ath.0.rxantenna

dev.ath.0.rxantenna: 2

sysctl dev.ath.0.rxantenna

dev.ath.0.rxantenna: 2

Is this right, some bug? this is changing without doing anything….

Thanks for your comments

werneman · Oct 14, 2007, 11:24 AM

Hello all,I have got still problems with ath0(In/Out errors and low RX rate). I use CM9 over reduction mini-PCI to PCI and antenna number 1.
Do you know where can be mistake please in conf. files? Thank .Ladislav

–-----------------------------------------------------------------------------------------------------
Interface status

WLAN_1 interface (ath0)
Status associated
DHCP down
MAC address 00:0b:6b:4e:40:b5
Media autoselect mode 11g <hostap>Channel 4
SSID LadaWerneman3
In/out packets 7582/9931 (1.17 MB/9.38 MB)
In/out errors 217898/5
Collisions 0
Bridge (bridge0) learning

sysctl dev.ath.0

dev.ath.0.%desc: Atheros 5212
dev.ath.0.%driver: ath
dev.ath.0.%location: slot=13 function=0
dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x185f subdevice=0x1012 class=0x020000
dev.ath.0.%parent: pci1
dev.ath.0.smoothing_rate: 95
dev.ath.0.sample_rate: 10
dev.ath.0.countrycode: 0
dev.ath.0.regdomain: 0
dev.ath.0.slottime: 9
dev.ath.0.acktimeout: 29
dev.ath.0.ctstimeout: 29
dev.ath.0.softled: 0
dev.ath.0.ledpin: 0
dev.ath.0.ledon: 0
dev.ath.0.ledidle: 2700
dev.ath.0.txantenna: 1
dev.ath.0.rxantenna: 1
dev.ath.0.diversity: 0
dev.ath.0.txintrperiod: 5
dev.ath.0.diag: 0
dev.ath.0.tpscale: 0
dev.ath.0.tpc: 0
dev.ath.0.tpack: 63
dev.ath.0.tpcts: 63
dev.ath.0.rfsilent: 1
dev.ath.0.rfkill: 1
dev.ath.0.monpass: 24

==========================================================================================

Here is my /cf/conf/config.xml

<pfsense><version>2.9</version>
<lastchange><theme>pfsense</theme>
<system><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>
<optimization>normal</optimization>
<hostname>pfsense</hostname>
<domain>local</domain>
<username>admin</username>
<password>$1$4XzahCD4$ISqQQcMiFDFI0Zpy9T0x/1</password>
<timezone>Etc/UTC</timezone>
<time-update-interval><timeservers>pool.ntp.org</timeservers>
<webgui><protocol>http</protocol>
<port><certificate><private-key></private-key></certificate></port></webgui>
<disablenatreflection>yes</disablenatreflection>
<ssh><authorizedkeys></authorizedkeys></ssh>
<enablesshd>yes</enablesshd>
<enableserial><maximumstates><shapertype><dnsallowoverride></dnsallowoverride></shapertype></maximumstates></enableserial></time-update-interval></system>
<interfaces><lan><if>fxp0</if>
<ipaddr>192.168.1.1</ipaddr>
<subnet>24</subnet>
<media><mediaopt><bandwidth>100</bandwidth>
<bandwidthtype>Mb</bandwidthtype></mediaopt></media></lan>
<wan><if>fxp1</if>
<mtu>1500</mtu>
<blockpriv><media><mediaopt><bandwidth>100</bandwidth>
<bandwidthtype>Mb</bandwidthtype>
<disableftpproxy><ipaddr>dhcp</ipaddr>
<dhcphostname><spoofmac></spoofmac></dhcphostname></disableftpproxy></mediaopt></media></blockpriv></wan>
<opt1><if>ath0</if>
<wireless><standard>11g</standard>
<mode>hostap</mode>
<protmode>rtscts</protmode>
<ssid>LadaWerneman3</ssid>
<channel>4</channel>
<authmode></authmode>
<txpower>99</txpower>
<distance>1200</distance>
<wpa><macaddr_acl></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></wpa>
<wep><enable><key><value>nhknnnk</value></key></enable></wep>
<apbridge><enable></enable></apbridge></wireless>
<descr>WLAN_1</descr>
<bridge>lan</bridge>
<enable><ipaddr>dhcp</ipaddr>
<subnet>32</subnet>
<gateway><spoofmac><mtu><disableftpproxy><dhcphostname></dhcphostname></disableftpproxy></mtu></spoofmac></gateway></enable></opt1></interfaces>
<staticroutes><pppoe><username><password></password></username></pppoe>
<pptp><username><password><local></local></password></username></pptp>
<bigpond><dyndns><type>dyndns</type>
<username><password></password></username></dyndns>
<dhcpd><lan><enable><range><from>192.168.1.100</from>
<to>192.168.1.199</to></range></enable></lan></dhcpd>
<pptpd><mode><redir><localip></localip></redir></mode></pptpd>
<ovpn><dnsmasq><enable></enable></dnsmasq>
<snmpd><syslocation><syscontact><rocommunity>public</rocommunity></syscontact></syslocation></snmpd>
<diag><ipv6nat></ipv6nat></diag>
<bridge><syslog><nat><ipsecpassthru><enable></enable></ipsecpassthru></nat>
<filter><rule><type>pass</type>
<interface>opt1</interface>
<max-src-nodes><max-src-states><statetimeout><statetype>keep state</statetype>
<os><nosync><source>
<network>opt1</network>

<destination><any></any></destination>
<log><descr><gateway>opt1</gateway></descr></log></nosync></os></statetimeout></max-src-states></max-src-nodes></rule>
<rule><type>pass</type>
<descr>Default LAN -> any</descr>
<interface>lan</interface>
<source>
<network>lan</network>

<destination><any></any></destination></rule></filter>
<shaper><ipsec><preferredoldsa></preferredoldsa></ipsec>
<aliases><proxyarp><cron><minute>0</minute>
<hour></hour>
<mday></mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/usr/bin/nice -n20 newsyslog
<minute>1,31</minute>
<hour>0-5</hour>
<mday></mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/usr/bin/nice -n20 adjkerntz -a
<minute>1</minute>
<hour></hour>
<mday>1</mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/usr/bin/nice -n20 /etc/rc.update_bogons.sh
<minute>/60</minute>
<hour></hour>
<mday></mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout
<minute>1</minute>
<hour>1</hour>
<mday></mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/usr/bin/nice -n20 /etc/rc.dyndns.update
<minute>/60</minute>
<hour></hour>
<mday></mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 virusprot
<minute>/60</minute>
<hour></hour>
<mday></mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/usr/bin/nice -n20 /usr/local/sbin/expiretable -t 3600 snort2c
<minute>/5</minute>
<hour></hour>
<mday></mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/usr/local/bin/checkreload.sh
<minute>/5</minute>
<hour></hour>
<mday></mday>
<month></month>
<wday></wday>
<who>root</who>
<command></command>/etc/ping_hosts.sh
<minute>/140</minute>
<hour></hour>
<mday></mday>
<month></month>
<wday>*</wday>
<who>root</who>
<command></command>/usr/local/sbin/reset_slbd.sh</cron>
<wol><installedpackages><miniupnpd><config><enable><iface_array><download><upload><overridewanip><logpackets><sysuptime><permdefault></permdefault></sysuptime></logpackets></overridewanip></upload></download></iface_array></enable></config></miniupnpd>
<package><name>Dashboard</name>
<descr>Adds pfSense dashboard that will be included with 1.3. This requires 1.2-BETA-2 or newer. WARNING! Cannot be deinstalled.</descr>
<category>System</category>
<config_file>http://www.pfsense.com/packages/config/dashboard/dashboard.xml</config_file>
<version>0.6.1</version>
<status>BETA</status>
<required_version>1.2-BETA-2</required_version>
<configurationfile>dashboard.xml</configurationfile></package>
<package><name>Developers</name>
<descr>Adds developers files such as GCC, etc to pfSense</descr>
<category>System</category>
<config_file>http://www.pfsense.com/packages/config/developers/developers.xml</config_file>
<version>0.1</version>
<status>BETA</status>
<required_version>1.2-BETA-2</required_version>
<configurationfile>developers.xml</configurationfile></package>
<package><name>phpSysInfo</name>
<website>http://phpsysinfo.sourceforge.net/</website>
<descr>PHPSysInfo is a customizable PHP Script that parses /proc, and formats information nicely. It will display information about system facts like Uptime, CPU, Memory, PCI devices, SCSI devices, IDE devices, Network adapters, Disk usage, and more.</descr>
<category>System</category>
<version>2.5.3</version>
<status>Beta</status>
<required_version>1.0</required_version>
<depends_on_package_base_url>http://www.pfsense.com/packages/All</depends_on_package_base_url>
<depends_on_package>mbmon-205_3.tbz</depends_on_package>
<config_file>http://www.pfsense.com/packages/config/phpsysinfo/phpsysinfo.xml</config_file>
<configurationfile>phpsysinfo.xml</configurationfile></package>
<package><name>pfflowd</name>
<website>http://www.mindrot.org/pfflowd.html</website>
<descr>pfflowd converts OpenBSD PF status messages (sent via the pfsync interface) to Cisco NetFlow datagrams. These datagrams may be sent (via UDP) to a host of one's choice. Utilising the OpenBSD stateful packet filter infrastructure means that flow tracking is very fast and accurate.</descr>
<category>Network Management</category>
<config_file>http://www.pfsense.com/packages/config/pfflowd.xml</config_file>
<depends_on_package_base_url>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/All</depends_on_package_base_url>
<depends_on_package>pfflowd-0.6.tbz</depends_on_package>
<version>0.6</version>
<status>Stable</status>
<required_version>1.0</required_version>
<configurationfile>pfflowd.xml</configurationfile>
<maintainer>nick@buraglio.com</maintainer></package>
<package><name>ntop</name>
<website>http://www.ntop.org/</website>
<descr>ntop is a network probe that shows network usage in a way similar to what top does for processes. In interactive mode, it displays the network status on the user's terminal. In Web mode it acts as a Web server, creating an HTML dump of the network status. It sports a NetFlow/sFlow emitter/collector, an HTTP-based client interface for creating ntop-centric monitoring applications, and RRD for persistently storing traffic statistics.</descr>
<category>Network Management</category>
<depends_on_package_base_url>http://www.pfsense.org/packages/All/</depends_on_package_base_url>
<depends_on_package>ntop-3.2_2.tbz</depends_on_package>
<version>3.2_2</version>
<status>BETA</status>
<required_version>1.0</required_version>
<config_file>http://www.pfsense.com/packages/config/ntop.xml</config_file>
<configurationfile>ntop.xml</configurationfile></package>
<package><name>Lightsquid</name>
<descr>High perfomance web proxy Report. Required squid.</descr>
<website>http://lightsquid.sf.net/</website>
<category>Network</category>
<version>1.7.1_1</version>
<maintainer>dv_serg@mail.ru</maintainer>
<depends_on_package_base_url>http://ftp.lv.freebsd.org/pub/FreeBSD/ports/packages/All/</depends_on_package_base_url>
<depends_on_package>lightsquid-1.7.1_1.tbz</depends_on_package>
<status>Beta1</status>
<required_version>1.2</required_version>
<config_file>http://www.pfsense.com/packages/config/lightsquid/lightsquid.xml</config_file>
<configurationfile>lightsquid.xml</configurationfile></package>
<package><name>bandwidthd</name>
<website>http://bandwidthd.sourceforge.net/</website>
<descr>BandwidthD tracks usage of TCP/IP network subnets and builds html files with graphs to display utilization. Charts are built by individual IPs, and by default display utilization over 2 day, 8 day, 40 day, and 400 day periods. Furthermore, each ip address's utilization can be logged out at intervals of 3.3 minutes, 10 minutes, 1 hour or 12 hours in cdf format, or to a backend database server. HTTP, TCP, UDP, ICMP, VPN, and P2P traffic are color coded.</descr>
<category>System</category>
<version>2.0.1.1</version>
<status>BETA</status>
<required_version>1.0</required_version>
<depends_on_package_base_url>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/All/</depends_on_package_base_url>
<depends_on_package>bandwidthd-2.0.1.tbz</depends_on_package>
<config_file>http://www.pfsense.org/packages/config/bandwidthd/bandwidthd.xml</config_file>
<configurationfile>bandwidthd.xml</configurationfile></package>
<package><name>iperf</name>
<website>http://dast.nlanr.net/Projects/Iperf/</website>
<descr>Iperf is a tool for measuring maximum TCP and UDP bandwidth, reminiscent of ttcp and nettest. It has been written to overcome the shortcomings of those aging tools. Iperf can also test UDP bandwidth, loss, and jitter.</descr>
<category>Network Management</category>
<config_file>http://www.pfsense.com/packages/config/iperf.xml</config_file>
<depends_on_package_base_url>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6-stable/All</depends_on_package_base_url>
<depends_on_package>iperf-2.0.2_1.tbz</depends_on_package>
<version>2.0.2_1</version>
<status>ALPHA</status>
<required_version>1.0</required_version>
<configurationfile>iperf.xml</configurationfile></package>
<package><name>squid</name>
<descr>High performance web proxy cache.</descr>
<website>http://www.squid-cache.org/</website>
<category>Network</category>
<version>2.6.5_1-p15</version>
<status>BETA</status>
<required_version>1.0</required_version>
<maintainer>fernando@netfilter.com.br seth.mos@xs4all.nl</maintainer>
<depends_on_package_base_url>http://www.pfsense.org/packages/All</depends_on_package_base_url>
<depends_on_package>squid-2.6.5.tbz</depends_on_package>
<depends_on_package>squid_radius_auth-1.0.8.tbz</depends_on_package>
<config_file>http://www.pfsense.org/packages/config/squid/squid.xml</config_file>
<configurationfile>squid.xml</configurationfile></package>
<package><name>darkstat</name>
<website>http://dmr.ath.cx/net/darkstat/</website>
<descr>darkstat is a network statistics gatherer. It's a packet sniffer that runs as a background process on a cable/DSL router, gathers all sorts of statistics about network usage, and serves them over HTTP.</descr>
<category>Network Management</category>
<depends_on_package_base_url>http://www.pfsense.org/packages/All/</depends_on_package_base_url>
<depends_on_package>darkstat-3.0.619.tbz</depends_on_package>
<depends_on_package>gettext-0.14.5_2.tbz</depends_on_package>
<version>3.0.619</version>
<status>Stable</status>
<required_version>1.0</required_version>
<maintainer>geekgod@geekgod.com</maintainer>
<config_file>http://www.pfsense.com/packages/config/darkstat/darkstat.xml</config_file>
<configurationfile>darkstat.xml</configurationfile></package>
<package><name>routed</name>
<descr>RIP v1 and v2 daemon - NOTE: As of 3/18/2007 this package is no longer necessary, it's included in pfSense base and will be removed when 1.0.1 is no longer the current release.</descr>
<website>http://www.pfsense.com/</website>
<maintainer>billm@pfsense.org</maintainer>
<category>Network Management</category>
<version>1.1</version>
<status>Stable</status>
<required_version>1.0</required_version>
<config_file>http://www.pfsense.com/packages/config/routed/routed.xml</config_file>
<configurationfile>routed.xml</configurationfile></package>

<menu>
<name>phpsysinfo</name>
<tooltiptext>Status
<url>/pkg_edit.php?xml=phpsysinfo.xml&id=0</url></tooltiptext> </menu>

<menu>
<name>pfflowd</name>
<tooltiptext>Modify pfflowd settings.</tooltiptext>
Services
<configfile>pfflowd.xml</configfile>
<url>/pkg_edit.php?xml=pfflowd.xml&id=0</url>
</menu>

<menu>
<name>ntop Settings</name>
<tooltiptext>Set ntop settings such as password and port.</tooltiptext>
Diagnostics
<url>/pkg_edit.php?xml=ntop.xml&id=0</url>
</menu>

<menu>
<name>ntop</name>
<tooltiptext>Access ntop</tooltiptext>
Diagnostics
<url>http://$myurl:3000</url>
<depends_on_service>ntop</depends_on_service>
</menu>

<menu>
<name>Proxy report</name>
<tooltiptext>Proxy server statistic report</tooltiptext>
Status
<url>/pkg_edit.php?xml=lightsquid.xml&id=0</url>
</menu>

<menu>
<name>BandwidthD</name>
<tooltiptext>Services
<url>/pkg_edit.php?xml=bandwidthd.xml&id=0</url></tooltiptext> </menu>

<menu>
<name>States New</name>
<tooltiptext>States by Paul Taylor</tooltiptext>
Diagnostics
<url>diag_new_states.php</url>
</menu>

<menu>
<name>iperf</name>
<tooltiptext>Run iperf in client or server mode.</tooltiptext>
Diagnostics
<configfile>iperf.xml</configfile>
</menu>

<menu>
<name>Proxy server</name>
<tooltiptext>Modify the proxy server's settings</tooltiptext>
Services
<url>/pkg_edit.php?xml=squid.xml&id=0</url>
</menu>

<menu>
<name>Darkstat Settings</name>
<tooltiptext>Setup darkstat specific settings</tooltiptext>
Diagnostics
<url>/pkg_edit.php?xml=darkstat.xml&id=0</url>
</menu>

<menu>
<name>RIP</name>
Services
<configfile>routed.xml</configfile>
<url>pkg_edit.php?xml=routed.xml&id=0</url>
</menu>

<phpsysinfo><config><hidepicklist><sensorprogram>on</sensorprogram>
<showmountpoint>on</showmountpoint>
<showinodes>on</showinodes>
<loadbar>on</loadbar>
<showerrors>on</showerrors></hidepicklist></config></phpsysinfo>
<service><name>pfflowd</name>
<rcfile>pfflowd.sh</rcfile>
<executable>pfflowd</executable></service>
<service><name>ntop</name>
<rcfile>ntop.sh</rcfile>
<executable>ntop</executable></service>
<service><name>bandwidthd</name>
<rcfile>bandwidthd.sh</rcfile>
<executable>bandwidthd</executable></service>
<service><name>iperf</name>
<executable>iperf</executable></service>
<service><name>squid</name>
<rcfile>squid.sh</rcfile>
<executable>squid</executable>
<description>Proxy server Service</description></service>
<service><name>darkstat</name>
<rcfile>darkstat.sh</rcfile>
<executable>darkstat</executable></service>
<ntop><config><password>dana</password>
<passwordagain>dana</passwordagain>
<interface_array>opt1</interface_array></config></ntop>
<bandwidthd><config><active_interface>opt1</active_interface>
<skipintervals>2</skipintervals>
<graphcutoff>3</graphcutoff>
<promiscuous>on</promiscuous>
<outputcdf>on</outputcdf>
<recovercdf>on</recovercdf>
<filter><drawgraphs>on</drawgraphs>
<meta_refresh>150</meta_refresh></filter></config></bandwidthd>
<darkstat><config><interface_array>opt1</interface_array></config></darkstat></installedpackages>
<revision><description>/interfaces_opt.php made unknown change</description>
<time>1192184466</time></revision>
<widgets><sequence>system_information-div:col1:show,carp_status-div:col1:close,cpu_graphs-div:col1:close,installed_packages-div:col1:close,interface_statistics-div:col1:show,interfaces-div:col1:show,ipsec-div:col2:close,load_balancer_status-div:col2:close,log-div:col2:close,services_status-div:col2:close,traffic_graphs-div:col2:show</sequence>
<traffic_graphs-config>WAN_graph-config:show,LAN_graph-config:hide,WLAN_1_graph-config:show,refreshInterval=3</traffic_graphs-config></widgets></wol></proxyarp></aliases></shaper></syslog></bridge></ovpn></bigpond></staticroutes></lastchange></pfsense></hostap>