Netmeas

Network measurement data is currently available by direct database connection. We use a PostgreSQL v8.3.5 database, which may be accessed with the following parameters:

hostname = citysense.net
username = guest
password = citysense

The network measurement data is currently divided up into 3 separate databases, as follows:

database contents
bbn_netmeas data from BBN outdoor nodes
citysense_netmeas data from Harvard outdoor nodes
citymd_netmeas data from Harvard indoor (citymd) nodes

The tables and their schemas are identical in all three databases.

Tables

The full list of public tables are listed here (note that there are a handful of administrative tables that are also present in each database, but the guest account does not have SELECT permission on these tables and they are not listed here).

ifconfig

host base hostname for the node
device interface description
mac_addr mac address of this network interface
if_hostname hostname of this network interface

example:

host device mac_addr if_hostname
citysense001 ath0 12:34:56:78:90 citysense001-mgmt

latest_batch_olsr_vw

This is a view on the olsr table that selects all data from the most recent batch retrieval.

linkloss

from_host sender of packets
to_host receiver of packets
timestamp time of measurement
phy_rate 802.11 phy rate that packets were sent at
recv_perc received-packets / sent-packets ("received" means received on an open socket)
datagram_size number of bytes sent as payload in the UDP datagrams
send_freq_ms duration between packet sends, in milliseconds
capture_perc captured-packets / sent-packets ("captured" means received by libpcap)
avg_rssi_signal average RSSI signal over all captured packets, as reported by the radiotap header
avg_rssi_noise average RSSI noise over all captured packets, as reported by the radiotap header

example:

from_host to_host timestamp phy_rate recv_perc datagram_size send_freq_ms capture_perc avg_rssi_signal avg_rssi_noise
citysense007-exp citysense001-exp 2009-02-25 04:14:40.050653-05 54 0.728 8 30 0.728 -74.54 -96

log

from_host "client" in measurement, if there was one
to_host "server" in measurement, if there was one
timestamp time of measurement or event
message text description of some event (usually an error)

example:

from_host to_host timestamp message
citysense012 citysense011 2009-02-20 00:48:31.40997-05 some error occurred...

olsr

from_host host from which routing data was retrieved
to_host destination host from from_host's routing table
gateway gateway to use when routing to to_host
timestamp time when routing data was retrieved
metric hopcount
etx etx value
interface network interface that olsr is running on
batch if this was a batch fetch (i.e. olsr data pulled from all nodes at the same time), then this field will be the same for all rows that correspond to that batch; otherwise, this field is null

example:

from_host to_host gateway timestamp metric etx interface batch
citysense012 192.168.128.0/20 192.168.144.4 2009-02-25 04:44:18.606717-05 2 2.02 ath1 2009-02-25 04:44:18.596525-05

phyrate

from_host the host that we are measuring the phyrate of
mac_addr destination mac address
timestamp time of measurement
phy_rate the phy rate that was used by from_host to send to mac_addr
fraction of ALL of the packets sent by from_host to mac_addr, what fraction used phy_rate
count of ALL of the packets sent by from_host to mac_addr, how many used phy_rate

example:

from_host mac_addr timestamp phy_rate fraction count
citysense007-exp 00:1d:d9:52:3b:a5 2009-02-25 04:15:00.778066-05 5.5 0.618487 368

ping

from_host ping source
to_host ping destination
timestamp time of measurement
packetloss what percent of pings were lost
min_rtt minimum round-trip time across all successful pings
avg_rtt average round-trip time across all successful pings
max_rtt maximum round-trip time across all successful pings
stddev_rtt standard deviation of round-trip times across all successful pings

example:

from_host to_host timestamp packetloss min_rtt avg_rtt max_rtt stddev_rtt
citysense007-exp citysense001-exp 2009-02-25 04:20:36.384595-05 0 0.799 12.564 36.856 13.117

rpcstats

from_host rpc client
to_host rpc server
start_time time when this series block of stats started
end_time time when this block of stats ended
result "successful" or a description of the error if the rpc failed
errno C errno if the rpc failed, or 0 if it succeeded
count how many time when rpcs were performed between from_host and to_host that had the specified result

example:

from_host to_host start_time end_time result errno count
citysense.net citysense007 2009-02-24 22:13:01.617842-05 2009-02-25 04:34:01.747621-05 Connection reset by peer 54 2

tcp_throughput_kbps

from_host tcp client
to_host tcp server
value average throughput, in Kbit per second
timestamp start of measurement
duration duration of measurement

example:

from_host to_host value timestamp duration
citysense007-exp citysense001-exp 7602 2009-02-25 04:19:14.633835-05 10

udp_throughput_kbps

from_host udp client
to_host udp server
value average throughput, in Kbit per second
timestamp start of measurement
duration duration of measurement
packet_loss packet loss as experienced by from_host
target_bw offered load on the client side (since UDP does not throttle)

example:

from_host to_host value timestamp duration packet_loss target_bw
citysense007-exp citysense001-exp 4849 2009-02-25 04:20:20.516646-05 10 0.081 5