NodeLogin

back to http://scratchpad.wikia.com/wiki/Sasecurity

Login to node
 Logging into a node wirelessly    

There are 2 ways to resolve this. 

OPTION 1  1. Set up a portable node that has its SSID set to LocustWorld and the main radio  set to channel 1  2. Turn it on and wait for it to mesh.  3. Once it is meshed login and using the VI editor make the relevent changes to the  wiana.config file.  NOTE: I normally keep a copy of the wiana.config file for all of my nodes so all i  have to do is upload it and reboot the nodes. 

 OPTION 2  If the node you are using is meshed with a machine that is a gateway with a wired interface.  1. Change the SSID on the main node to LocustWorld and set the main radio channel to 1 <BR> 2. Reboot the gateway node and wait until they mesh. <BR> 3. Login to the dev88 node and use the remotemanagement command. <BR> 4. change the settings of the gateway node back to what it should have been. <BR>

<P> QUES: <BR> I upgraded my node from dev87 to dev88 last night and it reverted back to <BR> factory defaults. Yes, I have preserve settings on. The unit is on a tower that <BR> I am unable to climb now, and the power/ethernet end is in a locked room, so I <BR> cant plug directly to it.I can however connect via adhoc mode to Locustworld, <BR> but I never get an IP. So please can someone tell me how I communicate with a <BR> mesh ap set to factory default wirelessly? <BR> I thought that factory defaults gave out DHCP.. am I wrong in this?<BR>

Login script
{{{ modify the cwradius1 script to log all logins to a file. make a new file in drv2 called logins. Then add the parts below. This only works on OSS and not pro, I have been asking Jon for ages to include this as software plugin, but you know how it is. Original post by Andrew McPherson. We have been running this for a long time, and have seen so many hackers, but also so many customers trying to login with the wrong username or password. Come Jon add this to the plugins. PLEASE!!! prefix="/usr/local" exec_prefix="${prefix}" bindir="/hj" !!!!!!! date=`date` echo $date >>/drv2/logins echo "username:-$1, Password:-$2,  MAC:-$3 " >>/drv2/logins !!!!!!! usage { echo "Usage: radtest user passwd radius-server[:port] nas-port-number secret [ppphint] [nasname]" >&2 exit 100 the bit that I added in, in-between the !!!!!!!!, don't include the !!!!!!!! you will also have to chmod 755 /drv2/logins so that it can access the file.
 * 1) echo "$*" >>/tmp/cw.log

I would like to log each authentication attempt and the user name and password being used in each attempt whether successful or not on a per node basis logging the mac address would really be nice also but i think that would be much more difficult so right now i will skip that part I tried to log the attempted user name and  password by making the following changes to the test node I manually ran touch /etc/loginattempts went to login.mesh and right below the line o='grep "^$a:$b$" /etc/remoteusers' then added the following line  cat /etc/remoteusers >> /etc/loginattemps then did a successful login to the node from an unauthenticated client and also made several bogus unsuccessful login attempts then cat /etc/loginattempts the loginattempts file is always empty apparantly i am not modifying the the right file because it didnt work so i need a little help here }}}