PingMesh

Category:Sasecurity
back to http://scratchpad.wikia.com/wiki/Sasecurity
=== Ping the Mesh ===
Try pingplotter http://www.pingplotter.com <http://www.pingplotter.com> 
, with this tool you can send alerts (send an e-mail, play a sound, 
launch an executable...) The tool don't send SMS but in UK you can try 
http://www.kapow.co.uk <http://www.kapow.co.uk> , you generate an 
from pingplotter.
Can anyone suggest a good ping prog for meshboxes. Usual issue. We 
all get node crash and they require a reboot. This is easy, however it 
would be good to know when a node is "dead". The usual progs that sms 
to admin are no good within a mesh for obvious reasons. Ping checkers 
are ok, however I would like to see something that perhaps will sound 
an alarm on a pc if a node goes down!! Any ideas.
How do you avoid this problem you describe? And still have dual radios?
but they draw a lot of power and if you're putting two of those on a single bus you have to consider whether
they'll suffer interference (which I think is very likely)
The only hardware I can really recommend is that which has passed
complete lab and field tests. So far that is the mini-itx based units you see on 
sale in the locustworld shop. I've looked at a number of boards but nothing 
with a better price / performance ratio has ever completed full testing.
Senao cards are generally good, but they draw a lot of power and if
you're putting two of those on a single bus you have to consider whether
they'll suffer interference (which I think is very likely) and whether the bus
can even support the peak drain of the cards, if it can't then it will 
crash and it's likely to do this fairly randomly but generally under higher 
loads.
As for the power over ethernet hookup you describe. I don't know enough 
electrical engineering to really work out whether that would supply
enough power within the tolerances of the particular board to work correctly.
I've tried wherever possible to stick to tried and tested solutions and off
the shelf equiment rather than any home brew stuff. 
I would recommend replacing the unit with a mini-itx based one if 
you're having problems with stability. If you need power over ethernet then 
try a unit similar to the one Joel recently recommend, I believe he's had 
good success with them. If you don't want to do that, then try changing one
of the aspects of the node, such as the radios, the power hookup etc.
> I have been having to downgrade back to dev85.
> Every unit that I upgraded to dev87 has locked up.
>
> I am using the WRAP motherboard first introduced to me Dave Peterson. 
> I have all senao mini-pci 200mw cards. I have 12volt Gel Cell 165amp 
> batteries using 20feet or less of 22guage cat5.
>
>
> My network was running great when it was in 2 halves. 2 weeks ago I 
> put in the perfect node.. It saw both sides of the network with 11meg 
> connections.
>
> Since that time my gateways have crashed twice a day or more. They 
> crash at 4am or 1pm.. Before I had the 3rd gateway in place, if 1 
> gateway crashed the other side would load up and crash within the 
> hour.
>
>
> I will use whatever the best hardware is.. Please point me in the 
> right direction. Help
> You shouldn't have any scalability issues, the system is specifically 
> designed for large meshes and there are plenty of a much bigger 
> scale.
> It sounds more
> like a hardware related problem.
>
> The things I would check first would be whether the unit is 
> overheating, the power supply, insulation from radio interference, 
> wireless firmware etc.
>
> Often its useful to swap out the node with another and see if you 
find
> any differences. If you're not running the latest build try that as 
> well.
> > I have 11 nodes in the mesh with 3 gateways.. Will lowering it to 7 
> > make it not be able to connect to the other 3? How do dual antennas 
> > count? Since I have 11 duals, that shows up as 11 1.x routes and 11 
> > 10.x routes.
> >
> > Now that I have 110 users it is really hard to just test these 
> > settings on them. Since last week when I really connected the whole 
> > mesh togther, I have been having lockups and reboots galore.
> >
> > I thought when the mesh got too big we were supposed to add more 
> > gateways.. I have 3 gateways and 11 nodes .. That is a 4-1 ration. 
> > That should work.
> > Try lowering the # of mesh nodes to use to something like 7 - it 
> > defaults to 20. That should fix it.
> >
> > It's my opinion that a large # of routes being used eats up too 
much
> > of your CPU resources and as such, causes the system to become 
> > unstable.
> >
> > Kenny
> >
> > > how did you get around the 9 or 10 node problem? I have about 15 
> > > nodes
> > >
> > > in my mesh with 3 gateways. 
> > > not a direct answer to your locking up issue but...
> > >
> > >
> > > have you tried setting the mesh watchdog = on function in wiana?
> > >
> > >
> > > I saw these same issues in the past, particularly the "... not 
own
> > > MAC" errors, and found that the mesh watchdog function provide a 
> > > workaround at least.
> > >
> > >
> > > Something else strange in your logs is the reference to "wlan1: 
> > > Could not find STA 00:00:00:00:00:00 for this TX error"
> > >
> > >
> > > Now this looks to me (YMMV etc!) like you might have a rogue 
> > > meshbox
> > >
> > > or client - as no one has an all 00 MAC address - either that or 
a
> > > malfunctioning wifi card perhaps?
> > >
> > >
> > > BTW, how complex and dense is your mesh right now? Once we hit 
the
> > > "9 or 10 nodes able to see each other" mark, then all kinds of 
> > > screwed-up
> > >
> > > routing and lock-out problems arise...
> > >
> > >
> > > this seems to be a basic scaleability problem with MeshAP, though 
> > > it
> > >
> > > might be due in part to the power restrictions that apply in the 
> > > UK which don't apply stateside so again YMMV :)
> > >> Ok I have been having the mesh lock issue for quite some time. I 
> > >> have
> > >> been having my meshpoints ftp me everything I can think of. 
> > >> uptime
> > >> > temp df -H >> temp dmesg -c >> temp cat
> > >> /var/state/dhcp/dhcpd.leases
> > >> >> temp ps -ef >> temp route >> temp iwconfig wlan0 >> temp 
> > >> >> iwlist
> > >> wlan0 scanning >> temp
> > >>
> > >> This is the report I got.. I noticed the 'handle_ap_item' error. 
> > >> I tried to login to see what was up, but I could not SSH in.. 
> > >> pingtest would work, but nno ssh I then watched and in few a 
> > >> minutes the access point went into ( 0% @ 0) and then a few 
> > >> minutes
> > >>
> > >> after that it went dark. Yesterday I saw this same error on 
> > >> another
> > >>
> > >> mesh point, and I was already sshed into the node. So I just 
> > >> issued
> > >>
> > >> a reboot command and all was well. Below is all the info I get 
> > >> from
> > >>
> > >> the
> > >>
> > >> mesh point .. Hope it helps.
> > >> 3:48pm up 22:05, load average: 0.46, 0.77, 0.70
> > >>
> > >> handle_ap_item - addr3(BSSID)=00:30:ab:14:fa:46 not own MAC
> > >> wlan1: STA 00:02:6f:32:3e:8d TX rate raised to 110
> > >> wlan1: Could not find STA 00:00:00:00:00:00 for this TX error
> > >> (@7953685) NET: 41 messages suppressed. 192.168.167.202 sent an 
> > >> invalid ICMP error to a broadcast. handle_ap_item - 
> > >> addr3(BSSID)=00:30:ab:14:fa:46 not own MAC handle_ap_item - 
> > >> addr3(BSSID)=00:02:6f:03:74:46 not own MAC wlan1: STA 
> > >> 00:40:96:55:2c:dd TX rate raised to 55 handle_ap_item - 
> > >> addr3(BSSID)=00:02:6f:03:74:46 not own MAC wlan1: Could not find 
> > >> STA 00:00:00:00:00:00 for this TX error (@7953717) 
handle_ap_item
> > >> -
> > >>
> > >> addr3(BSSID)=00:30:ab:14:fa:46 not own MAC wlan1: Could not find 
> > >> STA 00:00:00:00:00:00 for this TX error (@7953787) 
handle_ap_item
> > >> -
> > >>
> > >> addr3(BSSID)=00:30:ab:14:fa:46 not own MAC handle_ap_item - 
> > >> addr3(BSSID)=00:02:6f:03:74:46 not own MAC wlan1: Could not find 
> > >> STA 00:00:00:00:00:00 for this TX error (@7953812) 
handle_ap_item
> > >> -
> > >>
> > >> addr3(BSSID)=00:30:ab:14:fa:46 not own MAC handle_ap_item - 
> > >> addr3(BSSID)=00:02:6f:03:74:46 not own MAC wlan1: Could not find 
> > >> STA 00:00:00:00:00:00 for this TX error (@7953884) 
handle_ap_item
> > >> -
> > >>
> > >> addr3(BSSID)=00:30:ab:14:fa:46 not own MAC wlan1: Could not find 
> > >> STA 00:00:00:00:00:00 for this TX error (@7953901) 
handle_ap_item
> > >> -
> > >>
> > >> addr3(BSSID)=00:02:6f:03:74:46 not own MAC handle_ap_item - 
> > >> addr3(BSSID)=00:30:ab:14:fa:46 not own MAC handle_ap_item - 
> > >> addr3(BSSID)=00:30:ab:14:fa:46 not own MAC wlan1: Could not find 
> > >> STA 00:00:00:00:00:00 for this TX error (@7953996) PACKET_OUT: 
> > >> Couldn't find a route to: 10.16.151.4, sending out a RREQ ! 
> > >> handle_ap_item - addr3(BSSID)=00:02:6f:03:74:46 not own MAC
> > >> PACKET_OUT: Couldn't find a route to: 10.16.151.98, sending out 
a
> > >> RREQ ! PACKET_OUT: Couldn't find a route to: 10.16.151.95, 
> > >> sending out a RREQ ! wlan1: Could not find STA 00:00:00:00:00:00 
> > >> for this TX error (@7954001) handle_ap_item - 
> > >> addr3(BSSID)=00:30:ab:14:fa:46
> > >>
> > >> not own MAC
> > >> STORMWARNING: IN=br1 OUT= 
> > >> MAC=00:02:6f:09:a6:7e:00:02:6f:08:a4:d3:08:00 
SRC=192.168.167.208
> > >> DST=10.199.223.121 LEN=56 TOS=0x00 PREC=0x00 TTL=150 ID=0
>
> PROTO=ICMP
>
> > >> TYPE=3 CODE=2 [SRC=10.199.223.121 DST=255.255.255.255 LEN=92
>
> TOS=0x00
>
> > >> PREC=0x00 TTL=1 ID=0 PROTO=177 ] handle_ap_item - 
> > >> addr3(BSSID)=00:02:6f:03:74:46 not own MAC handle_ap_item - 
> > >> addr3(BSSID)=00:02:6f:03:74:46 not own MAC wlan1: Could not find 
> > >> STA 00:00:00:00:00:00 for this TX error (@7954023) 
handle_ap_item
> > >> -
> > >>
> > >> addr3(BSSID)=00:30:ab:14:fa:46 not own MAC wlan1: STA 
> > >> 00:02:6f:32:3e:8d TX rate lowered to 55
> > >>
> > >> PID TTY Uid Size State Command
> > >> 1 root 1592 S init
> > >> 2 root 0 S [keventd]
> > >> 3 root 0 R [ksoftirqd_CPU0]
> > >> 4 root 0 R [kswapd]
> > >> 5 root 0 S [bdflush]
> > >> 6 root 0 S [kupdated]
> > >> 7 root 0 S [kjournald]
> > >> 12 root 0 S [loop0]
> > >> 14 root 0 S [loop1]
> > >> 16 root 0 S [loop2]
> > >> 39 root 0 S [kjournald]
> > >> 40 root 0 S [loop3]
> > >> 41 root 0 S [loop4]
> > >> 42 root 0 S [loop5]
> > >> 43 root 0 S [loop6]
> > >> 44 root 0 S [loop7]
> > >> 45 root 0 S [loop8]
> > >> 46 root 0 S [loop9]
> > >> 47 root 0 S [loop10]
> > >> 79 root 1336 S atrbtr
> > >> 145 root 0 S [khubd]
> > >> 363 root 1360 S /usr/sbin/klogd -c 3 -x
> > >> 367 root 1416 S /usr/sbin/syslogd -l meshbox
>
> 375
>
> > >> root 2996 S /usr/sbin/sshd
> > >> 1681 root 1936 S /bin/sh /hj/searcher
> > >> 1746 root 1380 S /hj/svscan /service/
> > >> 1749 root 1340 S supervise dnscache
> > >> 2079 root 12140 S /hj/splashd
> > >> 3103 root 0 S [rebroadcast]
> > >> 3108 root 0 S [kernel-aodv]
> > >> 3463 root 1924 S /bin/sh /hj/stst
> > >> 3785 root 1932 S /bin/sh /hj/npwat
> > >> 6598 root 3352 S stunnel
> > >> 6599 root 1928 S /bin/sh /hj/ike
> > >> 6660 root 12140 S /hj/splashd
> > >> 6661 root 12140 S /hj/splashd
> > >> 6662 root 12140 S /hj/splashd
> > >> 6663 root 12140 S /hj/splashd
> > >> 6664 root 12140 S /hj/splashd
> > >> 6665 root 12140 S /hj/splashd
> > >> 6697 root 1400 S pptpd
> > >> 6714 root 1380 S pppoed -L 192.168.1.2 -I 
eth0
>
> -I
>
> > >> br0
> > >>
> > >> 6718 root 1368 S /hj/tcpserver -H -R -l 
rmpoll
> >
> > -c10
> >
> > >> -d -t10
> > >> 6725 root 1920 S /bin/sh /hj/ublockd
> > >> 6728 root 1480 S /usr/sbin/crond -l10
> > >> 6732 root 1368 S /hj/tcpserver -H -R -l
unblock
> > >> -c10
> > >> -d -t10
> > >> 6742 tty3 root 1600 S init
> > >> 6743 tty4 root 1600 S init
> > >> 28105 root 3352 S stunnel
> > >> 31965 root 1984 S pppd pty /hj/pppoe -n -I br0
-e
> > >> 1:00:02:6f: 31966 root 1364 S /hj/pppoe -n -I
br0
> >
> > -e
> >
> > >> 1:00:02:6f:31:4a:38 26846 root 1984 S pppd pty
> > >> /hj/pppoe -n -I br0 -e 2:00:02:6f: 26847 root 1364
>
> S
>
> > >> /hj/pppoe -n -I br0 -e 2:00:02:6f:31:4a:38 26932 root
> > >> 1984 S pppd pty /hj/pppoe -n -I br0 -e 3:00:02:6f: 26933
> > >> root 1364 S /hj/pppoe -n -I br0 -e 3:00:02:6f:31:4a:38
> >
> > 22813
> >
> > >> root 1984 S pppd pty /hj/pppoe -n -I br0 -e
> > >> 4:00:02:6f: 22814 root 1364 S /hj/pppoe -n -I
br0
> >
> > -e
> >
> > >> 4:00:02:6f:31:4a:38 29638 root 2656 S 
vtund[c]:
> > >> gateway165 tun tun0 29856 root 2376 S dhcpd
eth0
> > >> br0 br1 32194 dnscache 2648 S
/usr/local/bin/dnscache
> > >> 825 root 1576 S sleep 300
> > >> 1590 root 1572 S sleep 90
> > >> 1706 root 1576 S sleep 20
> > >> 1730 root 1576 S sleep 20
> > >> 1741 root 1920 S /bin/sh -c /hj/splashtest
> > >>
> > >> >/dev/null
> > >>
> > >> 2>&1
> > >> 1742 root 1920 S /bin/sh -c /hj/report.txt
> > >>
> > >> >/dev/null
> > >>
> > >> 1743 root 1928 S /bin/sh -c /hj/report.txt
> > >>
> > >> >/dev/null
> > >>
> > >> 1753 root 1720 R ps -ef
> > >> 1754 root 1916 S /bin/sh /hj/splashtest
> > >> 1755 root 1912 S /bin/sh /hj/setting
>
> captiveportal
>
> > >> 1756 root 1924 S /bin/sh /hj/stst 1758
> >
> > root
> >
> > >> 1468 R grep 0 packets received 1759 root
> >
> > 1912
> >
> > >> R /bin/sh /hj/setting captiveportal 1760 root
>
> 1912
>
> > >> R /bin/sh /hj/setting captiveportal
> > >> Kernel IP routing table
> > >> Destination Gateway Genmask Flags Metric Ref
> > >> Use Iface 1.36.193.213 1.36.193.213 255.255.255.255 UGH 
0
> > >> 0 0 br0 1.249.80.123 10.61.23.70 255.255.255.255
UGH
> >
> > 0
> >
> > >> 0 0 br1 10.212.136.98 1.209.151.211
255.255.255.255
> > >> UGH 0 0 0 br1 10.199.223.121 10.199.223.121
> > >> 255.255.255.255 UGH 0 0 0 br1 172.16.165.1 *
> > >> 255.255.255.255 UH 0 0 0 tun0 10.61.23.70
> > >> 10.61.23.70 255.255.255.255 UGH 0 0 0 br1
> > >> 1.234.170.131 10.190.72.111 255.255.255.255 UGH 0 0
> > >> 0 br1 1.115.234.136 1.175.148.139 255.255.255.255 UGH 0
>
> 0
>
> > >> 0 br1 1.209.151.211 1.209.151.211 255.255.255.255 UGH
0
> > >> 0 0 br1 1.230.156.212 1.230.156.212 255.255.255.255
UGH
> > >> 0 0 0 br0 10.59.60.123 1.36.193.213
>
> 255.255.255.255
>
> > >> UGH 0 0 0 br0 1.85.96.148 10.61.23.70
> > >> 255.255.255.255 UGH 0 0 0 br1 10.181.94.58
> > >> 1.175.148.139 255.255.255.255 UGH 0 0 0 br1
> > >> 10.79.158.180 1.175.148.139 255.255.255.255 UGH 0 0
> > >> 0 br1 1.177.90.22 10.61.23.70 255.255.255.255 UGH 0
>
> 0
>
> > >> 0 br1 10.207.55.122 1.196.111.174 255.255.255.255 UGH
0
> > >> 0 0 br0 10.190.72.111 10.190.72.111 255.255.255.255
UGH
> > >> 0 0 0 br1 1.196.111.174 1.196.111.174
>
> 255.255.255.255
>
> > >> UGH 0 0 0 br0 1.175.148.139 1.175.148.139
> > >> 255.255.255.255 UGH 0 0 0 br1 192.168.167.0 *
> > >> 255.255.255.0 U 0 0 0 br1 192.168.1.0
*
> > >> 255.255.255.0 U 0 0 0 eth0
>
> 192.168.165.0
>
> > >> * 255.255.255.0 U 0 0 0 br0
1.0.0.0
> > >> * 255.0.0.0 U 0 0 0 br0
> > >> 1.0.0.0 * 255.0.0.0 U 0 0
> > >> 0 br1 1.0.0.0 * 255.0.0.0 U 0
>
> 0
>
> > >> 0 br0 10.0.0.0 * 255.0.0.0 U
0
> > >> 0 0 br0 10.0.0.0 * 255.0.0.0 
U
> > >> 0 0 0 br1 loopback * 255.0.0.0
> > >> U 0 0 0 lo BASE-ADDRESS.MC *
>
> 240.0.0.0
>
> > >> U 0 0 0 br0 default 172.16.165.1
> > >> 0.0.0.0 UG 0 0 0 tun0
> >
> > Kenny Bain
Category:Mesh