Re: [Wing] Wing on Atheros platforms with openwrt

Keep an eye on this page:

http://www.wing-project.org/software:notebook

I will try to explain the most important handlers in the next few days.

A few of them (lt.hosts, lt.routes) should be self explanatory. Remember that
in wing the numeber that follows an IP address is the index of an interface, so:

6.1.2.3:1

refers to the first interface of node 6.1.2.3

R.

Il 10/04/2011 07:21, Ross Wakelin ha scritto:

ok thanks running a build now. What is the meaning of those numbers in the output, is that specified anywhere. There is bound to be the numbers I want in that lot, I just need to identify them.  On 10 April 2011 17:14, Outback Dingo <outbackdingo@gmail.com> wrote: 

Ah right, add src-svn wing http://gforge.create-net.org/svn/openwrt-pkgs/trunk to feeds.conf.default then run ./scripts/feeds update -a then run make menuconfig again :) your using the wing package from the packages tree wing_extra and cinder are in the wing feed only so far On Sun, Apr 10, 2011 at 1:08 AM, Ross Wakelin <ross.wakelin@gmail.com> wrote: 

 Thanks for that  A wing executable does not seem to exist in the openwrt build at the moment, its not listed in the Makefile anywhere.  I had already seen the read/write handler page you mentioned, I was hoping for an explanation of what info it displays back, metrics etc.  Thanks  On 10 April 2011 16:50, Outback Dingo <outbackdingo@gmail.com> wrote: 

Glad its working, ive noticed sometimes ( a while back) that 5Ghz radios for some odd reason needed to be kick started.... ive been using channel 161 with crda for a while now no problems wing status is an executable for the wing packages that displays stats, routes, neighbors similiar the olsr / batmans stats, but in different format http://wing-project.org/software:notebook you can read more on the handlers here. On Sun, Apr 10, 2011 at 12:36 AM, Ross Wakelin <ross.wakelin@gmail.com> wrote: 

 OK, so now its working.  Channel 40 was specified in each nodes config file, so why did I have to specify it manually?  Also what is "wing_status", it is not an executable on these nodes?  What is the best way to determine the "goodness" of a nodes connection?  with batman and olsr you can get a number expressing this.  I use it in a script to set the bullet leds to a pattern that lets me see instantly how good a connection each node has.  Is there something I can get to with read_handler?   On 10 April 2011 16:16, Outback Dingo <outbackdingo@gmail.com> wrote: 

also add in iwconfig output....  On Sun, Apr 10, 2011 at 12:08 AM, Ross Wakelin <ross.wakelin@gmail.com> wrote: 

 Bullet M5HP  uci show  dhcp.@dnsmasq[0]=dnsmasq dhcp.@dnsmasq[0].domainneeded=1 dhcp.@dnsmasq[0].boguspriv=1 dhcp.@dnsmasq[0].filterwin2k=0 dhcp.@dnsmasq[0].localise_queries=1 dhcp.@dnsmasq[0].rebind_protection=1 dhcp.@dnsmasq[0].rebind_localhost=1 dhcp.@dnsmasq[0].local=/lan/ dhcp.@dnsmasq[0].domain=lan dhcp.@dnsmasq[0].expandhosts=1 dhcp.@dnsmasq[0].nonegcache=0 dhcp.@dnsmasq[0].authoritative=1 dhcp.@dnsmasq[0].readethers=1 dhcp.@dnsmasq[0].leasefile=/tmp/dhcp.leases dhcp.@dnsmasq[0].resolvfile=/tmp/resolv.conf.auto dhcp.lan=dhcp dhcp.lan.interface=lan dhcp.lan.start=100 dhcp.lan.limit=150 dhcp.lan.leasetime=12h dhcp.lan.ignore=0 dhcp.wan=dhcp dhcp.wan.interface=wan dhcp.wan.ignore=1 dropbear.@dropbear[0]=dropbear dropbear.@dropbear[0].PasswordAuth=on dropbear.@dropbear[0].RootPasswordAuth=on dropbear.@dropbear[0].Port=22 firewall.@defaults[0]=defaults firewall.@defaults[0].syn_flood=1 firewall.@defaults[0].input=ACCEPT firewall.@defaults[0].output=ACCEPT firewall.@defaults[0].forward=REJECT firewall.@zone[0]=zone firewall.@zone[0].name=lan firewall.@zone[0].input=ACCEPT firewall.@zone[0].output=ACCEPT firewall.@zone[0].forward=ACCEPT firewall.@zone[0].network=lan firewall.@zone[1]=zone firewall.@zone[1].name=wan firewall.@zone[1].input=REJECT firewall.@zone[1].output=ACCEPT firewall.@zone[1].forward=REJECT firewall.@zone[1].masq=1 firewall.@zone[1].mtu_fix=1 firewall.@zone[1].network=wan firewall.@rule[0]=rule firewall.@rule[0].src=wan firewall.@rule[0].proto=udp firewall.@rule[0].dest_port=68 firewall.@rule[0].target=ACCEPT firewall.@rule[0].family=ipv4 firewall.@rule[1]=rule firewall.@rule[1].src=wan firewall.@rule[1].proto=icmp firewall.@rule[1].icmp_type=echo-request firewall.@rule[1].target=ACCEPT firewall.@include[0]=include firewall.@include[0].path=/etc/firewall.user firewall.@zone[2]=zone firewall.@zone[2].name=mesh firewall.@zone[2].input=ACCEPT firewall.@zone[2].output=ACCEPT firewall.@zone[2].forward=ACCEPT firewall.@zone[2].network= firewall.@forwarding[0]=forwarding firewall.@forwarding[0].dest=mesh firewall.@forwarding[0].src=lan firewall.@forwarding[1]=forwarding firewall.@forwarding[1].dest=lan firewall.@forwarding[1].src=mesh luci.main=core luci.main.lang=auto luci.main.mediaurlbase=/luci-static/openwrt.org luci.main.resourcebase=/luci-static/resources luci.flash_keep=extern luci.flash_keep.uci=/etc/config/ luci.flash_keep.dropbear=/etc/dropbear/ luci.flash_keep.openvpn=/etc/openvpn/ luci.flash_keep.passwd=/etc/passwd luci.flash_keep.opkg=/etc/opkg.conf luci.flash_keep.firewall=/etc/firewall.user luci.flash_keep.uploads=/lib/uci/upload/ luci.languages=internal luci.languages.en=English luci.sauth=internal luci.sauth.sessionpath=/tmp/luci-sessions luci.sauth.sessiontime=3600 luci.ccache=internal luci.ccache.enable=1 luci.themes=internal luci.themes.OpenWrt=/luci-static/openwrt.org network.loopback=interface network.loopback.ifname=lo network.loopback.proto=static network.loopback.ipaddr=127.0.0.1 network.loopback.netmask=255.0.0.0 network.lan=interface network.lan.ifname=eth0 network.lan.type=bridge network.lan.proto=static network.lan.netmask=255.255.255.0 network.lan.ipaddr=10.1.1.1 network.mesh=interface network.mesh.profile=bulk network.mesh.rc=minstrel network.mesh.ls=fcfs network.mesh.metric=wcett network.mesh.prefix=6 network.mesh.period=10000 network.mesh.tau=100000 network.mesh.debug=true network.mesh.proto=wing ntpclient.@ntpserver[0]=ntpserver ntpclient.@ntpserver[0].hostname=0.openwrt.pool.ntp.org ntpclient.@ntpserver[0].port=123 ntpclient.@ntpserver[1]=ntpserver ntpclient.@ntpserver[1].hostname=1.openwrt.pool.ntp.org ntpclient.@ntpserver[1].port=123 ntpclient.@ntpserver[2]=ntpserver ntpclient.@ntpserver[2].hostname=2.openwrt.pool.ntp.org ntpclient.@ntpserver[2].port=123 ntpclient.@ntpserver[3]=ntpserver ntpclient.@ntpserver[3].hostname=3.openwrt.pool.ntp.org ntpclient.@ntpserver[3].port=123 ntpclient.@ntpdrift[0]=ntpdrift ntpclient.@ntpdrift[0].freq=0 ntpclient.@ntpclient[0]=ntpclient ntpclient.@ntpclient[0].interval=600 system.@system[0]=system system.@system[0].hostname=OpenWrt system.@system[0].timezone=UTC system.@rdate[0]=rdate system.@rdate[0].interface=wan timeserver.@timeserver[0]=timeserver timeserver.@timeserver[0].hostname=ptbtime1.ptb.de timeserver.@timeserver[1]=timeserver timeserver.@timeserver[1].hostname=time-a.nist.gov timeserver.@timeserver[2]=timeserver timeserver.@timeserver[2].hostname=ntp.xs4all.nl timeserver.@timeserver[3]=timeserver timeserver.@timeserver[3].hostname=ptbtime2.ptb.de timeserver.@timeserver[4]=timeserver timeserver.@timeserver[4].hostname=time-b.nist.gov ucitrack.@network[0]=network ucitrack.@network[0].init=network ucitrack.@network[0].affects=dhcp radvd ucitrack.@wireless[0]=wireless ucitrack.@wireless[0].affects=network ucitrack.@firewall[0]=firewall ucitrack.@firewall[0].init=firewall ucitrack.@firewall[0].affects=luci-splash qos miniupnpd ucitrack.@olsr[0]=olsr ucitrack.@olsr[0].init=olsrd ucitrack.@dhcp[0]=dhcp ucitrack.@dhcp[0].init=dnsmasq ucitrack.@dropbear[0]=dropbear ucitrack.@dropbear[0].init=dropbear ucitrack.@httpd[0]=httpd ucitrack.@httpd[0].init=httpd ucitrack.@fstab[0]=fstab ucitrack.@fstab[0].init=fstab ucitrack.@qos[0]=qos ucitrack.@qos[0].init=qos ucitrack.@system[0]=system ucitrack.@system[0].init=led ucitrack.@system[0].affects=luci_statistics ucitrack.@luci_splash[0]=luci_splash ucitrack.@luci_splash[0].init=luci_splash ucitrack.@upnpd[0]=upnpd ucitrack.@upnpd[0].init=miniupnpd ucitrack.@ntpclient[0]=ntpclient ucitrack.@ntpclient[0].init=ntpclient ucitrack.@samba[0]=samba ucitrack.@samba[0].init=samba ucitrack.@tinyproxy[0]=tinyproxy ucitrack.@tinyproxy[0].init=tinyproxy uhttpd.main=uhttpd uhttpd.main.listen_http=0.0.0.0:80 uhttpd.main.listen_https=0.0.0.0:443 uhttpd.main.home=/www uhttpd.main.rfc1918_filter=1 uhttpd.main.cert=/etc/uhttpd.crt uhttpd.main.key=/etc/uhttpd.key uhttpd.main.cgi_prefix=/cgi-bin uhttpd.main.script_timeout=60 uhttpd.main.network_timeout=30 uhttpd.main.tcp_keepalive=1 uhttpd.px5g=cert uhttpd.px5g.days=730 uhttpd.px5g.bits=1024 uhttpd.px5g.country=DE uhttpd.px5g.state=Berlin uhttpd.px5g.location=Berlin uhttpd.px5g.commonname=OpenWrt wireless.phy0=wifi-device wireless.phy0.phy=phy0 wireless.phy0.type=mac80211 wireless.phy0.hwmode=11na wireless.phy0.channel=40 wireless.phy0.country=US wireless.@wifi-iface[0]=wifi-iface wireless.@wifi-iface[0].device=phy0 wireless.@wifi-iface[0].mode=monitor   On 10 April 2011 15:57, Outback Dingo <outbackdingo@gmail.com> wrote: 

this is a Bullet M5 correct ? built on OpenWRT using the ar71xx target for Ubiquiti devices ? Ive got Pico M2s running here fine which is the same image as the Bullet M5s anyway to get access to one of these devices from remote, somethings not right can you paste uci show from the device to me On Sat, Apr 9, 2011 at 11:51 PM, Ross Wakelin <ross.wakelin@gmail.com> wrote: 

 Yep, and even rebooted the boxes   On 10 April 2011 15:38, Outback Dingo <outbackdingo@gmail.com> wrote: 

So your /etc/config/wireless looks exactly like this below ? with nothing else added? and you ran wifi start, then ifup mesh after you changed the configuration config 'wifi-device' 'phy0'         option 'phy' 'phy0'         option 'type' 'mac80211'         option 'channel' '40'         option 'country' 'US'         option 'hwmode' '11na' config 'wifi-iface'         option 'device' 'phy0'         option 'mode' 'monitor'  On Sat, Apr 9, 2011 at 11:25 PM, Ross Wakelin <ross.wakelin@gmail.com> wrote: 

 I have made those changes to the wireless config file, sorry, no change in connection.  I am still seeing the following lines in the system log during the boot up, and they look suspicious to me:  Mar 28 01:49:06 OpenWrt user.info sysinit: ifconfig: SIOCSIFHWADDR: Invalid argument Mar 28 01:49:11 OpenWrt user.info sysinit: ifconfig: SIOCSIFADDR: No such device Mar 28 01:49:11 OpenWrt kern.info kernel: device wing-mesh entered promiscuous mode Mar 28 01:49:11 OpenWrt user.notice ifup: Enabling Router Solicitations on mesh (wing-mesh)  Its almost as if the low level wing/click stack can't get a connect to the wireless device. Is there any more debug I can turn on?    On 10 April 2011 12:25, Outback Dingo <outbackdingo@gmail.com> wrote: 

  On Sat, Apr 9, 2011 at 6:32 PM, Ross Wakelin <ross.wakelin@gmail.com> wrote: 

 Hi,  at this time, ifconfig show no packets transmitted or received on either the wlan0 or the wing-mesh interfaces  As requested, here is the config and debug info...  OpenWrt version trunk 26507 Hardware is Ubiquity Bullet M Kernel 2.6.37.6 kmod-ath9k version 2.6.37.6+2011-04-06-2 kmod-tun version 2.6.37.6-1 wing version 20110329-2  wing-mesh-log: warning: added 2 Align elements expensive Packet::push; have 10 wanted 12 expensive Packet::push; have 10 wanted 12 expensive Packet::push; have 10 wanted 12 expensive Packet::push; have 10 wanted 12 expensive Packet::push; have 10 wanted 12 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29 wr/gw :: WINGGatewaySelector :: start_ad :: hna 10.1.2.0 255.255.255.0 6.92.125.106 seq 29  wing-mesh.click: rates_1 :: AvailableRates(DEFAULT 12 18 24 36 48 72 96 108, 00:15:6D:5C:7D:6A 12 18 24 36 48 72 96 108); channels_1 :: AvailableChannels(DEFAULT 5180 5200 5220 5240 5260 5280 5300 5320, 00:15:6D:5C:7D:6A 5180 5200 5220 5240 5260 5280 5300 5320); dev_1 :: DevInfo(ETH 00:15:6D:5C:7D:6A, IFACE 1, CHANNEL 5200, CHANNELS channels_1, RATES rates_1); lt :: LinkTableMulti(IP 6.92.125.106, IFACES " 1", BETA 80); metric :: WINGETTMetric(LT lt); arp :: ARPTableMulti();  elementclass EtherSplit { input -> cl :: Classifier(6/00156D5C7D6A); cl[0] -> [0] output; }  elementclass LinkStat {    $debug| input -> ps :: PaintSwitch(); es_1 :: WINGLinkStat(IP 6.92.125.106,                                  DEV dev_1,                                  PERIOD 10000,                                  TAU 100000,                                  PROBES "12 60 12 1500 18 1500 24 1500 36 1500 48 1500 72 1500 96 1500 108 1500",                                  ARP arp,                                  LT lt,                                  METRIC metric,                                  DEBUG $debug); ps[0] -> es_1 -> output; }  elementclass WingRouter {  $ip, $nm, $rate, $debug|   outgoing :: SetTXRate($rate)  -> [0] output   es :: LinkStat($debug);   gw :: WINGGatewaySelector(IP $ip,                         PERIOD 15000,                         EXPIRE 30000,                         LT lt,                         ARP arp,                         DEBUG $debug);   track_flows :: WINGTrackFlows();   set_gateway :: WINGSetGateway(SEL gw);   forwarder :: WINGForwarder(IP $ip,                          ARP arp,                          DEBUG $debug);   querier :: WINGQuerier(QUERY_WAIT 5,                         TIME_BEFORE_SWITCH 5,                         IP $ip,                         ARP arp,                         LT lt,                         DEBUG $debug);   query_forwarder :: WINGMetricFlood(IP $ip,                                  LT lt,                                  ARP arp,                                  DEBUG $debug);   query_responder :: WINGQueryResponder(IP $ip,                                     LT lt,                                     ARP arp,                                     DEBUG $debug);   gw_responder ::  WINGGatewayResponder(IP $ip,                                 PERIOD 15000,                                 SEL gw,                                 LT lt,                                 RESPONDER query_responder,                                 DEBUG $debug);   gw -> outgoing; gw_responder -> outgoing; query_responder -> outgoing; query_forwarder -> outgoing;   query_forwarder [1] -> [0] query_responder;   input [1] -> host_cl :: IPClassifier(dst net $ip mask $nm, -) -> querier -> [1] output;   host_cl [1] -> set_gateway -> [0] track_flows [0] -> querier;   forwarder[0]  -> dt ::DecIPTTL  -> [1] output;   dt[1] -> ICMPError($ip, timeexceeded, 0) -> querier;   querier [1] -> [0] query_forwarder; es -> SetTimestamp() -> [0] output;   forwarder[1] // IP packets to me  -> WINGStripHeader()  -> CheckIPHeader(CHECKSUM false)  -> from_gw_cl :: IPClassifier(src net $ip mask $nm, -)  -> [2] output;   from_gw_cl [1] -> [1] track_flows [1] -> [2] output;   input [0]  -> ncl :: Classifier(15/01 , // forwarder                       15/02 , // queries                       15/03 , // replies                       15/04 , // es                       15/05 , // gw                      );    ncl[0] -> forwarder;  ncl[1] -> [1] query_forwarder;  ncl[2] -> [1] query_responder;  ncl[3] -> es;  ncl[4] -> gw;  }  elementclass RateControl {  $rate, $rates|   rate_control :: Minstrel(OFFSET 4, RT $rates);   input -> rate_control -> output;  input [1] -> [1] rate_control [1] -> [1] output;  };  elementclass LinkScheduler {  $lt, $arp|   input -> FullNoteQueue(10) -> output;  };  control :: ControlSocket("TCP", 7777);  err :: WifiDupeFilter()  -> WifiDecap()  -> WINGCheckHeader()  -> WINGRouteResponder(IP 6.92.125.106, LT lt, ARP arp, DEBUG true)  -> Discard();  // has one input and one output // takes and spits out ip packets elementclass LinuxIPHost {    $dev, $ip, $nm|  input -> KernelTun($ip/$nm, MTU 1500, DEVNAME $dev)  -> CheckIPHeader(CHECKSUM false)  -> output; }  elementclass SniffDevice {    $device|  from_dev :: FromDevice($device, PROMISC false, OUTBOUND true, SNIFFER false)  -> output;  input -> to_dev :: ToDevice($device); }  wr :: WingRouter (6.92.125.106, 255.0.0.0, 12, true);  linux_ip_host :: LinuxIPHost(wing-mesh, 6.92.125.106, 255.0.0.0) -> [1] wr;  rc_split :: EtherSplit(); sl_split :: EtherSplit();  wr [0] -> WINGSetHeader() -> sl_split; // queries, replies, bcast_stats wr [1] -> WINGSetHeader() -> rc_split; wr [2] -> linux_ip_host;  sniff_dev_1 :: SniffDevice(wlan0); rc_1 :: RateControl(12, rates_1); ls_1 :: LinkScheduler(lt, arp); outgoing_1 :: PrioSched() -> SetTXPower(POWER 60) -> RadiotapEncap() -> sniff_dev_1;  sl_split[0] -> FullNoteQueue() -> WifiEncap(0x0, 00:00:00:00:00:00) -> [0] outgoing_1; rc_split[0] -> ls_1 -> WifiEncap(0x0, 00:00:00:00:00:00) -> rc_1 -> [1] outgoing_1;  cl :: Classifier(12/06AA) // this protocol's ethertype -> WINGCheckHeader() -> wr;  sniff_dev_1 -> RadiotapDecap -> FilterPhyErr() -> Classifier(0/08%0c) //data -> tx_filter_1 :: FilterTX() -> WifiDupeFilter() -> WifiDecap() -> HostEtherFilter(00:15:6D:5C:7D:6A, DROP_OTHER true, DROP_OWN true) -> Paint(0) -> cl;  tx_filter_1[1] -> [1] rc_1 [1] -> err;  Section of the system log, showing initial startup of the mesh:  Mar 27 02:48:06 OpenWrt user.info sysinit: ifconfig: SIOCSIFHWADDR: Invalid argument Mar 27 02:48:06 OpenWrt user.notice mesh: No raw interfaces available. Exiting. Mar 27 02:48:11 OpenWrt user.info sysinit: ifconfig: SIOCSIFADDR: No such device Mar 27 02:48:11 OpenWrt kern.info kernel: device wing-mesh entered promiscuous mode Mar 27 02:48:12 OpenWrt user.notice ifup: Enabling Router Solicitations on mesh (wing-mes h)  network config file: config 'interface' 'loopback'        option 'ifname' 'lo'        option 'proto' 'static'        option 'ipaddr' '127.0.0.1'        option 'netmask' '255.0.0.0'  config 'interface' 'lan'        option 'ifname' 'eth0'        option 'proto' 'static'        option 'ipaddr' '192.168.1.1'        option 'netmask' '255.255.255.0'  config 'interface' 'mesh'        option 'profile' 'bulk'        option 'rc' 'minstrel'        option 'ls' 'fcfs'        option 'metric' 'wcett'        option 'prefix' '6'        option 'period' '10000'        option 'tau' '100000'        option 'debug' 'true'        option 'proto' 'wing'  wireless config file:  config 'wifi-device' 'radio0'        option 'type' 'mac80211'        option 'macaddr' '00:15:6d:5c:7d:6a'        option 'hwmode' '11na'        option 'htmode' 'HT20'        list 'ht_capab' 'SHORT-GI-40'        list 'ht_capab' 'TX-STBC'        list 'ht_capab' 'RX-STBC1'        list 'ht_capab' 'DSSS_CCK-40'        option 'disabled' '0'        option 'channel' '40'        option 'txpower' '17'        option 'country' 'US'  config 'wifi-iface'        option 'device' 'radio0'        option 'ssid' 'OpenWrt'        option 'network' 'mesh'        option 'mode' 'monitor'   

 This is a Bullet M5 ?  try this config on Both sides for wireless, its what im using  config 'wifi-device' 'phy0'         option 'phy' 'phy0'         option 'type' 'mac80211'         option 'channel' '40'         option 'country' 'US'         option 'hwmode' '11ng' config 'wifi-iface'         option 'device' 'phy0'         option 'mode' 'monitor'    

 On 9 April 2011 20:13, Roberto Riggio <roberto.riggio@create-net.org> wrote: 

Hi,  I need a few more info to pinpoint the problem. Could you provide me with the wireless and network configuration file. Plus I will also need the the wing-mesh.log file and the /tmp/wing-mesh.click file.  If you want to use the latest snapshot you could checkput the wing feed for openwrt:  src-svn wing http://gforge.create-net.org/svn/openwrt-pkgs/trunk  this should be appened to the feed.conf file in the openwrt directory. Also remember to run:  ./script/feed -p wing wing  In order to install the package from the wing feed.  Thanks R.  Il 09/04/2011 02:18, Ross Wakelin ha scritto: 

 Oops, finger trouble.  Anyway, I might be making progress with these devices.  Wing still fails, but in the wing log I now see:   ToDevice(wlan0) send: No such device or address.  and in the wlan0 log I get: wlan0.click.174: While initializing 'linux_ip_host/KernelTun@1 :: KernelTun' : warning: Linux universal tun failed: Invalid argument Router could not be initialized!  So it looks like its trying to bring up the tunnel interface and failing. So again, as I mentioned in the post that did not go to all the list (sorry), what versions/releases are people using that do play happily together?  Thanks   On 9 April 2011 11:46, Paul Adams<paul@pauladamsit.com>  wrote: 

 Hey Ross,  It would seem you sent this message to me only, not to the mailing list.  I'm just starting out - looking for a device to use to learn WING.   I already have a working SMESH network using WRT54GL devices.  Voice works fine but it is limited.  WING seems a much better solution.   Regards  Paul Adams   On Fri, 04/08/2011 at 3:19pm, "Ross Wakelin"<ross.wakelin@gmail.com>  wrote: 

 Hi everyone  I've spent the last two days trying to get wing running on Dir 615, Dir 825 and Ubiquity Bullet devices - all Atheros based. I am building from the latest trunk openwrt code, using the nightly snapshots.  I have not yet succeeded in getting any of these devices to talk to any other device (I have two of each).  The builds complete OK, install ok, and wing seems to configure ok.  Some of the symptoms I am seeing are: no packets ever being sent or received on the wing-mesh interface starting wing, it is killed automatically within two seconds, after generating a 1mb log file and filling up the ram.  In this case, the error message in the log file goes something like: KernelTun: resource not available bringing up the mesh (ifup mesh) and nothing happening - nothing in the kernel or system log files, no mesh log created, nothing.  Several people have mentioned that they have this running, could they please let us know what version of openwrt, kernel, wireless mac80211, wing etc. they have built against. The latest snapshot versions of the mac80211 have the tap patch already installed.  Thanks in advance  Ross  On 9 April 2011 10:06, Paul Adams<paul@pauladamsit.com>  wrote: 

 Hi,  The D-Link DIR-825 has a Atheros AR7161 processor, 8mb flash, 64mb ram.  It is known to run OpenWRT.  It has dual radio - one Atheros AR9223 802.11 b,g,n radio and one Atheros AR9220 a radio.    Bearing in mind the radiotap_rate patch for the ath9k cards - would this device be a good choice for running WING?  It seems very similar to the RouterStation device, except that uses separate radios.    Regards  Paul Adams    On Wed, 04/06/2011 at 6:12am, "Outback Dingo" wrote:  Roberto,  You can add Ubiquiti RousterStation / RouterStation Pro, and pretty much all their M units as they work  and I have at least one of each in the lab loaded and running  On Wed, Apr 6, 2011 at 3:42 AM, Roberto Riggio <roberto.riggio@create-net.org>  wrote: 

 Hi,  I've added a few instruction about how to build wing using the upstream openwrt sources. You can find it here:  http://www.wing-project.org/software:embedded  please let me know if there are enough information to acieve your task.  R.  Il 06/04/2011 01:23, Outback Dingo ha scritto:  On Tue, Apr 5, 2011 at 6:49 PM, Ross Wakelin<ross.wakelin@gmail.com> wrote: 

 Hi Has anyone successfully compiled and run wing on a smaller embedded device? I'm looking to use Dlink DIR-615 as my test bed, and Ubiquity Rocket/Bullet devices for the live network.  Both of these platforms are based on Atheros 9K cards, and things like OLSR, Batman and 802.11s run ok.  I'm running the custom compiles now, but wondered if someone had already done this, and any pitfalls they came up against.  I use OpenWrt trunk code with nightly updates from the svn. 

 been building/loading and testing in the lab for months now, all seems good to go now itll run on those devices fine, we use ubiquiti also, youll need the radiotap_rate patch for the ath9k cards also 

 Thanks  Ross  _______________________________________________ Wing mailing list Wing@create-net-ml.org    http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing 

 _______________________________________________ Wing mailing list Wing@create-net-ml.org    http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing   --   -------------------------------------------------------- Roberto Riggio, Ph.D. CREATE-NET Network&  Security Solutions for Pervasive Computing Systems (iNSPIRE) Senior Researcher Via alla Cascata 56/D - 38123 Povo Trento (Italy) e-mail: roberto.riggio@create-net.org Tel: ( 39) 0461 408400 - interno/extension 708 Fax: ( 39) 0461 421157 www.create-net.org/~rriggio   -------------------------------------------------------- The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited according to the Italian Law 196/2003 of the Legislature. If you received this in error, please contact the sender and delete the material from any computer. Le informazioni contenute in questo messaggio di posta elettronica e nei file allegati sono da considerarsi strettamente riservate. Il loro utilizzo e' consentito esclusivamente al destinatario del messaggio, per le finalita' indicate nel messaggio stesso. Qualora riceveste questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla cancellazione del messaggio stesso dal Vostro sistema. Trattenere il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalita' diverse, costituisce comportamento contrario ai principi dettati dal D. Lgs. 196/2003.  _______________________________________________ Wing mailing list Wing@create-net-ml.org    http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing  

 _______________________________________________ Wing mailing list Wing@create-net-ml.org    http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing  

_______________________________________________ Wing mailing list Wing@create-net-ml.org   http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing 

  -- -------------------------------------------------------- Roberto Riggio, Ph.D. CREATE-NET Network&  Security Solutions for Pervasive Computing Systems (iNSPIRE) Senior Researcher Via alla Cascata 56/D - 38123 Povo Trento (Italy) e-mail: roberto.riggio@create-net.org Tel: (+39) 0461 408400 - interno/extension 708 Fax: (+39) 0461 421157 www.create-net.org/~rriggio --------------------------------------------------------  The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited according to the Italian Law 196/2003 of the Legislature. If you received this in error, please contact the sender and delete the material from any computer.  Le informazioni contenute in questo messaggio di posta elettronica e nei file allegati sono da considerarsi strettamente riservate. Il loro utilizzo e' consentito esclusivamente al destinatario del messaggio, per le finalita' indicate nel messaggio stesso. Qualora riceveste questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla cancellazione del messaggio stesso dal Vostro sistema. Trattenere il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalita' diverse, costituisce comportamento contrario ai principi dettati dal D. Lgs. 196/2003.   _______________________________________________ Wing mailing list Wing@create-net-ml.org  http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing  

 _______________________________________________ Wing mailing list Wing@create-net-ml.org  http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing 

 _______________________________________________ Wing mailing list Wing@create-net-ml.org http://diana.create-net-ml.org/cgi-bin/mailman/listinfo/wing 

--  -------------------------------------------------------- Roberto Riggio, Ph.D. CREATE-NET Network & Security Solutions for Pervasive Computing Systems (iNSPIRE) Senior Researcher Via alla Cascata 56/D - 38123 Povo Trento (Italy) e-mail: roberto.riggio@create-net.org Tel: (+39) 0461 408400 - interno/extension 708 Fax: (+39) 0461 421157 www.create-net.org/~rriggio --------------------------------------------------------  The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited according to  the Italian Law 196/2003 of the Legislature. If you received this in  error, please contact the sender and delete the material from any  computer.  Le informazioni contenute in questo messaggio di posta elettronica e nei file allegati sono da considerarsi strettamente riservate. Il loro  utilizzo e' consentito esclusivamente al destinatario del messaggio, per  le finalita' indicate nel messaggio stesso. Qualora riceveste questo  messaggio senza esserne il destinatario, Vi preghiamo cortesemente di  darcene notizia via e-mail e di procedere alla cancellazione del  messaggio stesso dal Vostro sistema. Trattenere il messaggio stesso,  divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo,  od utilizzarlo per finalita' diverse, costituisce comportamento  contrario ai principi dettati dal D. Lgs. 196/2003.